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

Re: [lac-discuss-en] ? = Utf-8 q = 3A_Nueva_interpretaci RES = C3 = B3n_en_Po == q rtugues_para_llamadas_LACRALO_ utf-8 / utf-8 _New_interpretation_in_Po == q = rtuguese_for_LACRALO_calls?????
by dacostabastidas＠dtech.ec July 26, 2014

July 26, 2014

[[--Translated text (es -> en)--]] Subject: Re:? = Utf-8 q = 3A_Nueva_interpretaci RES = C3 = B3n_en_Po == q rtugues_para_llamadas_LACRALO_ utf-8 / utf-8 _New_interpretation_in_Po == q = rtuguese_for_LACRALO_calls????? From: dacostabastidas(a)dtech.ec LACRALO Sucesso! So we added a continent country paradoxically feel close but in reality is very far ours. (notwithstanding the recent worldwide) Diego Acosta Bastidas The July 26, 2014, 14:51, <sylvia(a)internautabrasil.org> wrote: > Qué buena noticia! > Ahora cabe a las 4 ALSs de Brasil comunicárselo tanto a sus miembros como > a > los usuarios en general para que puedan participar en LACRALO y ICANN. > Felicitaciones LACRALO! > > ___________________________________________________ > Sylvia Herlein Leite > sylvia(a)internautabrasil.org > Secretaria FLUI 2009-2015 > ex - Secretaria LACRALO-ICANN/ 2012-2014 – > ex – ALAC Member 2009-2011 - http://atlarge.icann.org > Skype: sylvia_leite > > > -----Mensagem original----- > De: lac-discuss-es-bounces(a)atlarge-lists.icann.org > [mailto:lac-discuss-es-bounces@atlarge-lists.icann.org] Em nome de Vanda > Scartezini > Enviada em: sábado, 26 de julio de 2014 17:31 > Para: Humberto Carrasco; lac-discuss-es(a)atlarge-lists.icann.org > Cc: Daniel Fink > Assunto: Re: [lac-discuss-es] Nueva interpretación en Portugues para > llamadas LACRALO / New interpretation in Portuguese for LACRALO calls > > Gracias a todos. Es una buena oportunidad para involucrar más > organizaciones > de Brasil! > Aqui copio Daniel Fink , el responsible por Brasil desde ICANN para que > inclua en su discurso. > Abrazos a todos y muchas gracias a Silvia Vivanco! > 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/26/14, 5:20, "Humberto Carrasco" <hcarrascob(a)gmail.com> wrote: > > >Estimados: > > > >Silvia Vivanco me ha solicitado les informe que para la próxima llamada > >de LACRALO tendremos interpretación en Portuges. > > > >Esto es un gran avance para la región. Felicitamos esta decisión. > > > >Saludos > > > >Dearall: > > > >Silvia Vivanco has asked me to inform you that next LACRALO call we > >will have interpretation in Portugues. > > > >This is a breakthrough for the region. We congratulate this decision. > > > >Regards > >_______________________________________________ > >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 > > > --- > Este mensaje no contiene virus ni malware porque la protección de avast! > Antivirus está activa. > http://www.avast.com > > _______________________________________________ > 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-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/239457f173.html --]]

1 0

??? = Iso-8859-1 RES = q == F3n_en 3A__Nueva_interpretaci = iso-8859-1 q _Portugues_para_llamadas_LACRALO_ / __New_interpretat == iso-8859-1 q = ion_in_Portuguese_for_LACRALO_calls???
by sylvia＠internautabrasil.org July 26, 2014

July 26, 2014

