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

Peter Saint-Andre <stpeter@stpeter.im> Wed, 16 February 2011 04:07 UTC

Return-Path: <stpeter@stpeter.im>
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 9B4543A6CD1; Tue, 15 Feb 2011 20:07:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.559
X-Spam-Level:
X-Spam-Status: No, score=-102.559 tagged_above=-999 required=5 tests=[AWL=0.040, 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 DJhvobNzJ75K; Tue, 15 Feb 2011 20:07:09 -0800 (PST)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id CABAF3A6CB6; Tue, 15 Feb 2011 20:07:09 -0800 (PST)
Received: from squire.local (dsl-251-175.dynamic-dsl.frii.net [216.17.251.175]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 27707400F6; Tue, 15 Feb 2011 21:25:40 -0700 (MST)
Message-ID: <4D5B4D86.3020102@stpeter.im>
Date: Tue, 15 Feb 2011 21:07:34 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
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> <4D413827.7040407@ericsson.com> <B4F0B107-4D84-43A5-A091-B6877D24C23B@cisco.com> <4D46B3B9.4050804@ericsson.com> <755A9333-6960-4BCC-B996-3775E76B5D9E@cisco.com> <4D4920F0.1070204@ericsson.com> <49CDF352-D900-4883-8D67-19172DBC8474@cisco.com> <4D5B4B98.4060704@vpnc.org> <6AA482E6-924C-4981-9E7F-69AD8EE3DD6F@cisco.com>
In-Reply-To: <6AA482E6-924C-4981-9E7F-69AD8EE3DD6F@cisco.com>
X-Enigmail-Version: 1.1.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="------------ms090609060805040009070606"
Cc: IESG IESG <iesg@ietf.org>, Magnus Westerlund <magnus.westerlund@ericsson.com>, IETF discussion list <ietf@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, tsvwg@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: Wed, 16 Feb 2011 04:07:10 -0000

Agreed, thanks to Paul for the proposed text.

On 2/15/11 9:02 PM, Cullen Jennings wrote:
> 
> Paul's text is much better than mine. That was what I trying to get
> at.
> 
> On Feb 15, 2011, at 8:59 PM, Paul Hoffman wrote:
> 
>> On 2/15/11 7:34 PM, Cullen Jennings wrote:
>>> I propose some text for the draft near the bottom of this
>>> email.... For the user ports the document should have some text
>>> along the lines of:
>>> 
>>> There is not IETF consensus on when it is appropriate to use a
>>> second port for a secure version of protocol therefor the export
>>> reviewer should not reject a request for a second port to run a
>>> secure variant of the protocol over.
>> 
>> That feels close, but too prescriptive. Also, the requests are
>> usually for a protocol with two ports, not a later request for a
>> second port. How about:
>> 
>> There is not IETF consensus on when it is appropriate to use a
>> second port for a secure version of protocol. Therefore, an expert
>> reviewer should not reject a proposal for a protocol that uses a
>> second part to run a secure variant for the sole reason that it
>> using two ports.