Re: [port-srv-reg] draft-ietf-tsvwg-iana-ports: status of draft-touch-tsvwg-port-use

Lars Eggert <lars.eggert@nokia.com> Thu, 17 February 2011 15:34 UTC

Return-Path: <lars.eggert@nokia.com>
X-Original-To: port-srv-reg@core3.amsl.com
Delivered-To: port-srv-reg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2DDE63A6E49 for <port-srv-reg@core3.amsl.com>; Thu, 17 Feb 2011 07:34:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.697
X-Spam-Level:
X-Spam-Status: No, score=-102.697 tagged_above=-999 required=5 tests=[AWL=-0.098, 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 niiu1JCTfbJU for <port-srv-reg@core3.amsl.com>; Thu, 17 Feb 2011 07:34:32 -0800 (PST)
Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by core3.amsl.com (Postfix) with ESMTP id 507173A6E36 for <port-srv-reg@ietf.org>; Thu, 17 Feb 2011 07:34:32 -0800 (PST)
Received: from mail.fit.nokia.com (esdhcp030222.research.nokia.com [172.21.30.222]) by mgw-da02.nokia.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p1HFZ1LO015080 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Feb 2011 17:35:02 +0200
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.96.5 at fit.nokia.com
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/signed; boundary="Apple-Mail-78--325368358"; protocol="application/pkcs7-signature"; micalg="sha1"
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <4D5D38F3.7040106@isi.edu>
Date: Thu, 17 Feb 2011 17:34:55 +0200
Message-Id: <A05700FF-7F5D-413D-8764-686D6BDB58DE@nokia.com>
References: <4D5D28CB.8080604@isode.com> <4D5D38F3.7040106@isi.edu>
To: Joe Touch <touch@isi.edu>
X-Mailer: Apple Mail (2.1082)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (mail.fit.nokia.com); Thu, 17 Feb 2011 17:34:55 +0200 (EET)
X-Nokia-AV: Clean
Cc: "port-srv-reg@ietf.org" <port-srv-reg@ietf.org>
Subject: Re: [port-srv-reg] draft-ietf-tsvwg-iana-ports: status of draft-touch-tsvwg-port-use
X-BeenThere: port-srv-reg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of updates to service name and transport protocol port registry <port-srv-reg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/port-srv-reg>, <mailto:port-srv-reg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/port-srv-reg>
List-Post: <mailto:port-srv-reg@ietf.org>
List-Help: <mailto:port-srv-reg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/port-srv-reg>, <mailto:port-srv-reg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Feb 2011 15:34:33 -0000

Hi,

so I'm getting confused by the flood of email. But I think there is a serious disconnect here in the community:

The purpose of iana-ports is to define the IANA procedures for managing the consolidated service-name/port-number registry. It is *not* a "handbook to the public on all things to know about ports assignments."

Yes, the document includes some material that is for the information of applicants. I think the basic idea was that we wanted to explain *why* the IANA procedures are the way they are. But that material is not covering everything, nor should (or could) it.

Especially for the assignment path via Expert Review, people seem to want us to add a lot of details about what principles the expert team is using, how they communicate with the applicant, etc.

I don't think this document is the right place for this content. I'm not even sure that we need any document with this content - I don't think there is any other IANA expert whose review process are prescribed by an RFC.

Are we all on the same page here? If yes, we should push back. (And if no, we should discuss what to do.)

Lars