Re: [mdnsext] Discussion of BoF during Berlin IETF

peter van der Stok <stokcons@xs4all.nl> Mon, 03 June 2013 13:44 UTC

Return-Path: <stokcons@xs4all.nl>
X-Original-To: mdnsext@ietfa.amsl.com
Delivered-To: mdnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1AFB21F9952 for <mdnsext@ietfa.amsl.com>; Mon, 3 Jun 2013 06:44:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.154
X-Spam-Level:
X-Spam-Status: No, score=-0.154 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HELO_EQ_FR=0.35, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, HTML_MESSAGE=0.001]
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 An3L11evgZKi for <mdnsext@ietfa.amsl.com>; Mon, 3 Jun 2013 06:44:31 -0700 (PDT)
Received: from smtp-vbr19.xs4all.nl (smtp-vbr19.xs4all.nl [194.109.24.39]) by ietfa.amsl.com (Postfix) with ESMTP id 3C7A021F9811 for <mdnsext@ietf.org>; Mon, 3 Jun 2013 06:44:30 -0700 (PDT)
Received: from roundcube.xs4all.nl (roundcube7.xs4all.net [194.109.20.205]) by smtp-vbr19.xs4all.nl (8.13.8/8.13.8) with ESMTP id r53DiK5s085842; Mon, 3 Jun 2013 15:44:20 +0200 (CEST) (envelope-from stokcons@xs4all.nl)
Received: from AMontpellier-654-1-76-97.w90-0.abo.wanadoo.fr ([90.0.171.97]) by roundcube.xs4all.nl with HTTP (HTTP/1.1 POST); Mon, 03 Jun 2013 15:44:19 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_1bf89b030b61509cc133cbd129a8c7e7"
Date: Mon, 03 Jun 2013 15:44:19 +0200
From: peter van der Stok <stokcons@xs4all.nl>
To: mdnsext@ietf.org, kerry lynn <kerlyn2001@gmail.com>
Organization: vanderstok consultancy
Mail-Reply-To: <consultancy@vanderstok.org>
In-Reply-To: <CABOxzu3TCqL5JXi+UMSA66oRuzo5uWYUaDp-bQbmz-eaOxbG1w@mail.gmail.com>
References: <BD87928F6BFAEF4EBEB883E1C4F58772342AC64A@PACDCEXMB01.cable.comcast.com> <3f9e642cbdc6f8bb1a996f786bc61b09@xs4all.nl> <CABOxzu3TCqL5JXi+UMSA66oRuzo5uWYUaDp-bQbmz-eaOxbG1w@mail.gmail.com>
Message-ID: <ffa6d0272910ea3f884219a5c954a32a@xs4all.nl>
X-Sender: stokcons@xs4all.nl (3NpoYe7FLKjxuagD16cRMHmirCGEWnbX)
User-Agent: XS4ALL Webmail
X-Virus-Scanned: by XS4ALL Virus Scanner
Subject: Re: [mdnsext] Discussion of BoF during Berlin IETF
X-BeenThere: mdnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: consultancy@vanderstok.org
List-Id: "Discussion of extensions to Bonjour \(mDNS and DNS-SD\) for routed networks." <mdnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mdnsext>, <mailto:mdnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mdnsext>
List-Post: <mailto:mdnsext@ietf.org>
List-Help: <mailto:mdnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mdnsext>, <mailto:mdnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jun 2013 13:44:37 -0000

 

Hi Kerry,

reacting to:

> under DNS-SD/mDNS the user has always had
the option of choosing

> a meaningful <Instance> label for a given
service. If the scope in

> which this label must

> be unique is too
large, the task of name conflict resolution becomes

> more complex.


<Instance> being unique within the autonomous network and
<Instance>.example.com being globally unique is enough for me.


Reacting to:

>I've been thinking 
along the lines of a user-visible
"alias" for domain names, e.g. "foo.local." might be 
made to appear in
a SD browser as "Living Room". 

or even may look like: "foo.".

Peter