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

Robert Sparks <rjsparks@estacado.net> Fri, 05 December 2008 18:45 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 1E1F528C167; Fri, 5 Dec 2008 10:45:25 -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 C750328C1BE for <gen-art@core3.amsl.com>; Fri, 5 Dec 2008 10:45:23 -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=[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 0gH8xUJ00Tzr for <gen-art@core3.amsl.com>; Fri, 5 Dec 2008 10:45:23 -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 8A18F28C167 for <gen-art@ietf.org>; Fri, 5 Dec 2008 10:45:22 -0800 (PST)
Received: from dn3-232.estacado.net (dn3-232.estacado.net [172.16.3.232]) (authenticated bits=0) by estacado.net (8.14.2/8.14.2) with ESMTP id mB5IjDO3017873 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 5 Dec 2008 12:45:14 -0600 (CST) (envelope-from rjsparks@estacado.net)
Message-Id: <D4E618C8-6ECF-43A9-9E4A-677877E58FCB@estacado.net>
From: Robert Sparks <rjsparks@estacado.net>
To: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <2CB27E7D-2483-4F81-9129-B0C26FD92208@nokia.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 05 Dec 2008 12:45:13 -0600
References: <32E142FF-7258-48DA-A55F-61D12DA8A52D@nostrum.com> <4165FB23-C6E7-4C89-9599-EA03FC14A040@estacado.net> <da309ff64b204dd78e5c55509b42748d.squirrel@webmail.eisler.com> <2C7FE4DC-82CE-4FF8-9F52-58FB600CDF09@estacado.net> <2CB27E7D-2483-4F81-9129-B0C26FD92208@nokia.com>
X-Mailer: Apple Mail (2.929.2)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "mike@eisler.com" <mike@eisler.com>, "nfsv4-chairs@tools.ietf.org" <nfsv4-chairs@tools.ietf.org>
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

To be clear, I'm asking about the limits on the description and  
contact fields (text for people and email addresses) in this message,  
not the restriction on the netid length.

Do we have, in the creation of other registries, explicit restrictions  
on how long the "who do you contact about this" field can be?

I'm not objecting strongly to the limits on these fields, but I do  
find them odd, and they add work for IANA (who will have to check  
things against those limits), which seems in conflict with your  
comment about not doing any reviewing below?

RjS

On Dec 5, 2008, at 12:54 AM, Lars Eggert wrote:

> On 2008-12-5, at 1:12, Robert Sparks wrote:
>>> 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.
>
> Is there any other registry that potentially names that are this  
> long? And with the first-com-first-served section of the registry,  
> IANA isn't supposed to do any reviewing.
>
> I think the limitation is reasonable and practical.
>
> Lars

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