Dear Bart, I support the resolution. Best regards! [cid:361af356-b72f-4d03-99e9-b5b1eb7a4924] ________________________________ De: Ccnso-council <ccnso-council-bounces@icann.org> en nombre de Alejandra Reynoso via Ccnso-council <ccnso-council@icann.org> Enviado: viernes, 30 de julio de 2021 9:52 a. m. Para: Bart Boswinkel <bart.boswinkel@icann.org> Cc: ccNSO-Council@icann.org <ccNSO-Council@icann.org> Asunto: Re: [ccnso-council] Adoption Template 2nd CSC Effectiveness Review Dear Bart I support the resolution with the observation that the Template should be updated on: 1. Part 8. Proposed Review Process item 3. Conduct a public session at ICANN 63 (October 2018) that is intended to provide an opportunity for the community to provide input to the process. * Should be ICANN 72 (October 2021) 2. Part 9. Review Schedule last bullet on October 2021 – November 2021 Consultation with CSC and PTI: Virtual Public consultation direct customers and other interested parties (ccTLD, gTLD operators, others) post ICANN71, * Should be ICANN 72 Best regards, Alejandra -- [Photograph] Alejandra Reynoso Investigación & Desarrollo | Dominios .gt P: +502 23688565 E: alejandra.reynoso@cctld.gt<mailto:alejandra.reynoso@cctld.gt> 18 Ave. 11-95 Zona 15, V.H. III. (A-109) Guatemala, Guatemala www.gt<http://www.gt/> On Tue, Jul 27, 2021 at 9:59 AM Bart Boswinkel via Ccnso-council <ccnso-council@icann.org<mailto:ccnso-council@icann.org>> wrote: Dear all, Please find included the proposed resolution on adoption the Template for the 2nd CSC Effectiveness Review. The topic was introduced on the latest Council call, and as agreed the Council would take a decision by email. For reference the Template is included. If you have any comments or questions regarding the process or template, please use this mailing list to raise them. Please vote by Tuesday. 3 August 2021 23.59 UTC, whether you Support, Abstain or Object to the resolution, Thank and Kind regards, Bart ------ Template 2nd CSC Effectiveness Reviews Draft Resolution Background The ICANN Bylaws and CSC Charter require that the “… effectiveness of the CSC will initially be reviewed two years after the first meeting of the CSC; and then every three years thereafter. The method of review will be determined by the ccNSO and GNSO.” The CSC was established in accordance with Article 17.3 (b) of the ICANN Bylaws and conducted its first meeting on 6 October 2016. In order to meet the timeline for the second review of the CSC Effectiveness, the ccNSO and GNSO Councils will need to determine the method for conducting the review before 1 October 2021. The second CSC Effectiveness Review is intended to consider the Effectiveness of the CSC in carrying out its mission as defined in its charter. Decision The ccNSO Council adopts the proposed Template for the 2nd CSC Effectiveness Review to determine the effevctiveness Customer Standing Committee (CSC) as required under the Bylaws and the Charter of the CSC. This adoption is conditional, dependent upon adoption of the Template as adopted by the GNSO Council, no later than 1 September 2021. The ccNSO Council request its Chair to inform the GNSO Council chair accordingly. If, and when the GNSO Council has adopted the Template, the ccNSO Council Chair, together with the Chair of the GNSO Council, is requested to inform the ICANN Board of Directors, the President and CEO of ICANN and the Chair of CSC accordingly. Further, the ccNSO Council request the secretariat to send out a call for Expression of Interest to seek two (2) ccNSO appointed members on the Effectiveness Review Team. Finally, the Council requests the secretariat to publish the decision and Template upon adoption as soon as possible. This resolution becoems effective seven (7) days after publication _______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org<mailto:Ccnso-council@icann.org> https://mm.icann.org/mailman/listinfo/ccnso-council _______________________________________________ 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. ***************Este mensaje (y sus adjuntos), en adelante "mensaje", ha sido enviado exclusivamente a su(s) destinatario(s) y es confidencial. Si usted recibe este mensaje por error, por favor bórrelo y comunique inmediatamente al remitente. Toda utilización o publicación, total o parcial, queda prohibida salvo autorización expresa. La UTP no podrá ser considerada responsable si el mensaje ha sido modificado y/o utilizado sin autorización. This message (and any attachments), are confidential intended solely for the people whose addresses appear. If you have received this message by error, please delete it and immediately notify the sender. Any use, dissemination or disclosure, either whole or partial, without formal approval is prohibited. The UTP will not therefore be liable for the message if modified and/or used without approval.************** ***************Este mensaje (y sus adjuntos), en adelante "mensaje", ha sido enviado exclusivamente a su(s) destinatario(s) y es confidencial. Si usted recibe este mensaje por error, por favor bórrelo y comunique inmediatamente al remitente. Toda utilización o publicación, total o parcial, queda prohibida salvo autorización expresa. La UTP no podrá ser considerada responsable si el mensaje ha sido modificado y/o utilizado sin autorización. This message (and any attachments), are confidential intended solely for the people whose addresses appear. If you have received this message by error, please delete it and immediately notify the sender. Any use, dissemination or disclosure, either whole or partial, without formal approval is prohibited. The UTP will not therefore be liable for the message if modified and/or used without approval.**************
