<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; "><span id="OLK_SRC_BODY_SECTION"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="font-size: 14px; font-family: Calibri, sans-serif;">Dear All,</div><div style="font-size: 14px; font-family: Calibri, sans-serif;"><br></div><div style="font-size: 14px; font-family: Calibri, sans-serif;">Following up on our conversation during the wrap up session on the public comment forum that has been opened on the introduction of two character domain names in the new gTLD namespace (see <a href="https://www.icann.org/public-comments/two-char-new-gtld-2014-06-12-en">https://www.icann.org/public-comments/two-char-new-gtld-2014-06-12-en</a>),
the recommendation of the GNSO Reserved Name Working Group in relation to this topic (see (<a href="http://gnso.icann.org/en/group-activities/inactive/2007/reserved-names" style="color: purple; ">http://gnso.icann.org/en/group-activities/inactive/2007/reserved-names</a>)
was as follows:</div><div style=""><ul><li><span style="font-style: normal; font-weight: normal; text-decoration: none;">We recommend that registries may propose release of two letter and/or number strings at the second level, provided that measures to avoid confusion with any corresponding country
codes are implemented. A standardized approach should be used which ensures consultation with appropriate parties, including the ccNSO and ISO-3166 Maintenance Agency, and where security and stability issues are identified, RSTEP. ** (** = </span>The existing
gTLD registry agreements provide for a method of potential release of two-character ASCII names at the second level. In addition, two letter and/or number ASCII strings at the second level may be released through the process for new registry services, which
process involves analysis of any technical or security concerns and provides opportunity for public input. Technical issues related to the release of two-letter and/or number strings have been addressed by the RSTEP Report on GNR.s proposed registry service.
The GAC has previously noted the WIPO II Report statement that .If ISO 3166 alpha-2 country code elements are to be registered as domain names in the gTLDs, it is recommended that this be done in a manner that minimises the potential for confusion with the
ccTLDs.)</li></ul><div>This recommendation was then rolled into recommendation 5 of the GNSO's Final Report on the Introduction of new Generic Top Level Domains (see <a href="http://gnso.icann.org/issues/new-gtlds/council-report-to-board-pdp-new-gtlds-11sep07.pdf">http://gnso.icann.org/issues/new-gtlds/council-report-to-board-pdp-new-gtlds-11sep07.pdf</a>):
'Strings must not be a Reserved Word'. </div></div><div style=""><br></div><div>This was implemented in the Applicant Guidebook as part of specification 5 (schedule of reserved names at the second level in gTLD registries) as follows: "Two-character labels. All two-character labels shall be initially reserved. The reservation of a two
character <span style="">label string may be released to the extent that Registry Operator reaches agreement with the </span>government and country-code manager. The Registry Operator may also propose release of these reservations based on its implementation
of measures to avoid confusion with the corresponding country codes". </div><div><br></div><div>And translated into the new gTLD Registry Agreement as: Specification 5 (Schedule of Reserved Names), Section 2: "All two-character ASCII labels shall be withheld from registration or allocated to
<abbr title="Registry">Registry</abbr> Operator at the second level within the <abbr title="Top Level Domain">
TLD</abbr>. Such labels may not be activated in the <abbr title="Domain Name System">
DNS</abbr>, and may not be released for registration to any person or entity other than
<abbr title="Registry">Registry</abbr> Operator, provided that such two-character label strings may be released to the extent that
<abbr title="Registry">Registry</abbr> Operator reaches agreement with the related government and country-code manager of the string as specified in the
<abbr title="International Organization for Standardization">ISO</abbr> 3166-1 alpha-2 standard. The
<abbr title="Registry">Registry</abbr> Operator may also propose the release of these reservations based on its implementation of measures to avoid confusion with the corresponding country codes, subject to approval by
<abbr class="" title="Internet Corporation for Assigned Names and Numbers">ICANN"</abbr>.</div><div><br></div><div>Please note that the public comment forum closes on 10 July with the reply period closing on 1 August. The GNSO Council may want to consider during its next meeting whether or not to provide input on this topic. </div></div></div></div></span><div><br></div><div>Best regards,</div><div><br></div><div>Marika</div><span id="OLK_SRC_BODY_SECTION"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="font-size: 14px; font-family: Calibri, sans-serif;"> </div></div></div><br></div></span></body></html>