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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|
09.09.2014 | Introduction of Two-Character Domain Names for .SOHU, .IMMO, .SAARLAND, .CLUB | ADOPTED by default, see this motion | Dev Anand Teelucksingh | 23.08.2014 | 29.08.2014 23:59 UTC | n/a | n/a | n/a | n/a | 30.08.2014 | Krista Papac | AL-ALAC-ST-0814-04-00-EN |
FINAL VERSION TO BE SUBMITTED IF RATIFIED
Please click here to download a copy of the PDF below.
FIRST DRAFT SUBMITTED
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 changes to countries and territories. For example, BQ, CW and SX were added to the ISO 3166-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-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.
3 Comments
Evan Leibovitch
Nothing more needs to be done here than to reference the general statement on two-character domains that has been passed by the ALAC.
Alan Greenberg
Agreed. I would suggest that we point to the comment posted earlier to make it clear that this is not a change from that version. Moreover, I suggest that if the previous vote did not make it crystal clear, that the next one be in response to this and all future similar PCs.
Dev Anand Teelucksingh
A Mea Culpa in my drafting of the statement, there is a typo in the 2nd paragraph which says "ISO 3166-2 alpha 2" when it should be "ISO 3166-1 alpha-2" (as it is in the 3rd paragraph)
The substance and intent of the statement is unchanged, however. I've updated the draft statement accordingly