<div dir="ltr"><div><span id="gmail-docs-internal-guid-394937ac-7fff-9510-7752-ebf83fa0fe52"><p dir="ltr" style="line-height:1.295;margin-top:0pt;margin-bottom:8pt"><span style="font-size:10.5pt;font-family:Arial;color:rgb(102,102,102);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">To Whom It May Concern,</span></p><br><p dir="ltr" style="line-height:1.295;margin-top:0pt;margin-bottom:8pt"><span style="font-size:10.5pt;font-family:Arial;color:rgb(102,102,102);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">The Latin American and the Caribbean ccTLD Organization (LACTLD), is a nonprofit association created on August 20th, 1998 in Buenos Aires, Argentina, during the International Forum on the White Paper (IFWP). LACTLD’s vision is to to be the regional organization that represents the interests and promotes the development of the ccTLDs in Latin America and the Caribbean. Following, is LACTLD’s input with respect to the Initial Report of the New gTLD Subsequent Procedures Policy Development Process Working Group, which is chartered to evaluate what changes or additions need to be made to existing new gTLD policy recommendations and includes materials from the full Working Group and four sub-teams within the Working Group, Work Tracks 1-4.  </span></p><br><p dir="ltr" style="line-height:1.295;margin-top:0pt;margin-bottom:8pt"><span style="font-size:10.5pt;font-family:Arial;color:rgb(102,102,102);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">In reference to the Initial Report following questions: “2.7.1.e.2: If there are no technical obstacles to the use of 2-character strings at the top level consisting of one letter and one digit (or digits more generally), should the reservation of those strings be removed? Why or why not? Do you believe that any additional analysis is needed to ensure that these types of strings will not pose harm or risk to security and stability? Please explain.”</span></p><br><p dir="ltr" style="line-height:1.295;margin-top:0pt;margin-bottom:8pt"><span style="font-size:10.5pt;font-family:Arial;color:rgb(102,102,102);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">LACTLD states that:</span></p><p dir="ltr" style="line-height:1.295;margin-top:0pt;margin-bottom:8pt"><span style="font-size:10.5pt;font-family:Arial;color:rgb(102,102,102);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">1.  In order to assess if there are no technical obstacles to the use of 2-character stings at the top level consisting of one letter and one digit, this</span></p><p dir="ltr" style="line-height:1.295;margin-top:0pt;margin-bottom:8pt"><span style="font-size:10.5pt;font-family:Arial;color:rgb(102,102,102);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap"> question should be addressed by DNS technical experts (such as ICANN’s Security and Stability Advisory Committee (SSAC)).</span></p><br><p dir="ltr" style="line-height:1.295;margin-top:0pt;margin-bottom:8pt"><span style="font-size:10.5pt;font-family:Arial;color:rgb(102,102,102);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">2. In reference to the question: If there are no technical obstacles to the use of two-character strings consisting of one letter and one digit, should they be permitted to be registered in future gTLD string application rounds?, LACTLD believes that two-character strings consisting of one letter and one digit should NOT be permitted to be registered in future gTLD applications for the following reasons:</span></p><p dir="ltr" style="line-height:1.295;margin-top:0pt;margin-bottom:8pt"><span style="font-size:10.5pt;font-family:Arial;color:rgb(102,102,102);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap"> a. Two-character top-level domains are firmly associated with country-code Top Level domains; ccTLDs are created by IANA/PTI from two character codes laid down in ISO 3166-1</span></p><p dir="ltr" style="line-height:1.295;margin-top:0pt;margin-bottom:8pt"><span style="font-size:10.5pt;font-family:Arial;color:rgb(102,102,102);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap"> – ccTLDs have an entirely different policy background to gTLDs. It is entirely foreseeable that the ISO Maintenance Agency could, in the future, decide to issue two character country codes including digits, as the ITU already has done: see Appendix 2 to ITU Radio Regulations (e.g., ‘4X’ for Israel, ‘2’ for the UK).</span></p><br><br><p dir="ltr" style="line-height:1.295;margin-top:0pt;margin-bottom:8pt"><span style="font-size:10.5pt;font-family:Arial;color:rgb(102,102,102);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">b. Homographic issues:</span></p><p dir="ltr" style="line-height:1.295;margin-top:0pt;margin-bottom:8pt"><span style="font-size:10.5pt;font-family:Arial;color:rgb(102,102,102);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">Homographic issues were not addressed by the GNSO.</span></p><p dir="ltr" style="line-height:1.295;margin-top:0pt;margin-bottom:8pt"><span style="font-size:10.5pt;font-family:Arial;color:rgb(102,102,102);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">Homographic issues pose a direct threat to the security and stability of the Internet’s system of unique identifiers, including ccTLDs that might be caught up in them; some examples are:</span></p><p dir="ltr" style="line-height:1.295;margin-top:0pt;margin-bottom:8pt"><span style="font-size:10.5pt;font-family:Arial;color:rgb(102,102,102);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">.ci -> .c1</span></p><p dir="ltr" style="line-height:1.295;margin-top:0pt;margin-bottom:8pt"><span style="font-size:10.5pt;font-family:Arial;color:rgb(102,102,102);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">.cl -> .c1</span></p><p dir="ltr" style="line-height:1.295;margin-top:0pt;margin-bottom:8pt"><span style="font-size:10.5pt;font-family:Arial;color:rgb(102,102,102);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">.co -> .c0</span></p><p dir="ltr" style="line-height:1.295;margin-top:0pt;margin-bottom:8pt"><span style="font-size:10.5pt;font-family:Arial;color:rgb(102,102,102);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">.do -> .d0</span></p><p dir="ltr" style="line-height:1.295;margin-top:0pt;margin-bottom:8pt"><span style="font-size:10.5pt;font-family:Arial;color:rgb(102,102,102);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">.nl -> .n1</span></p><p dir="ltr" style="line-height:1.295;margin-top:0pt;margin-bottom:8pt"><span style="font-size:10.5pt;font-family:Arial;color:rgb(102,102,102);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">.is -> .1s</span></p><p dir="ltr" style="line-height:1.295;margin-top:0pt;margin-bottom:8pt"><span style="font-size:10.5pt;font-family:Arial;color:rgb(102,102,102);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">.ls -> .1s</span></p><br><p dir="ltr" style="line-height:1.295;margin-top:0pt;margin-bottom:8pt"><span style="font-size:10.5pt;font-family:Arial;color:rgb(102,102,102);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">With sans-serif typefaces, there is considerable risk for consumer confusion and consequent security risks, including phishing attacks.</span></p><br><p dir="ltr" style="line-height:1.295;margin-top:0pt;margin-bottom:8pt"><span style="font-size:10.5pt;font-family:Arial;color:rgb(102,102,102);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">ICANN’s core mission is “…to coordinate the stable operation of the Internet's unique identifier systems.”. The introduction of homonym-conflicted two-character top-level domains would be in direct conflict with that core mission.</span></p><br><p dir="ltr" style="line-height:1.295;margin-top:0pt;margin-bottom:8pt"><span style="font-size:10.5pt;font-family:Arial;color:rgb(102,102,102);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">The GNSO’s proposal would introduce instability to the DNS via visual confusion of strings.</span></p><br><p dir="ltr" style="line-height:1.295;margin-top:0pt;margin-bottom:8pt"><span style="font-size:10.5pt;font-family:Arial;color:rgb(102,102,102);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">3. In reference to the questions :</span></p><p dir="ltr" style="line-height:1.295;margin-top:0pt;margin-bottom:8pt"><span style="font-size:10.5pt;font-family:Arial;color:rgb(102,102,102);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">Is additional analysis needed to ensure that the introduction of two-character strings consisting of one letter and one digit will not cause harm or risk to the security and stability of the DNS?</span></p><br><p dir="ltr" style="line-height:1.295;margin-top:0pt;margin-bottom:8pt"><span style="font-size:10.5pt;font-family:Arial;color:rgb(102,102,102);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">LACTLD states that as per Question 1, this must be addressed by DNS Technical Experts, such as the Security and Stability Advisory Committee (SSAC).</span></p><br><p dir="ltr" style="line-height:1.295;margin-top:0pt;margin-bottom:8pt"><span style="font-size:10.5pt;font-family:Arial;color:rgb(102,102,102);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">In conclusion, LACTLD believes that the technical questions asked by the GNSO Working Group need to be addressed and answered by relevant technical bodies, two-character strings, consisting of one letter and one digit, or two digits, should unequivocally not ever be permitted in future gTLD application rounds because of the conflict with ccTLD allocation policy and ISO two-character codes (which are external to ICANN), as well as the homographic issues discussed above.</span></p></span><br class="gmail-Apple-interchange-newline"></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><table width="400" border="0" cellspacing="0" cellpadding="0" style="color:rgb(0,0,0);font-family:Times;font-size:medium"><tbody><tr><td width="158px" style="background-image:initial;background-position:initial;background-repeat:initial"><img src="https://lactld.org/sites/default/files/inline-images/lactld-logo-firma.jpg" style="display:block"></td><td style="background:rgb(31,155,222)"><table width="100%" border="0" cellspacing="0" cellpadding="8px" style="background-image:initial;background-position:initial;background-repeat:initial"><tbody><tr><td><font face="arial" color="white" style="font-size:12px;line-height:8px"><strong style="font-size:16px">Miguel Ignacio Estrada</strong> <br>General Manager <br>LACTLD <br>+598 2 604 22 22 <br><a href="https://www.lactld.org" style="color:white" target="_blank">www.lactld.org</a></font><br></td></tr></tbody></table></td></tr></tbody></table></div></div></div>