My advanced, cautionary apologies because I might miss today’s meeting, or join quite late, given a day-job conflict. Will do my best, though. Javier Rúa-Jovet +1-787-396-6511 twitter: @javrua skype: javier.rua1 https://www.linkedin.com/in/javrua

On Feb 17, 2021, at 7:49 AM, Bart Boswinkel <bart.boswinkel@icann.org> wrote:

 Dear all, Please find included the agenda and drat resolutions. Also included (if time permits) the background material for the session on the Rules of the ccNSO. Kind regards, Bart

Agenda and Draft Resolutions ccNSO Council Meeting 170 18 February 2021 20.00 UTC

Welcome and roll call

Minutes & Action Items Minutes Meeting 169, circulated to the list 15 February 2021. Action items and To-do’s, if any Action Item 167-01 GRC to include note on definition of plurality in relevant guidelines. Ongoing

169-01: The Chair is requested to inform David on his appointment to IRP standing panel selection committee and relevant staff of ICANN Org accordingly. The Chair is also requested to inform the other Chairs of the Supporting Organizations and Advisory Committees and relevant ICANN Org staff that the ccNSO will only fill one seat. Completed

169-02 Send response to OEC letter. Completed See item 6 meeting 170

169-03 Chair to share information with Council on website status call Completed

To-do Alejandra Reynoso to forward Plenary session descriptions Completed

169-04 Chair to send email to Council asking for bilateral meeting topics (GNSO / ICANN Board) and whether the Council should meet with the Board as part of ICANN70 – outside of the usual QA session Council is asked to email as soon as possible. Completed. See item 10.b (i) meeting 170

Intermeeting Decisions (since 21 January 2021) Approval Terms of Reference OISC. Defer meeting with full Board Appointment Members IGLC Appointment Members MPC Appointment ccnSO Members Community Excellence Award Committee

ccPDP 3 Part 1 Retirement – Update Informational Part 2 Review Mechanism –Update Informational

IDN ccPDP4: Update Informational

Adoption Response to Board OEC letter For Decision Background Material: Draft Response to ICANN Board Organizational Effectiveness Committee

Draft Resolution The ccNSO Council agrees with the letter to the Board Organizational Effectiveness Committee, in response to their letter from 9 December 2020, to provide the OEC additional details and clarification per their request and inform them on the status of implementation of the recommendation of the second organizational review of the ccNSO. The Council requests its chair to send the letter as soon as feasible to the Chair of the OEC.

Approval of IANA Naming Function Contract Amendment per IFRT recommendation For Decision Background material: Request ICANN Org to support the recommended change IANA Naming Function Contract.

Draft Resolution Background The ccNSO Council has expressed its support for the recommendations of the IANA Function Review Team (online decision, November 2020). One of the recommendations (Recommendation 4) is to amend the text of the IANA Naming Function Contract section Article VII, Section 7.1 (a): Audits: “Contractor shall generate and publish via the IANA website a monthly audit report identifying each root zone file and root zone “WHOIS” database change request and its status. The relevant policies under which the changes are made shall be noted within each monthly report (emphasis added). Such audit report shall be due to ICANN no later than 15 calendar days following the end of each month.“ The IFRT recommends that the statement, "The relevant policies under which the changes are made shall be noted within each monthly report" be removed from the contract.

If the IFRT recommends amending the IANA Naming Function Contract, then and as part of the change process in accordance with section 18.3 of the Bylaws, both the ccNSO and GNSO Councils need to approve such change.

Decision Per request of the IFRT, dated 8 February, the ccNSO Council approves the proposed change of the IANA Naming Function Contract section Article VII, Section 7.1 (a): Audits, by striking the sentence The relevant policies under which the changes are made shall be noted within each monthly report (emphasis added) from the text of forementioned Article. The Chair of the ccNSO is requested to inform the Chairs of the IFRT and relevant ICANN staff accordingly, seven (7) days after this resolution is published. The secretariat is requested to publish this resolution as soon as possible and inform the community accordingly.

