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

Stuart Cheshire <cheshire@apple.com> Tue, 21 September 2010 04:08 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 44A063A691C for <port-srv-reg@core3.amsl.com>; Mon, 20 Sep 2010 21:08:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.485
X-Spam-Level:
X-Spam-Status: No, score=-106.485 tagged_above=-999 required=5 tests=[AWL=0.114, 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 S0M8CMOPts9E for <port-srv-reg@core3.amsl.com>; Mon, 20 Sep 2010 21:08:35 -0700 (PDT)
Received: from mail-out3.apple.com (mail-out.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id 4444D3A6922 for <port-srv-reg@ietf.org>; Mon, 20 Sep 2010 21:08:32 -0700 (PDT)
Received: from relay11.apple.com (relay11.apple.com [17.128.113.48]) by mail-out3.apple.com (Postfix) with ESMTP id 0F3D5AA11670; Mon, 20 Sep 2010 21:08:56 -0700 (PDT)
X-AuditID: 11807130-b7cf8ae0000058d2-98-4c982fd7a1e4
Received: from [17.202.46.71] (chesh1.apple.com [17.202.46.71]) by relay11.apple.com (Apple SCV relay) with SMTP id 09.C7.22738.8DF289C4; Mon, 20 Sep 2010 21:08:56 -0700 (PDT)
In-Reply-To: <4C924978.4010602@isi.edu>
References: <C8A6942D.282AF%michelle.cotton@icann.org> <E308508D-387D-4550-8960-1F74068B77EB@apple.com> <4C87B342.3040508@isi.edu> <4C91DF48.5010009@ericsson.com> <4C924978.4010602@isi.edu>
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <3DF309EA-4D18-4D5D-BBF0-9665719BE901@apple.com>
Content-Transfer-Encoding: 7bit
From: Stuart Cheshire <cheshire@apple.com>
Date: Mon, 20 Sep 2010 21:08:28 -0700
To: Joe Touch <touch@isi.edu>
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, 21 Sep 2010 04:08:36 -0000

On 16 Sep, 2010, at 09:44, Joe Touch wrote:

> Any time more than one string maps to the same port number it's a  
> kind of an 'alias'. The only way for the client to know the  
> difference is via in-band information.
>
> I.e., we would allow aliases for:
> 	- different services
> 	- that can be resolved in-band
>
> Unless BOTH of those apply, we would not allow aliases except:
>
> 	a) legacy (www, http)
> 	b) to support changeover to the new namespace
>
> Joe


I think we agree on the concept, but the terminology previously  
confused me.

When you said, "alias," I read that as meaning, "different names for  
the same service."

Now I see that when you say, "alias," you mean, "different services  
on the same port." (I'd call that a "collision", except in the  
special case of a new service which is a compatible extension to an  
old one on the same port.)

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