Dear Heiki, Thank you very much for your review of the draft ccNSO response to questions from ICANN legal regarding a Bylaw change to include IDN ccTLDs as members to the ccNSO. Following closure of the comment period, the drafting team met on 3 February, and discussed your comments. Please find included the response by the drafting team. Article 10, Section 10.4 (a) The drafting team fully agrees that it should be clear that only ccTLD managers can become members to the ccNSO. So to avoid confusion, the drafting team suggests to completely strike the second sentence: “Any organization or entity that meets the membership qualifications stated in this Section shall be entitled to be member of the ccNSO.” Please find a revised version with track changes enclosed (v3-03022021). Article 10, Section 10.4 (i) Regarding the tool used during elections, the suggestion is to replace “email” with “by electronic means”. There is a clear preference to use the more generic term in the ICANN Bylaws, to be technology independent. Details about the voting process and related tools will be provided in the ccNSO procedures. The drafting team hopes your concerns are addressed. If there are no further comments by Friday, 5 February (23:59 UTC), the ccNSO Council will be asked to adopt v3_03022021 of the draft response. Once adopted, the response will be sent to ICANN Legal for its consideration. Thank you. Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken@icann.org From: Heiki Sibul <heiki.sibul@internet.ee> Date: Friday, 22 January 2021 at 15:56 To: Joke Braeken <joke.braeken@icann.org> Subject: [Ext] Re: [ccnso-members] we seek your feedback | ccNSO response to questions from ICANN legal regarding a Bylaw change to include IDN ccTLDs as members to the ccNSO. Dear Joke, Thank you for seeking our input and feedback for the ccNSO response on the proposed draft changing the Bylaws of ICANN. Overall, we support the ICANN Legal's edits to the initial ccNSO's proposal. Regarding the ccNSO's response letter to ICANN Legal, we suggest the following edits to the letter: 1) Article 10, Section 10.4 (a): Not knowing the drafting team's reasoning behind this, we suggest not to change "any ccTLD manager" to "any organization or entity". Changing this would create a false perception that any organization or entity could become a member of ccNSO. According to the following Sections from the Bylaws, it is clear that only a ccTLD manager is entitled to be a member of ccNSO, not any organization or entity. For legal certainty and clarity, it would be reasonable not to change "any ccTLD manager" to "any organization or entity" in Article 10, Section 10.4 (a); 2) Article 10, Section 10.4(i): We agree that expanding the casting of the ballot from e-mail to electronic means could be necessary for the purpose of facilitating the transition to more virtual meetings in the future or transition to modern voting solutions, but could it be explained more precisely e.g. in the drafting team's memorandums, what is meant by electronic means? We would like to thank ccNSO drafting team for their efforts and if you have any questions do not hesitate to contact us. Best regards, Heiki Sibul Eesti Interneti SA • Paldiski mnt 80, 10617 Tallinn Tel + 372 727 1000 • Mob +372 504 6524 www.internet.ee [eestiinternet.ee]<https://urldefense.com/v3/__http:/www.eestiinternet.ee/__;!!PtGJab4!rAO2Ys72...> Kontakt Joke Braeken (<joke.braeken@icann.org<mailto:joke.braeken@icann.org>>) kirjutas kuupäeval N, 21. jaanuar 2021 kell 18:13: Dear ccNSO Members, I am forwarding you an email on behalf of Ai-Chin Lu, ccNSO Councillor leading the drafting team for the ccNSO response to questions from ICANN legal regarding a Bylaw change to include IDN ccTLDs as members to the ccNSO. Kindly note that the drafting team seeks your input. Close date is Monday, 1 February 2021 (23:59 UTC). Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken@icann.org<mailto:joke.braeken@icann.org> = = = = Dear ccNSO Members, In order to include IDN ccTLDs as members to the ccNSO, the ccNSO Council requested changes to article 10 in the ICANN Bylaws. Since ICANN legal raised some questions, a drafting team was tasked with writing a ccNSO response. The drafting team now seeks your input and feedback on the proposed draft, allowing for further considerations, and eventually adoption of a response by the ccNSO Council. Please find enclosed the proposed letter to ICANN legal, including an Annex. The drafting team seeks your comments. Close date is Monday, 1 February 2021 (23:59 UTC). Your input will be reviewed by the drafting team, prior to adoption of the final response by the ccNSO Council. Thank you. Best regards, Ai-Chin Lu (.tw) | drafting team Chair Hirofumi Hotta (.jp), Jiankang Yao (.cn), Mira Fajri (.id) Background * ccNSO request to amend article 10 of the ICANN bylaws [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/sites/default/files/field...>. (7 february 2020) * Response from ICANN legal - October 2020 [drive.google.com]<https://urldefense.com/v3/__https:/drive.google.com/file/d/1ZDpynivqNcPU4JYm...> * Guideline: ccNSO statements [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/sites/default/files/filef...> * ICANN Bylaws [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/governance/...> _______________________________________________ Ccnso-members mailing list Ccnso-members@icann.org<mailto:Ccnso-members@icann.org> https://mm.icann.org/mailman/listinfo/ccnso-members _______________________________________________ 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 [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/privacy/policy__;!!PtGJab4!...>) and the website Terms of Service (https://www.icann.org/privacy/tos [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/privacy/tos__;!!PtGJab4!rAO...>). 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.