Re: [port-srv-reg] Making progress

Joe Touch <touch@isi.edu> Tue, 07 September 2010 22:10 UTC

Return-Path: <touch@isi.edu>
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 48D7D3A6973 for <port-srv-reg@core3.amsl.com>; Tue, 7 Sep 2010 15:10:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.658
X-Spam-Level:
X-Spam-Status: No, score=-102.658 tagged_above=-999 required=5 tests=[AWL=-0.059, 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 l9pglStHdNhz for <port-srv-reg@core3.amsl.com>; Tue, 7 Sep 2010 15:10:34 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 389763A6862 for <port-srv-reg@ietf.org>; Tue, 7 Sep 2010 15:10:32 -0700 (PDT)
Received: from [75.217.170.146] (146.sub-75-217-170.myvzw.com [75.217.170.146]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id o87M9Wav005309 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 7 Sep 2010 15:09:43 -0700 (PDT)
Message-ID: <4C86B81E.3080808@isi.edu>
Date: Tue, 07 Sep 2010 15:09:34 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Mark Mcfadden <mark.mcfadden@icann.org>
References: <05B243F724B2284986522B6ACD0504D7D341083169@EXVPMBX100-1.exc.icann.org>, <4C86A82C.3020205@isi.edu> <05B243F724B2284986522B6ACD0504D7D34108316A@EXVPMBX100-1.exc.icann.org>
In-Reply-To: <05B243F724B2284986522B6ACD0504D7D34108316A@EXVPMBX100-1.exc.icann.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "port-srv-reg@ietf.org" <port-srv-reg@ietf.org>
Subject: Re: [port-srv-reg] Making progress
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, 07 Sep 2010 22:10:42 -0000

On 9/7/2010 2:07 PM, Mark Mcfadden wrote:
> It wasn't my suggestion, but I believe that it is useful to avoid potential confusion in names.
>
> this-svc    and
> this--svc
>
> would be easy to confuse.  I don't think that it (consecutive hyphens) is a necessary syntax feature.

The issue only arises when there are multiple names with hyphens in the 
same place, and that can be avoided by IANA during registration.

My concern is placing too many syntactical restrictions on the names. 
The only current restrictions are:

	- not all numeric
	(so a name is recognizable as such, rather than possibly being
	the port number it refers to)

	- no leading or trailing hyphen
	(not sure why this is required; it doesn't seem to mess with
	either the DNS or anything else, AFAICT)

I would favor less restrictions, rather than more.

Joe


 > ________________________________________
> From: Joe Touch [touch@isi.edu]
> Sent: Tuesday, September 07, 2010 4:01 PM
> To: Mark Mcfadden
> Cc: Stuart Cheshire; port-srv-reg@ietf.org
> Subject: Re: Making progress
>
> Only one point...
>
> - I don't see why we care about consecutive hyphens; prohibiting that
> should be dropped
>
> Joe
>
>
> On 9/7/2010 1:51 PM, Mark Mcfadden wrote:
>> The most recent version in the repository has the changes suggested by Michelle and Pearl.  The attachment has the before and after language.  Of course, a simple diff is also going to provide you with a view of the small changes that were made.  They were:
>>
>> - clarity in the introduction about the authority for registering port numbers and service names;
>> - the need to prohibit multiple consecutive hyphens in the service name; and,
>> - consistency of the contact and registration language in Section 8.
>>
>> mark
>>
>> Mark McFadden
>> mark.mcfadden@icann.org
>> IANA Resource Specialist