July 2014 - lac-discuss-en - lists.icann.org

Re: [lac-discuss-en] ? = Utf-8 q = 5Blac-discuss-en = 5D_Re_ = 26quot = utf-8 == 3BIntr oducci q = C3 = utf-8 B3n_de_dos_caracteres_de_nombres_de_dominio_en == q _el_Nuevo_gTLD_Namespace???? = 26quot = 3B_Los_comentarios_del_p? == utf-8? q? = C3 = BAblico? =
by devtee＠gmail.com July 22, 2014

July 22, 2014

[[--Translated text (es -> en)--]] Subject: Re:? = Utf-8 q = 5Blac-discuss-en = 5D_Re_ = 26quot = utf-8 == 3BIntr oducci q = C3 = utf-8 B3n_de_dos_caracteres_de_nombres_de_dominio_en == q _el_Nuevo_gTLD_Namespace???? = 26quot = 3B_Los_comentarios_del_p? == utf-8? q? = C3 = BAblico? = From: devtee(a)gmail.com Hello Alberto, I will be attempting to put a draft statement later today or early tomorrow at https://community.icann.org/x/VqzhAg Dev Anand On Tue, July 22, 2014 at 11:14 PM, Alberto Soto <asoto(a)ibero-americano.org> wrote: > Hola Dev, como no recibí respuesta, vuelvo a hacerte la consulta. Este > tema se está tratando en la reunión mensual de ALAC en el día de hoy, y > LACTRALO debería hacer una declaración. > Espero tus comentarios > Saludos cordiales > > Alberto Soto > > -----Mensaje original----- > De: Alberto Soto [mailto:asoto@ibero-americano.org] > Enviado el: lunes, 14 de julio de 2014 01:44 a.m. > Para: 'Dev Anand Teelucksingh'; 'devtee(a)gmail.com' > CC: 'LACRALO discussion list'; '<lac-discuss-es(a)atlarge-lists.icann.org>' > 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 > > 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(a)atlarge-lists.icann.org [mailto: > lac-discuss-en-bounces(a)atlarge-lists.icann.org] 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(a)atlarge-lists.icann.org> > 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(a)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(a)atlarge-lists.icann.org [ > > lac-discuss-en-bounces(a)atlarge-lists.icann.org] en nombre de Aida > > Noblia [ aidanoblia(a)gmail.com] Enviado el: domingo, 13 de julio de > > 2014 10:48 > > Hasta: <lac-discuss-es(a)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(a)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(a)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(a)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(a)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/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(a)atlarge-lists.icann.org > > > > > https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en > > > > > > > > > > > lac-discuss-es mailing list > > > lac-discuss-en(a)atlarge-lists.icann.org > > > https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en > > > > > > > > > [[--Original text (es) http://mm.icann.org/transbot_archive/0f346cd639.html --]]

1 0

Re: [lac-discuss-en] ??? = 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? =
by asoto＠ibero-americano.org July 22, 2014

July 22, 2014

