On 28 Feb 2014, at 6:31, Tony Finch <d...@dotat.at> wrote: > John Levine <jo...@taugh.com> wrote: > >> Since the device and the browser will not be online when you do the >> initial configuration, it seems to me that if you use a validating >> resolver you lose no matter what the name is. > > Hmm yes a very good point :-/ > > I think this is an argument in favour of registering a special use name > for this purpose which can be configured with a negative trust anchor. > > Unless someone has a bright idea for some alternative fix…
Bonjour. It works for every other device in the home that needs a direct connection to manage. Nobody assumes that “http://printer.home” is going to do anything useful; why is the gateway device different? (I’ve never owned a consumer-grade home gateway; whenever I’ve helped out a neighbour with theirs I’ve always just connected to whatever address the gateway’s DHCP server gave me as a default route. I had no idea there was any expectation that “router.home” would do anything sensible. It does go some way to explain what I saw at L-Root when I last had the opportunity to look, though :-) Joe _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
