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

Change Whois
by asoto＠ibero-americano.org July 14, 2014

July 14, 2014

[[--Translated text (es -> en)--]] Subject: Change Whois From: asoto(a)ibero-americano.org Dear, transcribe an article by Carlton Samuels, concise and enlightening Directory of Services for Generic Top-Level Domains (GTLD) from ICANN. Who wants to see the full report of WG, the end is the corresponding link. Best Regards Alberto Soto It's time to implement a paradigm shift By Carlton Samuels, Member of the Expert Working Group (EWG) on Services Directory for Generic Top Level Domains (gTLDs) ICANN. Aces as the Expert Working Group (EWG) on services Directory gTLD characterized its recommendations in its final report, the which proposes a new generation service, the Service Directory Check (RDS for its acronym in english). In its final report of 166 pages, the EWG recommends replacing the WHOIS problemtico model that is used today in giving, offering so and universal access to information users annimos registration of Generic top level domains (gTLD), which in turn is often inaccurate. Instead of this model, and after 15 months of study, the EWG report recommends a new system in which the basic data remains publicly available only while the rest will be accessible to duly registered applicants, who must be identified, state the purpose of your inquiry and accept responsibility for the use of such information. For over a decade, the system has generated WHOIS within the ICANN community insurmountable controversy. Although all were agree that the system improvements requera drsticas, had little agreement As for culture will be the best way to implement these improvements. ICANN CEO, Fadi Chehad, creel Working Group of Experts request of the Board in order to find a replacement for the current system. The EWG comenzsu work from scratch, questioning assumptions fundamental about the objectives, uses, recoleccin, maintenance and provisin of log data. The group considers each stakeholders, their needs for safety, access and data privacy, in addition to possible approaches to meet these needs effectively. The new system estdiseado to address problems privacy and the degradation of the quality of the data and, in turn, achieves a difficult balance between access and accountability. In making its revision, the EWG analiz2600 pblicos pages of comments, surveys and feasibility studies, many of whom identified WHOIS deficiencies. In its final report, the EWG leave the WHOIS standard (one-size-fits-all) used today in favor of a given model validated data access for YOU SPECIFIC propsitos hoping this will help improve privacy and accuracy of the data and the responsibility for them. The proposed system searches for the group: Provide adequate access to registration information accurate, reliable and uniform. Protecting the privacy of personal information. Enable a reliable mechanism to identify, establish and maintain ability to contact registrants. Support a framework for addressing issues related to registrants, including but not limited to the protection of the consumer, investigation of cybercrime and the protection of property intellectual. Provide adequate infrastructure to meet the law enforcement requirements. The EWG says its final report proveeruna solid foundation to help the ICANN community (a Travs of Names Supporting Organization Generic, GNSO) to create a new global policy to services directory for Generic Top-Level Domains (gTLDs). The final report of the Expert Working Group was given the CEO and ICANN Board and community serconsiderado now. The EWG responderpreguntas and escucharcomentarios on your report for several sessions of the meeting will take place ICANN50 that in London 22 to 26 June. The Final Report of the Expert Working Group on Services Directory gTLD (EWG) estdisponible here: https://www.icann.org/en/system/files/files/final-report-06jun14-en.pdf - See more at: http://prensa.lacnic.net/news/14junio_es/es-hora-de-implementar-un-cambio-de -Paradigm # sthash.TGt5qbqJ.dpuf _______________________________________________ [[--Original text (es) http://mm.icann.org/transbot_archive/a2c5587e3f.html --]]

1 0

Re: [lac-discuss-en] ? = Utf-8 Invitation-q = C3 = C3 = B3n_/_LACRALO B3n_Reuni = utf-8 == q = _llamada_mensual_-_Lunes_21_de_julio_2014???
by javierjosepallero＠gmail.com July 14, 2014

July 14, 2014

