See the end for something provocative. > ICANN do say what strings in the name space should be TLDs. > > IETF do say what strings in the name space should NOT be TLDs. > > The rest are just strings waiting to end up in one of the two groups. > > Patrik
Perfectly stated. There is really just one name space. Once a string is designated by the IETF for some purpose other than allocation as a top level domain, it is, IMO, permanently barred from being allocated as a TLD. As a practical matter, non-TLD strings regularly leak into the public domain name system and wind up at the root. In principle, this should not be a problem except for the additional load it places on the root servers, EXCEPT we have also seen end systems depend on the NXDOMAIN response from the root servers as part of their processing. This creates a nasty security hole. I propose augmenting the DNS to include entries in the root that serve the purpose of giving slow NXDOMAIN responses instead of quick responses for those strings that the IETF has identified as not TLDs. local, corp, home, mail, and others are what I have in mind. This is intended to incentivize developers not to release code that improperly depends on the NXDOMAIN response in their search path. Steve _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
