> On 08/28/2015 04:42 AM, Steven Barth wrote: >> Furthermore, as Markus noted, the IETF has MDNS and stateful DHCPv6 (or >> rather >> RFC 4704) in standards track and these protocols are widely supported by all >> kinds >> of clients already. >> > > So is plain old DNS. Then tell me how clients register their names using "plain old DNS" and how that is already widely deployed in client OSs.
> when there will manifestly be host changes to incorporate the brand new world > of in-home naming. There is nothing brand new here, it worked on single links for years. In my non-HNCP network I can type: http://printer.lan or even just http://printer to reach my HP printer, because it told my router that its hostname is "printer" when it got the DHCP lease and my router populates the name into the DNS cache that all clients are using. Similarly I can use http://printer.local and my PC finds the printer purely using MDNS without any router intervention or I can even enumerate it on the local link using DNS-SD without knowing its hostname and without router intervention. If I were to hookup my printer to an HNCP network that implements all the SHOULDs from the naming and service discovery section, I can also enumerate it using DNS-SD when it is on a different link than I am (without knowing its name or location) and I could also call it directly by its name using "plain old DNS" if I know where it is, e.g. printer.lan.office.home (if the router is named "office" and the link "lan"). That is purely using existing technologies without any host changes and on top of that completely zero-conf for the DNS-SD part. If I want meaningful plain old DNS names of course I have to tell the router that it is called "office" and its ethernet ports are called "lan" and that the printer is just "printer", but that issue you will probably always have with pure DNS. _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