Call for volunteers Outreach & Involvement Standing Committee For Decision Draft Resolution Background The ccNSO has adopted the Terms of Reference (ToR) of the Outreach & Involvement Standing Committee (OISC) recently. According to the ToR the OISC should consist of: Up to four (4) 4 ccNSO Councillors: at least one of them should be a NomCom appointed Councillor and one should be the Chair or Vice-Chair of the Council The ccNSO Meetings Programme Committee Chair Up to four (4) representatives of the Regional Organizations (ROs) Up to three (3) representatives from ccTLD Managers (members and non-members of the ccNSO alike) Decision The Secretariat is requested to launch a call for Expression of Interest for each to each of these groups listed in the ToR. The call should close on Friday 12 March 2021. The secretariat is requested to organize a webinar to introduce the OISC to the broader community and to solicit interest to actively participate.

Adoption ccNSO Statement procedure regarding the Amendment of Article 10 ICANN Bylaws For Decision Background material: draft cover note and detailed proposal

Draft Resolution Background At its meeting on 20 October 2020 the ccNSO Council decided to initiate the ccNSO Statement Procedure in response to suggestion and questions from ICANN legal on the recommended amendments of Article 10 and Annex B of the ICANN Bylaws to take away the barriers for IDNccTLD Managers to become member of the ccNSO. The recommended amendments were included in the Members Report of ccPDP2 (the overall policy on selection and inclusion of IDNccTLDs) and as supported by the ccNSO Membership in 2013.

The ccNSO Council established the required Drafting Team on 8 December 2020 by appointing: Ai-Chin Lu (chair) Hiro Hotta (.jp) Jiankang Yao (.cn) Mira Fajri (.id)

