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

Cullen Jennings <fluffy@cisco.com> Wed, 16 February 2011 03:59 UTC

Return-Path: <fluffy@cisco.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 7918A3A6CAB; Tue, 15 Feb 2011 19:59:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.19
X-Spam-Level:
X-Spam-Status: No, score=-110.19 tagged_above=-999 required=5 tests=[AWL=0.409, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 ABHJb3GhKt86; Tue, 15 Feb 2011 19:59:51 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id A8DEC3A6B77; Tue, 15 Feb 2011 19:59:51 -0800 (PST)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAMraWk2rR7Ht/2dsb2JhbAClYnOhWJtkhV4EhQaHAIM2
X-IronPort-AV: E=Sophos;i="4.60,478,1291593600"; d="scan'208";a="260669802"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-4.cisco.com with ESMTP; 16 Feb 2011 04:00:18 +0000
Received: from [192.168.4.2] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p1G40G0G018511; Wed, 16 Feb 2011 04:00:17 GMT
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
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <4D5B4B98.4060704@vpnc.org>
Date: Tue, 15 Feb 2011 21:02:30 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <6AA482E6-924C-4981-9E7F-69AD8EE3DD6F@cisco.com>
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>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1082)
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, tsvwg@ietf.org, IESG IESG <iesg@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 03:59:52 -0000

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.