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

Sam Hartman <hartmans-ietf@mit.edu> Wed, 16 February 2011 12:13 UTC

Return-Path: <hartmans@mit.edu>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EC61A3A6E3D; Wed, 16 Feb 2011 04:13:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.614
X-Spam-Level:
X-Spam-Status: No, score=-102.614 tagged_above=-999 required=5 tests=[AWL=-0.349, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, 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 NlAeAmTvmxnl; Wed, 16 Feb 2011 04:13:43 -0800 (PST)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by core3.amsl.com (Postfix) with ESMTP id 3F57D3A6B74; Wed, 16 Feb 2011 04:13:43 -0800 (PST)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 59812202FB; Wed, 16 Feb 2011 07:11:54 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 2410A4307; Wed, 16 Feb 2011 07:13:51 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
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> <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com> <4D421795.70505@isi.edu> <tslbp2vh8ig.fsf@mit.edu> <Pine.LNX.4.64.1102071321290.4671@adax.adax> <CEBCE3CF81D2D441B14B84256C3C46810BD95BD8@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com> <2803F25F-A2BE-46E3-8284-A256A9B9D415@cisco.com>
Date: Wed, 16 Feb 2011 07:13:51 -0500
In-Reply-To: <2803F25F-A2BE-46E3-8284-A256A9B9D415@cisco.com> (Cullen Jennings's message of "Tue, 15 Feb 2011 21:31:29 -0700")
Message-ID: <tslmxlwqirk.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, IESG IESG <iesg@ietf.org>, Christian Huitema <huitema@microsoft.com>, Sam Hartman <hartmans-ietf@mit.edu>, IETF discussion list <ietf@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 12:13:44 -0000

Cullen, there's a lot of history with port registrations.  As you're
probably aware in the past, there was a procedure for experts to sign an
NDA before reviewing port requests.  It's my understanding that is no
longer done.  However, it does suggest there's strong desire for
proprietary protocol support.
So, there's lots of complexity specific to this registry here that I
don't know about.

However, the general idea of having experts reviews on a public list, or
even soliciting comments on a public list is well supported. There's
specific discussion of this in RFC 5226. We've done it successfully in a
number of cases.  So, there's reason to believe that things in this
space could be effective for IANA registries.  I think soliciting public
comments on port requests would be bad; I think your proposal of having
the request/response be published would be as far as we should go for
this registry at this time.

So, I don't have the background to say this would be a good fit for the
port registry, but to the extent that my background supports something
like this I can support your idea. It's worked elsewhere at lesat.