[[--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(a)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(a)ibero-americano.org] Posted on: Monday, July 14, 2014 1:44 a.m. To: 'Dev Anand Teelucksingh'; 'Devtee(a)gmail.com' CC: 'LACRALO discussion list'; ' <lac-discuss-es(a)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(a)atlarge-lists.icann.org [mailto: lac-discuss-en-bounces(a)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(a)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(a)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(a)atlarge-lists.icann.org [ > lac-discuss-en-bounces(a)atlarge-lists.icann.org] en nombre de Aida > Noblia [ aidanoblia(a)gmail.com] Enviado el: domingo, 13 de julio de > 2014 10:48 > Hasta: <lac-discuss-es(a)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(a)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(a)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(a)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(a)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/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(a)atlarge-lists.icann.org > > > > https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en > > > > > > > > lac-discuss-es mailing list > > lac-discuss-en(a)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 --]]

1 0

????? = Iso-8859-1 == q 3A_Regional_Advice_needed_ALS Fwd = iso-8859-1 == q F1o_de_Derecho_y_Nuevas_ _Application_202_Instituto_Paname = iso-8859-1 q = Tecnolog = EDAS?
by hcarrascob＠gmail.com July 22, 2014

July 22, 2014

[[--Translated text (es -> en)--]] Subject:????? = Iso-8859-1 == q 3A_Regional_Advice_needed_ALS Fwd = iso-8859-1 == q F1o_de_Derecho_y_Nuevas_ _Application_202_Instituto_Paname = iso-8859-1 q = Tecnolog = EDAS? From: hcarrascob(a)gmail.com Dear all As you can see we have requested our opinion on this request. I created this wiki page to upload their comments: https://community.icann.org/pages/viewpage.action?pageId=48347994 The deadline is August 3, since 4 forward our opinion. Regards Dear all: As you can see, our review has-been Requested about this application. I created this wiki page to upload your comments: https://community.icann.org/pages/viewpage.action?pageId=48347994 The deadline is August 3th Because of the 4th we will send our opinion. Regards Dear Humberto, On the 23 ^ rd April 2014, we received an application from ALS LACRALO Panameo Institute of Law and New Technologies Please find the form attached Due Diligence, as well as further documentation compiled by Silvia through her Correspondence with the ALS applicant (Bylaws are numbered PDFs) We kindly ask you to Provide Us with the advice for this regional ALS in your capacity as Secretary LACRALO. Your advice will support the ALAC review on this application. ACCORDING to our timeline for ALS applications, the due date for the regional advice is the 04 August 2014. We would like to remind you That the DD form Could Contain sensitive information. Please read the form before sending it off Carefully to third parties. Regards, Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine and Terri Agnew ICANN Policy Staff in support of ALAC E-mail: staff(a)atlarge.icann.org <applewebdata://68497759-1B04-4F9B-84B7-B9445B8F305F/Regards,%20Heidi%20Ullrich,%20Silvia%20Vivanco,%20Matt%20Ashtiani,%20Ariel%20Liang,%20Gisella%20Gruber,%20Nathalie%20Peregrine%20and%20Julia%20Charvolen%20ICANN%20Policy%20Staff%20in%20support%20of%20ALACmailto:staff@atlarge.icann.org> Facebook: www.facebook.com / icann.atlarge < https://www.facebook.com/icann.atlarge> Twitter: @ ICANN_AtLarge < https://twitter.com/ICANN_AtLarge> [[--Original text (es) http://mm.icann.org/transbot_archive/18ee29b62b.html --]]

1 0

Re: [lac-discuss-en] ???? = Utf-8 q = REMINDER 3A_Reuni = C3 = utf-8 == B3n_de_la_inv Itaci q = C3 = utf-8 B3n_/_LACRALO_llamada_mensual_-_Lunes_21_de_jul == q io_2014?? =
by presidencia＠internauta.org.ar July 21, 2014

July 21, 2014

[[--Translated text (es -> en)--]] Subject: Re:???? = Utf-8 q = REMINDER 3A_Reuni = C3 = utf-8 == B3n_de_la_inv Itaci q = C3 = utf-8 B3n_/_LACRALO_llamada_mensual_-_Lunes_21_de_jul == q io_2014?? = From: presidencia(a)internauta.org.ar Please, will be able to call me at +54 223 471-5948? Thanks a lot! * Sergio Salinas Porto Argentina President Internauta Argentina Association of Internet Users <http://www.internauta.org.ar> / CTA <http://ctamdq.org.ar> FLUI-American Federation of Internet Users <http://www.fuilatin.org> facebook: salinasporto <http://www.facebook.com/salinasporto> & sergiosalinasII <http://www.facebook.com/sergiosalinasII> twitter: sergiosalinas <http://twitter.com/sergiosalinas> Google+: Sergio Salinas Porto < https://plus.google.com/104639152443153592254/posts> Hangout: presidencia(a)internauta.org.ar <Hangout%3Apresidencia(a)internauta.org.ar> / Pixelhub: salinasporto <http://pixelhub.me/salinasporto> Youtube: salinasporto <http://www.youtube.com/salinasporto> Skype: internautaargentina Mobi: +54 9 223 5 215819 * * "Ojalpodamos be disobedient, whenever we receive orders that humiliate our conscience or violate our common sense "Eduardo Galeano * > El 21 de julio de 2014, 9:36, <staff(a)atlarge.icann.org> escribió: > > > > > [[--Translated text (en -> es)--]] > > > > Tema: RECORDATORIO: Reunión de la invitación / LACRALO llamada mensual - > > Lunes 21 de julio 2014 > > De: staff(a)atlarge.icann.org > > > > Si necesita una llamada de salida, por favor póngase en contacto con el > > personal de At-Large en staff(a)atlarge.icann.org <mailto: > > staff(a)atlarge.icann.org> con su número preferido. > > > > > > Si Una Llamada NECESITA un su telefono, please PNGasa en contacto Con el > > personal de At-Large en staff(a)atlarge.icann.org <mailto: > > staff(a)atlarge.icann.org> COn Preferido do nmero. > > > > > > > > > > > > > > Queridos todos, > > > > > > > > > > > > > > La siguiente llamada LACRALO mensual está programada para el lunes 21 > > julio 2014 a las 2300 UTC. > > > > > > > > > > > > > > Para otras veces: > > > > > > http://tinyurl.com/mles7d9 > > > > > > > > > > > > > > El proyecto de orden del día (en curso) y la información de la llamada > > está disponible en: > > > > > > https://community.icann.org/x/TJ7hAg > > > > > > > > > > > > > > Adobe Connect: > > > > > > http://icann.adobeconnect.com/lacralo > > > > > > > > > > > > > > > > > > > > > > ID de conferencia: > > > > > > > > > > > > > > EN 1638 > > > > > > > > > > > > > > ES - 1738 > > > > > > > > > > > > > > > > > > > > > > Espacio de trabajo Wiki: > > > > > > https://community.icann.org/x/NJQi > > > > > > > > > > > > > > > > > > > > > > Por favor confirme su línea de salida y el número preferido: > > > > > > staff(a)atlarge.icann.org <mailto:staff@atlarge.icann.org> > > > > > > > > > > > > > > > > > > > > > > Gracias. > > > > > > > > > > > > > > Saludos, > > > > > > Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie > > Peregrine y Terri Agnew > > El personal de ICANN Política en apoyo de ALAC > > E-mail: staff(a)atlarge.icann.org > > > <applewebdata://68497759-1B04-4F9B-84B7-B9445B8F305F/Regards,%20Heidi%20Ullrich,%20Silvia%20Vivanco,%20Matt%20Ashtiani,%20Ariel%20Liang,%20Gisella%20Gruber,% > > > 20Nathalie%20Peregrine%20and%20Julia%20Charvolen%20ICANN%20Policy%20Staff%20in%20support%20of%20ALACmailto:staff@atlarge.icann.org > > > > > Facebook: www.facebook.com / icann.atlarge < > > https://www.facebook.com/icann.atlarge> > > Twitter: @ ICANN_AtLarge < https://twitter.com/ICANN_AtLarge> > > > > > > > > > > > > > > > > > > > > > > > > > > lac-discuss-es mailing list > > > > > > lac-discuss-en(a)atlarge-lists.icann.org <mailto: > > lac-discuss-en(a)atlarge-lists.icann.org> > > > > > > https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en > > _______________________________________________ > > > > > > [[--Original text (es) http://mm.icann.org/transbot_archive/96be375e75.html --]]

1 0

Re: [lac-discuss-en] ???? = Utf-8 q = REMINDER 3A_Reuni = C3 = utf-8 == B3n_de_la_inv Itaci q = C3 = utf-8 B3n_/_LACRALO_llamada_mensual_-_Lunes_21_de_jul == q io_2014?? =
by aidanoblia＠gmail.com July 21, 2014

July 21, 2014

[[--Translated text (es -> en)--]] Subject: Re:???? = Utf-8 q = REMINDER 3A_Reuni = C3 = utf-8 == B3n_de_la_inv Itaci q = C3 = utf-8 B3n_/_LACRALO_llamada_mensual_-_Lunes_21_de_jul == q io_2014?? = From: aidanoblia(a)gmail.com Dear all I request call 59829023380 or 59898456389 Greetings and Thanks The July 21, 2014, 9:36, <staff(a)atlarge.icann.org> I wrote: > > [[--Translated text (en -> es)--]] > > Tema: RECORDATORIO: Reunión de la invitación / LACRALO llamada mensual - > Lunes 21 de julio 2014 > De: staff(a)atlarge.icann.org > > Si necesita una llamada de salida, por favor póngase en contacto con el > personal de At-Large en staff(a)atlarge.icann.org <mailto: > staff(a)atlarge.icann.org> con su número preferido. > > > Si Una Llamada NECESITA un su telefono, please PNGasa en contacto Con el > personal de At-Large en staff(a)atlarge.icann.org <mailto: > staff(a)atlarge.icann.org> COn Preferido do nmero. > > > > > > > Queridos todos, > > > > > > > La siguiente llamada LACRALO mensual está programada para el lunes 21 > julio 2014 a las 2300 UTC. > > > > > > > Para otras veces: > > > http://tinyurl.com/mles7d9 > > > > > > > El proyecto de orden del día (en curso) y la información de la llamada > está disponible en: > > > https://community.icann.org/x/TJ7hAg > > > > > > > Adobe Connect: > > > http://icann.adobeconnect.com/lacralo > > > > > > > > > > > ID de conferencia: > > > > > > > EN 1638 > > > > > > > ES - 1738 > > > > > > > > > > > Espacio de trabajo Wiki: > > > https://community.icann.org/x/NJQi > > > > > > > > > > > Por favor confirme su línea de salida y el número preferido: > > > staff(a)atlarge.icann.org <mailto:staff@atlarge.icann.org> > > > > > > > > > > > Gracias. > > > > > > > Saludos, > > > Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie > Peregrine y Terri Agnew > El personal de ICANN Política en apoyo de ALAC > E-mail: staff(a)atlarge.icann.org > <applewebdata://68497759-1B04-4F9B-84B7-B9445B8F305F/Regards,%20Heidi%20Ullrich,%20Silvia%20Vivanco,%20Matt%20Ashtiani,%20Ariel%20Liang,%20Gisella%20Gruber,% > 20Nathalie%20Peregrine%20and%20Julia%20Charvolen%20ICANN%20Policy%20Staff%20in%20support%20of%20ALACmailto:staff@atlarge.icann.org > > > Facebook: www.facebook.com / icann.atlarge < > https://www.facebook.com/icann.atlarge> > Twitter: @ ICANN_AtLarge < https://twitter.com/ICANN_AtLarge> > > > > > > > > > > > > > lac-discuss-es mailing list > > > lac-discuss-en(a)atlarge-lists.icann.org <mailto: > lac-discuss-en(a)atlarge-lists.icann.org> > > > https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en > _______________________________________________ > > > [[--Original text (es) http://mm.icann.org/transbot_archive/39844252c9.html --]]

1 0

REMINDER: Meeting Invitation/ LACRALO monthly call - Monday 21 July 2014
by ICANN At-Large Staff July 21, 2014

July 21, 2014

If you require a dial-out please contact At-Large staff at staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> with your preferred number. Si necesita una llamada a su telefono, por favor póngase en contacto con el personal de At-Large en staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> con su número preferido. Dear All, The next monthly LACRALO call is scheduled on Monday 21 July 2014 at 2300 UTC. For other times: http://tinyurl.com/mles7d9 The draft agenda (in progress) and call details are available at: https://community.icann.org/x/TJ7hAg Adobe Connect: http://icann.adobeconnect.com/lacralo Conference ID: EN 1638 ES - 1738 Wiki workspace: https://community.icann.org/x/NJQi Please confirm your dial-out and preferred number to: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Regards, Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine and Terri Agnew ICANN Policy Staff in support of ALAC E-mail: staff(a)atlarge.icann.org<applewebdata://68497759-1B04-4F9B-84B7-B9445B8F305F/Regards,%20Heidi%20Ullrich,%20Silvia%20Vivanco,%20Matt%20Ashtiani,%20Ariel%20Liang,%20Gisella%20Gruber,%20Nathalie%20Peregrine%20and%20Julia%20Charvolen%20ICANN%20Policy%20Staff%20in%20support%20of%20ALACmailto:staff@atlarge.icann.org> Facebook: www.facebook.com/icann.atlarge<https://www.facebook.com/icann.atlarge> Twitter: @ICANN_AtLarge<https://twitter.com/ICANN_AtLarge> lac-discuss-en mailing list lac-discuss-en(a)atlarge-lists.icann.org<mailto:lac-discuss-en@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en

1 0

The rise of data and the death of politics
by José Francisco Arce July 20, 2014

July 20, 2014

FYI http://www.theguardian.com/technology/2014/jul/20/rise-of-data-death-of-pol…

1 0

Re: [lac-discuss-en] LACIGF 2014 - El Salvador
by natalia.enciso＠gmail.com July 19, 2014

July 19, 2014

[[--Translated text (es -> en)--]] Subject: Re: LACIGF 2014 - El Salvador From: natalia.enciso(a)gmail.com Congratulations to Gilberto, Fátima and Jospor the organization. What seguremotamente and truth has evolucinq note the forum in each edition. Continue the successes and work for the region. Regards, Natalia Sent from my iPhone > El 18/07/2014, a las 20:05, Vanda Scartezini <vanda(a)uol.com.br> escribió: > > It was really great! Personally I had a chance to congratulate them all. > It was very good and excellent organisation. All perfect. And the > technical results also very good. > Felicitaciones a todo, a Fatima e Olga en especial! > Abrazos a todos desde San Salvador. > Vanda Scartezini > Polo Consultores Associados > Av. Paulista 1159, cj 1004 > 01311-200- Sao Paulo, SP, Brazil > Land Line: +55 11 3266.6253 > Mobile: + 55 11 98181.1464 > > > > > > > > On 7/18/14, 16:57, "José Francisco Arce" <josefranciscoarce(a)gmail.com> > wrote: > >> Estimados, >> >> Terminado el Lacigf 2014, no me queda otra alternativa que felicitar a >> todo >> el equipo de "Conexión" por el increíble trabajo realizado. Y a todo el >> comité de programa (del cual tuve el honor de formar parte) por superarse >> año a año. >> >> Un saludo especial a Gilberto, Lito y todos los Salvadoreños !!! >> >> Saludos >> >> -- >> Arce, José F. >> http://lnkd.in/bPdTThz >> _______________________________________________ >> lac-discuss-es mailing list >> lac-discuss-es(a)atlarge-lists.icann.org >> https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es >> >> http://www.lacralo.org > > > _______________________________________________ > lac-discuss-es mailing list > lac-discuss-es(a)atlarge-lists.icann.org > https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es > > http://www.lacralo.org [[--Original text (es) http://mm.icann.org/transbot_archive/6ea8141d2c.html --]]

1 0

Re: [lac-discuss-en] [lac-discuss-es] LACIGF 2014 - El Salvador
by Vanda Scartezini July 19, 2014

July 19, 2014

It was really great! Personally I had a chance to congratulate them all. It was very good and excellent organisation. All perfect. And the technical results also very good. Felicitaciones a todo, a Fatima e Olga en especial! Abrazos a todos desde San Salvador. Vanda Scartezini Polo Consultores Associados Av. Paulista 1159, cj 1004 01311-200- Sao Paulo, SP, Brazil Land Line: +55 11 3266.6253 Mobile: + 55 11 98181.1464 On 7/18/14, 16:57, "José Francisco Arce" <josefranciscoarce(a)gmail.com> wrote: >Estimados, > >Terminado el Lacigf 2014, no me queda otra alternativa que felicitar a >todo >el equipo de "Conexión" por el increíble trabajo realizado. Y a todo el >comité de programa (del cual tuve el honor de formar parte) por superarse >año a año. > >Un saludo especial a Gilberto, Lito y todos los Salvadoreños !!! > >Saludos > >-- >Arce, José F. >http://lnkd.in/bPdTThz >_______________________________________________ >lac-discuss-es mailing list >lac-discuss-es(a)atlarge-lists.icann.org >https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es > >http://www.lacralo.org

2 1

Re: [lac-discuss-en] LACIGF 2014 - El Salvador
by vanda＠uol.com.br July 19, 2014

July 19, 2014

[[--Translated text (es -> en)--]] Subject: Re: LACIGF 2014 - El Salvador From: vanda(a)uol.com.br It was really great! Personally I had a chance to congratulate them all. It was very good and excellent organization. All perfect. And the also very good technical results. Congratulations to all, especially Fatima and Olga! Hugs to all from San Salvador. Vanda Scartezini Polo Consultores Associados Av Paulista 1159, 1004 cj 01311-200 - Sao Paulo, SP, Brazil Land Line: +55 11 3266.6253 Mobile: + 55 11 98181.1464 On 7/18/14, 16:57, "Arce JosFrancisco" <josefranciscoarce(a)gmail.com> wrote: > Dear, > > After the Lacigf 2014, I have no alternative but to congratulate > All > Team "connection" for the incredible work.And all the > Comitde program (I had the honor of being part of that) to excel > Aoaao. > > Special thanks to Gilberto, Lito and all Salvadorans! Greeting! > > Greetings > > - > Arce, JosF. > Http://lnkd.in/bPdTThz > _______________________________________________ > Lac-discuss-en mailing list > Lac-discuss-es(a)atlarge-lists.icann.org > https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es > > Http://www.lacralo.org _______________________________________________ [[--Original text (es) http://mm.icann.org/transbot_archive/d464d18755.html --]]

1 0