[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 04:37 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 1FFC821F8B52 for <port-srv-reg@ietfa.amsl.com>; Mon, 22 Aug 2011 21:37:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[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 afqS-iWbYYS9 for <port-srv-reg@ietfa.amsl.com>; Mon, 22 Aug 2011 21:37:29 -0700 (PDT)
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id 6BE4421F8B58 for <port-srv-reg@ietf.org>; Mon, 22 Aug 2011 21:37:29 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: text/plain; CHARSET="US-ASCII"
Received: from relay13.apple.com ([17.128.113.29]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LQD004XW68C4TK1@mail-out.apple.com> for port-srv-reg@ietf.org; Mon, 22 Aug 2011 21:38:36 -0700 (PDT)
X-AuditID: 1180711d-b7c5fae000001427-72-4e532e4dd557
Received: from koseret (koseret.apple.com [17.151.62.39]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate) by relay13.apple.com (Apple SCV relay) with SMTP id 6B.E0.05159.D4E235E4; Mon, 22 Aug 2011 21:36:29 -0700 (PDT)
Received: from [10.0.1.15] (173-164-252-149-SFBA.hfc.comcastbusiness.net [173.164.252.149]) by koseret.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LQD00IIG687PWA0@koseret.apple.com> for port-srv-reg@ietf.org; Mon, 22 Aug 2011 21:38:32 -0700 (PDT)
From: Stuart Cheshire <cheshire@apple.com>
Date: Mon, 22 Aug 2011 21:38:31 -0700
Message-id: <6BA107CB-7E6F-4720-ABDF-7B0D0733D607@apple.com>
To: Bobby Krupczak <rdk@krupczak.org>
X-Mailer: Apple Mail (2.1084)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupiluLIzCtJLcpLzFFi42IRnG6nruurF+xnsGO1vkXXNyEHRo8lS34y BTBGcdmkpOZklqUW6dslcGVMf9TPXNAmWvFh6XfGBsbDgl2MnBwSAiYSayZeZ4awxSQu3FvP 1sXIxSEk0MkksW17AytIgldAUOLH5HssXYwcHMwC8hIHz8uChJkFtCS+P2plgag/xiQx4flp JpAEG1DixecrbCD1wgIREh/nO4GEWQRUJd5fWwQ10kZiz65OFog5khKnV11mB7FFgGoWb/nK CtIqISAr0bQsYwIj3ywkR8xCOGIWkiMWMDKvYhQsSs1JrDQ01kssKMhJ1UvOz93ECAqhhkLZ HYz7f/IfYhTgYFTi4f11IMhPiDWxrLgy9xCjBAezkgjvwjtAId6UxMqq1KL8+KLSnNTiQ4zS HCxK4rwy14FSAumJJanZqakFqUUwWSYOTqkGxq5TLa+KmCbraH8tYlglf7bkaqvElBOBL8Le T6u03RTSLuB9OUSiaYqAY7PeR5tD8WfqrWfr7PrHu2GW1ItP0xnaAxxCI1lvrri/dOchX45b ZaeP583S3PLyWX72qrOvburs362UcmLZSrMpVzdzutz/O0WpbFXM8hbm3Rp32+9YWizs61u1 oUyJpTgj0VCLuag4EQBDF5WQHQIAAA==
Cc: port-srv-reg@ietf.org
Subject: [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 04:37:30 -0000

Bobby, I'm writing in reference to your service type registration for "xmp" (port 5270).

We recently merged the volunteer-run dns-sd.org registry and the official IANA "port numbers" registry, to make a new combined "Service Name and Port Number Registry". For more information, see:

<http://tools.ietf.org/html/draft-ietf-tsvwg-iana-ports>

Although combining the two registries is overall a great move, unfortunately in the process we discovered that there were three names which got registered differently in the two separate lists, one of which is "xmp".

Prior to your port registration, the "xmp" service name had already been registered in the dns-sd.org registry, for use with DNS-SD (aka "Bonjour") and similar name-based service-discovery mechanisms.

We've contacted the prior dns-sd.org registrant, and they inform us that the "xmp" service name has been in widespread commercial use in their software for many years, and continues to be used in their current products.

The implication of this is that if you were to use the "xmp" service name with DNS-SD (aka "Bonjour"), DNS SRV records, or similar name-based service-discovery mechanisms, then you would get inadvertent conflicts with their use of the name. Your clients would inadvertently discover instances of the other "xmp" service, which your clients don't know anything about, and clients of the other "xmp" service would inadvertently discover instances of your service, which they wouldn't know how to use. Of course this would be confusing and unhelpful for users.

This conflict does not affect your registered port 5270, only the name "xmp".

It is our hope that your software uses your registered port 5270 explicitly, and for you the "xmp" name was merely a mnemonic for human convenience, not actually used by your software for Bonjour service discovery or similar purposes. If this is the case then changing the name to something else (say "Cartographer", or "CartographerXMP"), would not cause any on-the-wire interoperability problems, and this inadvertent name collision can be resolved amicably.

If your software is using the "xmp" service name string (e.g. for Bonjour or similar on-the-wire service discovery protocols), then please let us know as soon as possible, and we'll try to work out a way forward that minimises disruption to all parties.

Ideally, if your software is not using the "xmp" service name string in APIs, protocols, or for service discovery, then we can simply change the mnemonic string for port 5270 without causing undue hardship for anyone involved.

Please let us know.

Thanks in advance.

Stuart Cheshire, on behalf of the IANA port-srv-reg team.