Re: [Gen-art] Fwd: genart LC review of draft-ietf-nfsv4-rpc-netid-03.txt (and -04)

Robert Sparks <rjsparks@estacado.net> Thu, 04 December 2008 23:13 UTC

Return-Path: <gen-art-bounces@ietf.org>
X-Original-To: gen-art-archive@optimus.ietf.org
Delivered-To: ietfarch-gen-art-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 53D293A6937; Thu, 4 Dec 2008 15:13:14 -0800 (PST)
X-Original-To: gen-art@core3.amsl.com
Delivered-To: gen-art@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8CE243A6AF4 for <gen-art@core3.amsl.com>; Thu, 4 Dec 2008 15:13:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dF9jpnlVtF+S for <gen-art@core3.amsl.com>; Thu, 4 Dec 2008 15:13:11 -0800 (PST)
Received: from estacado.net (estacado-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:266::2]) by core3.amsl.com (Postfix) with ESMTP id 0564A3A6A65 for <gen-art@ietf.org>; Thu, 4 Dec 2008 15:13:10 -0800 (PST)
Received: from [192.168.2.6] (pool-71-170-80-166.dllstx.fios.verizon.net [71.170.80.166]) (authenticated bits=0) by estacado.net (8.14.2/8.14.2) with ESMTP id mB4NCvHG000756 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 4 Dec 2008 17:13:02 -0600 (CST) (envelope-from rjsparks@estacado.net)
Message-Id: <2C7FE4DC-82CE-4FF8-9F52-58FB600CDF09@estacado.net>
From: Robert Sparks <rjsparks@estacado.net>
To: mike@eisler.com
In-Reply-To: <da309ff64b204dd78e5c55509b42748d.squirrel@webmail.eisler.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 04 Dec 2008 17:12:56 -0600
References: <32E142FF-7258-48DA-A55F-61D12DA8A52D@nostrum.com> <4165FB23-C6E7-4C89-9599-EA03FC14A040@estacado.net> <da309ff64b204dd78e5c55509b42748d.squirrel@webmail.eisler.com>
X-Mailer: Apple Mail (2.929.2)
Cc: nfsv4-chairs@tools.ietf.org, gen-art@ietf.org, lars.eggert@nokia.com
Subject: Re: [Gen-art] Fwd: genart LC review of draft-ietf-nfsv4-rpc-netid-03.txt (and -04)
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: gen-art-bounces@ietf.org
Errors-To: gen-art-bounces@ietf.org

inline:

On Dec 4, 2008, at 3:19 PM, mike@eisler.com wrote:
<trim>
>
>
>
>>> 1) There is an inconsistency between the text in 3.1 claiming
>>> "Netids can be up to 2^32 -1 octets in length" and the instructions
>>> in the rest of the document which restrict them to 128 octets.
>
> The XDR encoding for netids allows them to be 2^32-1 bytes long.
>
> That's obviously not feasible for an IANA registry, which is where the
> restriction comes in.
>
> From the I-D:
<trim>
>
> Tell me how I can make it clearer?

Perhaps in the sentence that says "2^32-1" you can explicitly say the  
XDR encoding allows
this long length, but this registry will only allow a much shorter  
length.

<trim>

>>> 5) Why are you putting length restrictions on what can go into the
>>> descriptive parts of the registry? (The description and point of
>>> contact)? Where did the limit values you selected come from?
>
> Regarding the latter question I looked at some registries, and these
> seemed to be acceptable limits. Regarding the former question, one
> has to have limits. What happens if someone submits a 1MB, 1GB, 1TB,  
> etc.
> entry?

IANA says "You've got to be kidding".

This hasn't been a problem, and IANA's not going to need this document  
as a shield
to protect against someone trying to do something like that in the  
future.

I think what you're really after here is guidance to the person making  
a registration request rather
than setting rules IANA has to enforce.


Thanks for your fast response!

RjS
_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art