Dear All, For your information, please find below a blog post in relation to the proposed process for releasing two-character second level domain names. Best regards, Marika ICANN Clears the Way for Two-character Second-level Domain Names <https://www.addthis.com/bookmark.php?v=300&winname=addthis&pub=ra-52fcc7eb243d6d89&source=tbx32-300&lng=en-US&s=linkedin&url=https%3A%2F%2Fwww.icann.org%2Fnews%2Fblog%2Ficann-clears-the-way-for-two-character-second-level-domain-names&title=ICANN%20Clears%20the%20Way%20for%20Two-character%20Second-level%20Domain%20Names%20-%20ICANN&ate=AT-ra-52fcc7eb243d6d89/-/-/54646de5bfbe0b48/2&frommenu=1&uid=54646de528e1ecc1&ct=1&tt=0&captcha_provider=nucaptcha><https://www.icann.org/news/blog/icann-clears-the-way-for-two-character-second-level-domain-names#><https://www.icann.org/news/blog/icann-clears-the-way-for-two-character-second-level-domain-names#><https://www.addthis.com/bookmark.php?v=300&winname=addthis&pub=ra-52fcc7eb243d6d89&source=tbx32-300&lng=en-US&s=sinaweibo&url=https%3A%2F%2Fwww.icann.org%2Fnews%2Fblog%2Ficann-clears-the-way-for-two-character-second-level-domain-names&title=ICANN%20Clears%20the%20Way%20for%20Two-character%20Second-level%20Domain%20Names%20-%20ICANN&ate=AT-ra-52fcc7eb243d6d89/-/-/54646de5bfbe0b48/3&frommenu=1&uid=54646de5c4cb247f&ct=1&tt=0&captcha_provider=nucaptcha><https://www.icann.org/news/blog/icann-clears-the-way-for-two-character-second-level-domain-names#><https://www.icann.org/news/blog/icann-clears-the-way-for-two-character-second-level-domain-names#> Currently, Specification 5 of the base new gTLD Registry Agreement (RA) requires registry operators to reserve all two-character ASCII labels at the second-level. The RA also states that registry operators can request permission from ICANN to release these labels. Earlier this year, many new gTLD registry operators requested permission from ICANN to release some, or all, of the reserved two-character labels. ICANN has processed these requests under the Registry Services Evaluation Policy (RSEP). To date, ICANN has processed over 60 RSEP requests<https://www.icann.org/resources/pages/rsep-2014-02-19-en> supporting the release of a variety of two-character labels for over 200 new gTLDs. Registry Agreement amendments permitting the requested releases were proposed and posted for Public Comment. ICANN batched these amendments for a combined total of five Public Comment periods<https://www.icann.org/public-comments>. The five Public Comment periods gave governments, trademark owners, registries, country-code operators, the technical community, and others the opportunity to comment on the proposed Registry Agreement amendments that would allow the release of two-character labels. After reviewing the summary and analysis of the first batch of Public Comments, the ICANN Board passed Resolution 2014.10.16.14<https://features.icann.org/introduction-two-character-domain-names-new-gtld-...> on 7 November 2014 directing ICANN staff to "develop and implement an efficient procedure for the release of two-character domains currently required to be reserved in the New gTLD Registry Agreement," while taking into consideration advice from the Governmental Advisory Committee (GAC) as published in the "Los Angeles Communiqué<https://www.icann.org/en/system/files/correspondence/gac-to-board-15oct14-en...>" [PDF, 127 KB]. Looking Forward Following the Board Resolution, ICANN has been working to develop a more efficient procedure enabling the release of two-character labels for new gTLDs, and I'm happy to say we're almost there. We plan to release an authorization process by 1 December that no longer requires Registry operators to reserve number/letter (2a), letter/number (a2), or number/number (22) labels at the second-level. This category of two-character labels has been determined not to raise significant security, stability and competition concerns and has received no objections from governments, country-code managers, members of the technical community, or rights holders. The remaining two-character ASCII labels, or letter/letter labels, will also be eligible for consideration for "authorization" to be released. The GAC's discussion on two-character labels focused on letter/letter (aa) two-character labels. The GAC stated "that the public comment period is an important transparency mechanism" and that relevant governments should be alerted when such requests arise. Accordingly ICANN has developed a Request for Authorization to Release process for registries who want to release letter/letter labels from reservation. The process consists of the following: 1. Registry operator submits a request to ICANN to release one or more letter/letter two-character labels. 2. ICANN reviews the request, and posts it for comment for 30 days. 3. ICANN notifies the GAC of the request and the comment period. 4. If there are no relevant and reasoned objections to the request, ICANN will authorize the requested letter/letter two-character labels to be released. The 30-day posting period provides the transparency valued by the GAC. Once a request is posted, governments will be provided with the opportunity to comment on registry requests. Under the new process, registries with RSEP requests that have completed the RSEP process and whose proposed RA amendment to release the requested two-character SLDs from reservation have undergone Public Comment will receive an authorization from ICANN by 1 December to release the requested SLDs from reservation. These requests have already been posted for an extended period (up to six months) while the community discussed and considered the issues raised by the requests, and they have each been subject to a 42-day public comment period. There were no comments opposing the proposed amendments that would allow registries to release the requested two-character SLDs from reservation. Those registries that have not had a proposed Registry Agreement amendment to release from reservation the requested two-character SLDs undergo Public Comment will be asked to use the new process outlined above. It is important for the community and registries to remember, that all authorizations to release two-character SLDs from reservation will continue to be subject to all terms of the Registry Agreement, including Rights Protection Mechanisms and the Name Collision Framework. We are pleased to launch this new process that allows for more efficient processing of applicable requests to release certain two-character SLDs from reservation, while respecting the requests of the GAC and other community members. We look forward to continuing to solicit feedback from various members of the community while improving efficiencies for contracted parties.