Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt

[Mark Andrews <[e-mail]>]

In message <[e-mail]>, "John Levine" writes:
> 
> >Perhaps all that is missing is some guidance that says "you shouldn't hijack
> >namespaces that you don't control, even for non-DNS applications; register a
> >domain instead".
> 
> 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". The router could easily serve the zone
locally and the vendor could have a insecure delegation to it so
it works if there are validating browsers being used.

http://router.home does not work with validating browsers.

If the CPE vendors want to use .home let them pony up the 100K for
it rather than hijack the namespace.

> What do they get for their $10/yr and extra config hassle that they
> would care about?
> 
> R's,
> John
> 
> PS: Don't miss ICANN's latest on this point:
> 
> http://www.icann.org/en/news/announcements/announcement-26feb14-en.htm
> 
> They commissioned a report that says to reserve .HOME .CORP and .MAIL,
> and to do a 120 day wildcard on new domains that returns 127.0.53.53
> to alert people to upcoming problems and see what the traffic is.  It
> notably does not suggest how to interpret the results after the 120
> days.
> 
> 
> --===============4405462344142669891==
> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
> 
> _______________________________________________
> DNSOP mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/dnsop
> 
> --===============4405462344142669891==--
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: [phone]                 INTERNET: [e-mail]