On Dec 5, 2013, at 12:40 AM, Stephane Bortzmeyer <bortzme...@nic.fr> wrote: >> If he doesn't have the .onion >> overlay software installed and configured, he's likely to be >> disappointed/confused/angry > But it is the same problem with <http://lolcats.local/>.
You carefully edited out the parenthetical immediately following "angry" >> (at least with .local if my PHB is an English speaker, he might have a hint) Yes, it's the same problem, but it is (currently) limited to essentially one TLD and one which has some (English-only) suggestion about its implications. > Or, for the > matter, for <http://192.168.1.1/>. It seems you're restarting old > wars. In the sense that I'm resurrecting the same arguments used whenever the latest VC comes up with the brilliant idea of alternative roots, I suppose you could say I'm continuing a war. With the proliferation of new TLDs, how is anyone supposed to know if a TLD is a real TLD and not some pseudo-domain that looks like a TLD but isn't really and they need some cool and nifty plugin or software package to actually make use of the name? Regards, -drc
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
