[[--Translated text (es -> en)--]] Subject: Re:??? = Utf-8 q = 5Blac-discuss-en = 5D = 09Re_ = 26quot = utf-8 == 3BIn troducci q = C3 = utf-8 B3n_de_dos_caracteres_de_nombres_de_dominio_ == q?? ? en_el_Nuevo_gTLD_Namespace = 26quot = 3B_Los_comentarios_del? == utf-8? b? IHDDumJsaWNv? = From: asoto@ibero-americano.org Hi Dev, as recibrespuesta, back to make the query. This topic esttratando the monthly reunin ALAC in for today, and should make a declaration LACTRALO. I hope your comments Best Regards Alberto Soto ----- Original Message ----- From: Alberto Soto [mailto: asoto@ibero-americano.org] Posted on: Monday, July 14, 2014 1:44 a.m. To: 'Dev Anand Teelucksingh'; 'Devtee@gmail.com' CC: 'LACRALO discussion list'; ' <lac-discuss-es@atlarge-lists.icann.org> ' Subject: RE: [lac-discuss-en] Re "Introduction of two-character domain names in the new gTLD Namespace" Comments from the public Dev, I think I know this subject in depth, and we've already opinin oriented one, and hope there will be more comments. Nevertheless, ABLE please prepare a draft declaration of LACRALO? Thank you! Best Regards Alberto Soto ----- Original Message ----- From: lac-discuss-en-bounces@atlarge-lists.icann.org [mailto: lac-discuss-en-bounces@atlarge-lists.icann.org] On Behalf Of Aida Noblia Posted on: Sunday, July 13 from 2014 2:00 pm To: Dr. Alejandro Pisanty Baruch CC: LACRALO discussion list; <lac-discuss-es@atlarge-lists.icann.org> Subject: Re: [lac-discuss-en] Re "Introduction of two-character domain names in the new gTLD Namespace" Comments from the public Alejandro agreement. I think it will be not cumplliendo ISO. Accepted that the end user will be little protection, because it leads to many conflicts. Regards 7/13/2014 13:19 GMT-03: 00 Dr. Alejandro Pisanty Baruch <apisan@unam.mx> :
Aída,
brevemente y para complementar tu análisis: el acuerdo con el país y el operador no pueden existir sino hasta que sea creada una nueva entidad.
En ese sentido se protegerían todas las combinaciones de dos caracteres alfabéticos ya que es imposible predecir cuáles entidades territoriales serían creadas en un futuro indefinido, y menos aún qué códigos les serían asignados.
Bajo .globo (es decir, **EN NUESTRA REGIÓN**) se propone liberar tanto los códigos de dos letras como los formados por una letra y un dígito. ¿Qué consecuencias puede tener esto? (la primera que me viene a la mente es la colisión con una marca de salsa para carne asada tipo "barbeque", A1).
Alejandro Pisanty
- - - - - - - - - - - - - - - - - - - - - - - - - - - Dr. Alejandro Pisanty Facultad de Química UNAM Av. Universidad 3000, 04510 Mexico DF Mexico
+52-1-5541444475 FROM ABROAD
+525541444475 DESDE MÉXICO 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 Mexico, http://www.isoc.org . . . . . . . . . . . . . . . .
________________________________________ Desde: lac-discuss-en-bounces@atlarge-lists.icann.org [ lac-discuss-en-bounces@atlarge-lists.icann.org] en nombre de Aida Noblia [ aidanoblia@gmail.com] Enviado el: domingo, 13 de julio de 2014 10:48 Hasta: <lac-discuss-es@atlarge-lists.icann.org> CC: LACRALO discussion list Asunto: Re: [lac-discuss-en] Re "Introducción de dos caracteres de nombres de dominio en el Nuevo gTLD Namespace" Los comentarios del público
La pregunta de DEV que focaliza el tema, dice que hay que ver:
"Si Especificación 5 está destinado a defender el principio de que los códigos de países ISO 3166-2 debe ser protegida en los nuevos gTLD, entonces se debe cumplir al asegurar que los países y territorios futuras con nuevas etiquetas de 2 caracteres ASCII están protegidos de la misma manera como los territorios y países en la actual.
La especificación 5 está transcripta en el sitio
https://community.icann.org/display/alacpolicydev/At-Large+Introductio n+of+Two-Character+Domain+Names+in+the+New+gTLD+Namespace+Workspace :
Dicha Especificación 5 dice:
"Todas las etiquetas de dos caracteres ASCII quedarán excluidas de la inscripción o asignación to Registry operador en el segundo nivel en el TLD. Dichas etiquetas pueden no estar activadas en el DNS, y no podrán ser liberados para el registro a cualquier persona o entidad que no sea operador de registro, siempre que dichas cadenas de etiquetas de dos caracteres pueden ser liberados en la medida en que el operador de registro alcanza un acuerdo con el gobierno relacionada y el gerente de código de país de la cadena como se especifica en the ISO 3166-1 alpha-2. El Operador de Registro También podrá proponer la liberación de estas reservas con base en la aplicación de medidas para evitar la confusión con los códigos de los países correspondientes, con sujeción a la aprobación de la ICANN."
Es claro que la redacción de esta cláusula es restrictiva. Tiene además exigencias que no ví que se hayan cumplido: Falta el acuerdo con el gobierno relacionado y con el gerente del código país de la cadena. Además tampoco aparece cumplido las medidas que aplicarán en cada país para evitar la confusión con los códigos de los países como lo pide la norma.
Entiendo además que el pedido de todas las cadenas indiscriminadamente, como es el pedido hecho, no está contemplado en la norma. Es una norma restrictiva y supone que se pide para un país y no globalmente.
La especificacion 5 es netamente protectora en primer lugar de los codigos pais. Admite solo por excepcion y con muchos requisitos, con el acuerdo del propio pais ademas. El criterio es claramente de dar prevalencia al dominio pais. Exige que ademas de cumplirse los requisitos anteriores se presenten medidas para evitar la confusion con el propio pais. Es muy restrictivo y da una proteccion muy estricta a los codigos pais.
Desde el punto de vista del usuario final el codigo pais en Internet es cada vez más importante por el sentido de identidad de un pueblo, de una idiosincracia, de un paradigma, también respecto hacia su persona y su país. Algo así como la bandera de cada país. Esto afirma la confianza en lo global a traves del reconocimiento de lo local como parte y dentro de lo global.
Saludos Aída
PD Por el momento no pude entrar en la wiki . Parece que es el sistema.. en cuanto pueda lo agrego
DEV The question that focuses the subject and then transcribe says to see:
If Specification 5 is intended to defend the principle that the ISO 3166-2 country codes must be protected in the new gTLDs, then you must meet to ensure that countries and future territories with new tags 2 ASCII characters are protected from same way as the regions and countries in today.
Specification 5 is transcribed at the site
https://community.icann.org/display/alacpolicydev/At-Large+Introductio n+of+Two-Character+Domain+Names+in+the+New+gTLD+Namespace+Workspace :
This Specification 5 says:
"All the labels of two ASCII characters will be excluded from enrollment or assignment to Registry Operator in the second level in the TLD. Such labels may not be active in the DNS, and may not be delivered for registration to any person or entity not registry operator if such label strings two characters may be it released to the extent that the Registry Operator reaches agreement with the related government and the head of country code string as specified in the ISO 3166-1 alpha-2. Registry Operator may also propose release of these reservations based on the introduction of measures to avoid confusion with the codes of the countries concerned, subject to the approval of ICANN. "
It is clear that the wording of this clause is restrictive. It also has not revealed requirements are met: Missing accordance with the related government and the country manager of the chain code. Also appears not fulfilled the measures applied in each country to avoid confusion with country codes as required by the standard.
I further understand that the request for all brands indiscriminately, as is done request is not covered by the standard. It is a restrictive rule and assumes that calls to a country and not globally.
Specification 5 is the first purely protective of country codes. Allowed only by exception and with many requirements, with the agreement of the country besides himself. The criterion is clearly to give prevalence to the country domain. Demands that also met the above requirements presented measures to avoid confusion with the country itself. It is very restrictive and gives a very strict protection for country codes.
From the point of view of the end user country code on the Internet is increasingly important for the sense of identity of a people, an idiosyncrasy, a paradigm, also with regard to himself and his country. Something like the flag of each country. This affirms confidence in global recognition through the local as part and within the global.
2014-07-11 9:59 GMT-03:00 <devtee@gmail.com>:
[[--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: devtee@gmail.com
Bueno, sólo puede haber un número fijo de permutaciones (676) para su posible utilizar en la norma ISO 3166 desde ISO 3166 sólo puede ser letras ASCII de AA a ZZ. Y Si bien puede no ser un número rápido de cambios, se han producido cambios ISO 3166 en los últimos 10 años.
Por ejemplo, en 2010, por ejemplo:
http://www.iso.org/iso/iso_3166-1_newsletter_vi-8_split_of_the_dutch_a ntilles_final-en.pdf
BQ, CW y SX se añadieron para Bonaire, San Eustaquio y Saba, Curaçao y Sint Maarten (parte neerlandesa) en el Caribe.
Dev Anand
El Jueves, 10 de julio 2014 a las 8: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
).
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
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
https://web.archive.org/web/20111101141651/http://www.iso.org/iso/coun try_codes/iso-3166-1_decoding_table.htm 5. 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-es mailing list lac-discuss-en@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en
[[--Original text (es) http://mm.icann.org/transbot_archive/99ee0243a0.html --]]