Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

FINAL VERSION TO BE SUBMITTED IF RATIFIED

Please click here to download a copy of the pdf below.

PDF
nameAL-ALAC-ST-0814-01-00-EN.pdf

 


Please click here to review the reason for abstention from Fatima Cambronero 

Toggle Cloak

...

Many of the RSEP requests are for the release of two character ASCII labels not on the ISO 3166-2 1 alpha 2 standard. However, the ISO 3166-2 1 alpha 2 standard is not a static document ; it will be updated to reflect changes to countries and territories. For example, BQ, CW and SX were added to the ISO 3166-2 1 alpha 2 standard in late 2010 (see http://www.iso.org/iso/iso_3166-1_newsletter_vi-8_split_of_the_dutch_antilles_final-en.pdf). This gives rise to a potential disparity in the implementation of Specification 5, Section 2 where future countries and territories would be treated differently than those countries and territories on today's ISO 3166-2 1 alpha 2 list.

However, two character ASCII labels at the second level have been made available for some gTLDs and many ccTLDs. Shorter domains are more desirable to potential registrants and two character ASCII labels can be used for alternative meanings than the one for the ISO 3166-1 alpha-2 standard. For these reasons, absent any DNS-related security or stability issues, the ALAC believes that all the restrictions of two character ASCII labels at the 2nd level within a TLD should ultimately be removed, and has no problem with the current exceptions being approved.

...

Many of the RSEP requests are for the release of two character ASCII labels not on the ISO 3166-2 1 alpha 2 standard. However, the ISO 3166-2 1 alpha 2 standard is not a static document ; it will be updated to reflect new countries and territories. For example, BQ, CW and SX were added to the ISO 3166-2 1 alpha 2 standard in late 2010. (http://www.iso.org/iso/iso_3166-1_newsletter_vi-8_split_of_the_dutch_antilles_final-en.pdf).

If RSEP requests are approved by ICANN and the registries make available two character ASCII labels not on today’s ISO 3166-2 1 alpha 2 list, what happens when future countries and territories with new 2 character codes assigned by ISO want the same protections as per Specification 5, Section 2 and find such codes already allocated by the registries?

...