Patrik, >>> Also note that there are ccTLDs allocated for codes that are not registered >>> in ISO3166 (UK, EU etc). >> >> IIUC these two are on the 3166 list as exceptionally reserved codes. > > Yes, but not REGISTERED, and that difference is something that created more > than just a little bit of "excitement" including ISO asking whether ICANN do > not understand what a registered code is when .EU was allocated.
Are you using a formal definition of "registered" in this context? Also, I'm curious: was there any "excitement" and/or did ISO ask similar questions when (say) .AC was created (in 1997, as opposed to .EU, which was created in 2005, according to IANA's whois)? That is, was Jon's (apparent) policy of allocating TLDs for "exceptionally reserved" codes (a policy continued by ICANN) a source of "excitement"/questions from ISO or others or was the eyebrow raising just because ICANN was involved in .EU? > I was just after 1. trying to not use the term "country" and 2. pointing out > a recognition that some ccTLDs are allocated with two character codes which > are not *registered* in ISO 3166. My understanding of the usage of "Exceptionally Reserved" codes is that they are codes that have been reserved for a particular use at special request of a national ISO member body, governments or international organizations and that as such, those codes cannot be used for any other "country". That would appear to fit the definition of "registered" to me, but I'm unsure what definition of "register" you're using. The point of this pedantism is that RFC 1591 (the basis for using 3166 for two-letter TLDs as far as I am aware) did not say that only "general purpose" codes could be used for "ccTLDs", it merely said "the two letter country codes from ISO-3166". Since ISO defines everything in "ISO-3166-1 Alpha-2" as a "country code" (even things that are clearly not countries, e.g., UM and FX), it would seem reasonable to me to simply put country in quotes (with perhaps a footnote saying the "countries" are more than just countries). Regards, -drc
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop