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

Andrew Sullivan <ajs@anvilwalrusden.com> Tue, 16 July 2013 15:14 UTC

Return-Path: <ajs@anvilwalrusden.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 A931111E80C5 for <mdnsext@ietfa.amsl.com>; Tue, 16 Jul 2013 08:14:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.783
X-Spam-Level:
X-Spam-Status: No, score=-0.783 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
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 a8T3biFvipTJ for <mdnsext@ietfa.amsl.com>; Tue, 16 Jul 2013 08:14:46 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id DD16A11E80DC for <mdnsext@ietf.org>; Tue, 16 Jul 2013 08:14:45 -0700 (PDT)
Received: from mx1.yitter.info (nat-08-mht.dyndns.com [216.146.45.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 4F3008A031 for <mdnsext@ietf.org>; Tue, 16 Jul 2013 15:14:45 +0000 (UTC)
Date: Tue, 16 Jul 2013 11:14:44 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: mdnsext@ietf.org
Message-ID: <20130716151444.GE23286@mx1.yitter.info>
References: <E36F274013087B4EA05E08EB5037503902C1DC@DEFTHW99EK5MSX.ww902.siemens.net> <CABOxzu27u5BMTZq2WKFk5O4nmLG87BXCdG6+M7+MeB-ZugDN9Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CABOxzu27u5BMTZq2WKFk5O4nmLG87BXCdG6+M7+MeB-ZugDN9Q@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
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: Tue, 16 Jul 2013 15:14:51 -0000

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