Hi, On Wed, Jul 20, 2016 at 02:10:05PM +0200, Ray Bellis wrote: > > On 20/07/2016 13:33, Ray Bellis wrote: > > > My expectation is that in a Homenet multi-subnet environment I will be > > able to just use http://<device>.<TBD>/ and just have it work regardless > > of which particular subnet that device is on [*].
Note that only one of those expectations is actually given you by RFC 7368 -- that it will just work no matter which subnet you're on. The <device>.<TBD> pattern (assuming TBD is a single label) is not. > There's a further corollary to this: since we can't mandate host > changes, the resolution of that name MUST be unicast DNS to an *on-net* > resolver. I think this is probably entailed, but RFC 7368 doesn't say that either. It just says that it probably needs to be (or needs to work somehow with DNS). > Having different resolvers for different parts of the namespace is a bad > idea [*] Except, of course, that's precisely what we have with Bonjour: DNS for everything except names ending in local. That label functions as a protocol switch to tell your combined resolver which names to resolve by mDNS and which ones to resolve by DNS. > [ Current host stacks don't have support for saying "if the suffix is > ".TBD", go here, otherwise go there. If you have one resolver for > ".TDB" and another for everything else and then just send all queries to > both, you still need host changes to cope with how you'll get a valid > answer from one but not the other ] Not necessarily. For instance, you could use Bonjour and the hybrid proxy approach and do it that way. It's not clear to me from RFC 7368 whether we're allowed to assume mDNS is available on any host, but given the zeroconf pattern and the stated desirability of it, probably we are. Best regards, A -- Andrew Sullivan [email protected] _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
