On 27.8.2015, at 15.38, Ray Hunter <[email protected]> wrote: > IMHO This is a very worthwhile discussion that we've glossed over for a long > time. > > I've seen several drafts over the course of the Homenet WG. > > e.g. > https://tools.ietf.org/html/draft-ietf-homenet-front-end-naming-delegation-03 > discusses how DNS can be bootstrapped and parent domains delegated to a > Homenet Border Router. > > So that seems to be one portion of the overall jigsaw. > > And https://tools.ietf.org/id/draft-jeong-homenet-device-name-autoconf-03.txt > talks about each device auto-naming then the router performing discovery > using NI [RFC4620] coupled with dynamic update [RFC2136] to seed LLN devices > into the (global) DNS.
Requires host changes. Out of scope. > We also have https://datatracker.ietf.org/doc/rfc7558/?include_text=1 that > details requirements for extending mDNS e.g. linking mDNS sub-domains of the > parent namespace to physical interfaces. > > Meanwhile windows in the enterprise generally uses a delegated portion of the > overall DNS namespace such as win.company.com and it's own update mechanisms > internally. > > So what are the expectations/requirements for naming in Homenet, and > particularly host - router interaction? > > How will name registration work? Ideally, zeroconf. So registration is a strong word here. > Are we looking at a single flat name space? Probably not, at least if mdns is leveraged - it’s conflict resolution is strictly per-link, and as we have multiple links, we either implement clumsy conflict resolution scheme within mdns -> dns conversion step (not recommend) or provide zone per link. > How will name conflicts be resolved? See above. > Are we looking at a name space that is link dependent? Depends. I can see two different namespaces in general: [1] manually configured, to be updated to local master, and then to ISP (Miguel’s stuff, i.o.w.); this could be flat [2] zeroconf, based on mDNS, that is zone-per-link, and the associated zeroconf paths; clearly not flat > Are we looking at a name space that includes delegations via subdomains for > special devices or technologies? Not sure what you mean by this. > Are we looking at supporting nodes that roam from link to link often within > the Homenet? Possibly. The manual (dns-update) based mechanism could ensure that laptop.fingon.iki.fi points to my laptop _wherever it is_, inside or outside home. It is also known as laptop.lan.home by default, by simple mDNS -> DNS conversion and local hnetd action. (I haven’t done the [1] part, so that part of the example is fictional in my laptop case.) > What about devices that couple and uncouple from the Homenet? (mobile phones > with wifi and 3G) See above. > Is this going to turn into (another) DNS/mDNS war, or is there a model in > which the two can peacefully co-exist? They coexist in my mind, see above. > e.g. query mDNS first? query both simultaneously? mDNS is not really useful in and of itself in homenet, as it is per-link. mDNS proxied to DNS (hello, hybrid proxy), on the other hand, is the bee’s knees :-) > e.g. seed mDNS into a DNS delegated domain? Seed mDNS hybrid proxy NS entries to DNS; I am not convinced of zeroconf DNS zone population via mDNS for various reasons. > e.g. translate mDNS queries into DNS and perhaps vice versa? Yes. > How will resolution work? draft-ietf-dnssd-hybrid, draft-stenberg-hybrid-proxy-zeroconf, HNCP. > Will the end host be responsible for performing multiple resolution? Or the > Homenet router? Host. > Are we looking at electing a single authoritative DNS server for all of > Homenet? With standby? No, see HNCP. We could do that for the manually configured part, see above. > Or one DNS server per Homenet Border Router? No. > Or is every Homenet device a DNS/name server and we deploy a (large) search > list. Yes. > Perhaps most importantly: What mechanisms do common host operating systems > support today? The operating systems I care about support mDNS, DNS and DNS-SD. Cheers, -Markus _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