[[--Translated text (es -> en)--]] Subject:??? = Iso-8859-1 RES = q == F3n_en 3A__Nueva_interpretaci = iso-8859-1 q _Portugues_para_llamadas_LACRALO_ / __New_interpretat == iso-8859-1 q = ion_in_Portuguese_for_LACRALO_calls??? From: sylvia(a)internautabrasil.org Qubuena news! Now it is at 4 ALS Brazil comunicrselo both its members and general users so they can participate in LACRALO and ICANN. LACRALO Congratulations! ___________________________________________________ Sylvia Herlein Leite sylvia(a)internautabrasil.org Secretary FLUI 2009-2015 ex - Secretary-LACRALO ICANN / 2012-2014 ex ALAC Member 2009-2011 - http://atlarge.icann.org Skype: sylvia_leite ----- Mensagem Original ----- From: lac-discuss-es-bounces(a)atlarge-lists.icann.org [Mailto: lac-discuss-es-bounces(a)atlarge-lists.icann.org] Em nome of Vanda Scartezini Posted in: saturday, 26 July 2014 17:31 To: Humberto Carrasco; lac-discuss-es(a)atlarge-lists.icann.org Cc: Daniel Fink Assunto: Re: [lac-discuss-es] New interpretation in Portuguese for LACRALO calls / New interpretation in Portuguese for LACRALO calls Thank you all. It's a good opportunity to involve more organizations Brazil! Here I copy Daniel Fink, the responsible for Brazil from ICANN to I included in his speech. Hugs to all and thank you very much Silvia Vivanco! 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/26/14 5:20, "Humberto Carrasco" <hcarrascob(a)gmail.com> wrote: > Dear: > > Silvia Vivanco has asked me to inform them that the next scheduled call > Temperature LACRALO interpretation in Portugues. > > This is a breakthrough for the region. Commend this decision. > > Greetings > > Dearall: > > Silvia Vivanco has asked me to inform you That we call next LACRALO > Will have interpretation in Portuguese. > > This is a breakthrough for the region. We congratulate THIS DECISION. > > Regards > _______________________________________________ > 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/e6f70c0993.html --]]

1 0

Re: [lac-discuss-en] ????? = Iso-8859-1 == q F3n_en_Portugu Nueva_interpretaci = iso-8859-1 q es_para_llamadas_LACRALO_ / __New_interpretation_in_Portugue == iso-8859-1 q = se_for_LACRALO_calls?
by vanda＠uol.com.br July 26, 2014

July 26, 2014

[[--Translated text (es -> en)--]] Subject: Re:????? = Iso-8859-1 == q F3n_en_Portugu Nueva_interpretaci = iso-8859-1 q es_para_llamadas_LACRALO_ / __New_interpretation_in_Portugue == iso-8859-1 q = se_for_LACRALO_calls? From: vanda(a)uol.com.br Thank you all. It's a good opportunity to involve more organizations in Brazil! Here I copy Daniel Fink, the responsible for Brazil from ICANN to I included in his speech. Hugs to all and thank you very much Silvia Vivanco! 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/26/14 5:20, "Humberto Carrasco" <hcarrascob(a)gmail.com> wrote: > Dear: > > Silvia Vivanco has asked me to inform them that the next scheduled call > Temperature LACRALO interpretation in Portugues. > > This is a breakthrough for the region. Commend this decision. > > Greetings > > Dearall: > > Silvia Vivanco has asked me to inform you That we will call next LACRALO > Have interpretation in Portuguese. > > This is a breakthrough for the region. We congratulate THIS DECISION. > > Regards > _______________________________________________ > 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/12b26bfdeb.html --]]

1 0

? = Iso-8859-1 == q F3n_en_Portugu Nueva_interpretaci = iso-8859-1 q es_para_llamadas_LACRALO_ / __New_interpretation_in_Portugue == iso-8859-1 q = se_for__LACRALO_calls?????
by hcarrascob＠gmail.com July 26, 2014

July 26, 2014

