March 2018 - lac-discuss-es

Re: [lac-discuss-es] Meeting Invitation: LACRALO Monthly Call on Monday, 26 March 2018 at 23:00 UTC
by Maritza Y. Aguero Minano March 22, 2018

March 22, 2018

[[--Translated text (en -> es)--]] [[--This message had format issues and was not translated properly--]] Tema:Re: Meeting Invitation: LACRALO Monthly Call on Monday, 26 March 2018 at 23:00 UTC De:"Maritza Y. Aguero Minano" <myaguero(a)msn.com> Querido Leon, Muchas gracias. Célebre. Saludos, Maritza De: lac-discuss-en <lac-discuss-en-bounces(a)atlarge-lists.icann.org> en nombre de León Felipe Sánchez Ambía <leonfelipe(a)sanchez.mx> Enviado: jueves, 22 de marzo de 2018 12:29 p.m.Para: Personal CC: lac-discuss-en(a)atlarge-lists.icann.org Asunto: Re: [lac-discuss-es] Invitación a la reunión: LACRALO Monthly Call el lunes 26 de marzo de 2018 a las 23:00 UTC Querida Maritza, Tenga en cuenta mis disculpas por esta llamada ya que estaré de vacaciones con mi familia. Te deseo una llamada muy productiva. Atentamente, León El 22/03/2018, a las 08:58, Personal de At-Large de la ICANN <staff(a)atlarge.icann.org> escribió: *** Tenga en cuenta que Adobe Connect NO se utilizará para esta reunión según Göran Marby s blog y más recientemente recibido blog de Ashwin Rangan, SVP Engineering & Chief Information Officer. *** Queridos todos, La próxima llamada mensual de LACRALO está programada para el lunes 26 de marzo de 2018 a las 23:00 UTC. Se proporcionarán interpretaciones en espa� ol, francés y portugués. Para otros horarios: https://tinyurl.com/yax9t67q La agenda (para ser actualizada) y los detalles de las llamadas están disponibles en: https://community.icann.org/x/yi68B ID de conferencia: EN 1638 ES 1738 FR 1838 PT 5393 Área de trabajo Wiki: https://community.icann.org/x/NJQi Por favor confirme su número de marcado y preferido a: staff(a)atlarge.icann.org Gracias. Saludos cordiales, 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 Facebook: facebook.com/icannatlarge Twitter: @ICANNAtLarge <image001.png> _______________________________________________ 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 (en) Translated by transbot 2.18-2.04 http://mm.icann.org/transbot_archive/d25d4ba335.html --]]

1 0

Re: [lac-discuss-es] RV: Meeting Invitation: LACRALO Monthly Call on Monday, 26 March 2018 at 23:00 UTC
by Maritza Y. Aguero Minano March 22, 2018

March 22, 2018

[[--Translated text (en -> es)--]] [[--This message had format issues and was not translated properly--]] Tema:Re: RV: Meeting Invitation: LACRALO Monthly Call on Monday, 26 March 2018 at 23:00 UTC De:"Maritza Y. Aguero Minano" <myaguero(a)msn.com> Estimado Alan: Nuestra llamada mensual está programada para el próximo lunes 26, antes de la llamada mensual de ALAC. Saludos, De: Alan Greenberg <alan.greenberg(a)mcgill.ca> Enviado: jueves, 22 de marzo de 2018 11:52 a.m. Para: Humberto Carrasco; Maritza Y. Aguero Minano CC: lista de discusión de LACRALO Asunto: Re: [lac-discuss-es] RV: Invitación a la reunión: Llamada mensual de LACRALO el lunes 26 de marzo de 2018 a las 23:00 UTC A partir de esta ma� ana, todavía no está funcionando. Tendremos que monitorearlo día a día. Al preparar el material para la reunión, asumiría que no funcionará y enviaré las cosas por correo a las personas con anticipación. Eso es lo que haremos para la llamada de ALAC el martes. Alan Al 22/03/2018 12:30 PM, Humberto Carrasco escribió: ¡Muchas gracias, Maritza! Es necesario saber si Adobe Connect funcionará correctamente. Recuerdos Enviado desde mi iPhone El 22-03-2018, a la (s) 13:21, Maritza Y.Aguero Minano <myaguero(a)msn.com> escribí : Estimado personal de la ICANN: Debido a los problemas dentro de la CA en ICANN61, significa que la llamada mensual de LACRALO se realizará mediante marcado / marcado solamente. ¿Estoy bien? Por favor, ¿puedes enfatizar esto a todos los miembros de la comunidad? Saludos, Maritza De: lac-discuss-en <lac-discuss-en-bounces(a)atlarge-lists.icann.org> en nombre de ICANN At-Large Staff <staff(a)atlarge.icann.org > Enviado: jueves, 22 de marzo de 2018 09:58 a.m.Para: lac-discuss-en(a)atlarge-lists.icann.org Asunto: [lac-discuss-es] Invitación a la reunión: Llamada mensual de LACRALO el lunes 26 de marzo de 2018 a las 23:00 UTC *** Tenga en cuenta que Adobe Connect NO se debe usar para esta reunión según GÃ corrió Marbyâ s blog y más recientemente recibido blog de Ashwin Rangan, SVP Engineering & Chief Information Officer. *** Estimados todos: La próxima llamada mensual de LACRALO está programada para el lunes 26 de marzo de 2018 a las 23:00 UTC. Se proporcionarán interpretaciones en espa� ol, francés y portugués.Para otros tiempos:https://tinyurl.com/yax9t67q La agenda (para ser actualizada) y los detalles de las llamadas están disponibles en: https://community.icann.org/x/yi68B ID de conferencia: EN 1638 ES 1738 FR 1838 PT 5393 Espacio de trabajo Wiki: https://community.icann.org / x / NJQi Confirme su marcación de salida y su número preferido a: staff(a)atlarge.icann.org Gracias. [ERROR: frase demasiado larga para traducir (2343> 1000 bytes)] [ERROR: frase demasiado larga para traducir (2173 > 1000 bytes)] [ERROR: frase demasiado larga para traducir (1952> 1000 bytes)][ERROR: frase demasiado larga para traducir (2866> 1000 bytes)] [[--Original text (en) Translated by transbot 2.18-2.04 http://mm.icann.org/transbot_archive/d3e71d3d78.html --]]

