Re: [Crisp] REMINDER: LAST CALL

David Blacka <davidb@verisignlabs.com> Fri, 02 April 2004 12:33 UTC

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 <crisp-archive@odin.ietf.org>; 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 <crisp-web-archive@ietf.org>; 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 <crisp@ietf.org>; 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 <davidb@verisignlabs.com>
Organization: VeriSign, Inc.
To: crisp@ietf.org
Subject: Re: [Crisp] REMINDER: LAST CALL
Date: Thu, 01 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: <https://www1.ietf.org/mailman/listinfo/crisp>, <mailto:crisp-request@ietf.org?subject=unsubscribe>
List-Id: Cross Registry Information Service Protocol <crisp.ietf.org>
List-Post: <mailto:crisp@ietf.org>
List-Help: <mailto:crisp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/crisp>, <mailto:crisp-request@ietf.org?subject=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 <limit> 
element.  It occurred to me that the <limit> 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 <limits> 
element.  This text could be used to either describe the actual limits in 
words, or provide other policy information.

-- 
David Blacka    <davidb@verisignlabs.com> 
Sr. Engineer    Verisign Applied Research

_______________________________________________
Crisp mailing list
Crisp@ietf.org
https://www1.ietf.org/mailman/listinfo/crisp