[[--Translated text (es -> en)--]] Subject:? = Iso-8859-1 == q F3n_en_Portugu Nueva_interpretaci = iso-8859-1 q es_para_llamadas_LACRALO_ / __New_interpretation_in_Portugue == iso-8859-1 q = se_for__LACRALO_calls????? From: hcarrascob(a)gmail.com Estimates: Silvia Vivanco has asked me to inform them that the next scheduled call we LACRALO interpretation in Portugues. This is a breakthrough for the region. Commend this decision. Regards Dearall: Silvia Vivanco has asked me to inform you That we will call next LACRALO have interpretation in Portuguese. This is a breakthrough for the region. We congratulate THIS DECISION. Regards _______________________________________________ [[--Original text (es) http://mm.icann.org/transbot_archive/7d8e609393.html --]]

1 0

Re: [lac-discuss-en] ? = Utf-8 q = C3 = Nominaci B3n_NomCom =?
by hcarrasco＠cmsz.cl July 25, 2014

July 25, 2014

[[--Translated text (es -> en)--]] Subject: Re:? = Utf-8 q = C3 = Nominaci B3n_NomCom =? From: hcarrasco(a)cmsz.cl Hi Guillermo, Thank you very much. We will create a page on the wiki with the nominations. Regards Sent from my iPhone > El 25-07-2014, a las 14:11, "Guillermo M. Zamora - Abogado" <gmzamora(a)gmail.com> escribió: > > Estimados: > > ADIAr desea nominar como candidato al Nomcom por LACRALO a Carlos Dionisio > Aguirre > > atte > > -- > Guillermo M. Zamora > Presidente Asociación de Derecho Informático de Argentina > Director Red Iberoamericana ElDerechoInformatico.com > <http://www.elderechoinformatico.com> > Trelew - Chubut > _______________________________________________ > 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/130aeff7ea.html --]]

1 0

? = Utf-8 q = C3 = Nominaci B3n_NomCom =?
by gmzamora＠gmail.com July 25, 2014

July 25, 2014

[[--Translated text (es -> en)--]] Subject:? = Utf-8 q = C3 = Nominaci B3n_NomCom =? From: gmzamora(a)gmail.com Estimates: ADIAR like to nominate as a candidate LACRALO Nomcom by Carlos Dionisio Aguirre atte - William M. Zamora President Association of Law Informtico Argentina Director Red Iberoamericana ElDerechoInformatico.com <http://www.elderechoinformatico.com> Trelew - Chubut _______________________________________________ [[--Original text (es) http://mm.icann.org/transbot_archive/582cb167d4.html --]]

1 0

Schedule to select LACRALO ALAC rep and NOMCOM rep - Nomination period open!
by ICANN At-Large Staff July 24, 2014

July 24, 2014

Dear LACRALO members, On behalf of LACRALO's Chair and Secretariat we would like to announce the following schedule to select the following positions 1. LACRALO representative to the ALAC for the period 2014-2015. This position is currently held by Dev Anand Teelucksingh<https://community.icann.org/x/kYFZAg> until the <https://archive.icann.org/en/committees/alac/#footix> (AGM 2014) (Trinidad and Tobago) ALAC Representative Schedule * Nominations Open: 23 July 2014 * Nominations Close: 30 July 2014 * Nomination Acceptance Deadline: On or before 4 August 2014 * Online Election period: Between 4- 8 August 2014 (cannot be re-elected) Note that the following positions are not up for election yet (see below;) * Fatima Cambronero<https://community.icann.org/x/yTl-Ag> x<https://archive.icann.org/en/committees/alac/#footx> (Argentina) (AGM 2015 ) - NO NEED FOR SELECTION * Leon Sanchez<http://www.icann.org/en/groups/nomcom/bios-02sep13-en.htm#leon-sanchez> iii<https://archive.icann.org/en/committees/alac/#footiii> (Mexico) (through AGM 2016)- NO NEED FOR SELECTION 1. 2015 ALAC Delegates to the 2015 NomCom Current position held by Vanda Scartezini- Term up in AGM 2014. The ALAC Leadership Team (ALT) suggested the following timetable for nominations and consultation recommendations from RALOs for consideration by the ALAC for appointment as the 2015 NomCom At-Large Delegate positions: Timeline: * Nominations Open: 23 July 2014 * Nominations Close: 30 July 2014 * Nomination Acceptance Deadline: On or before 4 August 2014 * RALO nominee prioritization period: Between 4- 8 August 2014 (this may include a vote if desired) * ALAC Notification: RALOs to transmit all accepted nominations with a recommendation for a preferred candidate if the RALO wishes to provide one by 8 August 2014 * ALAC Review of RALO Recommendations/Additional List of Nominations Accepted: 8 August - 11 August 2014 * ALAC selection and endorsement vote: Carried out on-line between 11August - 15 August 2014 * Notification to NomCom of Appointees: No later than 15 August 2014 or as arranged with NomCom Secretariat Staff and LACRALO Secretariat will note nominations in the WIKI page with the ALAC Elections, Selections and Appointments 2014. See https://community.icann.org/pages/viewpage.action?spaceKey=atlarge&title=At… 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>

3 2

Calendar to select representative LACRALO to the ALAC and NomCom - Nominations Open Period!
by staff＠atlarge.icann.org July 23, 2014

July 23, 2014

[[--Translated text (es -> en)--]] Subject: Calendar to select representative LACRALO to the ALAC and NomCom - Nominations Open Period! From: staff(a)atlarge.icann.org Dear members LACRALO On behalf of the President and Secretary of LACRALO we would like to announce the following schedule to select the following positions: 1. Representative LACRALO to ALAC for the period 2014-2015. This position currently occupied by the Dev Anand Teelucksingh <http://translate.google.com/translate?hl=es&prev=_t&sl=en&tl=es&u= https://community.icann.org/x/kYFZAg> Calendar for representative elections to ALAC * Open Nominations: July 23, 2014 * Close nominations close: July 30, 2014 * The date of acceptance of nomination limit: Until August 4, 2014 * Period of choice in Lnea: 4 to 8 August 2014 (can not be re-elected) Note that the following positions are not available to an election (vase ms later ;) Fatima Cambronero <http://translate.google.com/translate?hl=es&prev=_t&sl=en&tl=es&u= https://community.icann.org/x/yTl-Ag> x <http://translate.google.com/translate?hl=es&prev=_t&sl=en&tl=es&u= https://archive.icann.org/en/committees/alac/%23footx#footx> Len Sanchez <http://translate.google.com/translate?hl=es&prev=_t&sl=en&tl=es&u=http://ww…> iii <http://translate.google.com/translate?hl=es&prev=_t&sl=en&tl=es&u= https://archive.icann.org/en/committees/alac/%23footiii#footiii> Two. Delegate ALAC 2015 NomCom Position currently occupied by Vanda Scartezini whose term ends in 2014 AGM. The ALAC Leadership Team (ALT) proposes the following schedule for the submission of applications and recommendations for consulting RALOs for consideracin by ALAC for appointment to the positions of the At-Large delegate to NomCom 2015: Calendar: * Open Nominations: July 23, 2014 * Nominations Close: July 30, 2014 * The closing date for acceptance of nomination: The day of or before August 4, 2014 * Period of the THIN priorizacin nominated: 4 to August 8, 2014 (this may include a vote if desired) * ALAC notification: The RALOs transmitirn all nominations accepted a recommendation of a preferred candidate if the THIN want to provide for the August 8, 2014 * Revision of the Recommendations of the THIN by ALAC / Additional list of nominations accepted: From 8 to 11 August 2014 * Selection and approval of the voting ALAC: It takes place in line between 11 th to August 15, 2014 * Notificacina NomCom appointments: At the latest by 15 August 2014 or as agreed According to the Secretariat NomCom At Large staff and Secretariat LACRALO anotarn nominations in the wiki page with ALAC Elections, Selections and Appointments 2014 WIKI.: https://community.icann.org/pages/viewpage.action?spaceKey=atlarge&title=At…<http://translate.google.com/translate?hl=es&prev=_t&sl=en&tl=es&u=https://c…> Thank you very much Best 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/c89ac785ea.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 asoto＠ibero-americano.org 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: asoto(a)ibero-americano.org Thanks Dev!! Regards Alberto Soto From: Dev Anand Teelucksingh [mailto: devtee(a)gmail.com] Posted on: Tuesday, 22 July 2014 24:21 To: Alberto Soto CC: Dev Anand Teelucksingh; 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 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 <mailto:asoto@ibero-americano.org> > Wrote: 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 <mailto:asoto@ibero-americano.org> ] Posted on: Monday, July 14, 2014 1:44 a.m. To: 'Dev Anand Teelucksingh'; 'Devtee(a)gmail.com <mailto:devtee@gmail.com> ' CC: 'LACRALO discussion list'; ' <lac-discuss-es(a)atlarge-lists.icann.org <mailto:lac-discuss-es@atlarge-lists.icann.org> > ' Subject: RE: [lac-discuss-en] Re "Introduction of two-character domain names in the new gTLD Namespace" Comments from the public Dev, I think I know this subject in depth, and we've already opinin oriented one, and hope there will be more comments. Nevertheless, ABLE please prepare a draft declaration of LACRALO? Thank you! Best Regards Alberto Soto ----- Original Message ----- From: lac-discuss-en-bounces(a)atlarge-lists.icann.org <mailto:lac-discuss-en-bounces@atlarge-lists.icann.org> [Mailto: lac-discuss-en-bounces(a)atlarge-lists.icann.org <mailto:lac-discuss-en-bounces@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 <mailto:lac-discuss-es@atlarge-lists.icann.org> > Subject: Re: [lac-discuss-en] Re "Introduction of two-character domain names in the new gTLD Namespace" Comments from the public Alejandro agreement.I think it will be not cumplliendo ISO. Accepted that the end user will be little protection, because it leads to many conflicts. Regards 7/13/2014 13:19 GMT-03: 00 Dr. Alejandro Pisanty Baruch <apisan(a)unam.mx <mailto:apisan@unam.mx> >: > Aída, > > brevemente y para complementar tu análisis: el acuerdo con el país y > el operador no pueden existir sino hasta que sea creada una nueva entidad. > > En ese sentido se protegerían todas las combinaciones de dos > caracteres alfabéticos ya que es imposible predecir cuáles entidades > territoriales serían creadas en un futuro indefinido, y menos aún qué > códigos les serían asignados. > > Bajo .globo (es decir, **EN NUESTRA REGIÓN**) se propone liberar tanto > los códigos de dos letras como los formados por una letra y un dígito. > ¿Qué consecuencias puede tener esto? (la primera que me viene a la > mente es la colisión con una marca de salsa para carne asada tipo "barbeque", A1). > > Alejandro Pisanty > > > - - - - - - - - - - - - - - - - - - - - - - - - - - - > Dr. Alejandro Pisanty > Facultad de Química UNAM > Av. Universidad 3000, 04510 Mexico DF Mexico > > > > +52-1-5541444475 <tel:%2B52-1-5541444475> FROM ABROAD > > +525541444475 <tel:%2B525541444475> DESDE MÉXICO SMS +525541444475 <tel:%2B525541444475> > 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 <mailto:lac-discuss-en-bounces@atlarge-lists.icann.org> [ > lac-discuss-en-bounces(a)atlarge-lists.icann.org <mailto:lac-discuss-en-bounces@atlarge-lists.icann.org> ] en nombre de Aida > Noblia [ aidanoblia(a)gmail.com <mailto:aidanoblia@gmail.com> ] Enviado el: domingo, 13 de julio de > 2014 10:48 > Hasta: <lac-discuss-es(a)atlarge-lists.icann.org <mailto:lac-discuss-es@atlarge-lists.icann.org> > > CC: LACRALO discussion list > Asunto: Re: [lac-discuss-en] Re "Introducción de dos caracteres de > nombres de dominio en el Nuevo gTLD Namespace" Los comentarios > del público > > La pregunta de DEV que focaliza el tema, dice que hay que ver: > > "Si Especificación 5 está destinado a defender el principio de que los > códigos de países ISO 3166-2 debe ser protegida en los nuevos gTLD, > entonces se debe cumplir al asegurar que los países y territorios > futuras con nuevas etiquetas de 2 caracteres ASCII están protegidos de > la misma manera como los territorios y países en la actual. > > La especificación 5 está transcripta en el sitio > > https://community.icann.org/display/alacpolicydev/At-Large+Introductio > n+of+Two-Character+Domain+Names+in+the+New+gTLD+Namespace+Workspace > : > > Dicha Especificación 5 dice: > > "Todas las etiquetas de dos caracteres ASCII quedarán excluidas de la > inscripción o asignación to Registry operador en el segundo nivel en > el TLD. Dichas etiquetas pueden no estar activadas en el DNS, y no > podrán ser liberados para el registro a cualquier persona o entidad > que no sea operador de registro, siempre que dichas cadenas de > etiquetas de dos caracteres pueden ser liberados en la medida en que > el operador de registro alcanza un acuerdo con el gobierno relacionada > y el gerente de código de país de la cadena como se especifica en the > ISO 3166-1 alpha-2. El Operador de Registro También podrá proponer la > liberación de estas reservas con base en la aplicación de medidas para > evitar la confusión con los códigos de los países correspondientes, con sujeción a la aprobación de la ICANN." > > Es claro que la redacción de esta cláusula es restrictiva. Tiene > además exigencias que no ví que se hayan cumplido: Falta el acuerdo > con el gobierno relacionado y con el gerente del código país de la > cadena. Además tampoco aparece cumplido las medidas que aplicarán en > cada país para evitar la confusión con los códigos de los países como lo pide la norma. > > Entiendo además que el pedido de todas las cadenas > indiscriminadamente, como es el pedido hecho, no está contemplado en > la norma. Es una norma restrictiva y supone que se pide para un país y no globalmente. > > La especificacion 5 es netamente protectora en primer lugar de los > codigos pais. Admite solo por excepcion y con muchos requisitos, con > el acuerdo del propio pais ademas. El criterio es claramente de dar > prevalencia al dominio pais. Exige que ademas de cumplirse los > requisitos anteriores se presenten medidas para evitar la confusion > con el propio pais. Es muy restrictivo y da una proteccion muy estricta a los codigos pais. > > Desde el punto de vista del usuario final el codigo pais en Internet > es cada vez más importante por el sentido de identidad de un pueblo, > de una idiosincracia, de un paradigma, también respecto hacia su > persona y su país. Algo así como la bandera de cada país. Esto afirma > la confianza en lo global a traves del reconocimiento de lo local como > parte y dentro de lo global. > > > Saludos > Aída > > PD Por el momento no pude entrar en la wiki . Parece que es el > sistema.. en cuanto pueda lo agrego > > > DEV The question that focuses the subject and then transcribe says to see: > > If Specification 5 is intended to defend the principle that the ISO > 3166-2 country codes must be protected in the new gTLDs, then you must > meet to ensure that countries and future territories with new tags 2 > ASCII characters are protected from same way as the regions and > countries in today. > > Specification 5 is transcribed at the site > > https://community.icann.org/display/alacpolicydev/At-Large+Introductio > n+of+Two-Character+Domain+Names+in+the+New+gTLD+Namespace+Workspace > : > > This Specification 5 says: > > "All the labels of two ASCII characters will be excluded from > enrollment or assignment to Registry Operator in the second level in > the TLD. Such labels may not be active in the DNS, and may not be > delivered for registration to any person or entity not registry > operator if such label strings two characters may be it released to > the extent that the Registry Operator reaches agreement with the > related government and the head of country code string as specified in > the ISO 3166-1 alpha-2. Registry Operator may also propose release of > these reservations based on the introduction of measures to avoid > confusion with the codes of the countries concerned, subject to the approval of ICANN. " > > It is clear that the wording of this clause is restrictive. It also > has not revealed requirements are met: Missing accordance with the > related government and the country manager of the chain code. Also > appears not fulfilled the measures applied in each country to avoid > confusion with country codes as required by the standard. > > I further understand that the request for all brands indiscriminately, > as is done request is not covered by the standard. It is a restrictive > rule and assumes that calls to a country and not globally. > > Specification 5 is the first purely protective of country codes. > Allowed only by exception and with many requirements, with the > agreement of the country besides himself. The criterion is clearly to > give prevalence to the country domain. Demands that also met the above > requirements presented measures to avoid confusion with the country > itself. It is very restrictive and gives a very strict protection for country codes. > > From the point of view of the end user country code on the Internet is > increasingly important for the sense of identity of a people, an > idiosyncrasy, a paradigm, also with regard to himself and his country. > Something like the flag of each country. This affirms confidence in > global recognition through the local as part and within the global. > > > 2014-07-11 9:59 GMT-03:00 <devtee(a)gmail.com <mailto:devtee@gmail.com> >: > > > > > [[--Translated text (en -> es)--]] > > > > Asunto: Re: Re "Introducción de dos caracteres de nombres de > dominio > > en el Nuevo gTLD Namespace" Los comentarios del público > > De: devtee(a)gmail.com <mailto:devtee@gmail.com> > > > > Bueno, sólo puede haber un número fijo de permutaciones (676) para > > su posible utilizar en la norma ISO 3166 desde ISO 3166 sólo puede > > ser letras ASCII de AA a ZZ. Y Si bien puede no ser un número > > rápido de cambios, se han producido > cambios > > ISO 3166 en los últimos 10 años. > > > > > > Por ejemplo, en 2010, por ejemplo: > > > > > http://www.iso.org/iso/iso_3166-1_newsletter_vi-8_split_of_the_dutch_a > ntilles_final-en.pdf > > > > > > BQ, CW y SX se añadieron para Bonaire, San Eustaquio y Saba, > > Curaçao y Sint Maarten (parte neerlandesa) en el Caribe. > > > > > > Dev Anand > > > > > > > > > > > > > > > > > > > > > > El Jueves, 10 de julio 2014 a las 8:47 AM, Carlton Samuels < > > carlton.samuels(a)gmail.com <mailto:carlton.samuels@gmail.com> > > > escribió: > > > > > > > Closely reasoned and from the principle of cc assignment certainly > worthy > > > of the ALAC's consideration. > > > > > > While we're at it, lets consider that 3-character country codes > > > are possible. > > > > > > Giving protection for a future event suggests we have a definite > > knowledge > > > of country/territory breakdown and thusly, possible code assignment. > > Tying > > > up all permutations of 2 characters especially when you consider > > > IDNs > > would > > > be a tough sell. > > > > > > Carlton > > > ---------'--------''----- > > > > > > On Jul 10, 2014 2:04 AM, "Dev Anand Teelucksingh" > > > <devtee(a)gmail.com <mailto:devtee@gmail.com> > > > > wrote: > > > > > > > > Regarding the public comment on "Introduction of Two-Character > > > > Domain > > > Names > > > > in the New gTLD Namespace" at > > > > https://community.icann.org/x/VqzhAg > > > > which ends July 10 2014, I've posted the following at > > > > https://community.icann.org/x/VqzhAg > > > > for consideration: > > > > > > > > "Various registries for multiple gTLDs are applying for > > > > exceptions to Specification 5, Section 2 of the New gTLD > > > > Registry Agreement ("Specification 5") with some registries > > > > suggesting the release of 2 character ASCII labels not on the > > > > current ISO 3166 standard would > > > suffice. > > > > > > > > While this seems harmless, there is a possibility of new > > > > countries > and > > > > territories being created, and then allocated a new two > > > > character > ASCII > > > > label by ISO 3166/MA (see > > > > > > > > > > https://web.archive.org/web/20111101141651/http://www.iso.org/iso/coun <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 <mailto:lac-discuss-en@atlarge-lists.icann.org> > > > > https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en > > > > > > > > lac-discuss-es mailing list > > lac-discuss-en(a)atlarge-lists.icann.org <mailto:lac-discuss-en@atlarge-lists.icann.org> > > https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en > > > > > > [[--Original text (es) http://mm.icann.org/transbot_archive/da5b6784db.html --]]

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 Aida Noblia July 22, 2014

July 22, 2014

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 (en) > http://mm.icann.org/transbot_archive/2fe20b851c.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

4 6