1 0

Re: [lac-discuss-es] RV: Meeting Invitation: LACRALO Monthly Call on Monday, 26 March 2018 at 23:00 UTC
by Alan Greenberg March 22, 2018

March 22, 2018

[[--Translated text (en -> es)--]] [[--This message had format issues and was not translated properly--]] Tema:Re: RV: Meeting Invitation: LACRALO Monthly Call on Monday, 26 March 2018 at 23:00 UTC De:Alan Greenberg <alan.greenberg(a)mcgill.ca> A partir de esta ma� ana, todavía no está funcionando. Tendremos que monitorearlo día a día. Al preparar el material para la reunión, asumiría que no funcionará y enviaré las cosas por correo a las personas con anticipación. Eso es lo que haremos para la llamada de ALAC el martes. Alan Al 22/03/2018 12:30 PM, Humberto Carrasco escribió: ¡Muchas gracias, Maritza! Es necesario saber si Adobe Connect funcionará correctamente.Recuerdos Enviado desde mi iPhone El 22-03-2018, a la (s) 13:21, Maritza Y. Aguero Minano <myaguero(a)msn.com> escribí : Estimado personal de la ICANN: Debido a los problemas dentro de la CA en ICANN61, significa que la llamada mensual de LACRALO se realizará mediante marcado / marcado solamente. ¿Estoy bien? Por favor, ¿puedes enfatizar esto a todos los miembros de la comunidad? Saludos, Maritza De: lac-discuss-en <lac-discuss-en-bounces(a)atlarge-lists.icann.org> en nombre de ICANN At-Large Staff <staff(a)atlarge.icann.org > Enviado: jueves, 22 de marzo de 2018 09:58 a.m.Para: lac-discuss-en(a)atlarge-lists.icann.org Asunto: [lac-discuss-es] Invitación a la reunión: Llamada mensual de LACRALO el lunes 26 de marzo de 2018 a las 23:00 UTC *** Tenga en cuenta que Adobe Connect NO se debe usar para esta reunión según GÃ corrió Marbyâ s blog y más recientemente recibido blog de Ashwin Rangan, SVP Engineering & Chief Information Officer. *** Estimados todos: La próxima llamada mensual de LACRALO está programada para el lunes 26 de marzo de 2018 a las 23:00 UTC. Se proporcionarán interpretaciones en espa� ol, francés y portugués.Para otros horarios: https://tinyurl.com/yax9t67q La agenda (para actualizar) y los detalles de las llamadas están disponibles en: https://community.icann.org/x/yi68B ID de conferencia: EN 1638 ES 1738 FR 1838 PT Espacio de trabajo de 5393 Wiki: https://community.icann.org/x/NJQi Confirme su número de marcado y preferido a: staff(a)atlarge.icann.org Gracias. [ERROR: Sentencia demasiado larga para traducir (1689> 1000 bytes)] [[--Original text (en) Translated by transbot 2.18-2.04 http://mm.icann.org/transbot_archive/525b310e06.html --]]

1 0

Meeting Invitation: LACRALO Monthly Call on Monday, 26 March 2018 at 23:00 UTC
by ICANN At-Large Staff March 22, 2018

March 22, 2018

[[--Translated text (en -> es)--]] [[--This message had format issues and was not translated properly--]] Tema: Meeting Invitation: LACRALO Monthly Call on Monday, 26 March 2018 at 23:00 UTC 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);} *** Tenga en cuenta que Adobe Connect NO se utilizará para esta reunión según el blog de Göran Marby y, más recientemente, el blog recibido de Ashwin Rangan, vicepresidente senior de ingeniería y director de informática. *** Queridos todos, La próxima llamada mensual de LACRALO está programada para el lunes 26 de marzo de 2018 a las 23:00 UTC. Se proporcionarán interpretaciones en espa� ol, francés y portugués. Para otros tiempos:https://tinyurl.com/yax9t67q La agenda (para ser actualizada) y los detalles de las llamadas están disponibles en:https://community.icann.org/x/yi68B ID de conferencia: EN 1638 ES 1738 FR 1838 PT 5393 Área de trabajo de Wiki: https: //community.icann.org/x/NJQi Por favor, confirme su número de marcado y preferido a: staff(a)atlarge.icann.org Gracias. Saludos cordiales, 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 Facebook: facebook.com/icannatlarge Twitter: @ICANNAtLarge [[--Original text (en) Translated by transbot 2.18-2.04 http://mm.icann.org/transbot_archive/c098e599e9.html --]]

1 0

Send e mail
by lilian ivette de luque bruges March 21, 2018

March 21, 2018

[[--Translated text (en -> es)--]] Tema: Send e mail De:lilian ivette de luque bruges <lilidebru(a)hotmail.com> lidebru18(a)gmail.com [[--Original text (en) Translated by transbot 2.18-2.04 http://mm.icann.org/transbot_archive/70e464b240.html --]]

1 0

Envío correo lista
by lilian ivette de luque bruges March 21, 2018

March 21, 2018

lilidebru(a)hotmail.com

1 0

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