[[--Translated text (en -> es)--]] Asunto: Re: Re "Introducción de dos caracteres de nombres de dominio en el Nuevo gTLD Namespace" Los comentarios del público De: brainstreetceo@gmail.com Este es un problema de usuario y edición país (es decir GAC). Si uno mira la cantidad de 2 sin asignar etiquetas de caracteres en la tabla ISO 3166-1, podría difícil hacer un argumento para la protección sólo para asegurarse de que el futuro países y territorios tienen acceso ... sobre todo cuando se observa el velocidad a la que esto sucede. Desde una perspectiva puramente de usuario se puede uno argumentar que los más dominios disponibles, mejor. Lanza El Jueves, 10 de julio 2014 a las 2:04 AM, Dev Anand Teelucksingh <devtee@gmail.com> escribió:

Regarding the public comment on "Introduction of Two-Character Domain Names in the New gTLD Namespace" at https://community.icann.org/x/VqzhAg which ends July 10 2014, I've posted the following at https://community.icann.org/x/VqzhAg for consideration:

"Various registries for multiple gTLDs are applying for exceptions to Specification 5, Section 2 of the New gTLD Registry Agreement ("Specification 5") with some registries suggesting the release of 2 character ASCII labels not on the current ISO 3166 standard would suffice.

While this seems harmless, there is a possibility of new countries and territories being created, and then allocated a new two character ASCII label by ISO 3166/MA (see

https://web.archive.org/web/20111101141651/http://www.iso.org/iso/country_co... ).

Any new country or territory created after 2014 would therefore not receive the same protection as those in the 2014 ISO 3166-2 list and would find that their new 2 character label is "given away", should they wish for their 2 character ASCII label to be protected, as per Specification 5.

Now, should the principle established by Specification 5 protecting 2 character ASCII labels even be in the New gTLD Registry Agreement? Many would say, especially given the prevalence of two character labels in existing TLDs like .com, .org and .net that this principle shouldn't be applied to new gTLDs. However, this (IMO) is a separate issue to the question being asked for in the public comment.

If Specification 5 is meant to defend the principle that country codes in ISO 3166-2 should be protected in new gTLDs, then it should be enforced to ensure future countries and territories with new 2 character ASCII labels are protected in the same way as those territories and countries in today's ISO 3166-2 list.

Therefore, the proposals by Donuts for 143 of its new gTLDS, .kred by KredTLD Pty Ltd, .best by BestTLD Pty Ltd and .ceo by CEOTLD Pty Ltd. should be turned down in keeping with the principle of Specification 5.

The proposal by .wiki by Top Level Design LLC which specifies that the two character ASCII labels will only be used for languages identified by ISO 639-1 does appear to meet the threshold that the use will not be confused with the corresponding country codes, as per Specification 5 and could be approved.

Similarly, the proposal by .globo by Globo Comunicação e Participações S.A which proposed the use of two character ASCII labels that are not letters or by two characters where only one of the character is a letter are labels that would not be used by ISO 3166-2 and could be approved."

Thoughts?

Kind Regards,

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

Lanza Hinds Director de Tecnología BrainStreet Grupo 287 'C' Albert St. Georgetown Guyana Este mensaje contiene información que puede ser privilegiada y / o confidencial y es propiedad de Tecnologías BrainStreet o BrainStreet Aprender. La información contenida en este documento está destinado sólo para la persona o entidad a quien va dirigida y otros autorizados para recibirlo. Si usted no es el destinatario previsto, no está autorizado para leer, imprimir, retener, copiar, divulgar, distribuir o tomar cualquier acción confiando al contenido de esta información o parte de ella y puede ser ilegal hacerlo. Si recibe este mensaje por error, por favor notifique inmediatamente al remitente y elimine todas las copias de este mensaje su sistema. Tecnologías BrainStreet o BrainStreet aprendizaje no son ni responsable de la transmisión correcta y completa de la información contenida en esta comunicación ni ninguna demora en su recepción. _______________________________________________ lac-discuss-es mailing list lac-discuss-en@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en [[--Original text (en) http://mm.icann.org/transbot_archive/e1afbd32e5.html --]]