> On Nov 22, 2019, at 12:20 AM, Shane Kerr <sh...@time-travellers.org> wrote:
> "User-assigned codes - If users need code elements to represent country names 
> not included in ISO 3166-1, the series of letters AA, QM to QZ, XA to XZ, and 
> ZZ, and the series AAA to AAZ, QMA to QZZ, XAA to XZZ, and ZZA to ZZZ 
> respectively, and the series of numbers 900 to 999 are available.
> NOTE: Please be advised that the above series of codes are not universal, 
> those code elements are not compatible between different entities."
> 
> So the intention of the ISO at least is that these codes are used by users. 
> (I'm not sure what the scary warning means.) Certainly I have made heavy use 
> of .Q* and .X* in my own testing, with the assumption that these would never 
> be assigned (and yes, there is .TEST but sometimes you need more than one one 
> TLD).

Right.  And in fact, “unassigned” ISO codes _do_ get used, for places like 
Kosovo, that are in a state of disputed or partially-recognized countryhood, 
and ranges that are reserved for user use really should be left for that use, 
because they do in fact get used by users, so any centrally-coordinated use 
will run afoul of that.

Again, this is an argument from principle rather than an argument based on the 
specific case at hand.  I just think that we have a well-established precedent 
that all two-letter TLDs are derived from ISO 3166 Alpha-2, and it’s bad form 
to cross back over and start poaching in their territory.

                                -Bill

Attachment: signature.asc
Description: Message signed with OpenPGP

_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to