Re: [port-srv-reg] "xmp" service type and the unified IANA Service Name and Port Number Registry

Stuart Cheshire <cheshire@apple.com> Tue, 23 August 2011 23:53 UTC

Return-Path: <cheshire@apple.com>
X-Original-To: port-srv-reg@ietfa.amsl.com
Delivered-To: port-srv-reg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AC7D21F8C70 for <port-srv-reg@ietfa.amsl.com>; Tue, 23 Aug 2011 16:53:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.979
X-Spam-Level:
X-Spam-Status: No, score=-105.979 tagged_above=-999 required=5 tests=[AWL=0.620, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wrowcKoVcrBt for <port-srv-reg@ietfa.amsl.com>; Tue, 23 Aug 2011 16:53:47 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id 0044321F8C6F for <port-srv-reg@ietf.org>; Tue, 23 Aug 2011 16:53:46 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: text/plain; CHARSET="US-ASCII"; delsp="yes"; format="flowed"
Received: from relay15.apple.com ([17.128.113.54]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTP id <0LQE00FAQNPRL7J1@mail-out.apple.com> for port-srv-reg@ietf.org; Tue, 23 Aug 2011 16:54:56 -0700 (PDT)
X-AuditID: 11807136-b7c35ae000001055-ef-4e5440ec3275
Received: from [17.193.13.41] (chesh1.apple.com [17.193.13.41]) by relay15.apple.com (Apple SCV relay) with SMTP id 86.8A.04181.CE0445E4; Tue, 23 Aug 2011 17:08:12 -0700 (PDT)
In-reply-to: <4E53BF1F.5040708@krupczak.org>
References: <6BA107CB-7E6F-4720-ABDF-7B0D0733D607@apple.com> <4E53BF1F.5040708@krupczak.org>
Message-id: <9A7A3E75-3F30-4A39-8D35-94D3C2C9381B@apple.com>
From: Stuart Cheshire <cheshire@apple.com>
Date: Tue, 23 Aug 2011 16:54:54 -0700
To: Bobby Krupczak <rdk@krupczak.org>
X-Mailer: Apple Mail (2.753.1)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrILMWRmVeSWpSXmKPExsUieJBXU/eNQ4ifwdSdPBZd34Qstv1ZyubA 5LFkyU8mj0cnJ7IFMEVx2aSk5mSWpRbp2yVwZSzb+Im5YA9nxZe5y9gbGLezdzFyckgImEj8 vTyJFcIWk7hwbz1bFyMXh5DARkaJxsUrmEASnAI6EgsmnWMEsYUEYiRmNM1nBrF5BYwkrk6e CjSIg4NZwEVi4ZQ8iLCNxITPK8DmMwtISpxedRnKlpfY/nYOWCubgJbEi89X2EBsYYEoiS2r ToOtYhFQlViy6BdYXATIXrzlK9RtchKHT79inMDIPwvJ5lkIm2ch2bCAkXkVo2BRak5ipaGp XmJBQU6qXnJ+7iZGUMA1FJrtYNzxV+4QowAHoxIP740LwX5CrIllxZW5hxglOJiVRHi/8oT4 CfGmJFZWpRblxxeV5qQWH2KU5mBREuddeSvIT0ggPbEkNTs1tSC1CCbLxMEp1cAok31hUe28 05wJpReKzlq1aBxPeC++wupBgUriCeEpL9h7zlm57tBYm/wgryj3WLKCg554zMTyYNuH/9/8 812Qr5xyNcnJU7vmRIZT112n7y62x3MriyRML344yTLzVMa8s98/Hzd6efV7uQWv6WE1I7P+ 1SXWN/eLCG33tk64uf9b7flFgtJKLMUZiYZazEXFiQCVtMq6NAIAAA==
Cc: port-srv-reg@ietf.org
Subject: Re: [port-srv-reg] "xmp" service type and the unified IANA Service Name and Port Number Registry
X-BeenThere: port-srv-reg@ietf.org
X-Mailman-Version: 2.1.12
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/options/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, 23 Aug 2011 23:53:48 -0000

On 23 Aug, 2011, at 07:54, Bobby Krupczak wrote:

> The answer is yes I do use both the port and service name in code,  
> APIs, and rely on this registry.

Thank you for your answer.

Can you let us know for what specific purpose(s) you are using the  
"xmp" service name string in your code or on-the-wire protocols?

It seems clear that neither you nor the prior registrant of the "xmp"  
service name string are willing to change to a different name; they  
because as far as they are concerned they registered it first, and  
you because you consider your later registration to be more  
"official". No matter, we can't force either of you to do anything.  
It seems likely that you will both continue to use the same service  
name string, and deal with the resulting operational conflicts.

If you can let us know how you are actually using the "xmp" service  
name string (what APIs, in what on-the-wire protocols, etc.) then we  
can at least document what manner of problems users are likely to  
experience when trying to use "xmp".

Thank you for your help with this.

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