| Comment Close Date | Statement Name | Status | Assignee(s) | Call for Comments Open | Call for Comments Close | Vote Announcement | Vote Open | Vote Reminder | Vote Close | Date of Submission | Staff Contact and Email | Statement Number | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 10.07.2014 | Introduction of Two-Character Domain Names in the New gTLD Namespace |
| Unlicensed user | 08.08.2014 | 11.08.2014 20:00 UTC | 11.08.2014 23:00 UTC | 11.08.2014 23:00 UTC | 15.08.2014 | 16.08.2014 23:00 UTC | 16.08.2014 | Krista Papac | AL-ALAC-ST-0814-01-0001-EN |
...
The At-Large Community has taken note of the many Registry Services Evaluation Process (RSEP) requests submitted to ICANN by many New gTLD Registries applying for exceptions to Specification 5, Section 2 of the New gTLD Registry Agreement (see page 68 of the http://newgtlds.icann.org/en/applicants/agb/agreement-approved-09jan14-en.pdf for the text of Specification 5, Section 2)
...
Many of the RSEP requests are for the release of two character ASCII labels not on the ISO 3166-1 alpha 2 standard. However, the ISO 3166-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-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-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?
...