On Nov 22, 2019, at 1:33 PM, David Conrad <d...@virtualized.org> wrote: > I don’t understand why one would need to pick ZZ (or any other user defined > code) to mean by convention anything. It doesn’t hurt anything, I just don’t > see the point. > > I would turn the question around: > > Why not simply have an RFC that declares the user defined ISO 3166 codes as > the RFC 1918-space equivalent for the DNS and be done with it? If people > _really_ want to continue the bike shedding on a particular string, they > still can, but the folks who want a string (or strings) that they can use for > internal purposes without fear of it being delegated in some future round of > new gTLDs can just get on with their lives.
I agree completely. The RFC that declares this should advise potential users of these TLDs to use a random number to choose one of the available names, so that the likelihood of a collision is at least somewhat lessened in case of a future merger. Locking it to .ZZ or suggesting that people to pick based on preference creates a higher likelihood of such collisions. _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
