Re: [lac-discuss-en] Re "IntroducciÃn de dos caracteres de nombres de dominio en el Nuevo gTLD Namespace" Los comentarios del pÃblico
- To: "'Dev Anand Teelucksingh'" <admin@xxxxxxxxxxx>, <devtee@xxxxxxxxx>
- Subject: Re: [lac-discuss-en] Re "IntroducciÃn de dos caracteres de nombres de dominio en el Nuevo gTLD Namespace" Los comentarios del pÃblico
- From: "Alberto Soto" <asoto@xxxxxxxxxxxxxxxxxxx>
- Date: Mon, 14 Jul 2014 01:43:51 -0300
Dev, creo que conoces este tema en profundidad, y ya hemos orientado una
opiniÃn, y esperamos que haya mÃs comentarios. Pese a ello, podrÃas por favor
preparar un proyecto de declaraciÃn de LACRALO?
Gracias!
Saludos cordiales
Alberto Soto
-----Mensaje original-----
De: lac-discuss-en-bounces@xxxxxxxxxxxxxxxxxxxxxxx
[mailto:lac-discuss-en-bounces@xxxxxxxxxxxxxxxxxxxxxxx] En nombre de Aida Noblia
Enviado el: domingo, 13 de julio de 2014 02:00 p.m.
Para: Dr. Alejandro Pisanty Baruch
CC: LACRALO discussion list; <lac-discuss-es@xxxxxxxxxxxxxxxxxxxxxxx>
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
De acuerdo Alejandro. Creo que no se estarÃa cumplliendo la norma ISO.
De aceptarse esto el usuario final estarÃa poco protegido, porque da lugar a
muchos conflictos.
Saludos
2014-07-13 13:19 GMT-03:00 Dr. Alejandro Pisanty Baruch <apisan@xxxxxxx>:
> 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@xxxxxxxxxxxxxxxxxxxxxxx [
> lac-discuss-en-bounces@xxxxxxxxxxxxxxxxxxxxxxx] en nombre de Aida
> Noblia [ aidanoblia@xxxxxxxxx] Enviado el: domingo, 13 de julio de
> 2014 10:48
> Hasta: <lac-discuss-es@xxxxxxxxxxxxxxxxxxxxxxx>
> 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@xxxxxxxxx>:
>
> >
> > [[--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@xxxxxxxxx
> >
> > 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@xxxxxxxxx>
> > 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@xxxxxxxxx>
> > > 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/coun
> try_codes/iso-3166-1_decoding_table.htm
> > > > ).
> > > >
> > > > 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@xxxxxxxxxxxxxxxxxxxxxxx
> > > > https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en
> > >
> > >
> > lac-discuss-es mailing list
> > lac-discuss-en@xxxxxxxxxxxxxxxxxxxxxxx
> > https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en
> >
> >
> >
> > [[--Original text (en)
> > http://mm.icann.org/transbot_archive/2fe20b851c.html
> > --]]
> >
> >
> >
> > _______________________________________________
> > lac-discuss-es mailing list
> > lac-discuss-es@xxxxxxxxxxxxxxxxxxxxxxx
> > https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es
> >
> > http://www.lacralo.org
> >
>
>
>
> --
> Aida Noblia
> _______________________________________________
> lac-discuss-en mailing list
> lac-discuss-en@xxxxxxxxxxxxxxxxxxxxxxx
> https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en
>
--
Aida Noblia
_______________________________________________
lac-discuss-en mailing list
lac-discuss-en@xxxxxxxxxxxxxxxxxxxxxxx
https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en
_______________________________________________
lac-discuss-en mailing list
lac-discuss-en@xxxxxxxxxxxxxxxxxxxxxxx
https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en