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

Stuart Cheshire <cheshire@apple.com> Tue, 07 September 2010 23:14 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 A69EA3A6997 for <port-srv-reg@core3.amsl.com>; Tue, 7 Sep 2010 16:14:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.185
X-Spam-Level:
X-Spam-Status: No, score=-104.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, 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 EGGQNs2QspTQ for <port-srv-reg@core3.amsl.com>; Tue, 7 Sep 2010 16:14:12 -0700 (PDT)
Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id D011E3A6973 for <port-srv-reg@ietf.org>; Tue, 7 Sep 2010 16:14:11 -0700 (PDT)
Received: from relay11.apple.com (relay11.apple.com [17.128.113.48]) by mail-out4.apple.com (Postfix) with ESMTP id 0654AADC1B79; Tue, 7 Sep 2010 16:14:40 -0700 (PDT)
X-AuditID: 11807130-b7cf8ae0000058d2-40-4c86c75f69e3
Received: from [17.202.46.71] (chesh1.apple.com [17.202.46.71]) by relay11.apple.com (Apple SCV relay) with SMTP id 57.65.22738.F57C68C4; Tue, 7 Sep 2010 16:14:39 -0700 (PDT)
In-Reply-To: <C8A6942D.282AF%michelle.cotton@icann.org>
References: <C8A6942D.282AF%michelle.cotton@icann.org>
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <E308508D-387D-4550-8960-1F74068B77EB@apple.com>
Content-Transfer-Encoding: 7bit
From: Stuart Cheshire <cheshire@apple.com>
Date: Tue, 7 Sep 2010 16:14:38 -0700
To: Michelle Cotton <michelle.cotton@icann.org>
X-Mailer: Apple Mail (2.753.1)
X-Brightmail-Tracker: AAAAAA==
Cc: "port-srv-reg@ietf.org" <port-srv-reg@ietf.org>
Subject: Re: [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: Tue, 07 Sep 2010 23:14:14 -0000

On 3 Sep, 2010, at 12:01, Michelle Cotton wrote:

> I agree with all the changes below.
> Regarding the last point, can the service name aliases for future  
> registrations go in the notes column?
>
> Michelle


I don't think there will be any future aliases.

I don't see any reason to be allowing further creation of aliases  
that add nothing except being a new name for something else that  
already exists.

If someone says they want to register a new service name "wibble"  
which is in fact identical in all respects to "telnet", using the  
same message formats for the same purpose on the same port, then the  
answer is they're not allowed to do that because it's a bad idea.

It's like someone wanting to register IP protocol number 191 to be a  
new transport protocol identical in all respects to TCP, so that  
clients are now free to use *either* IP protocol number 6 *or* IP  
protocol number 191 to mean "TCP", and all servers have to handle  
both because a client may use either at the client's whim. And if one  
alias, why not ten or twenty different aliases for "TCP"? If someone  
wanted to do that we wouldn't allow them because it's a bad idea that  
serves no purpose.

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