- lac-discuss-es - lists.icann.org

Important - Available Travel Slots for ICANN62 in Panama
by ICANN At-Large Staff March 21, 2018

March 21, 2018

[[--Translated text (en -> es)--]] [[--This message had format issues and was not translated properly--]] Tema: Important - Available Travel Slots for ICANN62 in Panama De:ICANN At-Large Staff <staff(a)atlarge.icann.org> v \\: * {behavior: url (# default # VML);} o \\: * {behavior: url (# default # VML);} w \\: * {behavior: url (# default # VML);} .shape {comportamiento: url (# default # VML);} Queridos todos, El ALAC tiene varios espacios de viaje disponibles para la reunión ICANN62 en Panamá, del 25 al 28 de junio de 2018.Hay dos o más espacios de viaje que se asignarán a los participantes de At-Large que estén ACTIVAMENTE involucrados en alguna actividad de políticas de ICANN, o aquellos con un historial sólido de dicha participación en el pasado y un interés en reiniciar. Entre ellos se incluyen los PDP de gNSO o de ccNSO, los CCWG, los grupos de trabajo de apoyo de ALAC y la revisión At-Large (con un énfasis menor en este último). Se pueden abrir otros espacios debido a que otros viajeros no pueden asistir o no requieren fondos completos.Si está interesado en ser considerado para uno de estos espacios de viaje, complete la siguiente encuesta:https://goo.gl/forms/E5iDK174rW2k9j3t1 Tenemos muy poco tiempo para finalizar nuestra lista de viajeros, por lo que las respuestas deben enviarse antes de las 23:59 UTC del martes 27 de marzo de 2018. Gracias. Saludos cordiales, Personal de At-Large Personal de políticas de ICANN en apoyo de la comunidad At-Large E-mail: staff(a)atlarge.icann.org Sitio web: atlarge.icann.org [atlarge.icann.org] Facebook: facebook.com/icann [facebook.com] atlarge [facebook.com] Twitter: @ [twitter.com] ICANNAtLarge [twitter.com] [[--Original text (en) Translated by transbot 2.18-2.04 http://mm.icann.org/transbot_archive/93905f0e5b.html --]]

1 0

Draft comment to WT-5 session during ICANN61
by Carlos Raul Gutierrez March 21, 2018

March 21, 2018

Dear Leadership of LACRALO, As some of you know, I spent almost 3 years in a CWG ccNSO-GNSO on the use of country and territory names, and we got stuck on the 3 letter codes of the ISO 3166-1 list. Last week, during the SubPro WT5 meeting in PR, we also got stuck on that very same list and I almost lost my hope of any progress. But after talks with members of the WT5, including the Swiss GAC rep, the ccTLD managers of Estonia and New Zealand, and the most able ALAC Co-Chair of WT5, I came with some ideas on how to get rid of this stumbling block and continue making progress with a policy for full geo names for the future. In that sense I kindly ask for your comments, additions, corrections and eventual support of the draft motion attached, that I want to add to my comments on the microphone during that session. Of course, I want to submit my comments before the next call which is next week......... Glad to add the names of anyone who supports the motion DRAFT for comments and expression of support Dear WT5 Participants: We trust that all of us have returned home OK from San Juan following ICANN 61. For the record and with a view to our next conference call on 28 March, 05.00 UTC, this is just to recall some points made during the discussion on Wednesday morning, 14 March. For the Subsequent procedures PDP to go forward without delay, we need to make progress on a new geo.TLD policy for “full names” fast. Based on previous efforts (like the previous policy efforts of the ccNSO, the ccNSO-GNSO-CWG that followed, and the efforts within the GAC) it is not advisable to pursue the idea that the 2012 Applicant Guide Book (AGB) reserved list of geo.names (based on codes dependent on outside reference lists) a relevant default. That text (AGB) effectively failed to address several classes of names that are of significant interest to user communities, represents today a lacunae which gave rise to several disagreements and delays last time around (.amazon, .africa, .persiangulf). The first registered ccTLDs were .us <https://en.wikipedia.org/wiki/.us>, .uk <https://en.wikipedia.org/wiki/.uk>, and .il <https://en.wikipedia.org/wiki/.il>, all registered in 1985. But It has taken until today to (not) make a decision on the 3 letter alpha codes. In the meantime, other geography-related top-level domains have been successfully delegated, like is the case for the city TLDs (.Berlin, .London, .Rio, etc.) as well as some region and new countries, like .cat, .bzh and .srb. Obviously, as more exception emerge to reference codes dependent on outside reference lists there is a growing space for conflict. There remains a tremendous and growing inconsistency in the particular case with the 3-letter codes of the ISO 3166-1 list which own the last round served as the basis for another ineffective reservation. For that reason I have suggested during our meeting in ICANN61 that it is important for WT5 to eliminate the restrictions of the 3 letter ISO 3166-1 list is an important step, so that an effective “full.geo.name” evaluation policy, consistent with modern developments in the DNS space can be developed for subsequent rounds. Short codes/acronyms of the 3 letter ISO 3166-1 list are not “Generic” in the usual ICANN sense of the DNS expansion but for few exceptions. For that reason, I submit this modest draft PROPOSAL TO DELEGATE 3 letter codes to interested Governments and other geo related public interest entities previous or during the next round. Taking the delegation of 2-letter codes to ccTLD managers as a precedent n the mid-80s, we should assume that there is demand out there for the differentiated use of 3 letter ISO 3166-1 list codes, either by Governments, public entities, communities and even some ccTLD managers themselves. So instead of the 3-letter codes of the ISO- 3166-1 list remaining reserved, the WT5 should analyze the possibility of using subsequent rounds and use the proven evaluation methodology and assigning process of the last round (like in the case for city names) for the ISO list 3 letter codes. This option to delegate/register the whole 3-letter code ISO list, opens the space for other public interest parties to apply for a few IGO/IGNO specific 3 letter codes that also have been reserved (IOC, WHO, IMF) and then leaving all other 3 letter permutation outside the ISO list and IGO/INGOs open for creative applications in the generic domain space. A back of the envelope calculation will show that offering to delegate the first group and taking into account the existing 3 letter codes will amount to a total of less than 500 TLDs. That leaves more than 20’000 possible permutation open for evaluation as new gTLDs. WT5 should seriously consider a delegation process for the 3 letter ISO 3166-1 list (as opposed to maintaining an incongruent reservation list) under the following assignment conditions 1. Right of First Refusal To Governments of countries/territories to THEIR 3 Letter Codes (ISO...); 2. Right of Second Refusal al ccTLD manager del país o territorio correspondiente (en PR sería Gauss/PR Top Level Domain, no el Estado Libre Asociado); 3. Right of the Third Refusal to a pertinent linguistic, ethnic, indigenous community or people as said concepts are defined by International Law; as long as they get support from the respective political entities 4. If none of the above show interest in the pertinent 3 Letter Code of the ISO 3166-1, then to any IGO/INGO that has requested protection in the past 5. Finally, if then string shall be an available gTLD for any qualified applicant. Carlos Raúl Gutiérrez ISOC Costa Rica Chapter / ALS Costa Rica skype carlos.raulg +506 8837 7176 ________ Apartado 1571-1000 COSTA RICA

5 7

Re: [lac-discuss-es] Fwd: Draft comment to WT-5 session during ICANN61
by carlos dionisio aguirre March 20, 2018

March 20, 2018

Gracias a google y a vos Carlos. Carlos Dionisio Aguirre Enviado desde mi smartphone Samsung Galaxy. -------- Mensaje original -------- De: Carlos Raul Gutierrez <crg(a)isoc-cr.org> Fecha: 19/3/18 16:55 (GMT-04:00) Para: LACRALO <lac-discuss-es(a)atlarge-lists.icann.org> Asunto: [lac-discuss-es] Fwd: Draft comment to WT-5 session during ICANN61 -------- Mensaje original -------- De: Carlos Raul Gutierrez <crg(a)isoc-cr.org> Fecha: 19/3/18 16:55 (GMT-04:00) Para: LACRALO <lac-discuss-es(a)atlarge-lists.icann.org> Asunto: [lac-discuss-es] Fwd: Draft comment to WT-5 session during ICANN61 Traduccion cortesia de Google Estimado Liderazgo de LACRALO, Como algunos de ustedes saben, pasé casi 3 años en un CWG ccNSO-GNSO sobre el uso de nombres de países y territorios, y nos quedamos atrapados en los códigos de 3 letras de la lista ISO 3166-1. La semana pasada, durante la reunión de SubPro WT5 en PR, también nos quedamos atrapados en la misma lista y casi pierdo la esperanza de algún progreso. Pero después de las conversaciones con los miembros del WT5, incluido el representante del GAC de Suiza, los gerentes de ccTLD de Estonia y Nueva Zelanda, y el copresidente más hábil de ALA del WT5, vine con algunas ideas sobre cómo librarme de este obstáculo y Continuar haciendo progresos con una política de nombres geográficos completos para el futuro. En ese sentido, le pido amablemente sus comentarios, adiciones, correcciones y el eventual respaldo del proyecto de moción adjunto, que quiero agregar a mis comentarios en el micrófono durante esa sesión. Por supuesto, quiero enviar mis comentarios antes de la próxima convocatoria, que es la próxima semana ......... Me alegra agregar los nombres de cualquiera que apoye el movimiento BORRADOR para comentarios y expresión de apoyo Carlos Raúl Gutiérrez ISOC Costa Rica Chapter skype carlos.raulg +506 8837 7176 ________ Apartado 1571-1000 COSTA RICA ---------- Forwarded message ---------- From: Carlos Raul Gutierrez <crg(a)isoc-cr.org<mailto:crg@isoc-cr.org>> Date: Mon, Mar 19, 2018 at 4:51 PM Subject: Draft comment to WT-5 session during ICANN61 To: LACRALO <lac-discuss-es(a)atlarge-lists.icann.org<mailto:lac-discuss-es@atlarge-lists.icann.org>> Cc: Humberto Carrasco <hcarrascob(a)gmail.com<mailto:hcarrascob@gmail.com>>, Alberto Soto <asoto(a)ibero-americano.org<mailto:asoto@ibero-americano.org>>, "rihogris(a)gmail.com<mailto:rihogris@gmail.com>" <rihogris(a)gmail.com<mailto:rihogris@gmail.com>>, "Me on BartlettMorgan.com" <me(a)bartlettmorgan.com<mailto:me@bartlettmorgan.com>>, Bartlett Morgan <bartlett.morgan(a)gmail.com<mailto:bartlett.morgan@gmail.com>> Dear Leadership of LACRALO, As some of you know, I spent almost 3 years in a CWG ccNSO-GNSO on the use of country and territory names, and we got stuck on the 3 letter codes of the ISO 3166-1 list. Last week, during the SubPro WT5 meeting in PR, we also got stuck on that very same list and I almost lost my hope of any progress. But after talks with members of the WT5, including the Swiss GAC rep, the ccTLD managers of Estonia and New Zealand, and the most able ALAC Co-Chair of WT5, I came with some ideas on how to get rid of this stumbling block and continue making progress with a policy for full geo names for the future. In that sense I kindly ask for your comments, additions, corrections and eventual support of the draft motion attached, that I want to add to my comments on the microphone during that session. Of course, I want to submit my comments before the next call which is next week......... Glad to add the names of anyone who supports the motion DRAFT for comments and expression of support Dear WT5 Participants: We trust that all of us have returned home OK from San Juan following ICANN 61. For the record and with a view to our next conference call on 28 March, 05.00 UTC, this is just to recall some points made during the discussion on Wednesday morning, 14 March. For the Subsequent procedures PDP to go forward without delay, we need to make progress on a new geo.TLD policy for “full names” fast. Based on previous efforts (like the previous policy efforts of the ccNSO, the ccNSO-GNSO-CWG that followed, and the efforts within the GAC) it is not advisable to pursue the idea that the 2012 Applicant Guide Book (AGB) reserved list of geo.names (based on codes dependent on outside reference lists) a relevant default. That text (AGB) effectively failed to address several classes of names that are of significant interest to user communities, represents today a lacunae which gave rise to several disagreements and delays last time around (.amazon, .africa, .persiangulf). The first registered ccTLDs were .us<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipe…>, .uk<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipe…>, and .il<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipe…>, all registered in 1985. But It has taken until today to (not) make a decision on the 3 letter alpha codes. In the meantime, other geography-related top-level domains have been successfully delegated, like is the case for the city TLDs (.Berlin, .London, .Rio, etc.) as well as some region and new countries, like .cat, .bzh and .srb. Obviously, as more exception emerge to reference codes dependent on outside reference lists there is a growing space for conflict. There remains a tremendous and growing inconsistency in the particular case with the 3-letter codes of the ISO 3166-1 list which own the last round served as the basis for another ineffective reservation. For that reason I have suggested during our meeting in ICANN61 that it is important for WT5 to eliminate the restrictions of the 3 letter ISO 3166-1 list is an important step, so that an effective “full.geo.name<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Ffull.geo.n…>” evaluation policy, consistent with modern developments in the DNS space can be developed for subsequent rounds. Short codes/acronyms of the 3 letter ISO 3166-1 list are not “Generic” in the usual ICANN sense of the DNS expansion but for few exceptions. For that reason, I submit this modest draft PROPOSAL TO DELEGATE 3 letter codes to interested Governments and other geo related public interest entities previous or during the next round. Taking the delegation of 2-letter codes to ccTLD managers as a precedent n the mid-80s, we should assume that there is demand out there for the differentiated use of 3 letter ISO 3166-1 list codes, either by Governments, public entities, communities and even some ccTLD managers themselves. So instead of the 3-letter codes of the ISO-3166-1 list remaining reserved, the WT5 should analyze the possibility of using subsequent rounds and use the proven evaluation methodology and assigning process of the last round (like in the case for city names) for the ISO list 3 letter codes. This option to delegate/register the whole 3-letter code ISO list, opens the space for other public interest parties to apply for a few IGO/IGNO specific 3 letter codes that also have been reserved (IOC, WHO, IMF) and then leaving all other 3 letter permutation outside the ISO list and IGO/INGOs open for creative applications in the generic domain space. A back of the envelope calculation will show that offering to delegate the first group and taking into account the existing 3 letter codes will amount to a total of less than 500 TLDs. That leaves more than 20’000 possible permutation open for evaluation as new gTLDs. WT5 should seriously consider a delegation process for the 3 letter ISO 3166-1 list (as opposed to maintaining an incongruent reservation list) under the following assignment conditions 1. Right of First Refusal To Governments of countries/territories to THEIR 3 Letter Codes (ISO...); 2. Right of Second Refusal al ccTLD manager del país o territorio correspondiente (en PR sería Gauss/PR Top Level Domain, no el Estado Libre Asociado); 3. Right of the Third Refusal to a pertinent linguistic, ethnic, indigenous community or people as said concepts are defined by International Law; as long as they get support from the respective political entities 4. If none of the above show interest in the pertinent 3 Letter Code of the ISO 3166-1, then to any IGO/INGO that has requested protection in the past 5. Finally, if then string shall be an available gTLD for any qualified applicant. Carlos Raúl Gutiérrez ISOC Costa Rica Chapter / ALS Costa Rica skype carlos.raulg +506 8837 7176<tel:+506%208837%207176> ________ Apartado 1571-1000 COSTA RICA

2 1

Brigde Zoom to TTF Session
by Harold Arcos March 14, 2018

March 14, 2018

Estimados, por problemas de seguridad encontrados en el uso de Adobe Connect se está utilizando los audios en streaming y un puente de conexión con Zoom para la reunión que se desarrolla en el Technology Task Force. Aquí comparto el archivo de audio en Castellano que deben descargar y abrir con su Reproductor de Sonido preferido: http://stream.icann.org:8000/sju61-102abc-es.m3u Dear, due to security problems found in the use of Adobe Connect streaming audio is being used and a connection bridge with Zoom for the meeting that was developed in the Technology Task Force. Here I share the audio file in English that you must download and open with your preferred Sound Player: http://stream.icann.org:8000/sju61-102abc-en.m3u

1 0

Fwd: PLEASE READ - NEW SESSION INFORMATION ICANN61
by Dev Anand Teelucksingh March 14, 2018

March 14, 2018

[[--Translated text (en -> es)--]] [[--This message had format issues and was not translated properly--]] Tema: Fwd: PLEASE READ - NEW SESSION INFORMATION ICANN61 De:Dev Anand Teelucksingh <devtee(a)gmail.com> ---------- Mensaje reenviado ---------- De: Personal de At-Large de la ICANN <staff(a)atlarge.icann.org> Fecha: mié, 14 de marzo de 2018 a las 7:40 a.m. Asunto: [ALAC-Announce] POR FAVOR, LEA: NUEVA INFORMACIÓN DE LA SESIÓN ICANN61 Para: Viajeros At-Large ICANN61 <travelers(a)atlarge-lists.icann.org> , ALAC anuncia <alac-announce(a)atlarge-lists.icann.org> Queridos todos, Debido a dificultades de seguridad, (ver el blog de Goran aquí [icann.org] Las instalaciones de la sala Adobe Connect ya no estarán disponibles para ICANN61 Participantes. Para minimizar la interrupción, tenemos los siguientes pasos que te animamos a seguir: PARA UNIRSE AL AUDIO La transmisión de audio estará disponible para todas las reuniones abiertas y públicas. Campo de golf se puede encontrar en las páginas de la reunión del cronograma ICANN61: https://61.schedule.icann.org/ [61.schedule.icann.org] El puente de audio está disponible para aquellos que quieran preguntar preguntas o comentarios por teléfono. Marque en detalles para Las sesiones de At-Large son: Números de llamada de ADIGO:http://www.adigo.com/icann ID de conferencia: 1638 PARA ACCEDER A LAS PRESENTACIONES Todas las presentaciones estarán en nuestras páginas wiki de At-Large ICANN61. por hoy, miércoles 14 de marzo:https://community.icann.org/x/bAm8B Las presentaciones y los documentos también se distribuirán por correo electrónico a pedido Todas las presentaciones y documentos que se iban a mostrar en la sala de AC se cargará a la página correspondiente en el calendario ICANN61 páginas de reuniones:https://61.schedule.icann.org/ [61.schedule.icann.org] HACER PREGUNTAS Y COMENTAR EN FORMATO ESCRITO Estos serán entregados a través de la gestión en vivo de los comentarios por correo electrónico y preguntas del Administrador de participación remota. Por favor vea la lista de direcciones de correo electrónico de la sala de reuniones aquí: https://61.schedule.icann.org/pages/2350 [61.schedule.icann.org] Pedimos disculpas por las molestias causadas. Alentamos a los participantes que aún no lo hayan hecho para descargar la aplicación móvil ICANN61 por buscando "ICANN61" en sus tiendas de aplicaciones. Por favor no dudes en envíenos un correo electrónico a staff(a)atlarge.icann.org si necesita una marcación especificando a qué reunión le gustaría unirse y su contacto preferido número. Gracias Saludos cordiales, Gisella ------ Gisella Gruber Gerente, Soporte de operaciones, ALAC-At-Large Corporación de Internet para Nombres y Números Asignados (ICANN) Correo electrónico: gisella.gruber(a)icann.org Tel: +44 7545 334 360 ID de Skype: gisella.gw [gisella.gw] One World, One Internet _______________________________________________ Lista de correo de ALAC-Announce ALAC-Anounce(a)atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-announce Sitio oficial de At-Large:http://www.atlarge.icann.org _______________________________________________ lac-discuss-en lista de correo lac-discuss-en(a)atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en [[--Original text (en) Translated by transbot 2.18-2.04 http://mm.icann.org/transbot_archive/6d7e7281ae.html --]]

1 0

"Scorecard" a un año del proceso de mediación
by Alejandro Pisanty March 14, 2018

March 14, 2018

Colegas, hace poco más de un año un grupo de representantes de ALS fue convocado a un proceso de mediación para buscar nuevos acuerdos que permitan a LACRALO cumplir con su función dentro de ICANN en una forma constructiva. ICANN asignó el trabajo de mediación a dos personas extraordinariamente capacitadas y con antecedentes inigualables, quienes condujeron las reuniones en el sentido de identificar problemas, buscar soluciones, y construir lazos interpersonales que permiteran transformar nuestra actividad en beneficio de los usuarios de Internet de Latinoamérica y el Caribe. En la inminente reunión de ICANN en Puerto Rico habrá una nueva sesión en la que participarán algunos de los participantes originales además de otros que no estuvieron en la primera sesión. Para facilitar el trabajo y transmitir nuestro punto de vista he tomado los acuerdos registrados en la minuta de la reunión y elaborado una "scorecard" que está sujeta, desde luego, a ser complemnetada por otros particpantes. Me permito anexarla y solicitar a la Presidencia y el Secretariado que la agreguen al wiki de tal manera que se preserve una copia como la estoy presentando y otra esté disponible para ediciones por los miembros. Saludos. 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 . . . . . . . . . . . . . . . .

5 6

Hot Topics survey - LACRALO
by Humberto Carrasco March 13, 2018

March 13, 2018

[[--Translated text (en -> es)--]] Tema: Hot Topics survey - LACRALO De:Humberto Carrasco <hcarrascob(a)gmail.com> Queridos todos, Aquí puede encontrar un enlace a la encuesta que hemos preparado para determinar cuáles son los temas principales de ICANN para LACRALO. https://es.surveymonkey.com/r/PZLX6NG La fecha límite para responder es 10 días. Agradeciendo de antemano su participación. Saludos Humberto Carrasco Presidente - LACRALO Maritza Aguero Secretario - LACRALO [[--Original text (en) Translated by transbot 2.18-2.04 http://mm.icann.org/transbot_archive/250b791cb3.html --]]

3 2

Reunión de coordinación entre RALO Leadership y ALAC Members
by Maritza Y. Aguero Minano March 13, 2018

March 13, 2018

Estimados miembros de la Comunidad, El presente correo es para informales que el día de ayer, 12 de marzo, hemos tenido la tercera reunión de coordinación entre RALO Leadership y los ALAC Members. En esta oportunidad, nuestra reunión ha sido presencial y durante la reunión ICANN61 en Puerto Rico. En la citada reunión participaron: Alberto Soto, Ricardo Holmquist, Bartlett Morgan, Humberto Carrasco y Maritza Agüero A manera de resumen, los temas tratados fueron los siguientes: 1. Encuesta elaborada por Humberto Carrasco, la cual tuvo la reotralimentacion de los participantes de esta reunión. Se recibieron comentarios y se envió a la lista de correo de LACRALO para que los miembros de la Comunidad emitan sus opiniones y/o recomendaciones. 2. Se estableció un calendario para la participación de los ALAC members en las llamadas mensuales hasta noviembre 2018. 3. ALAC members elegirán los temas de relevancia para compartir con la región y de esta formar poder armar los WG respectivos. Con el establecimiento de las reuniones de coordinación, se da cumplimiento a uno de los puntos de la mediación. Gracias por su atención. Saludos, Humberto Carrasco / Maritza Aguero

1 0

Re: [lac-discuss-es] Hot Topics survey - LACRALO
by hamzah March 13, 2018

March 13, 2018

[[--Translated text (en -> es)--]] Tema:Re: Hot Topics survey - LACRALO De:hamzah <hamzah.haji(a)gmail.com> hecho El lun., 12 de mar. de 2018 5:49 PM, Humberto Carrasco <hcarrascob(a)gmail.com> escribió: Queridos todos, Aquí puede encontrar un enlace a la encuesta que hemos preparado para determinar cuáles son los temas principales de ICANN para LACRALO. https://es.surveymonkey.com/r/PZLX6NG La fecha límite para responder es 10 días. Agradeciendo de antemano su participación. Saludos Humberto Carrasco Presidente - LACRALO Maritza Aguero Secretario - LACRALO _______________________________________________ lac-discuss-en lista de correo lac-discuss-en@atlarge-lists.icann.orghttps://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en [[--Original text (en) Translated by transbot 2.18-2.04 http://mm.icann.org/transbot_archive/502009ec2b.html --]]

1 0

LAC session on PDPs
by Harold Arcos March 11, 2018

March 11, 2018

Estimada región Estamos iniciando la sesión de LAC session on PDPs Comparto enlace: https://participate.icann.org/sju61-208bc Saludos Harold

1 0