For your information and if anyone is interested. Best regards, Osvaldo Enviado desde mi iPhone Inicio del mensaje reenviado: De: "Drazek, Keith via council" <council@gnso.icann.org> Fecha: 3 de agosto de 2020, 17:42:50 UYT Para: "council@gnso.icann.org" <council@gnso.icann.org> Asunto: [council] FW: [gnso-secs] Call for volunteers: ccPDP4 on the (de)selection of IDN ccTLD strings Responder a: "Drazek, Keith" <kdrazek@verisign.com>  Hi all, The deadline for identifying GNSO representatives for the ccNSO’s policy development process on IDNs (ccPDP4) is this Friday, August 7. It will be important for the GNSO and ccNSO to understand our respective work in this area, so GNSO participation is encouraged. Please raise this with your SGs and Cs. Thanks, Keith From: Nathalie Peregrine <nathalie.peregrine@icann.org> Sent: Monday, August 3, 2020 1:24 PM To: Drazek, Keith <kdrazek@verisign.com> Subject: [EXTERNAL] FW: [gnso-secs] Call for volunteers: ccPDP4 on the (de)selection of IDN ccTLD strings From: Gnso-secs <gnso-secs-bounces@icann.org<mailto:gnso-secs-bounces@icann.org>> on behalf of Nathalie Peregrine <nathalie.peregrine@icann.org<mailto:nathalie.peregrine@icann.org>> Date: Friday, 17 July 2020 at 15:02 To: 'Bruna Martins dos Santos' <bruna.mrtns@gmail.com<mailto:bruna.mrtns@gmail.com>>, Joan Kerr <joankerr@fbsc.org<mailto:joankerr@fbsc.org>>, Stephanie Perrin <stephanie.perrin@mail.utoronto.ca<mailto:stephanie.perrin@mail.utoronto.ca>> Cc: "gnso-secs@icann.org<mailto:gnso-secs@icann.org>" <gnso-secs@icann.org<mailto:gnso-secs@icann.org>>, Maryam Bakoshi <maryam.bakoshi@icann.org<mailto:maryam.bakoshi@icann.org>> Subject: [gnso-secs] Call for volunteers: ccPDP4 on the (de)selection of IDN ccTLD strings Dear GNSO Chairs, All, The ccNSO seeks volunteers for the Working Group which is tasked to develop policy recommendations for the (de)selection of IDN ccTLD strings, as part of the fourth ccNSO Policy Development Process (ccPDP4). In time, the results of this ccPDP will replace the IDN ccTLD Fast Track Process, which currently guides the selection process of IDN ccTLD strings. This Working Group is open to participants from other ICANN stakeholder groups and the ccNSO welcomes GNSO representatives to join this important policy development effort. The call for volunteers will close Friday, 7 August 2020 (23:59 UTC), however participants can join after this date as well. The Group is expected to kick off its work at the start of September. Members, participants, and experts commit to participate actively and regularly in the work of the WG and are expected to have at least a basic understanding of the reference material (see attachment and included below). Those that apply also commit to the charter<https://secure-web.cisco.com/1s65TC2OFJzEjPSt7DE9koA7dOnsArkM0C_QlVwk9bGQ40H...> of the WG, including but not limited to the internal decision making and standards of behavior. Should there be interested parties that intend to join as a participants - once your respective SO/AC has completed its internal appoint procedure - please inform the ccNSO Secretariat (ccnsosecretariat@icann.org<mailto:ccnsosecretariat@icann.org>) about the names and email addresses, to add them to the mailing list. Read more * Detailed background information about ccPDP4 is included below. * Recently, the ccNSO Secretariat held a webinar to inform the community about the topics to be addressed and the working methods of the ccPDP4 WG. Consult the recording and slide deck here<https://secure-web.cisco.com/1EwMoKrr2C6iYXsCAli8ynCXGv3N0ury3Bh75_gXPCudvk-...>. * On 16 July, the ccNSO Secretariat shared a call for volunteers with the ccNSO membership and broader ccTLD community, targeted at ccTLD managers as potential members of the Working Group. Please find the call for volunteers here [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/en/announcements/announce...>. You may find the information regarding who can join, the workload and working method and the background and reference materials useful. * In attachment you will be able to find information regarding the call for volunteers, that can be shared with your respective SO/AC. Kindly ensure to adjust the “how to apply” section. About ccPDP4 In September 2013, the ccNSO submitted the IDN country code policy development process (ccPDP2) Board Report to the ICANN Board of Directors. The recommended policy ccPDP2 contains two parts: 1. High-level proposals for the criteria and requirements for the IDN ccTLD string selection and activities, roles, and responsibilities of the actors involved in the string selection and string evaluation processes and procedures. 2. Proposals to enable the inclusion of IDN ccTLDs in the ccNSO. By mutual understanding between the ccNSO and the ICANN Board, the Fast Track Process evolved, to test and gain more experience with the policy aspects pertaining to the introduction of IDN ccTLDs. The latest step in the evolution of the Fast Track Process was the introduction of the Risk Mitigation Panel and related process in case of confusing similarity of a requested IDNccTLD string in 2018. In March 2019 the ccNSO Council tasked a team (Preliminary Review Team or PRT) to review ccPDP2 in light of the impact of the following related processes on the recommended policies: * The evolved Fast Track Process, * The request of the ICANN Board of Directors with respect to IDN Variants and * Other relevant developments such as retirement of the (IDN) ccTLDs Based on its high-level analysis, the PRT identified various issues with the recommended policy for the selection of IDN ccTLD strings and advised Council to launch a ccNSO Policy Development Process (ccPDP4) to address these issues, including the de-selection of IDN ccTLD strings. In January 2020, the ccNSO Council requested an Issue Report. In May 2020, after the Issue Report was submitted to Council, including the opinion of ICANN’s General Counsel, the ccNSO Council initiated the ccNSO Policy Development Process 4 to develop policy for the (de-)selection of IDN ccTLD strings. In addition, it was proposed to conduct ccPDP4 by way of a chartered working group, according to the proposed timeline. The Issue report will be published for comments shortly. The public comments, if any, will be used to inform the discussions of the WG. Reference Materials & Links * Issue report<https://secure-web.cisco.com/1gUcPYhKIK559glvrjKWDlRn-e39dSsgVGicFxTgGcwhCU4...> * ccPDP4 section on ccNSO website: https://ccnso.icann.org/en/workinggroups/idn-cctld-strings.htm [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/en/workinggroups/idn-cctl...> * ccPDP4 Workspace: https://community.icann.org/x/ZoBIC<https://secure-web.cisco.com/1S8wIMCBWer14yfW6q_qJ9iHS-4vqliC14UgYHKM9Aen_FrMIhaf594qZHk1IU9ngPQCf6VKrbkbok2Yq3Dr2BJjeNKLkPnOdxnX-ZM1AcINSnpPc8PuLdTNh-_E7YCAHUPG2zlc_Z9VBH3vJol2V5uT08ywu9KPCWlrJuIEI3jKERU6Q9SCWSO0Kc1VgZvsRxlckSLzWwVeoEHPFEZV8tdunKAYVt1uDpIB_CLxcRLFxPdVMAZ8HySnodr9DwECQa3KaOHQzA_ujce-ZQQMK3g/https%3A%2F%2Fcommunity.icann.org%2Fx%2FZoBIC> Thank you. Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken@icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO [twitter.com]<https://urldefense.com/v3/__https:/twitter.com/ccNSO__;!!PtGJab4!oaAoZdUSgyV...> Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ [facebook.com]<https://urldefense.com/v3/__https:/www.facebook.com/ccnso/__;!!PtGJab4!oaAoZ...> http://ccnso.icann.org [ccnso.icann.org]<https://urldefense.com/v3/__http:/ccnso.icann.org__;!!PtGJab4!oaAoZdUSgyVj4Q...> _______________________________________________ Gnso-secs mailing list Gnso-secs@icann.org https://mm.icann.org/mailman/listinfo/gnso-secs _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on._______________________________________________ Gnso-secs mailing list Gnso-secs@icann.org https://mm.icann.org/mailman/listinfo/gnso-secs _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://urldefense.com/v3/__https://www.icann.org/privacy/policy__;!!PtGJab4... ) and the website Terms of Service (https://urldefense.com/v3/__https://www.icann.org/privacy/tos__;!!PtGJab4!oa... ). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. ________________________________ El presente correo y cualquier posible archivo adjunto está dirigido únicamente al destinatario del mensaje y contiene información que puede ser confidencial. Si Ud. no es el destinatario correcto por favor notifique al remitente respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su sistema. Está prohibida cualquier utilización, difusión o copia de este e-mail por cualquier persona o entidad que no sean las específicas destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con respecto a cualquier comunicación que haya sido emitida incumpliendo nuestra Política de Seguridad de la Información This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. ANTEL is not responsible for any communication emitted without respecting our Information Security Policy.