[[--Translated text (es -> en)--]] Subject: Re:? = Utf-8 Invitation-q = C3 = C3 = B3n_/_LACRALO B3n_Reuni = utf-8 == q = _llamada_mensual_-_Lunes_21_de_julio_2014??? From: javierjosepallero(a)gmail.com Friends of the staff. I confirm my attendance to the channel in Spanish and request call +549 3513455126 Greetings. Javier J. Pallero http://about.me/javierpallero <http://www.linkedin.com/in/javierpallero> On July 8, 2014, 14:57, <staff(a)atlarge.icann.org> I wrote: > > [[--Translated text (en -> es)--]] > > Asunto: Invitación Reunión / LACRALO llamada mensual - Lunes 21 de julio > 2014 > De: staff(a)atlarge.icann.org > > 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 (que se debe actualizar) y detalles de > llamadas están disponibles 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/6866d53b39.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 14, 2014

July 14, 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 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, 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/0ce347dab8.html --]]

1 0

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 aidanoblia＠gmail.com July 13, 2014

July 13, 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: aidanoblia(a)gmail.com Alejandro agreement. I think it will be not cumplliendo ISO. Accepted that the end user will be little protection, because it results 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+Introduction+of+… > : > > 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+Introduction+of+… > : > > 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_antill… > > > > > > 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/country_c… > > > > ). > > > > > > > > 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/15cf0dd22e.html --]]

1 0

Re: [lac-discuss-en] ??????????? = 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? =
by aidanoblia＠gmail.com July 12, 2014

July 12, 2014

[[--Translated text (es -> en)--]] Subject: 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? = From: aidanoblia(a)gmail.com I totally agree that you can not make a release generic. We must defend equality for potential new country code. Very important clarifications and warnings Dev too. It is subject of the whole community, beyond the group is directly ccTLD involved. We will have to make a declaration. The GAC also you might have to say on this. Regards 07.12.2014 8:37 GMT-03: 00 <apisan(a)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(a)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(a)atlarge-lists.icann.org [ > lac-discuss-es-bounces(a)atlarge-lists.icann.org] en Nombre de > devtee(a)gmail.com [devtee(a)gmail.com] > Enviado el: viernes, 11 de julio de 2014 07:59 > Hasta: lac-discuss-es(a)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(a)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_antill… > > > > > 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(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/country_c… > > > ). > > > > > > 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-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/34ec3faff5.html --]]

1 0

