Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry) to BCP

Alexey Melnikov <alexey.melnikov@isode.com> Sat, 12 February 2011 20:03 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F117E3A6A41; Sat, 12 Feb 2011 12:03:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 txdNbcyusqGF; Sat, 12 Feb 2011 12:03:15 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id F3DD83A6AEF; Sat, 12 Feb 2011 12:03:14 -0800 (PST)
Received: from [188.28.20.209] (188.28.20.209.threembb.co.uk [188.28.20.209]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <TVbnjwADL4vp@rufus.isode.com>; Sat, 12 Feb 2011 20:03:30 +0000
Message-ID: <4D56E75A.9070903@isode.com>
Date: Sat, 12 Feb 2011 20:02:34 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry) to BCP
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com> <4D421795.70505@isi.edu> <EFADE5D0-BB33-4418-B743-DFEC11B12740@cisco.com> <4D44F85D.5030407@isi.edu> <4D457FD9.5030905@vpnc.org> <B1E38EDF-E78E-47E2-B9A9-D7320A908217@nokia.com> <4D46CC62.1040006@vpnc.org>
In-Reply-To: <4D46CC62.1040006@vpnc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: Cullen Jennings <fluffy@cisco.com>, IESG IESG <iesg@ietf.org>, tsvwg@ietf.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Feb 2011 20:03:16 -0000

Paul Hoffman wrote:

> On 1/31/11 12:23 AM, Lars Eggert wrote:
>
>> On 2011-1-30, at 17:12, Paul Hoffman wrote:
>>
>>> The above emphatic statements means that IANA can reject a request 
>>> for an IETF-approved protocol that needs two ports without recourse.
>>
>> I don't follow. Assignments through IETF-stream documents do not go
>> through expert review.
>
> Then this should be made *much* clearer in the document.

I believe this was clarified in -10.

> In fact, the document says:
>    A key element of the procedural streamlining specified in this
>    document is to establish identical assignment procedures for all IETF
>    transport protocols.
>
> I assumed that "all" meant "all", not "all except those through 
> IETF-stream documents"; others might have read it the same way I did. 
> Further, the wording throughout the template description in 8.1 makes 
> it sound like that the restrictions in this document apply to 
> everything that needs a template, which clearly includes IETF-stream 
> documents.