In accordance with the Guideline: ccNSO Statements (2016) (https://ccnso.icann.org/sites/default/files/filefield_47783/guidelines-state...) the Drafting Team prepared a draft response and first consulted the Council and then the ccNSO Membership (from . The membership did not provide changes to the draft response nor did the drafting team receive any objections from the Membership

In preparing the response the Drafting Team noted and has informed the ccNSO Council: The Drafting Team expressed a clear preference to use the more generic term “by electronic means” instead of “email vote” as method of voting (see Article 10, Section 10.4 (i)in the ICANN Bylaws), to ensure technology-independency. Details about the voting process and related tools should be provided in the ccNSO internal procedures. The principle of one vote per member for those organizations or entities that manage multiple ASCII ccTLDs will not be affected by the proposed Bylaw change. This implies that those organizations or entities that have become member for two or more ccTLDs and have become member of the ccNSO will still be able to cast two or more votes in formal voting processes (in the Board nomination process, the Council elections and in membership approval voting of ccPDPs). As was noted in the ccPDP2 part 2, this issue may need to be addressed at one point, to ensure parity of members, who run multiple ccTLDs. Note, Organizations or entities who run multiple IDN ccTLDs related to one (1) country or territory will at a maximum have one (1) vote. The Drafting Team informs Council that the bylaw change will have consequences for the ccNSO Council election guideline and ccNSO Board nomination guideline (see: https://ccnso.icann.org/en/about/guidelines.htm [ccnso.icann.org] ), following Article 10, Section 10.4(h): nomination by any ccNSO member. The Drafting Team advises Council to ask the GRC to look at this issue in due time.

Decision The ccNSO Council supports and adopts the Response as proposed by the Drafting Team and asks the secretariat to publish this decision and the response as adopted as soon as possible. The Chair of the Council is requested to inform relevant ICANN staff (seven (7) days after publication of publication of this decision and sent the response as adopted accordingly o ICANN staff.

With respect to difference between the entities who manage multiple ASCII ccTLD and entities who run multiple IDNccTLDs relating to the same country or territory (point b above) the ccNSO Council requests the secretariat to update the Bylaw change repository accordingly as item that needs to be discussed as suggested.

With respect to point a. and b. above, the Chair is requested to inform the GRC of the need to update various Guidelines and the internal procedures to align the Guidelines and internal procedures with the proposed changes to Article 10 and Annex B of the ICANN Bylaws by the time they become effective.

Finally, the Council wholeheartedly thanks the Drafting Team and the secretariat for their hard work to bring the Response to a conclusion.

Update ICANN70 (related) sessions ccTLDs related sessions i. Tech Day ii. Members meeting sessions Governance session ccTLDs: looking at the future Q&A ccTLD related Board members IGLC: Digital Sovereignty iii. ccTLD News sessions Joint meetings: i. Meeting with the Board: Update ii. Meeting with GAC: Update iii. Meeting with GNSO Council: Update Council workshop: Tuesday 16 March 2021, 20.00 UTC i. Review role of chair and vice -chairs, Roles and responsibilities of Councillors ii. Work plan iii. Other? Council Preparatory meeting, Thursday 18 March 12.00 UTC

Update ECA & CSC ECA (Informational) CSC (Informational)

Update Chair, Vice-Chairs, Councillors, RO’s and Secretariat

Update WGs SOPC IGLC GRC

Update liaisons Update ALAC Liaison (written update) Update GNSO Liaison (written update to follow)

Meetings Next Council Meetings: February 18 – 20:00 UTC March 25 (ICANN70) 17:30-19:00 UTC April 22 – 12:00 UTC May 20 – 18.00 UTC

AOB

Discussion session on what needs to be included in future Rules of the ccNSO (if time permits) Informational Background The current Rules of the ccNSO have been established in 2004. Since 2004 the ccNSO itself and the environment in which it operates has evolved. For example, when the Rules were adopted in 2004, the ccNSO had around 50 members. Currently, there are 172 members. Another example, to address various needs of the growing (membership- and importance-wise) ccNSO, in 2007 the ccNSO started to develop internal procedures (guidelines) as envisioned in the Bylaws (currently, Article 10). Next example, the introduction of the Empowered Community and the role of the ccNSO as a decisional Participant. It is obvious that this new role was NOT envisioned at the time the Rules of the ccNSO were conceived. The need to update the Rules has been recognized and discussed by the ccNSO members at several meetings for the past 3 years.

If time permits, this session is intended to ask Councillors through break-out rooms to identify topics and aspects of the ccNSO Governance you would like to see included in future Rules of the ccNSO. Your input will be used by the GRC in its work.

Material: Possible topics to include in FUTURE Rules of the ccNSO ccNSO Rules of the ccNSO 2004

Closure

<Agenda and draft resolutionsCouncil meeting 170 - 21 February 2021 v2.pdf> <Agenda and draft resolutionsCouncil meeting 170 - 21 February 2021 v2.docx> <item 17 -Meeting 170 ccnso-rules-dec04-en.pdf> <Item 17 Meeting 170 POTENTIAL TOPICS FUTURE ccNSO RULES January 2021.pdf> _______________________________________________ Ccnso-council mailing list 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.

Hello All, Notes during today’s Council meeting will be taken here: https://docs.google.com/document/d/1eWW4CUA0JEVmyPNhOxQr9-6BBFoG6QkaY4QDEOk-... Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken@icann.org From: Ccnso-council <ccnso-council-bounces@icann.org> on behalf of Bart Boswinkel <bart.boswinkel@icann.org> Date: Wednesday, 17 February 2021 at 12:57 To: ccnso-council <ccNSO-Council@icann.org> Subject: [ccnso-council] Agenda and draft resolutions Meeting 170 ccNSO Council Dear all, Please find included the agenda and drat resolutions. Also included (if time permits) the background material for the session on the Rules of the ccNSO. Kind regards, Bart Agenda and Draft Resolutions ccNSO Council Meeting 170 18 February 2021 20.00 UTC 1. Welcome and roll call 1. Minutes & Action Items * Minutes Meeting 169, circulated to the list 15 February 2021. * Action items and To-do’s, if any Action Item 167-01 GRC to include note on definition of plurality in relevant guidelines. Ongoing 169-01: The Chair is requested to inform David on his appointment to IRP standing panel selection committee and relevant staff of ICANN Org accordingly. The Chair is also requested to inform the other Chairs of the Supporting Organizations and Advisory Committees and relevant ICANN Org staff that the ccNSO will only fill one seat. Completed 169-02 Send response to OEC letter. Completed See item 6 meeting 170 169-03 Chair to share information with Council on website status call Completed To-do Alejandra Reynoso to forward Plenary session descriptions Completed 169-04 Chair to send email to Council asking for bilateral meeting topics (GNSO / ICANN Board) and whether the Council should meet with the Board as part of ICANN70 – outside of the usual QA session Council is asked to email as soon as possible. Completed. See item 10.b (i) meeting 170 1. Intermeeting Decisions (since 21 January 2021) * Approval Terms of Reference OISC. * Defer meeting with full Board * Appointment Members IGLC * Appointment Members MPC * Appointment ccnSO Members Community Excellence Award Committee 1. ccPDP 3 * Part 1 Retirement – Update Informational * Part 2 Review Mechanism –Update Informational 1. IDN ccPDP4: Update Informational 1. Adoption Response to Board OEC letter For Decision Background Material: Draft Response to ICANN Board Organizational Effectiveness Committee Draft Resolution The ccNSO Council agrees with the letter to the Board Organizational Effectiveness Committee, in response to their letter from 9 December 2020, to provide the OEC additional details and clarification per their request and inform them on the status of implementation of the recommendation of the second organizational review of the ccNSO. The Council requests its chair to send the letter as soon as feasible to the Chair of the OEC. 1. Approval of IANA Naming Function Contract Amendment per IFRT recommendation For Decision Background material: Request ICANN Org to support the recommended change IANA Naming Function Contract. Draft Resolution Background The ccNSO Council has expressed its support for the recommendations of the IANA Function Review Team (online decision, November 2020). One of the recommendations (Recommendation 4) is to amend the text of the IANA Naming Function Contract section Article VII, Section 7.1 (a): Audits: “Contractor shall generate and publish via the IANA website a monthly audit report identifying each root zone file and root zone “WHOIS” database change request and its status. The relevant policies under which the changes are made shall be noted within each monthly report (emphasis added). Such audit report shall be due to ICANN no later than 15 calendar days following the end of each month.“ The IFRT recommends that the statement, "The relevant policies under which the changes are made shall be noted within each monthly report" be removed from the contract. If the IFRT recommends amending the IANA Naming Function Contract, then and as part of the change process in accordance with section 18.3 of the Bylaws, both the ccNSO and GNSO Councils need to approve such change. Decision Per request of the IFRT, dated 8 February, the ccNSO Council approves the proposed change of the IANA Naming Function Contract section Article VII, Section 7.1 (a): Audits, by striking the sentence The relevant policies under which the changes are made shall be noted within each monthly report (emphasis added) from the text of forementioned Article. The Chair of the ccNSO is requested to inform the Chairs of the IFRT and relevant ICANN staff accordingly, seven (7) days after this resolution is published. The secretariat is requested to publish this resolution as soon as possible and inform the community accordingly. 1. Call for volunteers Outreach & Involvement Standing Committee For Decision Draft Resolution Background The ccNSO has adopted the Terms of Reference (ToR) of the Outreach & Involvement Standing Committee (OISC) recently. According to the ToR the OISC should consist of: * Up to four (4) 4 ccNSO Councillors: at least one of them should be a NomCom appointed Councillor and one should be the Chair or Vice-Chair of the Council * The ccNSO Meetings Programme Committee Chair * Up to four (4) representatives of the Regional Organizations (ROs) * Up to three (3) representatives from ccTLD Managers (members and non-members of the ccNSO alike) Decision The Secretariat is requested to launch a call for Expression of Interest for each to each of these groups listed in the ToR. The call should close on Friday 12 March 2021. The secretariat is requested to organize a webinar to introduce the OISC to the broader community and to solicit interest to actively participate. 1. Adoption ccNSO Statement procedure regarding the Amendment of Article 10 ICANN Bylaws For Decision Background material: draft cover note and detailed proposal Draft Resolution Background At its meeting on 20 October 2020 the ccNSO Council decided to initiate the ccNSO Statement Procedure in response to suggestion and questions from ICANN legal on the recommended amendments of Article 10 and Annex B of the ICANN Bylaws to take away the barriers for IDNccTLD Managers to become member of the ccNSO. The recommended amendments were included in the Members Report of ccPDP2 (the overall policy on selection and inclusion of IDNccTLDs) and as supported by the ccNSO Membership in 2013. The ccNSO Council established the required Drafting Team on 8 December 2020 by appointing: * Ai-Chin Lu (chair) * Hiro Hotta (.jp) * Jiankang Yao (.cn) * Mira Fajri (.id) In accordance with the Guideline: ccNSO Statements (2016) (https://ccnso.icann.org/sites/default/files/filefield_47783/guidelines-state... [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/sites/default/files/filef...>) the Drafting Team prepared a draft response and first consulted the Council and then the ccNSO Membership (from . The membership did not provide changes to the draft response nor did the drafting team receive any objections from the Membership In preparing the response the Drafting Team noted and has informed the ccNSO Council: * The Drafting Team expressed a clear preference to use the more generic term “by electronic means” instead of “email vote” as method of voting (see Article 10, Section 10.4 (i)in the ICANN Bylaws), to ensure technology-independency. Details about the voting process and related tools should be provided in the ccNSO internal procedures. * The principle of one vote per member for those organizations or entities that manage multiple ASCII ccTLDs will not be affected by the proposed Bylaw change. This implies that those organizations or entities that have become member for two or more ccTLDs and have become member of the ccNSO will still be able to cast two or more votes in formal voting processes (in the Board nomination process, the Council elections and in membership approval voting of ccPDPs). As was noted in the ccPDP2 part 2, this issue may need to be addressed at one point, to ensure parity of members, who run multiple ccTLDs. Note, Organizations or entities who run multiple IDN ccTLDs related to one (1) country or territory will at a maximum have one (1) vote. * The Drafting Team informs Council that the bylaw change will have consequences for the ccNSO Council election guideline and ccNSO Board nomination guideline (see: https://ccnso.icann.org/en/about/guidelines.htm [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/en/about/guidelines.htm__...> ), following Article 10, Section 10.4(h): nomination by any ccNSO member. The Drafting Team advises Council to ask the GRC to look at this issue in due time. Decision The ccNSO Council supports and adopts the Response as proposed by the Drafting Team and asks the secretariat to publish this decision and the response as adopted as soon as possible. The Chair of the Council is requested to inform relevant ICANN staff (seven (7) days after publication of publication of this decision and sent the response as adopted accordingly o ICANN staff. With respect to difference between the entities who manage multiple ASCII ccTLD and entities who run multiple IDNccTLDs relating to the same country or territory (point b above) the ccNSO Council requests the secretariat to update the Bylaw change repository accordingly as item that needs to be discussed as suggested. With respect to point a. and b. above, the Chair is requested to inform the GRC of the need to update various Guidelines and the internal procedures to align the Guidelines and internal procedures with the proposed changes to Article 10 and Annex B of the ICANN Bylaws by the time they become effective. Finally, the Council wholeheartedly thanks the Drafting Team and the secretariat for their hard work to bring the Response to a conclusion. 1. Update ICANN70 (related) sessions * ccTLDs related sessions i. Tech Day ii. Members meeting sessions * Governance session * ccTLDs: looking at the future * Q&A ccTLD related Board members * IGLC: Digital Sovereignty iii. ccTLD News sessions * Joint meetings: i. Meeting with the Board: Update ii. Meeting with GAC: Update iii. Meeting with GNSO Council: Update * Council workshop: Tuesday 16 March 2021, 20.00 UTC i. Review role of chair and vice -chairs, Roles and responsibilities of Councillors ii. Work plan iii. Other? * Council Preparatory meeting, Thursday 18 March 12.00 UTC 1. Update ECA & CSC * ECA (Informational) * CSC (Informational) 1. Update Chair, Vice-Chairs, Councillors, RO’s and Secretariat 1. Update WGs * SOPC * IGLC * GRC 1. Update liaisons * Update ALAC Liaison (written update) * Update GNSO Liaison (written update to follow) 1. Meetings Next Council Meetings: * February 18 – 20:00 UTC * March 25 (ICANN70) 17:30-19:00 UTC * April 22 – 12:00 UTC * May 20 – 18.00 UTC 1. AOB 1. Discussion session on what needs to be included in future Rules of the ccNSO (if time permits) Informational Background The current Rules of the ccNSO have been established in 2004. Since 2004 the ccNSO itself and the environment in which it operates has evolved. For example, when the Rules were adopted in 2004, the ccNSO had around 50 members. Currently, there are 172 members. Another example, to address various needs of the growing (membership- and importance-wise) ccNSO, in 2007 the ccNSO started to develop internal procedures (guidelines) as envisioned in the Bylaws (currently, Article 10). Next example, the introduction of the Empowered Community and the role of the ccNSO as a decisional Participant. It is obvious that this new role was NOT envisioned at the time the Rules of the ccNSO were conceived. The need to update the Rules has been recognized and discussed by the ccNSO members at several meetings for the past 3 years. If time permits, this session is intended to ask Councillors through break-out rooms to identify topics and aspects of the ccNSO Governance you would like to see included in future Rules of the ccNSO. Your input will be used by the GRC in its work. Material: Possible topics to include in FUTURE Rules of the ccNSO ccNSO Rules of the ccNSO 2004 1. Closure