Re: [lac-discuss-es] ??????????? = Iso-8859-1 q = Re_ 26quot = 3BIntroducci = F3n_de_do == q iso-8859-1 s_caracteres_de_nombres_de_dominio_en_el_Nuevo_gTLD_Namesp == iso-8859-1 q ace = 26quot = 3B_Los_comentarios_del_p = FAblico? =
[[--Translated text (en -> es)--]] Asunto: Re:??????????? = Iso-8859-1 q = Re_ 26quot = 3BIntroducci = F3n_de_do == q iso-8859-1 s_caracteres_de_nombres_de_dominio_en_el_Nuevo_gTLD_Namesp == iso-8859-1 q ace = 26quot = 3B_Los_comentarios_del_p = FAblico? = De: apisan@unam.mx Dev, porción gracias this informacin Valiosa. El mundo de las Iniciales de dos letras es msmvil Que Lo Que sí Piensa frecuentemente; Cambios hijo y los trascendentales, CUANDO SE Presentan. ESTO Por Este tema de debe interesar a Aquellos Colegas de LACRALO Que Han Dado importância a Temas territoriales. Slo estafa do Iniciativa serposible Que Nuestra Comunidad Emprenda algoritmo en el Tema. Alejandro Pisanty --------------------------- Dr. Alejandro Pisanty Facultad de Qumica UNAM Av. Universidad 3000, 04510 Mexico DF México +52-1-5541444475 DESDE EL EXTRANJERO +525541444475 DESDE Mxico SMS +525541444475 Blog: http://pisanty.blogspot.com LinkedIn: http://www.linkedin.com/in/pisanty Unete al Grupo UNAM en LinkedIn, http://www.linkedin.com/e/gis/22285/4A106C0C8614 Twitter: http://twitter.com/apisanty ---- >> Unete a ISOC México, http://www.isoc.org . . . . . . . . . . . . . . . . ________________________________________ Desde: lac-discuss-es-bounces@atlarge-lists.icann.org [lac-discuss-es-bounces@atlarge-lists.icann.org] en Nombre de devtee@gmail.com [devtee@gmail.com] Enviado el: viernes, 11 de julio de 2014 07:59 Hasta: lac-discuss-es@atlarge-lists.icann.org CC: lista de discusión de LACRALO Asunto: Re: Re "Introduccin de dos Caracteres de Nombres de Dominio en el Nuevo gTLD Namespace" Los comentarios del Pblico [[- Texto traducido (es -> es) -]] Asunto: Re: Re "Introduccin de dos Caracteres de Nombres de Dominio en el Nuevo gTLD Namespace" Los comentarios del Pblico De: devtee@gmail.com Bueno, slo Puede del Contrato Maestro sin nmero Fijo de permutaciones (676) párr do Posible utilizar en la norma ISO 3166 ISO 3166 from Puede del slo letras ASCII servicio de AA a ZZ. Y Si bien Florerias no sin servicio rpido nmero de casas de cambio, casas de cambio en sí de han Producido ISO 3166 en el los ltimos 10 aos. EJEMPLO Por, es 2010, EJEMPLO by: http://www.iso.org/iso/iso_3166-1_newsletter_vi-8_split_of_the_dutch_antille... BQ, CW y SX sí aadieron párr Bonaire, San Eustaquio y Saba, Curazao y Sint Maarten (neerlandesa parte) en el Caribe. Dev Anand El Jueves, 10 de julio 2014 a las 08:47 AM, Carlton Samuels <carlton.samuels@gmail.com> escribi:
Closely reasoned and from the principle of cc assignment certainly worthy of the ALAC's consideration.
While we're at it, lets consider that 3-character country codes are possible.
Giving protection for a future event suggests we have a definite knowledge of country/territory breakdown and thusly, possible code assignment. Tying up all permutations of 2 characters especially when you consider IDNs would be a tough sell.
Carlton ---------'--------''-----
On Jul 10, 2014 2:04 AM, "Dev Anand Teelucksingh" <devtee@gmail.com> wrote:
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
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/83854e2f65.html --]]
Estoy totalmente de acuerdo en que no se puede hacer una liberación genérica. Hay que defender la equidad para los posibles nuevos código país. Muy importantes las aclaraciones y advertencias de Dev tambień. Es tema de toda la comunidad, más allá de que el grupo ccTLD es directamente involucrado . Habrá que hacer una declaración al respecto. El GAC también podría tener que decir en esto. Saludos 2014-07-12 8:37 GMT-03:00 <apisan@unam.mx>:
[[--Translated text (en -> es)--]]
Asunto: Re:??????????? = Iso-8859-1 q = Re_ 26quot = 3BIntroducci = F3n_de_do == q iso-8859-1 s_caracteres_de_nombres_de_dominio_en_el_Nuevo_gTLD_Namesp == iso-8859-1 q ace = 26quot = 3B_Los_comentarios_del_p = FAblico? = De: apisan@unam.mx
Dev,
porción gracias this informacin Valiosa.
El mundo de las Iniciales de dos letras es msmvil Que Lo Que sí Piensa frecuentemente; Cambios hijo y los trascendentales, CUANDO SE Presentan.
ESTO Por Este tema de debe interesar a Aquellos Colegas de LACRALO Que Han Dado importância a Temas territoriales. Slo estafa do Iniciativa serposible Que Nuestra Comunidad Emprenda algoritmo en el Tema.
Alejandro Pisanty
--------------------------- Dr. Alejandro Pisanty Facultad de Qumica UNAM Av. Universidad 3000, 04510 Mexico DF México
+52-1-5541444475 DESDE EL EXTRANJERO
+525541444475 DESDE Mxico SMS +525541444475 Blog: http://pisanty.blogspot.com LinkedIn: http://www.linkedin.com/in/pisanty Unete al Grupo UNAM en LinkedIn, http://www.linkedin.com/e/gis/22285/4A106C0C8614 Twitter: http://twitter.com/apisanty ---- >> Unete a ISOC México, http://www.isoc.org . . . . . . . . . . . . . . . .
________________________________________ Desde: lac-discuss-es-bounces@atlarge-lists.icann.org [ lac-discuss-es-bounces@atlarge-lists.icann.org] en Nombre de devtee@gmail.com [devtee@gmail.com] Enviado el: viernes, 11 de julio de 2014 07:59 Hasta: lac-discuss-es@atlarge-lists.icann.org CC: lista de discusión de LACRALO Asunto: Re: Re "Introduccin de dos Caracteres de Nombres de Dominio en el Nuevo gTLD Namespace" Los comentarios del Pblico
[[- Texto traducido (es -> es) -]]
Asunto: Re: Re "Introduccin de dos Caracteres de Nombres de Dominio en el Nuevo gTLD Namespace" Los comentarios del Pblico De: devtee@gmail.com
Bueno, slo Puede del Contrato Maestro sin nmero Fijo de permutaciones (676) párr do Posible utilizar en la norma ISO 3166 ISO 3166 from Puede del slo letras ASCII servicio de AA a ZZ. Y Si bien Florerias no sin servicio rpido nmero de casas de cambio, casas de cambio en sí de han Producido ISO 3166 en el los ltimos 10 aos.
EJEMPLO Por, es 2010, EJEMPLO by:
http://www.iso.org/iso/iso_3166-1_newsletter_vi-8_split_of_the_dutch_antille...
BQ, CW y SX sí aadieron párr Bonaire, San Eustaquio y Saba, Curazao y Sint Maarten (neerlandesa parte) en el Caribe.
Dev Anand
El Jueves, 10 de julio 2014 a las 08:47 AM, Carlton Samuels < carlton.samuels@gmail.com> escribi:
Closely reasoned and from the principle of cc assignment certainly worthy of the ALAC's consideration.
While we're at it, lets consider that 3-character country codes are possible.
Giving protection for a future event suggests we have a definite knowledge of country/territory breakdown and thusly, possible code assignment. Tying up all permutations of 2 characters especially when you consider IDNs would be a tough sell.
Carlton ---------'--------''-----
On Jul 10, 2014 2:04 AM, "Dev Anand Teelucksingh" <devtee@gmail.com> wrote:
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
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/83854e2f65.html --]]
_______________________________________________ lac-discuss-es mailing list lac-discuss-es@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es
-- Aida Noblia
participants (2)
-
Aida Noblia -
apisan＠unam.mx