IETF Logo Mail Archive

Re: [port-srv-reg] status check

Pearl Liang <pearl.liang@icann.org> Tue, 27 April 2010 17:27 UTC

Return-Path: <pearl.liang@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 33FF93A6B58 for <port-srv-reg@core3.amsl.com>; Tue, 27 Apr 2010 10:27:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.998
X-Spam-Level:
X-Spam-Status: No, score=-5.998 tagged_above=-999 required=5 tests=[BAYES_50=0.001, GB_I_LETTER=-2, 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 ClA5FLl+-JuL for <port-srv-reg@core3.amsl.com>; Tue, 27 Apr 2010 10:27:18 -0700 (PDT)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by core3.amsl.com (Postfix) with ESMTP id 2BA9D28C160 for <port-srv-reg@ietf.org>; Tue, 27 Apr 2010 10:26:48 -0700 (PDT)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Tue, 27 Apr 2010 10:26:36 -0700
From: Pearl Liang <pearl.liang@icann.org>
To: Lars Eggert <lars.eggert@nokia.com>, "port-srv-reg@ietf.org" <port-srv-reg@ietf.org>
Date: Tue, 27 Apr 2010 10:27:19 -0700
Thread-Topic: [port-srv-reg] status check
Thread-Index: AcriBOsLLzYnritVQ02lR7VFIgtnogEKfhGH
Message-ID: <C7FC6C87.1D4DD%pearl.liang@icann.org>
In-Reply-To: <00FBD5BD-9B3D-43D1-A1C8-613C4C7CE983@nokia.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C7FC6C871D4DDpearlliangicannorg_"
MIME-Version: 1.0
Subject: Re: [port-srv-reg] status check
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: Tue, 27 Apr 2010 17:27:22 -0000

Hello All,

Apologies in advance if the following issue has been discussed previously.  I just joined this mailing list.

It appears that Section 5.1 re-defines the length of a new Service Name to be within 15 characters long.
The current registry "Protocol And Service Names" (located at http://www.iana.org/assignments/service-names) allows 40 characters for a new service name:

[[[
A protocol or service may be up to 40 characters taken from the set of
uppercase letters, digits, and the punctuation character hyphen.  It
must start with a letter, and end with a letter or digit.
]]]

Question: would it be reasonable to modify the "max" number in the registry so that we would not have a new service name with 20 or more characters long when the port document is published?

Thank you,
~pl


On 4/22/10 3:15 AM, "Lars Eggert" <lars.eggert@nokia.com> wrote:

Hi,

where are we with regards to this document and the issues we identified in Anaheim? The last commit to the svn repository was on 2010-01-11 by Magnus...

Lars

PS: I'm not sure if you've heard that Michelle will be offline for a while due to a health issue. So we'll need to move this forward without her for a bit.

v2.8.7 | Report a Bug | By Email