>> Well, even worse, what happens if <name-your-next-OS-vendor> decides to >> create a new dns-like protocol that uses .foo, does that mean that we should >> automatically block it? > > No. We can add it to the special-use domain name registry if the IETF has > consensus to do so, but there's nothing automatic about it, as Christian > Grothoff can testify.
Interesting choice: .FOO already exists. How is the IESG going to make a decision about whether to pre-empt Charleston Road Registry's use of that TLD in favor of <name-your-next-OS-vendor>'s use of that 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
