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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|
03.10.2014 | Introduction of Two-Character Domain Names for .JETZT, .GLOBAL, .NEUSTAR, .KIWI, .BERLIN | by default, see this motion | Dev Anand Teelucksingh | 15.09.2014 | 22.09.2014 23:59 UTC | n/a | n/a | n/a | n/a | 23.09.2014 | Krista Papac krista.papac@icann.org | AL-ALAC-ST-0914-02-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.
2 Comments
Dev Anand Teelucksingh
A question re: Neustar's and .global's RSEP applications which are different from recent RSEP requests. Neustar and .global are asking for the release of all two characters (letters and digits) at the 2nd level, irrespective of whether the two characters are on the ISO 3166-1 alpha 2 list or not. The ISO list consists of combinations of two letters.
Neustar's and .global RSEP requests would mean that two character combinations of letters and numbers are possible at the 2nd level for .neustar and .global.
Would having domains where the letter o could be interchanged with the digit zero be a DNS related security issue, given the visual similarity of the letter "o" and the number zero ("0"), ?
For example:
Dev Anand
Olivier Crepin-Leblond
Re: zero vs. the letter o we are starting to reach dangerous waters. Nobody's ever complained of visual similarity between l or 1 or I yes they are so visibly similar.. and the list continues...