Re: [lac-discuss-en] [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? =
by Aida Noblia July 12, 2014

July 12, 2014

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(a)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(a)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(a)atlarge-lists.icann.org [ > lac-discuss-es-bounces(a)atlarge-lists.icann.org] en Nombre de > devtee(a)gmail.com [devtee(a)gmail.com] > Enviado el: viernes, 11 de julio de 2014 07:59 > Hasta: lac-discuss-es(a)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(a)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_antill… > > > > > 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(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/country_c… > > > ). > > > > > > 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-en(a)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(a)atlarge-lists.icann.org > https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es > > http://www.lacralo.org > -- Aida Noblia

1 0

Re: [lac-discuss-en] Re "Introducción de dos caracteres de nombres de dominio en el Nuevo gTLD Namespace" Los comentarios del público
by Dr. Alejandro Pisanty Baruch July 12, 2014

July 12, 2014

Dev, gracias por esta valiosa información. El mundo de las iniciales de dos letras es más móvil que lo que se piensa frecuentemente; y los cambios son trascendentales, cuando se presentan. Por esto este tema debe interesar a aquellos colegas de LACRALO que han dado importancia a temas territoriales. Sólo con su iniciativa será posible que nuestra comunidad emprenda algo en el tema. 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-es-bounces(a)atlarge-lists.icann.org [lac-discuss-es-bounces(a)atlarge-lists.icann.org] en nombre de devtee(a)gmail.com [devtee(a)gmail.com] Enviado el: viernes, 11 de julio de 2014 07:59 Hasta: lac-discuss-es(a)atlarge-lists.icann.org CC: LACRALO discussion list Asunto: Re: Re "Introducción de dos caracteres de nombres de dominio en el Nuevo gTLD Namespace" Los comentarios del público [[--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_antill… 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/country_c… > > ). > > > > 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 (en) http://mm.icann.org/transbot_archive/2fe20b851c.html --]]

1 0

Re: [lac-discuss-en] ? = Iso-8859-1 q = Re_ = 26quot F3n_de_do == 3BIntroducci = iso-8859-1 == q s_caracteres_de_nombres_de_dominio_en_el_Nuevo_gTLD_Namesp iso-8859-1 q = ace = 26quot???? 3B_Los_comentarios_del_p = FAblico? =
by apisan＠unam.mx July 12, 2014

July 12, 2014

[[--Translated text (es -> en)--]] Subject: Re:? = Iso-8859-1 q = Re_ = 26quot F3n_de_do == 3BIntroducci = iso-8859-1 == q s_caracteres_de_nombres_de_dominio_en_el_Nuevo_gTLD_Namesp iso-8859-1 q = ace = 26quot???? 3B_Los_comentarios_del_p = FAblico? = From: apisan(a)unam.mx Dev thanks for this valuable information. The World of the initial two letters is msmvil what is often thought; and changes are momentous, when present. Therefore this issue should interest those LACRALO colleagues who have given importance to territorial issues. Slo your serposible our community initiative undertake something in the subject. Alejandro Pisanty --------------------------- Dr. Alejandro Pisanty UNAM Faculty of Chemistry 3000 University Avenue, 04510 Mexico DF Mexico +52-1-5541444475 FROM ABROAD SMS +525541444475 +525541444475 FROM MEXICO Blog: http://pisanty.blogspot.com LinkedIn: http://www.linkedin.com/in/pisanty Join the LinkedIn group UNAM, http://www.linkedin.com/e/gis/22285/4A106C0C8614 Twitter: http://twitter.com/apisanty ---- >> Join ISOC Mexico, http://www.isoc.org . . . . . . . . . . . . . . . . ________________________________________ From: lac-discuss-es-bounces(a)atlarge-lists.icann.org [lac-discuss-es-bounces(a)atlarge-lists.icann.org] on behalf of devtee(a)gmail.com [devtee(a)gmail.com] Posted on: Friday, July 11, 2014 7:59 To: lac-discuss-es(a)atlarge-lists.icann.org CC: LACRALO discussion list Subject: Re: Re "Introduction of two-character domain names in the new gTLD Namespace" Comments from the public [[- Translated text (en -> en) -]] Subject: Re: Re "Introduction of two-character domain names in the new gTLD Namespace" Comments from the public From: devtee(a)gmail.com Well, there may be only a fixed number of permutations (676) for possible used in ISO 3166 from ISO 3166 can only be ASCII letters AA to ZZ. And While it may not be a fast number of changes, there have been changes ISO 3166 in the last 10 years. For example, in 2010, for example: http://www.iso.org/iso/iso_3166-1_newsletter_vi-8_split_of_the_dutch_antill… BQ, CW and SX aadieron for Bonaire, St. Eustatius and Saba, Curaao and Sint Maarten (Dutch part) in the Caribbean. Dev Anand On Thursday, July 10, 2014 at 8:47 PM, Carlton Samuels <carlton.samuels(a)gmail.com> I wrote: > 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/country_c… > > ). > > > > 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-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/b2683cd3a9.html --]]

1 0

Re "Introduction of Two-Character Domain Names in the New gTLD Namespace" Public comment
by Dev Anand Teelucksingh July 11, 2014

July 11, 2014

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_c… ). 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

3 3

Re: [lac-discuss-en] = iso-8859-1 q = Re_ = 26quot F3n_de_do == 3BIntroducci = iso-8859-1 == q s_caracteres_de_nombres_de_dominio_en_el_Nuevo_gTLD iso-8859-1 q = 26quot = _Namespace????? 3B_Los_comentarios_del_p = FAblico? =
by asoto＠ibero-americano.org July 10, 2014

July 10, 2014

[[--Translated text (es -> en)--]] Subject: Re: = iso-8859-1 q = Re_ = 26quot F3n_de_do == 3BIntroducci = iso-8859-1 == q s_caracteres_de_nombres_de_dominio_en_el_Nuevo_gTLD iso-8859-1 q = 26quot = _Namespace????? 3B_Los_comentarios_del_p = FAblico? = From: asoto(a)ibero-americano.org From what I saw, ESTN GenRich asking for deliverance. I agree with Lance you can not make a general reservation, but also no liberation general. MUST ask especfica liberation, with the justification corresponding. Best Regards Alberto Soto ----- Original Message ----- From: lac-discuss-es-bounces(a)atlarge-lists.icann.org [Mailto: lac-discuss-es-bounces(a)atlarge-lists.icann.org] On Behalf Of devtee(a)gmail.com Posted on: Thursday, July 10, 2014 3:06 a.m. To: lac-discuss-es(a)atlarge-lists.icann.org Subject: Re "Introduction of two-character domain names in the New gTLD Namespace "Comments from the public [[- Translated text (en -> en) -]] Subject: Re "Introduction of two-character domain names in the New gTLD Namespace "Comments from the public From: devtee(a)gmail.com As for public comment on "Introduction of two character domain name in the New gTLD namespace "in https://community.icann.org/x/VqzhAg ending July 10, 2014, I posted the following on https://community.icann.org/x/VqzhAg for consideracin: "Several records for multiple gTLDs ESTN requesting exceptions to Specification 5, Section 2 to the new gTLD registry ("Specification for the 5") with some records suggesting 2 liberation ASCII character tags are not in the ISO standard Current 3166 will suffice. While this seems harmless, there is a possibility of new countries and territories are created, and then assign a new two ASCII characters ISO 3166/MA label (see https://web.archive.org/web/20111101141651/http://www.iso.org/iso/country_co des/iso-3166-1_decoding_table.htm ). Any new step territory created after 2014, therefore no receive the same protection as those in the ISO 3166-2 list 2014 find your new character label 2 "gives" if aslo want for your label 2 ASCII characters to protect, according to the specification 5. Now, if the principle set out in the Specification for the protection May 2 ESTN an ASCII character tags in the registry agreement for new gTLDs? Many will say, especially given the prevalence of the two Character tags in existing TLDs, such as. com,. org and. net this principle should not be applied to new gTLDs. However, this (IMO) is a separate issue from the question being asked in the the public comment. If Specification for the 5 estdestinado to defend the principle that ISO 3166-2 codes of passes must be protected in the new gTLDs, then you must meet to ensure that future passes and territories with new tags 2 ASCII characters ESTN protected in the same how territories and countries in the current ISO 3166-2 list. Therefore, the proposals of Donuts of 143 of their new gTLDs. Kred by KredTLD Pty Ltd,. Best Pty Ltd and by BestTLD. Ceo for CEOTLD Pty Ltd. must be rejected in accordance with the principle of specification 5. The proposed. Wiki for Top Level Design LLC, which specifies that the two ASCII character tags are only for languages \u200b\u200butilizarn sealados by ISO 639-1 sparece meet the threshold should not be confused use with the codes of the respective countries, according to the 5 specification may be approved. Similarly, the proposal. Globo Globo Comunicaoe Participaes SA the utilization of two ASCII characters labels is proposed that no letters are or two characters that only one character is a letter labels are I will not used by ISO 3166-2 and may be approved. " Thoughts? Best 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 [[--Original text (es) http://mm.icann.org/transbot_archive/f0985622c7.html --]]

1 0