In message <20140227031921.7962.qm...@joyce.lan>, "John Levine" writes: > >> That's a relatively high bar for all the residential broadband users > >> who buy a router at Best Buy (Future Shop to you), plug it in, and set > >> up the router via the configuration page at http://router.home. > > > >And why wasn't that "http://router.netgear.com"; or > >"http://router.linksys.com";. > > I dunno, but that doesn't help much once the network is online and > there are other devices with .home names.
Whether is it router.home or router.vendor.com, both names assume that the CPE device is in the DNS lookup path to get the correct address returned for the name. If the CPE puts out a search list of "home.arpa" rather than "home" in the DHCP lease and added the machines to home.arpa rather than home zone I doubt many people would notice. Most home users would be using unqualified names and the resolver's search will qualify them. This is all about getting sensible defaults in new CPE devices and have a reserved place for them. This should already be configurable if they doing this sort of thing. > >If the CPE vendors want to use .home let them pony up the 100K for > >it rather than hijack the namespace. > > Um, it's a wee bit late for that. > > R's, > John -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
