Re: Services and top-level DNS names (was: Re: Update of RFC 2606

[John Levine <[e-mail]>]

> 	Again you are asserting that no one has ever been effected.

No, I'm saying that you can only cry wolf so many times.

The disaster you are predicting has in fact been in progress for over
a decade, and the mountains of casualties are nowhere to be found.

Someone claiming to be you said:

>        I suspect that other sites that used the names just put up
>        with the pain of renamimg hosts along with the resultant
>        risk of email being misdirected.

There's at least one well known mail host whose name has matched a TLD 
with an MX for ten years now.  Did they rename?  Are they losing floods of 
mail to the Caribbean?  Uh, well, if they are, they're not telling anyone. 
How do we explain this conspiracy of silence?

Finally, as I presume you're aware, some browsers including Firefox retry 
with an appended .com if the address you type doesn't resolve, so if you 
type something like www.pets into your browser, it will find www.pets.com. 
This means that if ICANN creates new TLDs that match any of the 70 million 
existing .com domains, users of popular current software will suddenly 
find that they're not seeing the sites they used to see.  (We're not 
talking about records at the apex of a TLD here, it's www.blah.com vs. 
www.blah.)  Should all of the existing .com domain names be reserved as 
TLDs?  If not, why not?  It's the same problem, only it affects a lot more 
people.

R's,
John

PS to everyone else: I'll stop beating this dead horse now.
_______________________________________________
Ietf mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/ietf