[lac-discuss-en] = iso-8859-1 q = Re_ = 26quot F3n_de_do == 3BIntroducci = iso-8859-1 == q s_caracteres_de_nombres_de_dominio_en_el_Nuevo_gTLD iso-8859-1 q = 26quot = _Namespace????? 3B_Los_comentarios_del_p = FAblico? =

[asoto at ibero-americano.org]

[[--Translated text (es -> en)--]]

 Subject: Re: = iso-8859-1 q = Re_ = 26quot F3n_de_do == 3BIntroducci = iso-8859-1 == q s_caracteres_de_nombres_de_dominio_en_el_Nuevo_gTLD iso-8859-1 q = 26quot = _Namespace????? 3B_Los_comentarios_del_p = FAblico? = 
 From: asoto at ibero-americano.org

 From what I saw, ESTN GenRich asking for deliverance. I agree with Lance 
 you can not make a general reservation, but also no liberation 
 general. MUST ask especfica liberation, with the justification 
 corresponding. 
 Best Regards 


 Alberto Soto 


 ----- Original Message ----- 
 From: lac-discuss-es-bounces at atlarge-lists.icann.org 
 [Mailto: lac-discuss-es-bounces at atlarge-lists.icann.org] On Behalf Of 
 devtee at gmail.com 
 Posted on: Thursday, July 10, 2014 3:06 a.m. 
 To: lac-discuss-es at atlarge-lists.icann.org 
 Subject: Re "Introduction of two-character domain names in the 
 New gTLD Namespace "Comments from the public 




 [[- Translated text (en -> en) -]]


 Subject: Re "Introduction of two-character domain names in the 
 New gTLD Namespace "Comments from the public 
 From: devtee at gmail.com 


 As for public comment on "Introduction of two character 
 domain name in the New gTLD namespace "in 
 https://community.icann.org/x/VqzhAg 
 ending July 10, 2014, I posted the following on 
 https://community.icann.org/x/VqzhAg 
 for consideracin: 




 "Several records for multiple gTLDs ESTN requesting exceptions to 
 Specification 5, Section 2 to the new gTLD registry 
 ("Specification for the 5") with some records suggesting 
 2 liberation ASCII character tags are not in the ISO standard 
 Current 3166 will suffice. 




 While this seems harmless, there is a possibility of new countries and 
 territories are created, and then assign a new two ASCII characters 
 ISO 3166/MA label (see 
 https://web.archive.org/web/20111101141651/http://www.iso.org/iso/country_co 
 des/iso-3166-1_decoding_table.htm 
 ). 




 Any new step territory created after 2014, therefore no 
 receive the same protection as those in the ISO 3166-2 list 2014 
 find your new character label 2 "gives" if 
 aslo want for your label 2 ASCII characters to protect, according to the 
 specification 5. 




 Now, if the principle set out in the Specification for the protection May 2 
 ESTN an ASCII character tags in the registry agreement for new gTLDs? 
 Many will say, especially given the prevalence of the two 
 Character tags in existing TLDs, such as. com,. org and. net this 
 principle should not be applied to new gTLDs. 
 However, this (IMO) is a separate issue from the question being asked in the 
 the public comment. 




 If Specification for the 5 estdestinado to defend the principle that 
 ISO 3166-2 codes of passes must be protected in the new gTLDs, 
 then you must meet to ensure that future passes and territories 
 with new tags 2 ASCII characters ESTN protected in the same 
 how territories and countries in the current ISO 3166-2 list. 




 Therefore, the proposals of Donuts of 143 of their new gTLDs. Kred 
 by KredTLD Pty Ltd,. Best Pty Ltd and by BestTLD. Ceo for CEOTLD Pty Ltd. 
 must be rejected in accordance with the principle of specification 5. 




 The proposed. Wiki for Top Level Design LLC, which specifies that the two 
 ASCII character tags are only for languages \u200b\u200butilizarn sealados by 
 ISO 
 639-1 sparece meet the threshold should not be confused use 
 with the codes of the respective countries, according to the 
 5 specification may be 
 approved. 




 Similarly, the proposal. Globo Globo Comunicaoe 
 Participaes SA 
 the utilization of two ASCII characters labels is proposed that no 
 letters are 
 or two characters that only one character is a letter labels are 
 I will not used by ISO 3166-2 and may be approved. 
 " 




 Thoughts? 




 Best Regards, 




 Dev Anand Teelucksingh 
 _______________________________________________ 
 lac-discuss-en mailing list 
 lac-discuss-en at atlarge-lists.icann.org 
 https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en 









[[--Original text (es)
http://mm.icann.org/transbot_archive/f0985622c7.html
--]]