[port-srv-reg] Updates on document, registry and Meeting in Anaheim

Michelle Cotton <michelle.cotton@icann.org> Thu, 04 February 2010 22:33 UTC

Return-Path: <michelle.cotton@icann.org>
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 A1C0F3A6DB2 for <port-srv-reg@core3.amsl.com>; Thu, 4 Feb 2010 14:33:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.443
X-Spam-Level:
X-Spam-Status: No, score=-6.443 tagged_above=-999 required=5 tests=[AWL=0.155, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 LPSCnIY1udGc for <port-srv-reg@core3.amsl.com>; Thu, 4 Feb 2010 14:33:26 -0800 (PST)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by core3.amsl.com (Postfix) with ESMTP id 08CAA3A67EF for <port-srv-reg@ietf.org>; Thu, 4 Feb 2010 14:33:26 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Thu, 4 Feb 2010 14:34:13 -0800
From: Michelle Cotton <michelle.cotton@icann.org>
To: "port-srv-reg@ietf.org" <port-srv-reg@ietf.org>
Date: Thu, 4 Feb 2010 14:37:54 -0800
Thread-Topic: Updates on document, registry and Meeting in Anaheim
Thread-Index: Acql6rDDyEWS40vZhEGa9NqpCvd7jw==
Message-ID: <C7908C42.203B0%michelle.cotton@icann.org>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C7908C42203B0michellecottonicannorg_"
MIME-Version: 1.0
Subject: [port-srv-reg] Updates on document, registry and Meeting in Anaheim
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, 04 Feb 2010 22:33:31 -0000

Ports Group:

I'm writing this message to check with everyone to see where we are at.

Status of the Document?
Version 04 was uploaded on 1/11/10
Michelle sent a message to TSVWG Working Group, DNSOPS Working Group and APPS AREA Working Group asking for feedback on version 04
(I'm not sure which message didn't get through due to needing moderator approval - perhaps you can tell me if you saw them go by)
We did receive comments back from Tom Petch (see below).  These are the only comments I received.

***

You said that feedback would be appreciated:-)

I have a problem with this I-D in that it would appear to make no
distinction between allocation and assignment, and would seem to
include registration in the mix as well, at least at times, while hinting that
whatever these may be, ownership is something else.  In the limited context of
transport
identifiers, this may not cause confusion but in closely allied registries,
allocation and assignment are fundamentally different processes and those who
interchange the two are confused and cause confusion.

If, as I suspect, you are using the terms interchangeably, then at the very
least you need a terminology section as 1.1 to say that the two (or three) terms
are used interchangeably, but for myself, I would regard this as inadequate.
Really, you should choose one and eliminate the other(s) with a brief note to
say that
historically, both were used but as of now, a........ is the correct term.

More fundamentally, this I-D is largely about a bureaucratic process without
stating clearly, IMO, what the point of this process is, except to generate
bureaucracy (and confusion over this would appear to have triggered some
discussion recently on the tsvwg list).  The I-D should state up front, not hint
at it in section 7, just why this bureaucracy should exist, of what benefit it
would be bureaucracy is to the IETF etc.  The I-D argues for improving the
bureacracy, not for why it should exist.

Tom Petch

***

When are we going to WG Last Call the document?
Are there still unresolved issues?  If so what are they and do we have a plan to make decisions.

Status of the revised registry?
The revised Ports and Service Names registry will be ready to review very soon.  I need some text from Stuart before completing our recent revisions.

Meeting in Anaheim?
It appears we need to have another lunch meeting on either Tuesday or Thursday of the IETF meeting.  I will set up a doodle calendar to find the best day.
Some additional Area Directors will be joining us to discuss some related issues (Lars can provide more information)

Thanks,

Michelle