Dear All: The next ccNSO meeting will take place next *Thursday September 19th., at 12:00 UTC* Here is the *DRAFT AGENDA* <https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Report...> *BACKGROUND MATERIALS and Council Workspace* <https://community.icann.org/x/HQEZEw> and *STATEMENTS and RESPONSES* <https://ccnso.icann.org/en/about/statements.htm> ***If you would like to join as an observer, you are welcome, please, send an email to Claudia Ruiz claudia.ruiz@icann.org <claudia.ruiz@icann.org> and she will send you the zoom link.* ccNSO Council Meeting 209 (draft agenda, including one draft resolution) Thursday, 19 September 2024 at 12:00 UTC AGENDA 1. Welcome *a) **Establish Whether Meeting Is Quorate* 2. Updates Statements of Interest Fill out the ccNSO Statement of Interest form: https://forms.gle/79Jw4wSnNhn5W4Z46 Check your SOI here: https://community.icann.org/x/doAFEg Consult the ccNSO SOI Guideline: https://ccnso.icann.org/sites/default/files/field-attached/ccnso-internal-pr... ADMINISTRATIVE MATTERS 3. Relevant Correspondence *a) **Notice of Resignation of Board Member Katrina Sataki to ccNSO Council Chair and Secretariat | 23 August 2024* *b) **Secretary's Notice of Resignation of Board Member Katrina Sataki to ECA and ccNSO Council Chair | 24 August 2024* 4. Minutes & Action Items *a) **Minutes Meeting 208: Circulated 10 September 2024* 2. *Action Items* ● *Action item 208-01: Completed* Following the departure of Tatiana Tropina from Council, the Secretariat is requested to add the topic to the agenda of Council meeting 209, regarding filling the vacancies for one (1) member to the Triage Committee, and one (1) Council liaison to IGLC. ● *Action item 208-02: Completed* The secretariat is requested to publish the resolution regarding the CSC effectiveness review deferral ● *Action item 208-03: Completed* The ccNSO Chair to send letter to ICANN Board Chair, regarding the CSC effectiveness review deferral ● *Action item 208-04: Completed (see agenda item 14, Council meeting 209)* Once the Travel Fund Committee finalises the proposed revised Travel Fund Guideline, the secretariat is requested to send it to Council for review, and then to the community, unless Council raises any concerns. ● *Action item 208-05: Completed (see agenda item 15, Council meeting 209)* The Secretariat is requested to prepare a boilerplate text for the invite to ccTLD managers to join the ccNSO, and send to the draft to Council for discussion ● *Action item 208-06: Completed (see agenda item 17, Council meeting 209)* The volunteers that stepped forward during Council meeting 207 are requested to draft a cover note regarding the ccNSO response to the Board Caucus regarding the questions about the proposed ccPDP3-RM policy. ● *Action item 208-07: Completed (see agenda item 11, Council meeting 209)* The ccNSO Chair is requested to keep Council informed about developments in the ICANN “how we meet” initiative. ● *Action item 208-08: Ongoing (see agenda item 18, Council meeting 209)* The ccNSO Council members are requested to suggest topics for the joint session between the ccNSO and the ICANN Board at ICANN 81. ● *Action item 208-09: Completed* The ccNSO Council members interested in joining the planning committee for the ICANN 81 Plenary session on the ALAC topic proposal are invited to inform the Council chair. ● *Action item 208-10: Completed (see agenda item 16, Council meeting 209)* The Secretariat is requested to propose to Council a template for the DASC review. ● *Action item 208-11: Completed* Council members are invited to participate in the DASC survey 5. Intermeeting Decisions (Since Meeting 208, August 2024) *208-A: *Appointment of Jordan Carter and Peter Koch as members to the informal WSIS+20 Discussion Group, and Biyi Oladipo as alternate. *208-B:* Adoption Board Seat 12 Nomination Process timeline and appointment Joke Braeken as Nomination Process Manager *208-C: *Selection Eyitayo Iortim as ccNSO Delegate to the 2025 NomCom 6. Intermeeting Decisions Triage Committee The Triage Committee has made no decisions since the last meeting. UPDATES 7. Update ECA, IFRT & CSC (Written Updates) Informational 8. Update Working Groups (Written Updates) Informational *a) **ccPDP3-Review Mechanism - Dormant* *b) **ccPDP4-IDN - Dormant* *c) **DASC* *d) **GRC* *e) **IGLC* *f) **MPC* *g) **OMC - First meeting prior to ICANN81* *h) **PGA WG * *i) **SOPC* *j) **Tech WG - Had no meeting since Council meeting 208* *k) **TLD-OPS SC - Had no meeting since Council meeting 208* *l) **UAC* *m) **Triage Committee - Had no meeting since Council meeting 208* *n) **CCG WS2 Implementation- Had no meeting since Council meeting 208* *o) **IRP Panel Selection - Had no meeting since Council meeting 208* *p) **Planning Prioritization Process group - Had no meeting since Council meeting 208* *q) **RZERC* *r) **RSS GWG* *s) **CIP-CCG * 9. Update Liaisons (Written Updates) Informational *a) **Update ALAC Liaison * *b) **Update GNSO Liaison * *c) **Update UASG Liaison* 10. Update ccNSO Website Redesign Informational 11. Update Chair, Vice-Chairs, Councillors, Regional Organisations and Secretariat Informational *a) **Update on “How we meet”-initiative by ICANN org* *b) **Heads up: Council leadership meeting with ICANN President and CEO on 2 October* *c) **Update on progress by WSIS+20 discussion group* 12. Update Board Seat 12 Nomination Process by the Nomination Process Manager Informational 13. Update Council Election Process by the Election Process Manager Informational ADMINISTRATIVE MATTERS & DECISIONS 14. Appointment Members to Committees and Working Groups, if any For decision *Background* Following a call for volunteers, two persons applied to join the ccNSO Universal Acceptance Standing Committee (UAC). One volunteer spontaneously stepped forward to join the ccNSO Meetings Programme Committee (MPC). Following a call for volunteers, several persons applied to become a member of the ccNSO Onboarding and Mentoring Committee (OMC). As per the respective charters, members to the Committee need to be appointed by Council. Secondly, following a call for nominations, the UAC reconfirmed Qing Cai (.cn) for another term as ccNSO liaison to UASG. Furthermore, Councillors volunteered to replace Tatiana Tropina on the ccNSO Council Triage Committee, and as Council liaison to the ccNSO Internet Governance Liaison Committee (IGLC). Finally, following a call for nominations for one (1) ccNSO Policy Gap Analysis Working Group (PGA WG) Chair and one (1) PGA WG Vice Chair, the working group selected Jordan Carter (.au) as its Chair, and Maria Camila Rojas (.co) as its Vice Chair. *Decision* (placeholder) 15. Adoption proposed ccNSO Travel Support Guideline For decision *Background* The ccNSO Travel Support Committee, consisting of a subset of Councillors, proposed changes to the ccNSO Travel Support Guideline. The Travel Support Committee used the Continuous Improvement Model as previously adopted by Council to guide its review. The Committee seeks to achieve two things: Firstly, a fair and equitable distribution of the ccNSO travel funding slots, with a better balance between enabling the participation of individuals who can contribute significantly to the work of the ccNSO and encouraging broader participation. Secondly, the ccNSO Travel Fund guideline, including the selection criteria, should be clear and easily accessible to all. The draft guideline was shared with Council for review and comments. Following minor adjustments to the proposed phrasing, the draft guideline was sent to the community for review and comments. *Decision* (placeholder) 16. Discussion boilerplate text: letter inviting ccTLD managers to become ccNSO members For discussion *Background* Council was requested to send a letter to an individual ccTLD, inviting them to join the ccNSO as a member. Council noted that such letter, if any, needs to be addressed to the current ccTLD Manager as listed in the Root Zone delegation record. Therefore, the proposal is to not publish a generic letter on the ccNSO website, but rather to encourage ccTLDs to reach out to the Secretariat, should they require such a letter. The Secretariat was requested to draft a boilerplate text and send it to Council for review. 17. Discussion template ccNSO DNS Abuse Standing Committee (DASC) review For discussion *Background* DASC met for the first time in May 2022. As per the Terms of Reference of the DASC, a review of its Terms of Reference and the activities of the Committee will take place every two years, or earlier when considered necessary. An update to the Terms of Reference will not become effective until it has been approved by both the Committee and the ccNSO Council and published on the ccNSO website. SUBSTANTIVE MATTERS & DECISIONS 18. Board Caucus request for clarification on the proposed ccPDP3-Review Mechanism Policy *a) **Adoption proposed response to the Board Caucus on ccPDP3-RM questions* For decision *Background* The fourth ccNSO Policy Development Process (ccPDP4) will provide a framework to ICANN and the broader community for (i) the selection of IDN country code Top-Level Domain (ccTLD) strings and variants thereof, (ii) the delegation, transfer, revocation, and retirement of the selected IDN ccTLD string and its variants, (iii) the use of the review mechanism pertaining to decisions concerning the delegation, transfer, revocation, and retirement of IDN ccTLDs. The proposed policy does not amend or change the current policies on delegation, transfer, revocation, and retirement of ccTLDs, but rather builds upon them. Council adopted the recommended policy at its ICANN79 meeting. The ccNSO membership supports the ccNSO Council's recommendation to adopt the proposed policy. A report on the voting was sent to the Issue Manager. The report has been included in the Draft Board Report, which - following approval by the ccNSO Council at ICANN80 - has been submitted to the ICANN Board of Directors, as per Annex B, section 14 of the ICANN Bylaws. The proposed policy is currently under Board consideration. The Board Caucus on ccPDP3-Review Mechanism, overseeing the policy implementation feasibility, shared some questions for clarification. A group of members of the ccPDP3-RM Working Group and Councillors prepared a draft response, and a cover letter. *Decision* THE CCNSO COUNCIL RESOLVES TO adopt the response to the questions for clarification by the Board Caucus on ccPDP3-Review Mechanism. The Council requests its chair to inform the Board Caucus, by sending the response that was drafted for that purpose, after this resolution becomes effective. The ccNSO Council wholeheartedly thanks the response team. The Council requests the secretariat to publish the response on the ccNSO website correspondence page. This resolution becomes effective seven (7) days after publication. *b) **Adoption proposed cover letter for the response to the Board Caucus on ccPDP3-RM* *Background* The Board Caucus on ccPDP3-Review Mechanism, overseeing the policy implementation feasibility, shared some questions for clarification. A group of members of the ccPDP3-RM Working Group and Councillors prepared a draft response, and a cover letter. The cover note addresses the following: ● Information on how the responses were structured ● An invite to the Caucus and relevant support staff to meet to discuss the requests and responses. This is suggested to avoid losing time by sending further written communication back and forth. ● A response on the foundational assumption made in the cover note which (paraphrased) asks to confirm that the ccPDP3-RM Policy is limited to a procedural review. The substantive material review of an IFO Decision is not subject to a CCRM review. ● A request for clarity of the scope of Annex B section 15(a) of the ICANN Bylaws. What can the ccNSO expect to be included in “Procedures for Board Consideration”? ● An alert to the Board and ICANN org that last year the ccNSO has adopted an Outline <https://ccnso.icann.org/en/about/outline-ccnso-policy-implementation-assista...> on how it intends to organize its work during the implementation phase of a Board adopted ccNSO policy. *Decision* THE CCNSO COUNCIL RESOLVES TO adopt the cover letter to the response to the questions for clarification by the Board Caucus on ccPDP3-Review Mechanism. The Council requests its chair to inform the Board Caucus, by sending the cover letter together with the response that was drafted for that purpose, after this resolution becomes effective. The ccNSO Council thanks the drafting team. The Council requests the secretariat to publish the response on the ccNSO website correspondence page. This resolution becomes effective seven (7) days after publication. 19. Tentative ccNSO Block Schedule ICANN81 *a) **Council preparatory meeting* *b) **Council workshop* *c) **Council meeting* *d) **Joint meeting: ccNSO and ICANN Board* * i. **Topics for discussion* *e) **Joint meeting: ccNSO and GAC* * i. **Topics for discussion* *f) **Working Group and Committee meetings* *g) **Tech Day* *h) **ccNSO Members Meeting sessions* *i) **Plenary Session* 20. AOB 21. Next Council Meetings 17 October 2024 | 21:00 UTC, Meeting 210 14 November 2024 | 10:15-11:30 UTC, Meeting 211 (at ICANN81) 12 December 2024 | 12:00 UTC, Meeting 212 16 January 2025 | 18:00 UTC, Meeting 213 13 February 2025 | 12:00 UTC, Meeting 214 22. Adjourn I will send the report after the meeting. Thank you! Kindest Regards, -- *Laura Margolis* ALAC Liaison to ccNSO margolisl@gmail.com +59899690992 skype: lauri.margolis ccNSO Liaison Workspace <https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Report...>