Re: [mdnsext] Hierarchical (host) domain names in mDNS?

Kerry Lynn <kerlyn@ieee.org> Wed, 17 July 2013 14:13 UTC

Return-Path: <kerlyn2001@gmail.com>
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 B05EC21F9A1E for <mdnsext@ietfa.amsl.com>; Wed, 17 Jul 2013 07:13:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-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 8onKkNEZQ0xZ for <mdnsext@ietfa.amsl.com>; Wed, 17 Jul 2013 07:13:28 -0700 (PDT)
Received: from mail-oa0-x22c.google.com (mail-oa0-x22c.google.com [IPv6:2607:f8b0:4003:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id D092B21F99D7 for <mdnsext@ietf.org>; Wed, 17 Jul 2013 07:13:27 -0700 (PDT)
Received: by mail-oa0-f44.google.com with SMTP id l10so2598452oag.31 for <mdnsext@ietf.org>; Wed, 17 Jul 2013 07:13:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=mys+KAIrKY4C8eDTVmY6+UxYnkTovA1kchzNAn8MWhY=; b=H5A8eAPa5oeDeQLx8gsOen37q6I0rM7fINItb6kBTgLxZxDYcizWMKjCpEXufQlX5n KWeBvGEHFK0+QkVbX9vZ1JAb7lrTMdEZ2503/Mq/VvzPU00idh1T4DKw4Q6JXSVmt+Zv TmEBjpTyekGR72pOE1aZBIg4HBuDi5PQBwFO8EJWTlTrpKcJ6RcqvumFcYQPOkofl5VW 5HKUMJZgxXk0ZZyZmeVfF48pGDc6ozcJIpBAAu8xFCMTHwhYLHoGqTTzuivDf+BBQ+f7 GAIxu35e9zSGCbHFMXXIAmNMIAovn1YTppbz/4Ym8/JAzcCV+bhepi2b8I7xeoZceFRl M3Hg==
MIME-Version: 1.0
X-Received: by 10.60.144.69 with SMTP id sk5mr8674861oeb.0.1374070407320; Wed, 17 Jul 2013 07:13:27 -0700 (PDT)
Sender: kerlyn2001@gmail.com
Received: by 10.60.94.239 with HTTP; Wed, 17 Jul 2013 07:13:27 -0700 (PDT)
In-Reply-To: <E36F274013087B4EA05E08EB5037503902C2BA@DEFTHW99EK5MSX.ww902.siemens.net>
References: <E36F274013087B4EA05E08EB5037503902C1DC@DEFTHW99EK5MSX.ww902.siemens.net> <CABOxzu27u5BMTZq2WKFk5O4nmLG87BXCdG6+M7+MeB-ZugDN9Q@mail.gmail.com> <20130716151444.GE23286@mx1.yitter.info> <E36F274013087B4EA05E08EB5037503902C2BA@DEFTHW99EK5MSX.ww902.siemens.net>
Date: Wed, 17 Jul 2013 10:13:27 -0400
X-Google-Sender-Auth: JniDEz8nrS43sjfEx5YGHqrOQRw
Message-ID: <CABOxzu2gWyNnbWTHS5D3hCodVeBFuqVkXk8CX4p0Y5DJMF8qiA@mail.gmail.com>
From: Kerry Lynn <kerlyn@ieee.org>
To: "Albrecht, Harald" <harald.albrecht@siemens.com>
Content-Type: multipart/alternative; boundary=047d7b3a7f80865d6404e1b5b287
Cc: mdnsext@ietf.org
Subject: Re: [mdnsext] Hierarchical (host) domain names in mDNS?
X-BeenThere: mdnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Wed, 17 Jul 2013 14:13:28 -0000

On Wed, Jul 17, 2013 at 3:13 AM, Albrecht, Harald <
harald.albrecht@siemens.com> wrote:

> Thanks for the reply,
>
> control over the software stack is right down to one of the problems:
> there is not a single software stack, there are multiple ones, so while we
> may have control over some of our own stacks, we won't have over the ones
> already out in the wild and which we want to interoperate with. Maybe a
> change would be possible, but my view is that this would first need
> consensus (where exactly? here in this group?) and in the "worst cast" an
> update to the RFC. Would this be a feasible approach at all?
>
> Harald,

As I said previously, if your application provides a qualified domain name
ending in
".local" or ".local." then what you propose should work fine with an
mDNS-aware
resolver.  It is the TLD ".local" that triggers the behavior to multicast
the request to
port 5353.  What an mDNS-aware resolver won't do is to append ".local" to a
multi-
label host name if your application omits it.

IMO, this does not constitute "full control of the stack", nor is an update
to RFC 6762
required.  This is not a difficult experiment to set up; I have tried it
with OS X and
Ubuntu LTS.  You can ensure it works on Windows by installing Bonjour for
Windows.

-K-


> With best regards,
> Harald Albrecht
>
> Siemens AG
> Industry Sector
> Industry Automation Division
> Industrial Automation Systems
> I IA AS CTO DH 1
> Gleiwitzer Str. 555
> 90475 Nürnberg, Deutschland
> Tel: +49 911 895-3847
> Fax: +49 911 895-2105
> mailto:harald.albrecht@siemens.com
>
> Siemens Aktiengesellschaft: Vorsitzender des Aufsichtsrats: Gerhard
> Cromme; Vorstand: Peter Löscher, Vorsitzender; Roland Busch, Brigitte
> Ederer, Klaus Helmrich, Joe Kaeser, Barbara Kux, Hermann Requardt,
> Siegfried Russwurm, Peter Y. Solmssen, Michael Süß; Sitz der Gesellschaft:
> Berlin und München, Deutschland; Registergericht: Berlin Charlottenburg,
> HRB 12300, München, HRB 6684; WEEE-Reg.-Nr. DE 23691322
>
>
>
> > -----Ursprüngliche Nachricht-----
> > Von: mdnsext-bounces@ietf.org [mailto:mdnsext-bounces@ietf.org] Im
> > Auftrag von Andrew Sullivan
> > Gesendet: Dienstag, 16. Juli 2013 17:15
> > An: mdnsext@ietf.org
> > Betreff: Re: [mdnsext] Hierarchical (host) domain names in mDNS?
> >
> > On Tue, Jul 16, 2013 at 10:49:11AM -0400, Kerry Lynn wrote:
> >
> > > the hen house.  One should still expect "controller.machine2.local."
> > > to resolve properly,
> >
> > Yes, if you tried to resolve "controller.machine2.local.", then it
> _would_
> > resolve correctly.  The difficulty, however, is that most resolving
> applications
> > don't actually work truly fully-qualified that way (i.e. by appending
> the final
> > dot).  So it will work fine if you have special name-handling code to
> make
> > sure that everything is actually really fully qualified always in local.
>  I think it
> > would be extremely wise to test how well that works in practice, but
> those
> > who have complete control over their application stack and so on might be
> > able to do it.
> >
> > Best,
> >
> > A
> >
> > --
> > Andrew Sullivan
> > ajs@anvilwalrusden.com
> > _______________________________________________
> > mdnsext mailing list
> > mdnsext@ietf.org
> > https://www.ietf.org/mailman/listinfo/mdnsext
> _______________________________________________
> mdnsext mailing list
> mdnsext@ietf.org
> https://www.ietf.org/mailman/listinfo/mdnsext
>