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> Wed, 16 February 2011 11:11 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 903623A6DF8; Wed, 16 Feb 2011 03:11:48 -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=[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 BwfkcyQkyw7z; Wed, 16 Feb 2011 03:11:42 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 97F153A6E05; Wed, 16 Feb 2011 03:11:41 -0800 (PST)
Received: from [188.28.83.64] (188.28.83.64.threembb.co.uk [188.28.83.64]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <TVuxAwADL2Lh@rufus.isode.com>; Wed, 16 Feb 2011 11:12:06 +0000
Message-ID: <4D5BB0E8.5000503@isode.com>
Date: Wed, 16 Feb 2011 11:11:36 +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: Peter Saint-Andre <stpeter@stpeter.im>, 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> <4D5B4D86.3020102@stpeter.im>
In-Reply-To: <4D5B4D86.3020102@stpeter.im>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, Paul Hoffman <paul.hoffman@vpnc.org>, 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: Wed, 16 Feb 2011 11:11:48 -0000

Peter Saint-Andre wrote:

>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.
>>    
>>
Agreed, I will add this as an RFC Editor's note.

>>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
>>>is using two ports.
>>>      
>>>