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

Stuart Cheshire <cheshire@apple.com> Fri, 19 August 2011 23:09 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 2268521F8862 for <port-srv-reg@ietfa.amsl.com>; Fri, 19 Aug 2011 16:09:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.359
X-Spam-Level:
X-Spam-Status: No, score=-105.359 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_LWSHORTT=1.24, 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 cvcZ+tICXG4K for <port-srv-reg@ietfa.amsl.com>; Fri, 19 Aug 2011 16:09:53 -0700 (PDT)
Received: from mail-out.apple.com (honeycrisp.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id 7A63121F884C for <port-srv-reg@ietf.org>; Fri, 19 Aug 2011 16:09:53 -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 <0LQ70004T702MY20@mail-out.apple.com> for port-srv-reg@ietf.org; Fri, 19 Aug 2011 16:10:43 -0700 (PDT)
X-AuditID: 11807136-b7c35ae000001055-5f-4e4ef060eeff
Received: from [17.193.13.41] (chesh1.apple.com [17.193.13.41]) by relay15.apple.com (Apple SCV relay) with SMTP id C2.5B.04181.060FE4E4; Fri, 19 Aug 2011 16:23:12 -0700 (PDT)
In-reply-to: <CADk6zomrV+hToAOEc9mxdBfJrr67=xP=Fdfg8j04EeLYSE3U1g@mail.gmail.com>
References: <A699AE70-0165-4C9C-A429-1FB1C0DA13E6@apple.com> <CADk6zomrV+hToAOEc9mxdBfJrr67=xP=Fdfg8j04EeLYSE3U1g@mail.gmail.com>
Message-id: <B90CD5C6-0D50-4761-B4DB-B6BAE7FE050D@apple.com>
From: Stuart Cheshire <cheshire@apple.com>
Date: Fri, 19 Aug 2011 16:09:59 -0700
To: "Daniel G. Taylor" <dan@programmer-art.org>
X-Mailer: Apple Mail (2.753.1)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrALMWRmVeSWpSXmKPExsUieJBXUzfhg5+fwcsJWhYfX0ZZdH0TcmDy WLLkJ5PHjfWL2QKYorhsUlJzMstSi/TtErgy/t7lLnjNW3HtwQPWBsZfXF2MnBwSAiYSB9/u ZIKwxSQu3FvP1sXIxSEksJFR4uzGFmaQBKdAoMTUs/NYIRKNjBJrDj1nAUnwChhJXJ08lb2L kYODWcBFYuGUPIiwjcSTSRvYQGxmAUmJ06sus0PY8hLb384Bm8kmoCXx4vMVsBphgViJya07 wGwWAVWJax3/wWpEBHQlJm7byw5xnJzE4dOvGCcw8s9CsnkWwuZZSDYsYGRexShYlJqTWGlo qpdYUJCTqpecn7uJERRuDYVmOxh3/JU7xCjAwajEw/twop+fEGtiWXFl7iFGCQ5mJRHevs1A Id6UxMqq1KL8+KLSnNTiQ4zSHCxK4rwrDvv6CQmkJ5akZqemFqQWwWSZODilGhhzD706dGaF gcq7100Xst+uEXf8J+dis3/dH0b7txt8Piw4GTj19NO9LC4O3O/OFyVOuf/ja9tduftzPbwP c4U9DrL6uOLncS+FOYxpX2dp8Gn8U3200vqC5mS3OX7HtaY9jlwmqPI6aFv2t8slOQ02ekyF tbpTmVZNFZpQl+3QnrkgR+r8aZ5eJZbijERDLeai4kQAe6L/7DMCAAA=
Cc: port-srv-reg@ietf.org
Subject: Re: [port-srv-reg] "recipe" 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: Fri, 19 Aug 2011 23:09:54 -0000

On 18 Aug, 2011, at 06:31, Daniel G. Taylor wrote:

> Stuart,
>
> Thanks for contacting me. The recipe DNS-SD moniker is in use in an
> active open source project, but due to still being under active
> development and not having yet been packaged for various distributions
> or operating systems it should be fairly trivial to change with little
> to no fallout. The protocol itself is also still a draft, having only
> one active implementation in the wild so it should be fairly easy to
> update.
>
> Do you have a suggested alternative to use and a timeframe in which it
> should be applied?
>
> Take care,
> Daniel

This is excellent news, since it lets us resolve this inadvertent  
name collision amicably. Thanks for your help with this.

I would suggest using the service name "Recipe-Sharing", which fits  
within the 15-character limit. We will record it as such, or if you  
prefer something else, let us know.

The timeframe for making this change in your code is "as soon as  
reasonably convenient for your code".

In the short term, using "recipe" is not going to make the sky fall,  
but continuing to use it longer term could invite complaints of,  
"Hey, you're using our name." Potentially your clients could  
inadvertently discover instances of the other "recipe" service, which  
your clients don't know anything about, and clients of the other  
"recipe" service could inadvertently discover instances of your  
service, which they wouldn't know how to use. Of course this would be  
confusing and unhelpful for users.

Thanks again for your help, and feel free to ask me if you have any  
questions.

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