From exim@www1.ietf.org Tue Mar 16 14:19:30 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19226 for ; Tue, 16 Mar 2004 14:19:30 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B3K5f-000383-15 for crisp-archive@odin.ietf.org; Tue, 16 Mar 2004 14:19:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2GJJ2Ac012023 for crisp-archive@odin.ietf.org; Tue, 16 Mar 2004 14:19:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B3K5e-00037q-Qv for crisp-web-archive@optimus.ietf.org; Tue, 16 Mar 2004 14:19:02 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19204 for ; Tue, 16 Mar 2004 14:18:59 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B3K5c-0006V7-00 for crisp-web-archive@ietf.org; Tue, 16 Mar 2004 14:19:00 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B3K4e-0006NS-00 for crisp-web-archive@ietf.org; Tue, 16 Mar 2004 14:18:01 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B3K3j-0006Gi-00 for crisp-web-archive@ietf.org; Tue, 16 Mar 2004 14:17:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B3K3g-0002zU-D9; Tue, 16 Mar 2004 14:17:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B3K2l-0002wr-CH for crisp@optimus.ietf.org; Tue, 16 Mar 2004 14:16:03 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19073 for ; Tue, 16 Mar 2004 14:16:00 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B3K2i-000695-00 for crisp@ietf.org; Tue, 16 Mar 2004 14:16:01 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B3K1q-00063Y-00 for crisp@ietf.org; Tue, 16 Mar 2004 14:15:07 -0500 Received: from shell-ng.nominum.com ([81.200.64.181]) by ietf-mx with esmtp (Exim 4.12) id 1B3K18-0005vx-00 for crisp@ietf.org; Tue, 16 Mar 2004 14:14:22 -0500 Received: by shell-ng.nominum.com (Postfix, from userid 10182) id 135195686D; Tue, 16 Mar 2004 11:13:51 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by shell-ng.nominum.com (Postfix) with ESMTP id 10FE456856; Tue, 16 Mar 2004 11:13:51 -0800 (PST) Date: Tue, 16 Mar 2004 11:13:51 -0800 (PST) From: April Marine To: CRISP WG Cc: George Michaelson , April Marine Message-ID: <20040316111206.H32023@shell-ng.nominum.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Crisp] Minutes of Seoul Mtg Sender: crisp-admin@ietf.org Errors-To: crisp-admin@ietf.org X-BeenThere: crisp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Cross Registry Information Service Protocol List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Here are the minutes (many thanks to Shane Kerr). Pls take a moment to look a them and send any corrections. I hope to send them along to the Secretariat this week. thanks! A. CRISP minutes Tuesday, 2004-03-02 09:00 to 11:30 CHAIRS: April Marine april.marine@nominum.com George Michaelson ggm@apnic.net Minutes: Shane Kerr o Welcome, Agenda Bashing, Status Update Chairs - 10 min Status: requirements now RFC iris-(core|dreg|beep) about to be submitted for WG last call o Update on latest drafts: draft-ietf-crisp-iris-core-05.txt draft-ietf-crisp-iris-dreg-05.txt draft-ietf-crisp-iris-beep-05.txt Changes centered around XML mechanics: Andy Newton - 30 min Changes centered around internationalization and language issues: Marcos Sanz - 30 min George Michaelson suggests requiring E.164 would be "bold and useful". Marcos does not want to eliminate potential users Shane suggests it's not hard and makes it hard on client users Andy notes that domain registries exist who don't have valid data Jakob Schlyter notes that a '+' is enough to differentiate between E.164 and other formats Richard Shockey specifies that a '+' means E.164, and otherwise not Consensus: if use a '+', MUST be E.164 o Next Steps - 10 min April says these docs will be sent to WG last call within 2 weeks. o Status of draft-ietf-crisp-iris-areg-05.txt Ed Lewis stars as Cathy Murphy - 20 mins Ted Hardie: what about registries "below" the RIR? Would the "number resource registry" point to the RIR or the other organization? Ed: don't know, can't remember Ted: As long as it's consistent, it doesn't matter George: We should specify Marcos: Useful if areg and dreg could concur on definitions? For example, contact objects? Andy: I don't know. Don't want to weigh down RIRs with domain registry policy. Shane: Can we reference the dreg from the areg? Andy: I don't think it buys you a lot. John Klensin: Why are we using first name, middle name, last name? Ed: We removed that and replaced with a "common name". John: We need a "surname" field, for sorting and searching. If we can do better, we should, but we need something. George: There is an IETF RFC that references this. I will look for this. Patrik [jabber]: People interested in name conversion should look at RFC2426, RFC2218 Shane: pretty much done with address requirements, will send in a few weeks o Nesting text for IP ranges Engin Gunduz - 5 mins Engin: Last week sent test to mailing list. Part was included in areg, the rest will go into address requirements. Includes what we think are all address registry needs. Defines less specific, more specific, etc. Covers requirements for searching on these, for RIPE NCC. Andy: Need to change more/less/etc. terminology to understand equivalences. George: Need to do more to cover cases that don't fit the more/less/etc. behavior? Andy: Yes. Maybe two more terms to describe the administrative-only relationships. o Other topics (if any arise) Shane: Interested in what the plans are for production services. John: Wants to know what the feedback is, to explain to GNSO where we are. Patrik: bringing to RIPE meeting in May? Shane: Yes Scott Hollenbeck: what is the question? Shane: what services you will be bringing on-line, and when? folks pls discuss after adjourn. _______________________________________________ Crisp mailing list Crisp@ietf.org https://www1.ietf.org/mailman/listinfo/crisp From exim@www1.ietf.org Thu Mar 18 11:21:06 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22672 for ; Thu, 18 Mar 2004 11:21:06 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B40G5-00019S-Lu for crisp-archive@odin.ietf.org; Thu, 18 Mar 2004 11:20:38 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2IGKbxN004422 for crisp-archive@odin.ietf.org; Thu, 18 Mar 2004 11:20:37 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B40G5-00019F-E5 for crisp-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 11:20:37 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22666 for ; Thu, 18 Mar 2004 11:20:34 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B40G4-00017Y-00 for crisp-web-archive@ietf.org; Thu, 18 Mar 2004 11:20:36 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B40FA-00014f-00 for crisp-web-archive@ietf.org; Thu, 18 Mar 2004 11:19:40 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B40Eb-00011S-00 for crisp-web-archive@ietf.org; Thu, 18 Mar 2004 11:19:05 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B40EX-0000yA-4n; Thu, 18 Mar 2004 11:19:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B40Dx-0000vR-6v for crisp@optimus.ietf.org; Thu, 18 Mar 2004 11:18:25 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22559 for ; Thu, 18 Mar 2004 11:18:22 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B40Dv-0000zH-00 for crisp@ietf.org; Thu, 18 Mar 2004 11:18:23 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B40D3-0000xf-00 for crisp@ietf.org; Thu, 18 Mar 2004 11:17:29 -0500 Received: from shell-ng.nominum.com ([81.200.64.181]) by ietf-mx with esmtp (Exim 4.12) id 1B40C9-0000uM-00 for crisp@ietf.org; Thu, 18 Mar 2004 11:16:33 -0500 Received: by shell-ng.nominum.com (Postfix, from userid 10182) id B257F56856; Thu, 18 Mar 2004 08:16:01 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by shell-ng.nominum.com (Postfix) with ESMTP id A9E995684D; Thu, 18 Mar 2004 08:16:01 -0800 (PST) Date: Thu, 18 Mar 2004 08:16:01 -0800 (PST) From: April Marine To: CRISP WG Cc: Andrew Newton , sanz@denic.de, George Michaelson , April Marine Message-ID: <20040318080801.I29888@shell-ng.nominum.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Crisp] WG Last Call Sender: crisp-admin@ietf.org Errors-To: crisp-admin@ietf.org X-BeenThere: crisp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Cross Registry Information Service Protocol List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Hi all, At this point, we are ready for Working Group Last Call on the following three docs: draft-ietf-crisp-iris-core-05.txt draft-ietf-crisp-iris-dreg-05.txt draft-ietf-crisp-iris-beep-05.txt These are the docs we've been working on since dirt was young, so hopefully you are familiar with them. :) Andy and Marcos currently have some small edits to make as a result of the meeting in Korea and from chair feedback, but these are minor. They will combine those changes with feedback from the last call for one last rev before we send the docs up to our AD for IESG consideration. This is a two week last call. Please have comments in by April 4. Pls send comments to the list (unless they are things like misspellings). thanks, April and George _______________________________________________ Crisp mailing list Crisp@ietf.org https://www1.ietf.org/mailman/listinfo/crisp From exim@www1.ietf.org Thu Mar 18 11:23:07 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22829 for ; Thu, 18 Mar 2004 11:23:06 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B40I3-0001OG-8d for crisp-archive@odin.ietf.org; Thu, 18 Mar 2004 11:22:39 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2IGMd3k005338 for crisp-archive@odin.ietf.org; Thu, 18 Mar 2004 11:22:39 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B40I3-0001O1-3z for crisp-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 11:22:39 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22820 for ; Thu, 18 Mar 2004 11:22:36 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B40I2-0001DC-00 for crisp-web-archive@ietf.org; Thu, 18 Mar 2004 11:22:38 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B40H4-0001Au-00 for crisp-web-archive@ietf.org; Thu, 18 Mar 2004 11:21:39 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B40GU-00018H-00 for crisp-web-archive@ietf.org; Thu, 18 Mar 2004 11:21:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B40GU-0001Eu-Vh; Thu, 18 Mar 2004 11:21:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B40Fv-000185-Cc for crisp@optimus.ietf.org; Thu, 18 Mar 2004 11:20:27 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22629 for ; Thu, 18 Mar 2004 11:20:24 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B40Fu-00015x-00 for crisp@ietf.org; Thu, 18 Mar 2004 11:20:26 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B40Ey-00012o-00 for crisp@ietf.org; Thu, 18 Mar 2004 11:19:29 -0500 Received: from shell-ng.nominum.com ([81.200.64.181]) by ietf-mx with esmtp (Exim 4.12) id 1B40E1-0000yi-00 for crisp@ietf.org; Thu, 18 Mar 2004 11:18:29 -0500 Received: by shell-ng.nominum.com (Postfix, from userid 10182) id 1445C5684D; Thu, 18 Mar 2004 08:17:59 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by shell-ng.nominum.com (Postfix) with ESMTP id 118D256838; Thu, 18 Mar 2004 08:17:59 -0800 (PST) Date: Thu, 18 Mar 2004 08:17:59 -0800 (PST) From: April Marine To: CRISP WG Cc: April Marine , George Michaelson In-Reply-To: <20040316111206.H32023@shell-ng.nominum.com> Message-ID: <20040318081738.T29888@shell-ng.nominum.com> References: <20040316111206.H32023@shell-ng.nominum.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Crisp] Re: Minutes of Seoul Mtg Sender: crisp-admin@ietf.org Errors-To: crisp-admin@ietf.org X-BeenThere: crisp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Cross Registry Information Service Protocol List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 and while I'm bugging you, any comments on the minutes? On Tue, 16 Mar 2004, April Marine wrote: > Here are the minutes (many thanks to Shane Kerr). Pls take a moment to > look a them and send any corrections. I hope to send them along to the > Secretariat this week. > > thanks! > A. > > > > CRISP minutes > Tuesday, 2004-03-02 09:00 to 11:30 > > CHAIRS: > April Marine april.marine@nominum.com > George Michaelson ggm@apnic.net > > Minutes: Shane Kerr > > o Welcome, Agenda Bashing, Status Update > Chairs - 10 min > > Status: > requirements now RFC > iris-(core|dreg|beep) about to be submitted for WG last call > > o Update on latest drafts: > draft-ietf-crisp-iris-core-05.txt > draft-ietf-crisp-iris-dreg-05.txt > draft-ietf-crisp-iris-beep-05.txt > > > Changes centered around XML mechanics: > Andy Newton - 30 min > > Changes centered around internationalization and language issues: > Marcos Sanz - 30 min > > George Michaelson suggests requiring E.164 would be "bold and useful". > Marcos does not want to eliminate potential users > Shane suggests it's not hard and makes it hard on client users > Andy notes that domain registries exist who don't have valid data > Jakob Schlyter notes that a '+' is enough to differentiate between > E.164 and other formats > Richard Shockey specifies that a '+' means E.164, and otherwise not > > Consensus: if use a '+', MUST be E.164 > > o Next Steps - 10 min > > April says these docs will be sent to WG last call within 2 weeks. > > o Status of draft-ietf-crisp-iris-areg-05.txt > > Ed Lewis stars as Cathy Murphy - 20 mins > > Ted Hardie: what about registries "below" the RIR? Would the "number > resource registry" point to the RIR or the other organization? > Ed: don't know, can't remember > Ted: As long as it's consistent, it doesn't matter > George: We should specify > > Marcos: Useful if areg and dreg could concur on definitions? For > example, contact objects? > Andy: I don't know. Don't want to weigh down RIRs with domain registry policy. > Shane: Can we reference the dreg from the areg? > Andy: I don't think it buys you a lot. > > John Klensin: Why are we using first name, middle name, last name? > Ed: We removed that and replaced with a "common name". > John: We need a "surname" field, for sorting and searching. If we can > do better, we should, but we need something. > George: There is an IETF RFC that references this. I will look for this. > > Patrik [jabber]: People interested in name conversion should look at > RFC2426, RFC2218 > > Shane: pretty much done with address requirements, will send in a few weeks > > o Nesting text for IP ranges > > Engin Gunduz - 5 mins > > Engin: Last week sent test to mailing list. Part was included in > areg, the rest will go into address requirements. Includes what we > think are all address registry needs. Defines less specific, more > specific, etc. Covers requirements for searching on these, for RIPE > NCC. > > Andy: Need to change more/less/etc. terminology to understand equivalences. > George: Need to do more to cover cases that don't fit the > more/less/etc. behavior? > Andy: Yes. Maybe two more terms to describe the administrative-only > relationships. > > o Other topics (if any arise) > > Shane: Interested in what the plans are for production services. > John: Wants to know what the feedback is, to explain to GNSO where we are. > > Patrik: bringing to RIPE meeting in May? > Shane: Yes > Scott Hollenbeck: what is the question? > Shane: what services you will be bringing on-line, and when? folks pls > discuss after adjourn. > _______________________________________________ Crisp mailing list Crisp@ietf.org https://www1.ietf.org/mailman/listinfo/crisp From exim@www1.ietf.org Thu Mar 18 12:21:06 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26075 for ; Thu, 18 Mar 2004 12:21:06 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B41CB-0007Yl-RI for crisp-archive@odin.ietf.org; Thu, 18 Mar 2004 12:20:40 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2IHKdmr029057 for crisp-archive@odin.ietf.org; Thu, 18 Mar 2004 12:20:39 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B41CB-0007Ya-N0 for crisp-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 12:20:39 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26044 for ; Thu, 18 Mar 2004 12:20:36 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B41CA-0005IT-00 for crisp-web-archive@ietf.org; Thu, 18 Mar 2004 12:20:38 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B41BQ-0005Ee-00 for crisp-web-archive@ietf.org; Thu, 18 Mar 2004 12:19:53 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B41Ab-0005AG-00 for crisp-web-archive@ietf.org; Thu, 18 Mar 2004 12:19:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B41Ab-0007CA-2K; Thu, 18 Mar 2004 12:19:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B41AB-00077s-HJ for crisp@optimus.ietf.org; Thu, 18 Mar 2004 12:18:35 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25966 for ; Thu, 18 Mar 2004 12:18:31 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B41AA-00057k-00 for crisp@ietf.org; Thu, 18 Mar 2004 12:18:34 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B419L-00054b-00 for crisp@ietf.org; Thu, 18 Mar 2004 12:17:44 -0500 Received: from zak.ecotroph.net ([216.93.164.123]) by ietf-mx with esmtp (Exim 4.12) id 1B418m-00051K-00 for crisp@ietf.org; Thu, 18 Mar 2004 12:17:08 -0500 Received: from [10.131.244.249] ([::ffff:216.168.239.87]) (AUTH: LOGIN anewton, SSL: TLSv1/SSLv3,128bits,RC4-SHA) by zak.ecotroph.net with esmtp; Thu, 18 Mar 2004 12:16:57 -0500 Mime-Version: 1.0 (Apple Message framework v613) Content-Type: text/plain; charset=US-ASCII; format=flowed Resent-Date: Thu, 18 Mar 2004 12:16:50 -0500 Message-Id: <0B9DD0F1-7900-11D8-84D5-000A95B3BA44@hxr.us> Content-Transfer-Encoding: 7bit Resent-To: crisp@ietf.org Resent-Message-Id: From: Andrew Newton Resent-From: Andrew Newton Date: Tue, 16 Mar 2004 18:52:14 -0500 To: "Marcos Sanz/Denic" X-Mailer: Apple Mail (2.613) Resent-Date: Thu, 18 Mar 2004 12:17:08 -0500 Content-Transfer-Encoding: 7bit Subject: [Crisp] Edits to -05 (Modified by Andrew Newton) Sender: crisp-admin@ietf.org Errors-To: crisp-admin@ietf.org X-BeenThere: crisp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Cross Registry Information Service Protocol List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit The following are the edits collected since the Seoul meeting to the -05 documents up for last call consideration: iris-dreg: 1) The text describing and in section 3.2.4 will read: " - elements containing a voice phone number for this contact. If it begins with a '+' (plus) character, it MUST be a number defined by [13]. The format number defined in [13] is RECOMMENDED." [13] being the E.164 specification. 2) In 3.2.4, add a element as a child of . The type element will contain either a , , , or element. Each of these elements may have elements. This is similar to 'domainStatusType' in 3.2.1 except without the child. 3) In 6.2 and 6.3, clarifying text so the "no records found" is referencing a failure to connect to a server via the direct resolution process. Also 6.3, "leftmost" should be "rightmost" and "right of leftmost" should be "left of rightmost". iris-core: 1) In 3.3.5, make maxOccurs for to unbounded. iris-beep: 1) Add the following text to section 3: "A server MUST honor queries for all advertised registry types on any channel opened with an IRIS profile URI." -andy _______________________________________________ Crisp mailing list Crisp@ietf.org https://www1.ietf.org/mailman/listinfo/crisp From exim@www1.ietf.org Thu Mar 18 21:45:12 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24193 for ; Thu, 18 Mar 2004 21:45:12 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B4A04-0001mu-FO for crisp-archive@odin.ietf.org; Thu, 18 Mar 2004 21:44:45 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2J2iixf006866 for crisp-archive@odin.ietf.org; Thu, 18 Mar 2004 21:44:44 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B4A04-0001mf-A5 for crisp-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 21:44:44 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24186 for ; Thu, 18 Mar 2004 21:44:40 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B4A01-0004I2-00 for crisp-web-archive@ietf.org; Thu, 18 Mar 2004 21:44:41 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B49z6-0004GC-00 for crisp-web-archive@ietf.org; Thu, 18 Mar 2004 21:43:45 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B49yN-0004EO-00 for crisp-web-archive@ietf.org; Thu, 18 Mar 2004 21:42:59 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B49yO-0001jU-Mh; Thu, 18 Mar 2004 21:43:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B49yB-0001jJ-4M for crisp@optimus.ietf.org; Thu, 18 Mar 2004 21:42:47 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24155 for ; Thu, 18 Mar 2004 21:42:43 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B49y8-0004De-00 for crisp@ietf.org; Thu, 18 Mar 2004 21:42:44 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B49xA-0004BU-00 for crisp@ietf.org; Thu, 18 Mar 2004 21:41:45 -0500 Received: from zak.ecotroph.net ([216.93.164.123]) by ietf-mx with esmtp (Exim 4.12) id 1B49we-00049d-00 for crisp@ietf.org; Thu, 18 Mar 2004 21:41:12 -0500 Received: from thinkingcat.com ([::ffff:68.71.234.169]) (AUTH: LOGIN leslie, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by zak.ecotroph.net with esmtp; Thu, 18 Mar 2004 21:41:12 -0500 Message-ID: <405A5D74.8060405@thinkingcat.com> Date: Thu, 18 Mar 2004 21:39:48 -0500 From: Leslie Daigle User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: April Marine CC: CRISP WG , George Michaelson Subject: Re: [Crisp] Re: Minutes of Seoul Mtg References: <20040316111206.H32023@shell-ng.nominum.com> <20040318081738.T29888@shell-ng.nominum.com> In-Reply-To: <20040318081738.T29888@shell-ng.nominum.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: crisp-admin@ietf.org Errors-To: crisp-admin@ietf.org X-BeenThere: crisp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Cross Registry Information Service Protocol List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit One nit... > George Michaelson suggests requiring E.164 would be "bold and useful". > Marcos does not want to eliminate potential users > Shane suggests it's not hard and makes it hard on client users > Andy notes that domain registries exist who don't have valid data > Jakob Schlyter notes that a '+' is enough to differentiate between > E.164 and other formats > Richard Shockey specifies that a '+' means E.164, and otherwise not I think it should be specified that these comments applied to the phone number related elements (, ). Not everyone on the planet knows that E.164 is the specification for globally routable phone number formats. Leslie. April Marine wrote: > and while I'm bugging you, any comments on the minutes? > > > > On Tue, 16 Mar 2004, April Marine wrote: > > >>Here are the minutes (many thanks to Shane Kerr). Pls take a moment to >>look a them and send any corrections. I hope to send them along to the >>Secretariat this week. >> >>thanks! >>A. >> >> >> >>CRISP minutes >>Tuesday, 2004-03-02 09:00 to 11:30 >> >>CHAIRS: >>April Marine april.marine@nominum.com >>George Michaelson ggm@apnic.net >> >>Minutes: Shane Kerr >> >>o Welcome, Agenda Bashing, Status Update >> Chairs - 10 min >> >>Status: >>requirements now RFC >>iris-(core|dreg|beep) about to be submitted for WG last call >> >>o Update on latest drafts: >> draft-ietf-crisp-iris-core-05.txt >> draft-ietf-crisp-iris-dreg-05.txt >> draft-ietf-crisp-iris-beep-05.txt >> >> >> Changes centered around XML mechanics: >> Andy Newton - 30 min >> >> Changes centered around internationalization and language issues: >> Marcos Sanz - 30 min >> >>George Michaelson suggests requiring E.164 would be "bold and useful". >>Marcos does not want to eliminate potential users >>Shane suggests it's not hard and makes it hard on client users >>Andy notes that domain registries exist who don't have valid data >>Jakob Schlyter notes that a '+' is enough to differentiate between >>E.164 and other formats >>Richard Shockey specifies that a '+' means E.164, and otherwise not >> >>Consensus: if use a '+', MUST be E.164 >> >>o Next Steps - 10 min >> >>April says these docs will be sent to WG last call within 2 weeks. >> >>o Status of draft-ietf-crisp-iris-areg-05.txt >> >> Ed Lewis stars as Cathy Murphy - 20 mins >> >>Ted Hardie: what about registries "below" the RIR? Would the "number >>resource registry" point to the RIR or the other organization? >>Ed: don't know, can't remember >>Ted: As long as it's consistent, it doesn't matter >>George: We should specify >> >>Marcos: Useful if areg and dreg could concur on definitions? For >>example, contact objects? >>Andy: I don't know. Don't want to weigh down RIRs with domain registry policy. >>Shane: Can we reference the dreg from the areg? >>Andy: I don't think it buys you a lot. >> >>John Klensin: Why are we using first name, middle name, last name? >>Ed: We removed that and replaced with a "common name". >>John: We need a "surname" field, for sorting and searching. If we can >>do better, we should, but we need something. >>George: There is an IETF RFC that references this. I will look for this. >> >>Patrik [jabber]: People interested in name conversion should look at >>RFC2426, RFC2218 >> >>Shane: pretty much done with address requirements, will send in a few weeks >> >>o Nesting text for IP ranges >> >> Engin Gunduz - 5 mins >> >>Engin: Last week sent test to mailing list. Part was included in >>areg, the rest will go into address requirements. Includes what we >>think are all address registry needs. Defines less specific, more >>specific, etc. Covers requirements for searching on these, for RIPE >>NCC. >> >>Andy: Need to change more/less/etc. terminology to understand equivalences. >>George: Need to do more to cover cases that don't fit the >>more/less/etc. behavior? >>Andy: Yes. Maybe two more terms to describe the administrative-only >>relationships. >> >>o Other topics (if any arise) >> >>Shane: Interested in what the plans are for production services. >>John: Wants to know what the feedback is, to explain to GNSO where we are. >> >>Patrik: bringing to RIPE meeting in May? >>Shane: Yes >>Scott Hollenbeck: what is the question? >>Shane: what services you will be bringing on-line, and when? folks pls >>discuss after adjourn. >> > > > _______________________________________________ > Crisp mailing list > Crisp@ietf.org > https://www1.ietf.org/mailman/listinfo/crisp _______________________________________________ Crisp mailing list Crisp@ietf.org https://www1.ietf.org/mailman/listinfo/crisp From exim@www1.ietf.org Fri Mar 19 19:12:04 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03015 for ; Fri, 19 Mar 2004 19:12:04 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B4U5S-0008Oo-35 for crisp-archive@odin.ietf.org; Fri, 19 Mar 2004 19:11:38 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2K0Bcp2032283 for crisp-archive@odin.ietf.org; Fri, 19 Mar 2004 19:11:38 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B4U5R-0008Oc-SI for crisp-web-archive@optimus.ietf.org; Fri, 19 Mar 2004 19:11:37 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03008 for ; Fri, 19 Mar 2004 19:11:33 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B4U5O-0004tY-00 for crisp-web-archive@ietf.org; Fri, 19 Mar 2004 19:11:34 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B4U4M-0004p3-00 for crisp-web-archive@ietf.org; Fri, 19 Mar 2004 19:10:31 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B4U3u-0004kk-00 for crisp-web-archive@ietf.org; Fri, 19 Mar 2004 19:10:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B4U3u-0008L2-BE; Fri, 19 Mar 2004 19:10:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B4U3O-0008K3-78 for crisp@optimus.ietf.org; Fri, 19 Mar 2004 19:09:30 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02951 for ; Fri, 19 Mar 2004 19:09:25 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B4U3K-0004jB-00 for crisp@ietf.org; Fri, 19 Mar 2004 19:09:26 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B4U2K-0004dZ-00 for crisp@ietf.org; Fri, 19 Mar 2004 19:08:24 -0500 Received: from shell-ng.nominum.com ([81.200.64.181]) by ietf-mx with esmtp (Exim 4.12) id 1B4U1M-0004Up-00 for crisp@ietf.org; Fri, 19 Mar 2004 19:07:24 -0500 Received: by shell-ng.nominum.com (Postfix, from userid 10182) id 80A3756877; Fri, 19 Mar 2004 16:06:48 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by shell-ng.nominum.com (Postfix) with ESMTP id 7DDD35684D; Fri, 19 Mar 2004 16:06:48 -0800 (PST) Date: Fri, 19 Mar 2004 16:06:48 -0800 (PST) From: April Marine To: Leslie Daigle Cc: April Marine , CRISP WG , George Michaelson Subject: Re: [Crisp] Re: Minutes of Seoul Mtg In-Reply-To: <405A5D74.8060405@thinkingcat.com> Message-ID: <20040319160637.T72812@shell-ng.nominum.com> References: <20040316111206.H32023@shell-ng.nominum.com> <20040318081738.T29888@shell-ng.nominum.com> <405A5D74.8060405@thinkingcat.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: crisp-admin@ietf.org Errors-To: crisp-admin@ietf.org X-BeenThere: crisp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Cross Registry Information Service Protocol List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 thanks Leslie, got it. :) On Thu, 18 Mar 2004, Leslie Daigle wrote: > > One nit... > > > George Michaelson suggests requiring E.164 would be "bold and useful". > > Marcos does not want to eliminate potential users > > Shane suggests it's not hard and makes it hard on client users > > Andy notes that domain registries exist who don't have valid data > > Jakob Schlyter notes that a '+' is enough to differentiate between > > E.164 and other formats > > Richard Shockey specifies that a '+' means E.164, and otherwise not > > > I think it should be specified that these comments applied > to the phone number related elements (, ). Not > everyone on the planet knows that E.164 is the specification for > globally routable phone number formats. > > Leslie. > > April Marine wrote: > > > and while I'm bugging you, any comments on the minutes? > > > > > > > > On Tue, 16 Mar 2004, April Marine wrote: > > > > > >>Here are the minutes (many thanks to Shane Kerr). Pls take a moment to > >>look a them and send any corrections. I hope to send them along to the > >>Secretariat this week. > >> > >>thanks! > >>A. > >> > >> > >> > >>CRISP minutes > >>Tuesday, 2004-03-02 09:00 to 11:30 > >> > >>CHAIRS: > >>April Marine april.marine@nominum.com > >>George Michaelson ggm@apnic.net > >> > >>Minutes: Shane Kerr > >> > >>o Welcome, Agenda Bashing, Status Update > >> Chairs - 10 min > >> > >>Status: > >>requirements now RFC > >>iris-(core|dreg|beep) about to be submitted for WG last call > >> > >>o Update on latest drafts: > >> draft-ietf-crisp-iris-core-05.txt > >> draft-ietf-crisp-iris-dreg-05.txt > >> draft-ietf-crisp-iris-beep-05.txt > >> > >> > >> Changes centered around XML mechanics: > >> Andy Newton - 30 min > >> > >> Changes centered around internationalization and language issues: > >> Marcos Sanz - 30 min > >> > >>George Michaelson suggests requiring E.164 would be "bold and useful". > >>Marcos does not want to eliminate potential users > >>Shane suggests it's not hard and makes it hard on client users > >>Andy notes that domain registries exist who don't have valid data > >>Jakob Schlyter notes that a '+' is enough to differentiate between > >>E.164 and other formats > >>Richard Shockey specifies that a '+' means E.164, and otherwise not > >> > >>Consensus: if use a '+', MUST be E.164 > >> > >>o Next Steps - 10 min > >> > >>April says these docs will be sent to WG last call within 2 weeks. > >> > >>o Status of draft-ietf-crisp-iris-areg-05.txt > >> > >> Ed Lewis stars as Cathy Murphy - 20 mins > >> > >>Ted Hardie: what about registries "below" the RIR? Would the "number > >>resource registry" point to the RIR or the other organization? > >>Ed: don't know, can't remember > >>Ted: As long as it's consistent, it doesn't matter > >>George: We should specify > >> > >>Marcos: Useful if areg and dreg could concur on definitions? For > >>example, contact objects? > >>Andy: I don't know. Don't want to weigh down RIRs with domain registry policy. > >>Shane: Can we reference the dreg from the areg? > >>Andy: I don't think it buys you a lot. > >> > >>John Klensin: Why are we using first name, middle name, last name? > >>Ed: We removed that and replaced with a "common name". > >>John: We need a "surname" field, for sorting and searching. If we can > >>do better, we should, but we need something. > >>George: There is an IETF RFC that references this. I will look for this. > >> > >>Patrik [jabber]: People interested in name conversion should look at > >>RFC2426, RFC2218 > >> > >>Shane: pretty much done with address requirements, will send in a few weeks > >> > >>o Nesting text for IP ranges > >> > >> Engin Gunduz - 5 mins > >> > >>Engin: Last week sent test to mailing list. Part was included in > >>areg, the rest will go into address requirements. Includes what we > >>think are all address registry needs. Defines less specific, more > >>specific, etc. Covers requirements for searching on these, for RIPE > >>NCC. > >> > >>Andy: Need to change more/less/etc. terminology to understand equivalences. > >>George: Need to do more to cover cases that don't fit the > >>more/less/etc. behavior? > >>Andy: Yes. Maybe two more terms to describe the administrative-only > >>relationships. > >> > >>o Other topics (if any arise) > >> > >>Shane: Interested in what the plans are for production services. > >>John: Wants to know what the feedback is, to explain to GNSO where we are. > >> > >>Patrik: bringing to RIPE meeting in May? > >>Shane: Yes > >>Scott Hollenbeck: what is the question? > >>Shane: what services you will be bringing on-line, and when? folks pls > >>discuss after adjourn. > >> > > > > > > _______________________________________________ > > Crisp mailing list > > Crisp@ietf.org > > https://www1.ietf.org/mailman/listinfo/crisp > _______________________________________________ Crisp mailing list Crisp@ietf.org https://www1.ietf.org/mailman/listinfo/crisp From exim@www1.ietf.org Fri Mar 26 13:32:59 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06551 for ; Fri, 26 Mar 2004 13:32:59 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B6w87-0000Ky-0J for crisp-archive@odin.ietf.org; Fri, 26 Mar 2004 13:32:31 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2QIWUrj001295 for crisp-archive@odin.ietf.org; Fri, 26 Mar 2004 13:32:30 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B6w86-0000Ko-Nr for crisp-web-archive@optimus.ietf.org; Fri, 26 Mar 2004 13:32:30 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06530 for ; Fri, 26 Mar 2004 13:32:28 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B6w84-00031s-00 for crisp-web-archive@ietf.org; Fri, 26 Mar 2004 13:32:28 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B6w6y-0002x6-00 for crisp-web-archive@ietf.org; Fri, 26 Mar 2004 13:31:21 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B6w6g-0002u3-00 for crisp-web-archive@ietf.org; Fri, 26 Mar 2004 13:31:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B6w6e-000069-IM; Fri, 26 Mar 2004 13:31:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B6w60-00004u-Na for crisp@optimus.ietf.org; Fri, 26 Mar 2004 13:30:20 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06414 for ; Fri, 26 Mar 2004 13:30:18 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B6w5y-0002ru-00 for crisp@ietf.org; Fri, 26 Mar 2004 13:30:18 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B6w52-0002nI-00 for crisp@ietf.org; Fri, 26 Mar 2004 13:29:20 -0500 Received: from shell-ng.nominum.com ([81.200.64.181]) by ietf-mx with esmtp (Exim 4.12) id 1B6w41-0002fm-00 for crisp@ietf.org; Fri, 26 Mar 2004 13:28:17 -0500 Received: by shell-ng.nominum.com (Postfix, from userid 10182) id BA7B056897; Fri, 26 Mar 2004 10:27:47 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by shell-ng.nominum.com (Postfix) with ESMTP id B7FC55688A; Fri, 26 Mar 2004 10:27:47 -0800 (PST) Date: Fri, 26 Mar 2004 10:27:47 -0800 (PST) From: April Marine To: CRISP WG Cc: April Marine , George Michaelson , Ted Hardie Message-ID: <20040326102350.G66144@shell-ng.nominum.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Crisp] REMINDER: LAST CALL Sender: crisp-admin@ietf.org Errors-To: crisp-admin@ietf.org X-BeenThere: crisp@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Cross Registry Information Service Protocol List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Just a reminder that we are about halfway through working group last call on the following docs: draft-ietf-crisp-iris-core-05.txt draft-ietf-crisp-iris-dreg-05.txt draft-ietf-crisp-iris-beep-05.txt So far discussion has been, well, minimal is too big a word. That's fine if you have no issues. But I should warn you that we are going to be inclined to give "after last call" input as little attention as we possibly can without ignoring some show-stopping item should it descend upon us. thanks, April _______________________________________________ Crisp mailing list Crisp@ietf.org https://www1.ietf.org/mailman/listinfo/crisp