From exim@www1.ietf.org Fri Apr 2 07:33:21 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 HAA06500 for ; Fri, 2 Apr 2004 07:33:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B9Kcx-0004v6-8K for crisp-archive@odin.ietf.org; Fri, 02 Apr 2004 04:06:15 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3296FfC018913 for crisp-archive@odin.ietf.org; Fri, 2 Apr 2004 04:06:15 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B9GFX-0000o6-Bd for crisp-web-archive@optimus.ietf.org; Thu, 01 Apr 2004 23:25: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 XAA02014 for ; Thu, 1 Apr 2004 23:25:44 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B9GFV-0003G1-00 for crisp-web-archive@ietf.org; Thu, 01 Apr 2004 23:25:45 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B9GCN-0002Uv-00 for crisp-web-archive@ietf.org; Thu, 01 Apr 2004 23:22:31 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B9G9r-0001vF-00 for crisp-web-archive@ietf.org; Thu, 01 Apr 2004 23:19:55 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B9D9B-0002FM-Hd; Thu, 01 Apr 2004 20:07:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B99T7-0006QZ-4g for crisp@optimus.ietf.org; Thu, 01 Apr 2004 16:11:21 -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 QAA02646 for ; Thu, 1 Apr 2004 16:11:18 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B99T5-00046v-00 for crisp@ietf.org; Thu, 01 Apr 2004 16:11:19 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B99SB-00040w-00 for crisp@ietf.org; Thu, 01 Apr 2004 16:10:23 -0500 Received: from cliffie.verisignlabs.com ([65.201.175.9] helo=mail.verisignlabs.com) by ietf-mx with esmtp (Exim 4.12) id 1B99Rf-0003vd-00 for crisp@ietf.org; Thu, 01 Apr 2004 16:09:51 -0500 Received: from pinion.verisignlabs.com ([::ffff:216.168.239.87]) (AUTH: PLAIN davidb, TLS: TLSv1/SSLv3,128bits,RC4-MD5) by mail.verisignlabs.com with esmtp; Thu, 01 Apr 2004 16:09:18 -0500 From: David Blacka Organization: VeriSign, Inc. To: crisp@ietf.org Subject: Re: [Crisp] REMINDER: LAST CALL Date: Thu, 1 Apr 2004 16:09:19 -0500 User-Agent: KMail/1.6.1 References: <20040326102350.G66144@shell-ng.nominum.com> In-Reply-To: <20040326102350.G66144@shell-ng.nominum.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200404011609.19464.davidb@verisignlabs.com> 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 On Friday 26 March 2004 1:27 pm, April Marine wrote: > 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. Given that there has be zero discussion on this last call, I thought that I would report that I have actually reviewed iris-core-05 and hope to review beep-05 and dreg-05 very shortly. I did not find any substative issues with core-05 (except... see below) but I did find a number of editorial issues that I have forwarded to the authors. The only non-editorial issue that I found in iris-core was about the element. It occurred to me that the element is, by its very nature, unable to express all of the possible different actual policies that might be in effect. It might be a good idea to 1) allow servers to express in XML that there are additional unepxressed limits in place and 2) provide a way for server operators to point clients at (arbitrary) text within the element. This text could be used to either describe the actual limits in words, or provide other policy information. -- David Blacka Sr. Engineer Verisign Applied Research _______________________________________________ Crisp mailing list Crisp@ietf.org https://www1.ietf.org/mailman/listinfo/crisp From exim@www1.ietf.org Fri Apr 2 17:08:24 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 RAA06584 for ; Fri, 2 Apr 2004 17:08:24 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B9WpR-0004tc-3c for crisp-archive@odin.ietf.org; Fri, 02 Apr 2004 17:07:57 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i32M7viE018816 for crisp-archive@odin.ietf.org; Fri, 2 Apr 2004 17:07:57 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B9Vvx-0003hC-Ov for crisp-web-archive@optimus.ietf.org; Fri, 02 Apr 2004 16:10: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 QAA29453 for ; Fri, 2 Apr 2004 16:10:35 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B9Vvw-0000rl-00 for crisp-web-archive@ietf.org; Fri, 02 Apr 2004 16:10:36 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B9VuL-0000O6-00 for crisp-web-archive@ietf.org; Fri, 02 Apr 2004 16:08:58 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B9Vsb-0007gK-00 for crisp-web-archive@ietf.org; Fri, 02 Apr 2004 16:07:09 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B9SKn-0007nc-QL; Fri, 02 Apr 2004 12:20:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B9QYb-0005nH-Jg for crisp@optimus.ietf.org; Fri, 02 Apr 2004 10:26:09 -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 KAA13747 for ; Fri, 2 Apr 2004 10:26:04 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B9QYX-0006ZO-00 for crisp@ietf.org; Fri, 02 Apr 2004 10:26:05 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B9QXd-0006R8-00 for crisp@ietf.org; Fri, 02 Apr 2004 10:25:09 -0500 Received: from zak.ecotroph.net ([216.93.164.123]) by ietf-mx with esmtp (Exim 4.12) id 1B9QX4-0006It-00 for crisp@ietf.org; Fri, 02 Apr 2004 10:24:34 -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; Fri, 02 Apr 2004 10:24:33 -0500 In-Reply-To: <200404011609.19464.davidb@verisignlabs.com> References: <20040326102350.G66144@shell-ng.nominum.com> <200404011609.19464.davidb@verisignlabs.com> Mime-Version: 1.0 (Apple Message framework v613) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit Cc: crisp@ietf.org From: Andrew Newton Subject: Re: [Crisp] REMINDER: LAST CALL Date: Fri, 2 Apr 2004 10:24:27 -0500 To: David Blacka X-Mailer: Apple Mail (2.613) 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=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit On Apr 1, 2004, at 4:09 PM, David Blacka wrote: > > Given that there has be zero discussion on this last call, I thought > that I > would report that I have actually reviewed iris-core-05 and hope to > review > beep-05 and dreg-05 very shortly. I did not find any substative > issues with > core-05 (except... see below) but I did find a number of editorial > issues > that I have forwarded to the authors. > Thanks for the edits. > The only non-editorial issue that I found in iris-core was about the > > element. It occurred to me that the element is, by its very > nature, > unable to express all of the possible different actual policies that > might be > in effect. It might be a good idea to 1) allow servers to express in > XML > that there are additional unepxressed limits in place and 2) provide a > way > for server operators to point clients at (arbitrary) text within the > > element. This text could be used to either describe the actual limits > in > words, or provide other policy information. > (this is referencing 3.3.7.2, btw) Marcos and I debated this in the last round. We decided there were two approaches: 1) go overboard and express everything imaginable, or 2) just express things we've seen. We opted for 2. But this is a good idea. Adding an (or something) and a help. -andy _______________________________________________ Crisp mailing list Crisp@ietf.org https://www1.ietf.org/mailman/listinfo/crisp From exim@www1.ietf.org Fri Apr 2 17:30:56 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 RAA10002 for ; Fri, 2 Apr 2004 17:30:56 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B9XBF-0004LK-MB for crisp-archive@odin.ietf.org; Fri, 02 Apr 2004 17:30:29 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i32MUTmr016695 for crisp-archive@odin.ietf.org; Fri, 2 Apr 2004 17:30:29 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B9XBF-0004LC-Gu for crisp-web-archive@optimus.ietf.org; Fri, 02 Apr 2004 17:30:29 -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 RAA09980 for ; Fri, 2 Apr 2004 17:30:26 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B9XBD-0001xU-00 for crisp-web-archive@ietf.org; Fri, 02 Apr 2004 17:30:27 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B9XAX-0001oU-00 for crisp-web-archive@ietf.org; Fri, 02 Apr 2004 17:29:45 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B9X9n-0001cW-00 for crisp-web-archive@ietf.org; Fri, 02 Apr 2004 17:28:59 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B9X9o-0003l5-OV; Fri, 02 Apr 2004 17:29:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B9X8w-0003Lb-TI for crisp@optimus.ietf.org; Fri, 02 Apr 2004 17:28:06 -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 RAA09652 for ; Fri, 2 Apr 2004 17:28:03 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B9X8u-0001P2-00 for crisp@ietf.org; Fri, 02 Apr 2004 17:28:04 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B9X7U-00013c-00 for crisp@ietf.org; Fri, 02 Apr 2004 17:26:37 -0500 Received: from cliffie.verisignlabs.com ([65.201.175.9] helo=mail.verisignlabs.com) by ietf-mx with esmtp (Exim 4.12) id 1B9X4e-0000Ft-00 for crisp@ietf.org; Fri, 02 Apr 2004 17:23:40 -0500 Received: from pinion.verisignlabs.com ([::ffff:216.168.239.87]) (AUTH: PLAIN davidb, TLS: TLSv1/SSLv3,128bits,RC4-MD5) by mail.verisignlabs.com with esmtp; Fri, 02 Apr 2004 17:23:10 -0500 From: David Blacka Organization: VeriSign, Inc. To: crisp@ietf.org Date: Fri, 2 Apr 2004 17:23:10 -0500 User-Agent: KMail/1.6.1 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200404021723.10613.davidb@verisignlabs.com> Content-Transfer-Encoding: 7bit Subject: [Crisp] comments on iris-dreg-05 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 I've sent some language and clarification issues to the authors directly, but I also came up with something that could use wider group input: In sections 3.1.3 and 3.1.4 ( and ) there is both a element containing (possibly) a and element. There is also a element. This led to the question about : do the contents of include the or not? If looking for "foo*bar.com", should you say: com foo bar ? or is it bar.com ? Wouldn't it have to be the latter if, for instance, were not specified? For simplicity's sake, my opinion is that should be dropped. seems useful in the other queries in which it appears, though. -- David Blacka Sr. Engineer Verisign Applied Research _______________________________________________ Crisp mailing list Crisp@ietf.org https://www1.ietf.org/mailman/listinfo/crisp From exim@www1.ietf.org Sat Apr 3 11:26:25 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 LAA25750 for ; Sat, 3 Apr 2004 11:26:25 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B9ny1-0006MZ-AL for crisp-archive@odin.ietf.org; Sat, 03 Apr 2004 11:25:57 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i33GPvE0024455 for crisp-archive@odin.ietf.org; Sat, 3 Apr 2004 11:25:57 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B9ny1-0006MM-1q for crisp-web-archive@optimus.ietf.org; Sat, 03 Apr 2004 11:25:57 -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 LAA25692 for ; Sat, 3 Apr 2004 11:25:54 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B9ny0-0002xH-00 for crisp-web-archive@ietf.org; Sat, 03 Apr 2004 11:25:56 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B9nx4-0002oK-00 for crisp-web-archive@ietf.org; Sat, 03 Apr 2004 11:24:59 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B9nwC-0002g3-00 for crisp-web-archive@ietf.org; Sat, 03 Apr 2004 11:24:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B9nw9-0005bM-IZ; Sat, 03 Apr 2004 11:24:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B9nw5-0005ar-AK for crisp@optimus.ietf.org; Sat, 03 Apr 2004 11:23:57 -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 LAA25551 for ; Sat, 3 Apr 2004 11:23:54 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B9nw4-0002ed-00 for crisp@ietf.org; Sat, 03 Apr 2004 11:23:56 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B9nv0-0002Wa-00 for crisp@ietf.org; Sat, 03 Apr 2004 11:22:50 -0500 Received: from zak.ecotroph.net ([216.93.164.123]) by ietf-mx with esmtp (Exim 4.12) id 1B9nu3-0002Ju-00 for crisp@ietf.org; Sat, 03 Apr 2004 11:21:51 -0500 Received: from [10.0.1.154] ([::ffff:64.83.8.178]) (AUTH: LOGIN anewton, SSL: TLSv1/SSLv3,128bits,RC4-SHA) by zak.ecotroph.net with esmtp; Sat, 03 Apr 2004 11:21:22 -0500 In-Reply-To: <200404021723.10613.davidb@verisignlabs.com> References: <200404021723.10613.davidb@verisignlabs.com> Mime-Version: 1.0 (Apple Message framework v613) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit Cc: crisp@ietf.org From: Andrew Newton Subject: Re: [Crisp] comments on iris-dreg-05 Date: Sat, 3 Apr 2004 11:21:21 -0500 To: David Blacka X-Mailer: Apple Mail (2.613) 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=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit On Apr 2, 2004, at 5:23 PM, David Blacka wrote: > > For simplicity's sake, my opinion is that should be > dropped. > > seems useful in the other queries in which it appears, > though. > This makes sense to me. it's much clearer without it but no loss of functionality. -andy _______________________________________________ Crisp mailing list Crisp@ietf.org https://www1.ietf.org/mailman/listinfo/crisp From exim@www1.ietf.org Mon Apr 5 16:45:49 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 QAA05582 for ; Mon, 5 Apr 2004 16:45:49 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BAayA-0004v9-HR for crisp-archive@odin.ietf.org; Mon, 05 Apr 2004 16:45:22 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i35KjMOe018913 for crisp-archive@odin.ietf.org; Mon, 5 Apr 2004 16:45:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BAayA-0004uy-Cj for crisp-web-archive@optimus.ietf.org; Mon, 05 Apr 2004 16:45:22 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05521 for ; Mon, 5 Apr 2004 16:45:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BAay8-0000jS-00 for crisp-web-archive@ietf.org; Mon, 05 Apr 2004 16:45:20 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BAaQN-0005d5-00 for crisp-web-archive@ietf.org; Mon, 05 Apr 2004 16:10:28 -0400 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BAaLQ-0004ng-00 for crisp-web-archive@ietf.org; Mon, 05 Apr 2004 16:05:21 -0400 Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1BAaLP-0005nj-IY for crisp-web-archive@ietf.org; Mon, 05 Apr 2004 16:05:19 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BAaLB-0003fA-Sq; Mon, 05 Apr 2004 16:05:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BAaKQ-0003M2-OY for crisp@optimus.ietf.org; Mon, 05 Apr 2004 16:04:18 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03433 for ; Mon, 5 Apr 2004 16:04:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BAaKP-0004Zk-00 for crisp@ietf.org; Mon, 05 Apr 2004 16:04:17 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BAaAu-0002qu-00 for crisp@ietf.org; Mon, 05 Apr 2004 15:54:29 -0400 Received: from zak.ecotroph.net ([216.93.164.123]) by ietf-mx with esmtp (Exim 4.12) id 1BAZnA-0000CE-00 for crisp@ietf.org; Mon, 05 Apr 2004 15:29:56 -0400 Received: from [10.0.1.69] ([::ffff:64.83.8.178]) (AUTH: LOGIN anewton, SSL: TLSv1/SSLv3,128bits,RC4-SHA) by zak.ecotroph.net with esmtp; Mon, 05 Apr 2004 15:29:55 -0400 Mime-Version: 1.0 (Apple Message framework v613) In-Reply-To: <200404021723.10613.davidb@verisignlabs.com> References: <200404021723.10613.davidb@verisignlabs.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Andrew Newton Subject: Re: [Crisp] comments on iris-dreg-05 Date: Mon, 5 Apr 2004 15:29:58 -0400 To: crisp@ietf.org X-Mailer: Apple Mail (2.613) 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=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit This small change came in privately on Friday, and Marcos and I spent the weekend going through it: There are some registries that do A and CNAME hosting as well as NS delegations. There is a desire to have a object clearly specify this state. The solution is to put an optional, boolean 'hosting' attribute on the and entity references. Additionally, we found that the entity reference is misnamed and should be . -andy _______________________________________________ Crisp mailing list Crisp@ietf.org https://www1.ietf.org/mailman/listinfo/crisp From exim@www1.ietf.org Fri Apr 9 18:40:26 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 SAA29029 for ; Fri, 9 Apr 2004 18:40:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BC4fH-0004Tg-IX for crisp-archive@odin.ietf.org; Fri, 09 Apr 2004 18:39:59 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i39Mdxkc017212 for crisp-archive@odin.ietf.org; Fri, 9 Apr 2004 18:39:59 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BC4fG-0004TX-Cf for crisp-web-archive@optimus.ietf.org; Fri, 09 Apr 2004 18:39:59 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28927 for ; Fri, 9 Apr 2004 18:39:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BC4fC-0002gN-00 for crisp-web-archive@ietf.org; Fri, 09 Apr 2004 18:39:54 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BC4c1-0002Nt-00 for crisp-web-archive@ietf.org; Fri, 09 Apr 2004 18:36:38 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BC4Xn-00020P-00 for crisp-web-archive@ietf.org; Fri, 09 Apr 2004 18:32:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BC4Xa-0003Dl-LS; Fri, 09 Apr 2004 18:32:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BC4XK-0003Bw-N3 for crisp@optimus.ietf.org; Fri, 09 Apr 2004 18:31:46 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28428 for ; Fri, 9 Apr 2004 18:31:41 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BC4XE-0001wZ-00 for crisp@ietf.org; Fri, 09 Apr 2004 18:31:41 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BC4Tj-0001WG-00 for crisp@ietf.org; Fri, 09 Apr 2004 18:28:04 -0400 Received: from cliffie.verisignlabs.com ([65.201.175.9] helo=mail.verisignlabs.com) by ietf-mx with esmtp (Exim 4.12) id 1BC4O7-00012b-00 for crisp@ietf.org; Fri, 09 Apr 2004 18:22:15 -0400 Received: from pinion.verisignlabs.com ([::ffff:216.168.239.87]) (AUTH: PLAIN davidb, TLS: TLSv1/SSLv3,128bits,RC4-MD5) by mail.verisignlabs.com with esmtp; Fri, 09 Apr 2004 18:21:40 -0400 From: David Blacka Organization: VeriSign, Inc. To: crisp@ietf.org Date: Fri, 9 Apr 2004 18:21:40 -0400 User-Agent: KMail/1.6.1 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200404091821.40051.davidb@verisignlabs.com> Content-Transfer-Encoding: 7bit Subject: [Crisp] controls in IRIS 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 I realize that this is officially past WG last call, but this is the sort of thing I only notice when I try to implement the specification. I'm currently struggling with architecting and elements. After noodling about with this for (an admittedly) short time, I've come to the following conclusion: As currently specified, controls may only be (sensically) defined at the IRIS-core level: that is, as features that *all* registryTypes nominally support. In this sense, whether or not a server accepts a control or not is entirely a policy decision, and not based on what registryTypes the server happens to support. If the intent was to create a mechanism for registryTypes to exend for themselves, then the location of the control element is not optimally placed. For that situation, one of the following things must occur: 1) rules should be described on how to deal with controls that only apply to some subset of the searchSets present in a request. Currently, this is totally unspecified. 2) the control element should be moved into the searchSet element, thus making it possible to be registryType specific. 3) or, we could do nothing and Let Chaos Rule! At the moment, I cannot see what advantage controls gain by being placed at the level of the request rather than the searchSet. -- David Blacka Sr. Engineer Verisign Applied Research _______________________________________________ Crisp mailing list Crisp@ietf.org https://www1.ietf.org/mailman/listinfo/crisp From exim@www1.ietf.org Sat Apr 10 12:30:22 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 MAA11062 for ; Sat, 10 Apr 2004 12:30:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BCLMg-0004yY-Ql for crisp-archive@odin.ietf.org; Sat, 10 Apr 2004 12:29:54 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3AGTsVd019126 for crisp-archive@odin.ietf.org; Sat, 10 Apr 2004 12:29:54 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BCLMg-0004yP-Mq for crisp-web-archive@optimus.ietf.org; Sat, 10 Apr 2004 12:29:54 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11046 for ; Sat, 10 Apr 2004 12:29:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BCLMe-0007K1-00 for crisp-web-archive@ietf.org; Sat, 10 Apr 2004 12:29:52 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BCLLW-0007Ab-00 for crisp-web-archive@ietf.org; Sat, 10 Apr 2004 12:28:43 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BCLKr-00070q-00 for crisp-web-archive@ietf.org; Sat, 10 Apr 2004 12:28:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BCLKr-0004jn-9w; Sat, 10 Apr 2004 12:28:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BCLJu-0004h5-Bu for crisp@optimus.ietf.org; Sat, 10 Apr 2004 12:27:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10995 for ; Sat, 10 Apr 2004 12:26:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BCLJr-0006qh-00 for crisp@ietf.org; Sat, 10 Apr 2004 12:26:59 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BCLIh-0006gi-00 for crisp@ietf.org; Sat, 10 Apr 2004 12:25:48 -0400 Received: from zak.ecotroph.net ([216.93.164.123]) by ietf-mx with esmtp (Exim 4.12) id 1BCLHp-0006Vd-00 for crisp@ietf.org; Sat, 10 Apr 2004 12:24:53 -0400 Received: from [10.0.1.74] ([::ffff:64.83.8.178]) (AUTH: LOGIN anewton, SSL: TLSv1/SSLv3,128bits,RC4-SHA) by zak.ecotroph.net with esmtp; Sat, 10 Apr 2004 12:24:42 -0400 In-Reply-To: <200404091821.40051.davidb@verisignlabs.com> References: <200404091821.40051.davidb@verisignlabs.com> Mime-Version: 1.0 (Apple Message framework v613) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <90DE7F8D-8B0B-11D8-9210-000A95B3BA44@hxr.us> Content-Transfer-Encoding: 7bit Cc: crisp@ietf.org From: Andrew Newton Subject: Re: [Crisp] controls in IRIS Date: Sat, 10 Apr 2004 12:24:39 -0400 To: David Blacka X-Mailer: Apple Mail (2.613) 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=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit This seems to be supposing an operator unfamiliar with the types of registries being run and the types of controls and policies being enforced by their own server -- a situation that is not probable. Getting into a situation where a server does not understand the controls it implements vs the registries it implements seems to me to be an implementation issue. By keeping the controls at the request level, a server must only process the control against authorization once. Putting it at the search set level means the server must do this checking multiple times per request. Additionally, controls are a client initiated mechanism (unlike bags), and it is unlikely that an end user desiring policy exception processing based on their accepted level of access means for this exception state to be applied to some searches and not others. -andy On Apr 9, 2004, at 6:21 PM, David Blacka wrote: > I realize that this is officially past WG last call, but this is the > sort of > thing I only notice when I try to implement the specification. > > I'm currently struggling with architecting and > elements. > After noodling about with this for (an admittedly) short time, I've > come to > the following conclusion: > > As currently specified, controls may only be (sensically) defined at > the > IRIS-core level: that is, as features that *all* registryTypes > nominally > support. > > In this sense, whether or not a server accepts a control or not is > entirely a > policy decision, and not based on what registryTypes the server > happens to > support. > > If the intent was to create a mechanism for registryTypes to exend for > themselves, then the location of the control element is not optimally > placed. > > For that situation, one of the following things must occur: > > 1) rules should be described on how to deal with controls that only > apply to > some subset of the searchSets present in a request. Currently, this is > totally unspecified. > > 2) the control element should be moved into the searchSet element, > thus making > it possible to be registryType specific. > > 3) or, we could do nothing and Let Chaos Rule! > > At the moment, I cannot see what advantage controls gain by being > placed at > the level of the request rather than the searchSet. > > -- > David Blacka > Sr. Engineer Verisign Applied Research > > _______________________________________________ > 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 Sun Apr 11 03:36:42 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 DAA15800 for ; Sun, 11 Apr 2004 03:36:42 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BCZVl-0002fR-OH for crisp-archive@odin.ietf.org; Sun, 11 Apr 2004 03:36:13 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3B7aDh5010253 for crisp-archive@odin.ietf.org; Sun, 11 Apr 2004 03:36:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BCZVk-0002fG-4v for crisp-web-archive@optimus.ietf.org; Sun, 11 Apr 2004 03:36:13 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA15762 for ; Sun, 11 Apr 2004 03:36:10 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BCZVh-0004PE-00 for crisp-web-archive@ietf.org; Sun, 11 Apr 2004 03:36:09 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BCZR6-0003yd-00 for crisp-web-archive@ietf.org; Sun, 11 Apr 2004 03:31:26 -0400 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BCZOR-0003QB-00 for crisp-web-archive@ietf.org; Sun, 11 Apr 2004 03:28:39 -0400 Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1BCZ6K-0004F4-9n for crisp-web-archive@ietf.org; Sun, 11 Apr 2004 03:09:56 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BCZ65-0008Mi-NX; Sun, 11 Apr 2004 03:09:41 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BCYOl-0004gM-RC for crisp@optimus.ietf.org; Sun, 11 Apr 2004 02:24:55 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14139 for ; Sun, 11 Apr 2004 02:24:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BCYOg-0003h8-00 for crisp@ietf.org; Sun, 11 Apr 2004 02:24:50 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BCYMr-0003Ze-00 for crisp@ietf.org; Sun, 11 Apr 2004 02:22:58 -0400 Received: from cliffie.verisignlabs.com ([65.201.175.9] helo=mail.verisignlabs.com) by ietf-mx with esmtp (Exim 4.12) id 1BCYLz-0003Kq-00 for crisp@ietf.org; Sun, 11 Apr 2004 02:22:04 -0400 Received: from [10.0.1.2] ([::ffff:68.54.92.10]) (AUTH: PLAIN davidb, TLS: TLSv1/SSLv3,128bits,RC4-SHA) by mail.verisignlabs.com with esmtp; Sun, 11 Apr 2004 02:21:30 -0400 Mime-Version: 1.0 (Apple Message framework v613) In-Reply-To: <90DE7F8D-8B0B-11D8-9210-000A95B3BA44@hxr.us> References: <200404091821.40051.davidb@verisignlabs.com> <90DE7F8D-8B0B-11D8-9210-000A95B3BA44@hxr.us> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <77813C08-8B80-11D8-AA06-000A95CC77E2@verisignlabs.com> Content-Transfer-Encoding: 7bit From: David Blacka Subject: Re: [Crisp] controls in IRIS Date: Sun, 11 Apr 2004 02:21:28 -0400 To: crisp@ietf.org X-Mailer: Apple Mail (2.613) 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 Again, I realize that I'm posting after the end of last call (which was April 6, I think). The working group can tell me that a) this is not an issue (I think I could be convinced), or b) it may be an issue, but since we are passed last call, we aren't going to talk about it. But absent any other input, I will continue to discuss this issue. On Apr 10, 2004, at 12:24 PM, Andrew Newton wrote: > This seems to be supposing an operator unfamiliar with the types of > registries being run and the types of controls and policies being > enforced by their own server -- a situation that is not probable. > Getting into a situation where a server does not understand the > controls it implements vs the registries it implements seems to me to > be an implementation issue. I don't *think* I supposed this, but maybe I did. I think I can see how, in some sense, this is all an implementation issue, as any particular way of handling controls will be indistinguishable from "policy". However, I think (and I could be mistaken), my concerns are not just implementation issues, as they effect client expectations. > By keeping the controls at the request level, a server must only > process the control against authorization once. Putting it at the > search set level means the server must do this checking multiple times > per request. Additionally, controls are a client initiated mechanism > (unlike bags), and it is unlikely that an end user desiring policy > exception processing based on their accepted level of access means for > this exception state to be applied to some searches and not others. I didn't understand this paragraph. However, it is possible that my main concern is fairly easily remedied. First, some background. Although iris-core-05 doesn't really have any text about this, it is fairly obvious that the mechanism described is intended to be extended without versioning. I say this is obvious because that is only reason that I can see for allowing elements from any namespace in the element. Also, since there is no text describing, precisely, what controls *are*, I imagine them to be, generically: something that alters the behavior of queries. In general, I would expect controls to be applicable to all queries for a registryType(s), and to be somewhat orthogonal to the queries themselves. So my base question comes down to: what happens when a control is provided that isn't defined for all of the queries in the request? This question will come up the first time someone defines a new control, I think. The problem is really just lack of specification. I think that decent behavior can be specified fairly easily, though. I think iris-core should say something vaguely like: Servers accept or reject controls based on policy and on whether or not the server has ever heard of a particular control [it sort of already says this, I think]. Servers should accept or reject the control independently from the rest of the request (i.e., the queries themselves). When processing a searchSet, if the control is not defined for the target registryType, then the control is simply ignored. Clients SHOULD only include a control when that control is defined for all target registryTypes in the request. (That is, clients SHOULD NOT put themselves in a situation where the control will be ignored). [This rule is probably not absolutely necessary] And section 7.1 should add a requirement for registryTypes to declare what controls are supported. In addition, I think we need to specify what should happen if a control is rejected. Does the server then process the request of the request as if the control did not exist? Or does it stop and return an error? If so, what does this error look like? I think the answer to this is that servers MUST not process the rest of the request, and return some sort of response that includes the reaction and probably an empty . I think this last point is sort of important, as I think without it could be pretty annoying to use, as I'm pretty sure that if I'm probing a server with the control, I really don't want results back, no matter what. _______________________________________________ Crisp mailing list Crisp@ietf.org https://www1.ietf.org/mailman/listinfo/crisp From exim@www1.ietf.org Tue Apr 13 06:20:29 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 GAA02619 for ; Tue, 13 Apr 2004 06:20:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BDL0k-0003Oi-8D for crisp-archive@odin.ietf.org; Tue, 13 Apr 2004 06:20:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3DAJMu4013060 for crisp-archive@odin.ietf.org; Tue, 13 Apr 2004 06:19:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BDKzR-0003Mq-3h for crisp-web-archive@optimus.ietf.org; Tue, 13 Apr 2004 06:19:22 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02527 for ; Tue, 13 Apr 2004 06:17:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BDKzN-0003db-00 for crisp-web-archive@ietf.org; Tue, 13 Apr 2004 06:17:57 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BDKyY-0003X6-00 for crisp-web-archive@ietf.org; Tue, 13 Apr 2004 06:17:06 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BDKwY-0003RD-00 for crisp-web-archive@ietf.org; Tue, 13 Apr 2004 06:15:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BDKwX-00033m-GJ; Tue, 13 Apr 2004 06:15:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BDKua-00031V-RS for crisp@optimus.ietf.org; Tue, 13 Apr 2004 06:14:22 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02408 for ; Tue, 13 Apr 2004 06:12:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BDKuW-0003Ji-00 for crisp@ietf.org; Tue, 13 Apr 2004 06:12:56 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BDKtT-0003FV-00 for crisp@ietf.org; Tue, 13 Apr 2004 06:11:51 -0400 Received: from smtp.denic.de ([81.91.161.3]) by ietf-mx with esmtp (Exim 4.12) id 1BDKsK-000381-00 for crisp@ietf.org; Tue, 13 Apr 2004 06:10:40 -0400 Received: from notes.denic.de ([192.168.0.77]) by smtp.denic.de with esmtp id 1BDKrk-0000ga-00; Tue, 13 Apr 2004 12:10:04 +0200 In-Reply-To: <77813C08-8B80-11D8-AA06-000A95CC77E2@verisignlabs.com> To: David Blacka Cc: crisp@ietf.org Subject: Re: [Crisp] controls in IRIS MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 From: Marcos Sanz/Denic Message-ID: Date: Tue, 13 Apr 2004 12:08:36 +0200 X-MIMETrack: Serialize by Router on notes/Denic(Release 6.0.3|September 26, 2003) at 13.04.2004 12:10:04, Serialize complete at 13.04.2004 12:10:04 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.1 required=5.0 tests=AWL autolearn=no version=2.60 David, > Also, since > there is no text describing, precisely, what controls *are*, I imagine > them to be, generically: something that alters the behavior of queries. Section 3.1: "[...] This child element allows a client to signal to a server the desire for special states or processing" The formulation is pretty abstract, but it's the definition we have and which your understanding of it has well covered. > So my base question comes down to: what happens when a control is > provided that isn't defined for all of the queries in the request? [...] > In addition, I think we need to specify what should happen if a control > is rejected. Does the server then process the request of the request > as if the control did not exist? Or does it stop and return an error? > If so, what does this error look like? Admittedly, section 3.3.8 doesn't address these (rather unlikely) points and leaves imagination of implementors open. I would like to add some wording, if we are still in time. Regards, Marcos _______________________________________________ Crisp mailing list Crisp@ietf.org https://www1.ietf.org/mailman/listinfo/crisp From exim@www1.ietf.org Fri Apr 16 16:51:50 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 QAA07934 for ; Fri, 16 Apr 2004 16:51:49 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BEa40-0004TS-2o for crisp-archive@odin.ietf.org; Fri, 16 Apr 2004 16:35:52 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3GKZqtj017198 for crisp-archive@odin.ietf.org; Fri, 16 Apr 2004 16:35:52 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BEZas-0006x0-D4 for crisp-web-archive@optimus.ietf.org; Fri, 16 Apr 2004 16:05:46 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03071 for ; Fri, 16 Apr 2004 16:05:44 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BEZaq-0002JT-Qb for crisp-web-archive@ietf.org; Fri, 16 Apr 2004 16:05:44 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BEZZg-0002Bd-00 for crisp-web-archive@ietf.org; Fri, 16 Apr 2004 16:04:32 -0400 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BEZYo-00025d-00 for crisp-web-archive@ietf.org; Fri, 16 Apr 2004 16:03:38 -0400 Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1BEZYp-0003V9-2Q for crisp-web-archive@ietf.org; Fri, 16 Apr 2004 16:03:39 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BEZB9-0005sM-UO; Fri, 16 Apr 2004 15:39:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BEZ7s-0004lt-GY for crisp@optimus.ietf.org; Fri, 16 Apr 2004 15:35:48 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00870; Fri, 16 Apr 2004 15:35:46 -0400 (EDT) Message-Id: <200404161935.PAA00870@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org Cc: crisp@ietf.org From: Internet-Drafts@ietf.org Date: Fri, 16 Apr 2004 15:35:46 -0400 Subject: [Crisp] I-D ACTION:draft-ietf-crisp-iris-dreg-06.txt 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.5 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME autolearn=no version=2.60 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Cross Registry Information Service Protocol Working Group of the IETF. Title : IRIS - A Domain Registry (dreg) Type for the Internet Registry Information Service Author(s) : A. Newton, M. Sanz Filename : draft-ietf-crisp-iris-dreg-06.txt Pages : 57 Date : 2004-4-16 This document describes an IRIS registry schema for registered DNS information. The schema extends the necessary query and result operations of IRIS to provide the functional information service needs for syntaxes and results used by domain registries and registrars. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-crisp-iris-dreg-06.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-crisp-iris-dreg-06.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-crisp-iris-dreg-06.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-4-16154408.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-crisp-iris-dreg-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-crisp-iris-dreg-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-4-16154408.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Crisp mailing list Crisp@ietf.org https://www1.ietf.org/mailman/listinfo/crisp From exim@www1.ietf.org Fri Apr 16 16:54:02 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 QAA08310 for ; Fri, 16 Apr 2004 16:54:01 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BEa4V-0004ey-8g for crisp-archive@odin.ietf.org; Fri, 16 Apr 2004 16:36:23 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3GKaNOB017906 for crisp-archive@odin.ietf.org; Fri, 16 Apr 2004 16:36:23 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BEZdB-0008FS-MZ for crisp-web-archive@optimus.ietf.org; Fri, 16 Apr 2004 16:08:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03301 for ; Fri, 16 Apr 2004 16:08:07 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BEZdA-0002en-42 for crisp-web-archive@ietf.org; Fri, 16 Apr 2004 16:08:08 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BEZbh-0002RP-00 for crisp-web-archive@ietf.org; Fri, 16 Apr 2004 16:06:38 -0400 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BEZaR-0002G0-00 for crisp-web-archive@ietf.org; Fri, 16 Apr 2004 16:05:19 -0400 Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1BEZaR-0003ZZ-B5 for crisp-web-archive@ietf.org; Fri, 16 Apr 2004 16:05:19 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BEZBC-0005sm-D4; Fri, 16 Apr 2004 15:39:14 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BEZ8D-0004xo-NF for crisp@optimus.ietf.org; Fri, 16 Apr 2004 15:36:09 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00914; Fri, 16 Apr 2004 15:36:07 -0400 (EDT) Message-Id: <200404161936.PAA00914@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org Cc: crisp@ietf.org From: Internet-Drafts@ietf.org Date: Fri, 16 Apr 2004 15:36:07 -0400 Subject: [Crisp] I-D ACTION:draft-ietf-crisp-iris-core-06.txt 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.5 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME autolearn=no version=2.60 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Cross Registry Information Service Protocol Working Group of the IETF. Title : IRIS - The Internet Registry Information Service (IRIS) Core Protocol Author(s) : A. Newton, M. Sanz Filename : draft-ietf-crisp-iris-core-06.txt Pages : 61 Date : 2004-4-16 This document describes an application layer client-server protocol for a framework of representing the query and result operations of the information services of Internet registries. Specified in XML, the protocol defines generic query and result operations and a mechanism for extending these operations for specific registry service needs. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-crisp-iris-core-06.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-crisp-iris-core-06.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-crisp-iris-core-06.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-4-16154422.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-crisp-iris-core-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-crisp-iris-core-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-4-16154422.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Crisp mailing list Crisp@ietf.org https://www1.ietf.org/mailman/listinfo/crisp From exim@www1.ietf.org Fri Apr 16 16:55:20 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 QAA08668 for ; Fri, 16 Apr 2004 16:55:19 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BEaAc-00087Q-Rh for crisp-archive@odin.ietf.org; Fri, 16 Apr 2004 16:42:42 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3GKggtG031202 for crisp-archive@odin.ietf.org; Fri, 16 Apr 2004 16:42:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BEZfj-0000zQ-Hi for crisp-web-archive@optimus.ietf.org; Fri, 16 Apr 2004 16:10:47 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03700 for ; Fri, 16 Apr 2004 16:10:45 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BEZfh-00031Z-TD for crisp-web-archive@ietf.org; Fri, 16 Apr 2004 16:10:45 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BEZek-0002uw-00 for crisp-web-archive@ietf.org; Fri, 16 Apr 2004 16:09:47 -0400 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BEZdq-0002m2-00 for crisp-web-archive@ietf.org; Fri, 16 Apr 2004 16:08:50 -0400 Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1BEZdq-0003e8-TA for crisp-web-archive@ietf.org; Fri, 16 Apr 2004 16:08:50 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BEZBF-0005tF-1T; Fri, 16 Apr 2004 15:39:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BEZ8I-0004xy-CC for crisp@optimus.ietf.org; Fri, 16 Apr 2004 15:36:14 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00939; Fri, 16 Apr 2004 15:36:12 -0400 (EDT) Message-Id: <200404161936.PAA00939@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org Cc: crisp@ietf.org From: Internet-Drafts@ietf.org Date: Fri, 16 Apr 2004 15:36:12 -0400 Subject: [Crisp] I-D ACTION:draft-ietf-crisp-iris-beep-06.txt 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.5 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME autolearn=no version=2.60 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Cross Registry Information Service Protocol Working Group of the IETF. Title : IRIS - Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP) Author(s) : A. Newton, M. Sanz Filename : draft-ietf-crisp-iris-beep-06.txt Pages : 19 Date : 2004-4-16 This document specifies how to use the Blocks Extensible Exchange Protocol (BEEP) as the application transport substrate for the Internet Registry Information Service (IRIS). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-crisp-iris-beep-06.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-crisp-iris-beep-06.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-crisp-iris-beep-06.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-4-16154433.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-crisp-iris-beep-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-crisp-iris-beep-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-4-16154433.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Crisp mailing list Crisp@ietf.org https://www1.ietf.org/mailman/listinfo/crisp From exim@www1.ietf.org Thu Apr 22 13:33:31 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 NAA12445 for ; Thu, 22 Apr 2004 13:33:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BGhuq-0003Ob-V4 for crisp-archive@odin.ietf.org; Thu, 22 Apr 2004 13:23:13 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3MHNCnH013047 for crisp-archive@odin.ietf.org; Thu, 22 Apr 2004 13:23:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BGhqV-0001st-8c for crisp-web-archive@optimus.ietf.org; Thu, 22 Apr 2004 13:18:43 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11422 for ; Thu, 22 Apr 2004 13:18:38 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BGhqR-0006Bj-7c for crisp-web-archive@ietf.org; Thu, 22 Apr 2004 13:18:39 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BGhoW-0005Rl-00 for crisp-web-archive@ietf.org; Thu, 22 Apr 2004 13:16:41 -0400 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BGhnX-00057l-03 for crisp-web-archive@ietf.org; Thu, 22 Apr 2004 13:15:39 -0400 Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1BGhlx-0007yU-HP for crisp-web-archive@ietf.org; Thu, 22 Apr 2004 13:14:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BGheD-0005zs-Ai; Thu, 22 Apr 2004 13:06:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BGhWj-0003tp-Km for crisp@optimus.ietf.org; Thu, 22 Apr 2004 12:58:17 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10386 for ; Thu, 22 Apr 2004 12:58:13 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BGhWf-0000bQ-Hy for crisp@ietf.org; Thu, 22 Apr 2004 12:58:13 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BGhVk-0000Ih-00 for crisp@ietf.org; Thu, 22 Apr 2004 12:57:16 -0400 Received: from shell-ng.nominum.com ([81.200.64.181]) by ietf-mx with esmtp (Exim 4.12) id 1BGhUr-0007Vk-00 for crisp@ietf.org; Thu, 22 Apr 2004 12:56:21 -0400 Received: by shell-ng.nominum.com (Postfix, from userid 10182) id 2DEF056835; Thu, 22 Apr 2004 09:55:47 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by shell-ng.nominum.com (Postfix) with ESMTP id 2BBCC56830; Thu, 22 Apr 2004 09:55:47 -0700 (PDT) Date: Thu, 22 Apr 2004 09:55:47 -0700 (PDT) From: April Marine To: CRISP WG Cc: George Michaelson , April Marine Message-ID: <20040422095250.I66749@shell-ng.nominum.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Crisp] CRISP docs to AD/IESG 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 Hi all, As you know, we have completed WG last call on the following docs and the authors have updated them based on comments received (thanks David Blacka! :). draft-ietf-crisp-iris-core-06.txt draft-ietf-crisp-iris-dreg-06.txt draft-ietf-crisp-iris-beep-06.txt We have officially asked Ted Hardie, our AD, to take the next steps in getting them to RFC. Next steps are his own review and IETF Last Call. This is significant progress for the group--many thanks to all! Special thanks to Marcos Sanz and extra special thanks to Andy Newton for all their work. fyi, April and George _______________________________________________ Crisp mailing list Crisp@ietf.org https://www1.ietf.org/mailman/listinfo/crisp From exim@www1.ietf.org Fri Apr 23 17:50:26 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 RAA15593 for ; Fri, 23 Apr 2004 17:50:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BH8Mb-00044F-2y for crisp-archive@odin.ietf.org; Fri, 23 Apr 2004 17:37:37 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3NLbbpr015627 for crisp-archive@odin.ietf.org; Fri, 23 Apr 2004 17:37:37 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BH894-0006uP-TS for crisp-web-archive@optimus.ietf.org; Fri, 23 Apr 2004 17:23:38 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13876 for ; Fri, 23 Apr 2004 17:23:34 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BH892-0005Yv-Je for crisp-web-archive@ietf.org; Fri, 23 Apr 2004 17:23:36 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BH88V-0005IC-00 for crisp-web-archive@ietf.org; Fri, 23 Apr 2004 17:23:04 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BH87a-0004xl-00 for crisp-web-archive@ietf.org; Fri, 23 Apr 2004 17:22:06 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BH7tx-0001Ju-Cq; Fri, 23 Apr 2004 17:08:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BH5mj-0006bj-RC for crisp@optimus.ietf.org; Fri, 23 Apr 2004 14:52:25 -0400 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27571 for ; Fri, 23 Apr 2004 14:52:22 -0400 (EDT) Received: from nobody by optimus.ietf.org with local (Exim 4.20) id 1BH5JY-0002KY-Ai; Fri, 23 Apr 2004 14:22:16 -0400 X-test-idtracker: no To: IETF-Announce :; From: The IESG Reply-to: iesg@ietf.org Message-Id: Date: Fri, 23 Apr 2004 14:22:16 -0400 Subject: [Crisp] Last Call: 'IRIS - The Internet Registry Information Service (IRIS) Core Protocol' to Proposed Standard 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=1.4 required=5.0 tests=AWL,TO_HAS_SPACES autolearn=no version=2.60 The IESG has received a request from the Cross Registry Information Service Protocol WG to consider the following document: - 'IRIS - The Internet Registry Information Service (IRIS) Core Protocol ' as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2004-05-07. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-crisp-iris-core-06.txt _______________________________________________ Crisp mailing list Crisp@ietf.org https://www1.ietf.org/mailman/listinfo/crisp From exim@www1.ietf.org Tue Apr 27 18:38: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 SAA07970 for ; Tue, 27 Apr 2004 18:38:06 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIb9z-0007wn-Ce for crisp-archive@odin.ietf.org; Tue, 27 Apr 2004 18:34:39 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3RMYdYL030540 for crisp-archive@odin.ietf.org; Tue, 27 Apr 2004 18:34:39 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIb4x-00077j-OD for crisp-web-archive@optimus.ietf.org; Tue, 27 Apr 2004 18:29:27 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07327 for ; Tue, 27 Apr 2004 18:29:22 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BIb4s-0004YR-LH for crisp-web-archive@ietf.org; Tue, 27 Apr 2004 18:29:22 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BIb42-0004RM-00 for crisp-web-archive@ietf.org; Tue, 27 Apr 2004 18:28:31 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BIb3O-0004JY-00 for crisp-web-archive@ietf.org; Tue, 27 Apr 2004 18:27:50 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIapB-0002TQ-4Z; Tue, 27 Apr 2004 18:13:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIaEM-0007IZ-Qh for crisp@optimus.ietf.org; Tue, 27 Apr 2004 17:35:06 -0400 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03317 for ; Tue, 27 Apr 2004 17:35:02 -0400 (EDT) Received: from nobody by optimus.ietf.org with local (Exim 4.20) id 1BIa37-0005xm-FC; Tue, 27 Apr 2004 17:23:29 -0400 X-test-idtracker: no To: IETF-Announce :; From: The IESG Reply-to: iesg@ietf.org Message-Id: Date: Tue, 27 Apr 2004 17:23:29 -0400 Subject: [Crisp] Last Call: 'IRIS - Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP)' to Proposed Standard 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=1.4 required=5.0 tests=AWL,TO_HAS_SPACES autolearn=no version=2.60 The IESG has received a request from the Cross Registry Information Service Protocol WG to consider the following document: - 'IRIS - Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP) ' as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2004-05-12. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-crisp-iris-beep-06.txt _______________________________________________ Crisp mailing list Crisp@ietf.org https://www1.ietf.org/mailman/listinfo/crisp From exim@www1.ietf.org Tue Apr 27 18:38:10 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 SAA08009 for ; Tue, 27 Apr 2004 18:38:10 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIbA2-0007xD-Ty for crisp-archive@odin.ietf.org; Tue, 27 Apr 2004 18:34:42 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3RMYgnY030567 for crisp-archive@odin.ietf.org; Tue, 27 Apr 2004 18:34:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIb5g-0007Bv-Nh for crisp-web-archive@optimus.ietf.org; Tue, 27 Apr 2004 18:30:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07434 for ; Tue, 27 Apr 2004 18:30:07 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BIb5b-0004ek-Pa for crisp-web-archive@ietf.org; Tue, 27 Apr 2004 18:30:07 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BIb4d-0004WT-00 for crisp-web-archive@ietf.org; Tue, 27 Apr 2004 18:29:07 -0400 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BIb3d-0004LG-00 for crisp-web-archive@ietf.org; Tue, 27 Apr 2004 18:28:05 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIapB-0002Ta-BT; Tue, 27 Apr 2004 18:13:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BIaEn-0007LT-CR for crisp@optimus.ietf.org; Tue, 27 Apr 2004 17:35:33 -0400 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03359 for ; Tue, 27 Apr 2004 17:35:29 -0400 (EDT) Received: from nobody by optimus.ietf.org with local (Exim 4.20) id 1BIa4A-0006Fp-2Z; Tue, 27 Apr 2004 17:24:34 -0400 X-test-idtracker: no To: IETF-Announce :; From: The IESG Reply-to: iesg@ietf.org Message-Id: Date: Tue, 27 Apr 2004 17:24:34 -0400 Subject: [Crisp] Last Call: 'IRIS - A Domain Registry (dreg) Type for the Internet Registry Information Service' to Proposed Standard 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=1.4 required=5.0 tests=AWL,TO_HAS_SPACES autolearn=no version=2.60 The IESG has received a request from the Cross Registry Information Service Protocol WG to consider the following document: - 'IRIS - A Domain Registry (dreg) Type for the Internet Registry Information Service ' as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2004-05-12. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-crisp-iris-dreg-06.txt _______________________________________________ Crisp mailing list Crisp@ietf.org https://www1.ietf.org/mailman/listinfo/crisp