On 22/03/2017 08:11, Tim Chown wrote:
> I’d like to think such uses are largely all GUI/icon driven. Or perhaps > increasingly voice driven, like Alexa. How often will foo.homenet.arpa, > or foo.homenet be used in typical cases? I use ".local" to access several devices in my home network that are not hidden behind a UI "discovery client", including my ADSB receiver and my NAS. I also use it for SSH access to devices that announce that service via Bonjour rather than having to put their IPs in /etc/hosts everywhere. Arguably I'm not "typical", but IMHO we shouldn't be designing for the lowest common denominator. Either way, the Homenet WG has reached its consensus decision to request ".homenet" rather than ".homenet.arpa". I personally don't mind if it takes longer for the requested insecure delegation to happen than for the special-use reservation to happen - the former shouldn't be a blocker for the latter. To those that say "no insecure delegations in the root zone" because "DNSSEC is good", my argument is that in this particular case blocking the request would *inhibit* use of DNSSEC in edge networks and on stub resolvers. The whole point of the insecure delegation is to *facilitate* correct use of DNSSEC within Homenets. Ray (no hat) _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
