[port-srv-reg] Four final points for discussion

Stuart Cheshire <cheshire@apple.com> Fri, 03 September 2010 07:16 UTC

Return-Path: <cheshire@apple.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 27B653A6807 for <port-srv-reg@core3.amsl.com>; Fri, 3 Sep 2010 00:16:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.855
X-Spam-Level:
X-Spam-Status: No, score=-105.855 tagged_above=-999 required=5 tests=[AWL=0.744, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 DUTVKzKzAFIe for <port-srv-reg@core3.amsl.com>; Fri, 3 Sep 2010 00:16:05 -0700 (PDT)
Received: from mail-out4.apple.com (mail-out.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id 8F0AC3A67FD for <port-srv-reg@ietf.org>; Fri, 3 Sep 2010 00:16:04 -0700 (PDT)
Received: from relay16.apple.com (relay16.apple.com [17.128.113.55]) by mail-out4.apple.com (Postfix) with ESMTP id 1D29EACF4B15 for <port-srv-reg@ietf.org>; Fri, 3 Sep 2010 00:16:26 -0700 (PDT)
X-AuditID: 11807137-b7b43ae00000547d-80-4c80a0c9f605
Received: from et.apple.com (et.apple.com [17.151.62.12]) by relay16.apple.com (Apple SCV relay) with SMTP id 65.47.21629.9C0A08C4; Fri, 3 Sep 2010 00:16:26 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from [192.168.99.3] (208-106-97-96.dsl.static.sonic.net [208.106.97.96]) by et.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0L850049UTJD85B0@et.apple.com> for port-srv-reg@ietf.org; Fri, 03 Sep 2010 00:16:25 -0700 (PDT)
From: Stuart Cheshire <cheshire@apple.com>
In-reply-to: <6EC7B8A7-C3B3-4E63-85A9-0DC31F4D45B4@nokia.com>
Date: Fri, 03 Sep 2010 00:16:25 -0700
Message-id: <5D2DD7D7-A429-4CFC-BD27-EF09CEF5AE1B@apple.com>
References: <6EC7B8A7-C3B3-4E63-85A9-0DC31F4D45B4@nokia.com>
To: port-srv-reg@ietf.org
X-Mailer: Apple Mail (2.1081)
X-Brightmail-Tracker: AAAAAA==
Subject: [port-srv-reg] Four final points for discussion
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: Fri, 03 Sep 2010 07:16:19 -0000

I have four final points for discussion

1. Name of the Registry

Right now the document calls it:

   Transport Protocol Port Number and Service Name Registry

However, Section 5 says:

   Service names are the unique key in the Port and Service Name registry.

Since Service names really are the primary identifier, and the port number is optional, and we expect to see more and more registrations without port numbers, would it make sense to switch the order of the words, and make it:

   Registry of Service Names and Transport Protocol Port Numbers

2. Service Name Rules

I liked Joe's earlier suggestion to disallow all-numeric service names, to avoid service names that look like a numeric port number. However, even with that rule, we still allow service names like this: "6000-6063" (looks like the X Window System port range). Do we care? We could prevent that by requiring that all service names contain at least one alphabetic character.

3. Inconsistent terminology.

We use the term "Registered Ports" in some places to mean "ports in the range 1024-49151", and in other places to mean any "port recorded by IANA in the Registry".

For example, the first meaning:

          <t>the Well Known Ports, also known as the System Ports, from 0-1023
          (assigned by IANA)</t>

          <t>the Registered Ports, also known as the User Ports, from
          1024-49151 (assigned by IANA)</t>

          <t>the Dynamic Ports, also known as the Private Ports, from
          49152-65535 (never assigned)</t>

and now the second:

      <t>It is important to note that ownership of registered port numbers and
      service names remains with IANA. For protocols developed by IETF working

      Thousands of applications and application-level
      protocols have registered ports and service names for their use, and
      there is every reason to believe that this trend will continue into the
      future.

Would it be better to strictly use the terms "System Ports" and "User Ports" to denote the ranges, and keep the term "registered port" to just mean generically, "recorded by IANA in the Registry"?

4. Aliases

The document says:

      <t>IANA is also instructed to indicate which service name aliases in the
      existing registry are the primary aliases (see <xref target="srvname"/>).</t>

Why should we burden IANA with this decision making? I bet there aren't that many. Let's just work it out ourselves, and list them in the document. I'll grep the IANA ports page and send a followup email with the list of aliased names.

Stuart Cheshire <cheshire@apple.com>
* Wizard Without Portfolio, Apple Inc.
* www.stuartcheshire.org