September 2024 - Ccnso-council

Appointment ccNSO Council Chair and Vice-Chairs
by Bart Boswinkel March 24, 2026

March 24, 2026

17 March 2022 Appointment ccNSO Council Chair and Vice-Chairs Dear John, At its meeting on 10 March 2022 and ion accordance with the temporary election procedure adopted on 24 February 2022, the ccNSO Council appointed Alejandra Reynoso (.gt) as Jordan Carter (.nz) and Adebiyi Oladipo (.ng) as Vice-Chairs. The Chair and Vice-Chairs have been appointed to serve until the end of the ccNSO Council during ICANN76. On behalf of the ccNSO Council, Bart Boswinkel ccNSO Secretariat

1 2

CIP-CCG
by Sean Copeland Oct. 30, 2024

Oct. 30, 2024

Dear fellow council members, I've attached a presentation related to the CIP-CCG cross-community group. Please review it and respond with any questions or comments. I believe it will be on our agenda for Thursday. The ccNSO has two voices, and Irina, in her role, has been invited to provide her valuable insights. Chris is also a part of this group and, while not directly asked to provide commentary, is well-positioned to offer additional insight. For background, it is essential to know that moving from an external group conducting interviews and making recommendations to one adopting continuous improvement is, at its heart, a culture shift. This means creating and implementing mechanisms to facilitate feedback, flexibility, and ease of adoption. There is a natural tendency in an organization to be reluctant to change and embrace new ideas. While this may not be true within the ccNSO, other groups' responses still need to be seen. Continuous improvement exercises have shown that this approach relies heavily on active and consistent engagement within the community. It is critical to use tools that ensure unbiased feedback, especially from new members who may not feel they have a voice. It's important to note that the degree of ‘standardization' that ICANN Org may seek could pose challenges and lead to inconsistency across the broader community. A 'light-touch' approach is advocated from the perspective of the ccNSO. Similarly, there could be an opportunity for individuals from different communities to facilitate, resulting in cross-learning. This could be a powerful way to gain insights into significant issues in other communities. When reviewing the slide show, please remember that “continuous” can take on multiple meanings, including the allocation of time, people, and potentially financial resources to be successful. Regarding the ccNSO, engagement with members, including those who may have only been seen at one event and are not actively participating in workgroups, has been positive. Communication is crucial to ensuring that continuous improvement is effectively utilized. Despite the current fiscal issues ICANN is experiencing, teaching facilitation along with leadership could significantly reduce costs compared to hiring an external party for a top-down review. This approach requires careful planning, clear communication, strong leadership, and a commitment to a new culture. The GRC is confident in the ccNOS's culture to address these areas. A light hand from Org will benefit the broader community and the ccNSO. That said, the effort should be fully supported. Should the council wish to present this slide show to the broader ccNSO community, a webinar can be organized; however, it may be premature. Please let Irina or me know if you have any questions or concerns. Respectfully,

2 1

Approval Terms of Reference DASC review
by Bart Boswinkel Oct. 1, 2024

Oct. 1, 2024

Dear all, Per email of 19 September 2024, the draft Terms of Reference for the DASC review were circulated to you, seeking your feed-back and comments and no additional comments were made. As said in the email, the review is required under the ToR of the DASC itself. In order to move this forward you now are asked to approve the Terms of Reference, and related the timeline for call for expression of interest to serve on the review team. Please note that according to the ToR for the Review at least two members of Council are expected to serve on the RT ( and these Councillors are not expected to be a member of the DASC). It would be appreciated if you could express your support for the resolution, or raise objections or your comments on list by Thursday 3 October 2024. Thank you and Kind regards, Bart Draft Resolution Decision The ccNSO Council approves the 26 September 2024 Terms of Reference for the effectiveness review of the DNS Abuse Committee. The secretariat is requested to publish this decision upon on 4 October 2024 and launch a call for expression to serve on the review team on 4 October 2024, which closes on 18 October 2024. This resolution becomes effective upon publication.

2 1

The September 2024 edition (issue 56) of the ccNSO newsletter is out now.
by Joke Braeken Sept. 30, 2024

Sept. 30, 2024

Dear All, The September 2024 edition (issue 56) of the ccNSO newsletter<https://community.icann.org/x/UgirBQ> is out now. Subscribe here to receive future editions of the newsletter: https://community.icann.org/x/UgirBQ Highlights from this month's edition: * SOPC response to FY26-30 ICANN draft strategic and operating plans * ccNSO UAC holds webinar to promote UA Day 2025 event proposals * Keep informed about the work of the ccNSO * Start nominations for 5 seats on the ccNSO Council * Who can nominate or second a nomination? ccTLD representatives only * Status update Board Seat 12 nominations * ccNSO seeks liaisons to ALAC and GNSO Council * application deadline extended * Join the TLD-OPS Ransomware Tabletop exercise at ICANN81 * Calling all marketing, legal, and communication experts: your skills are vital for a stronger incident response! * ICANN81 session highlights: sneak preview * Pre-register now<file:///“Sustaining%20Legitimacy/%20How%20Would%20You%20Increase%20Participation%20in%20ccNSO%20Decision-Making%3F> and join the GRC Virtual World Café session on 8 October at 13:00 UTC * Theme: “Sustaining Legitimacy: How Would You Increase Participation in ccNSO Decision-Making? * ccNSO Council highlights Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 0

Call for nominations to the ccNSO Council
by Joke Braeken Sept. 30, 2024

Sept. 30, 2024

Read the announcement below here: https://ccnso.icann.org/en/announcements/announcement-27sep24-en.htm Dear ccNSO members, The 3-year term for five members of the ccNSO Council will end in March 2025: * Africa: Biyi Oladipo * Asia Pacific: Jordan Carter * Europe: Nick Wenban-Smith * Latin America/Caribbean: Demi Getschko * North America: Pablo Rodriguez On Tuesday, 1 October 2024 (00:01 UTC), the ccNSO will open a call for nominations to fill those seats. The nomination and secondment procedure closes on Tuesday, 22 October 2024 (23:59 UTC). Note: As per the ccNSO Guideline, only the Representative from a ccNSO member will be able to nominate and second candidates to serve as a ccNSO Councillor. Further instructions are included below. The ICANN Bylaws, Article 10 – Section 10.4 (g)<https://www.icann.org/resources/pages/governance/bylaws-en/#article10> state: "(g) The ccNSO Council members selected by the ccNSO members from each Geographic Region (see Section 10.3(a)(i)) shall be selected through nomination, and if necessary, election, by the ccNSO members within that Geographic Region. At least 90 days before the end of the regular term of any ccNSO-member-selected member of the ccNSO Council, or upon the occurrence of a vacancy in the seat of such a ccNSO Council member, the ccNSO Council shall establish a nomination and election schedule, which shall be sent to all ccNSO members within the Geographic Region and posted on the Website." How to nominate and second a candidate TIMELINE | The nomination and secondment procedure starts Tuesday, 1 October 2024 (00:01 UTC) and closes Tuesday, 22 October 2024 (23:59 UTC). WHO CAN NOMINATE OR SECOND? | The ICANN Bylaws, Article 10 – Section 10.4 (h)<https://www.icann.org/resources/pages/governance/bylaws-en/#article10> state: "(h) Any ccNSO member may nominate an individual to serve as a ccNSO Council member representing the ccNSO member's Geographic Region. Nominations must be seconded by another ccNSO member from a different Territory, from the same Geographic Region. By accepting their nomination, individuals nominated to the ccNSO Council agree to support the policies committed to by ccNSO members." The ccNSO Council election guideline, section 3.2<https://ccnso.icann.org/sites/default/files/field-attached/guideline-ccnso-…>, states: "Only the Representative from a ccNSO member will be able to nominate and second candidates to serve as a ccNSO Councillor. New ccNSO members can participate in the nomination process if their ccNSO membership application has been approved by the ccNSO Council one day prior to the day the nomination process starts. A Representative from a ccNSO member may self-nominate, but is then not allowed to second their self-nomination. Self-nominations must be seconded by two Representatives from two other Territories in the Region." The Glossary of the Internal ccNSO Rules, states:<https://ccnso.icann.org/sites/default/files/field-attached/internal-members…> "Representative - Each ccTLD manager may designate in writing a person, organization, or entity to represent the ccTLD manager in matters relating to the ccNSO ("Representative"). In the absence of such a designation, the person, organization, or entity listed as the administrative contact in the IANA database shall be deemed to be the designate of the ccTLD manager by whom the ccNSO member shall be represented." Contact joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>, in case you have questions regarding who is listed as the Representative for your ccTLD. NEW ccNSO MEMBERS | Note that new ccNSO members can participate in the nomination process if the ccNSO membership application has been approved by the ccNSO Council one day prior to the nomination process start, i.e., latest on 30 September 2024. SELF-NOMINATIONS | As per the relevant ccNSO guideline<https://ccnso.icann.org/sites/default/files/field-attached/guideline-ccnso-…>, ccNSO members may self-nominate themselves, but are not allowed to second their nomination. Self-nominations must be seconded by two ccNSO members from the region. INSTRUCTIONS | Nominations and secondments should be sent by e-mail to the Election Manager at the following e-mail address: ccnso-nominations(a)icann.org<mailto:ccnso-nominations@icann.org>. Templates for nominating and seconding nominations are provided below. You are kindly invited to follow these instructions closely, and not to use alternative templates. Consult the archive for nominations and secondments here: https://lists.icann.org/hyperkitty/list/ccnso-nominations@icann.org/ = = = please send to ccnso-nominations(a)icann.org<mailto:ccnso-nominations@icann.org> TEMPLATE | NOMINATION TO THE ccNSO COUNCIL Your full name: Your e-mail address: Your ccTLD: Your geographic region: Full name of the person you nominate to the ccNSO council: e-mail address of the person you nominate: = = = send to ccnso-nominations(a)icann.org<mailto:ccnso-nominations@icann.org> TEMPLATE | SECONDING A NOMINATION TO THE CCNSO COUNCIL Your full name Your e-mail address: Your ccTLD: Your geographic region: Full name of the nominee you would like to second: ELIGIBILITY REQUIREMENTS TO BE ELECTED TO CCNSO COUNCIL | A Councillor can be any individual nominated, seconded, and elected as described in the ccNSO Council Election Guideline. Individuals are elected in their personal capacity and serve the ccTLD community. Councillors do not represent the views and interests of their employers. Candidates need to be neither resident in the region, nor a citizen of a country, within the region in which they stand for election. During a Council Election Webinar (held on 26 September 2024), the ccNSO Chair gave an overview of the election process, the need to replace Councillors at reasonable and regular intervals, the required skill sets for Councillors, their expected time commitment and working methods. Consult the webinar recording<https://community.icann.org/display/ccnsowkspc/ccNSO+Webinars> here. VALID CANDIDATES | A valid candidate is one that has been nominated and seconded according to the ccNSO council Election Guideline, and that has accepted the nomination. If there is more than one valid candidate in a Geographical Region, an election shall be conducted in that region. Voting will be by secret ballot: the ballot is identified only by a code and not by a name. ACCEPTING NOMINATIONS | After closure of the nomination period, the Election Manager will ask the candidates that are nominated to accept their nomination. Self-nominations are understood to have accepted their nomination. The Election Manager will provide a list with the name(s) of the candidate(s) who have accepted their nomination. A record of who has nominated and seconded the candidate(s) is publicly available: https://lists.icann.org/hyperkitty/list/ccnso-nominations@icann.org/ NEXT STEPS | The Election Manager will ask the candidates to provide a written candidate statement. A Question and Answer session with the candidate(s) will be held on Wednesday, 12 November 2024 (13:15-14:30 local in Istanbul, 10:15-11:30 UTC), during ICANN81. In preparation of the Q&A session, the written candidate statements will be posted on the ccNSO website. The Q&A session gives the ccNSO members and broader ccTLD community an opportunity to interact with the candidates. If at the close of nominations there are no more valid candidates in a particular geographic region than there are seats on the ccNSO Council available for that geographic region, then the nominated candidates shall be selected to serve on the ccNSO Council. Otherwise, an election shall be held for that geographic region, to select the ccNSO Councillors from among the valid candidates. The first election round (if any), will start Wednesday, 27 November 2024 (00:01 UTC) and will close Wednesday, 18 December 2024 (23:59 UTC), as per the timeline adopted by the Council. LINKS * ICANN bylaws, Article 10<https://www.icann.org/resources/pages/governance/bylaws-en/#article10> * ccNSO Internal Membership Rules<https://ccnso.icann.org/en/about/internal-membership-rules-26oct22-en.pdf> * Archive for nominations and secondments<https://lists.icann.org/hyperkitty/list/ccnso-nominations@icann.org/> * Relevant ccNSO guideline<https://ccnso.icann.org/sites/default/files/field-attached/guideline-ccnso-…> * Timeline<https://ccnso.icann.org/sites/default/files/field-attached/timeline-electio…> * ccNSO Council Election Webinar: recording<https://community.icann.org/display/ccnsowkspc/ccNSO+Webinars> * Announcements related to Council elections<https://ccnso.icann.org/en/about/elections/council.htm> Best regards, The Council Election Process Manager Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 0

Deadline has been Extended | Call for Volunteers: ccNSO appointed Liaison to the ALAC
by Claudia Ruiz Sept. 30, 2024

Sept. 30, 2024

Dear all, The ccNSO is looking for a member of the ccTLD community to be appointed as ccNSO liaison to the ALAC. This call for volunteers has been extended until Friday, 04 October 2024 (23:59 UTC). On Wednesday, 25 September 2024 the ccNSO held a webinar with previous liaisons to discuss responsibilities and expectations for the role. Recording of the webinar can be found here<https://community.icann.org/x/HBwFBQ> . Roles and responsibilities of the ccNSO Liaison to the ALAC As specified in the ccNSO Guideline Liaison and Observers (https://ccnso.icann.org/sites/default/files/file/field-file-attach/2017-04/…) the ccNSO appointed liaison to the ALAC shall report to the ccNSO Council not less than monthly on the activities of the respective organization. The ccNSO appointed Liaison to the ALAC shall represent ccNSO values in these efforts, shall pursue specific direction from the ccNSO Council as and when given, and shall seek ccNSO Council advice as and when needed. Furthermore, the ccNSO Liaison to the ALAC is committed to: * Participate diligently and actively in the meetings and activities of the ALAC on an ongoing and long-term basis * Communicate and advocate the positions of the ccNSO to the ALAC; * Report to the ccNSO on current and upcoming activities of the ALAC that may be of relevance to the ccNSO and broader ccTLD community. * If feasible and considered relevant ask to the ccNSO for advance guidance, if any, on matters that are going to be discussed by the ALAC. * Participate in ALAC-ccNSO Council meetings agenda committee to prepare the f-2-f meetings, if any. The ccNSO liaison to the ALAC shall not be a member of or entitled to vote on the ccNSO council or the Councils of other organizations, but otherwise shall be entitled to participate in the respective Council meetings. How to Apply If you are interested in applying for this position, please submit your application by Friday, 04 October 2024 (23:59 UTC). To apply, complete the form here: <https://forms.gle/PaWZLUfSXAisWbrQ7> https://forms.gle/tLYKfeKguEfrSWun9 You will be asked to provide your full name and contact details, your ccTLD affiliation, and a brief statement detailing your interest in serving as ccNSO Liaison to the ALAC and what you will bring to this position. Next Steps Timeline * Call for volunteers: Wednesday, 11 September 2024 until Friday, 27 September 2024 * Evaluation of the candidates and selection by the council: Monday, 30 September 2024 until Monday, 07 October 2024 * Appointment selected candidate: approval election report by the ccNSO Council during its meeting on 17 October 2024. * The candidate will assume its role at the end of ICANN81 in Istanbul. In the event only one person has volunteered, this person shall be appointed by the ccNSO Council at the first council meeting following the call for volunteers. In the event two or more persons have volunteered for the same position, the ccNSO Council will conduct an email vote for the appointment. The Secretariat will then act as Selection manager. The volunteer who receives the majority of the votes lodged shall be considered to be appointed by the ccNSO Council as of the date of adoption of the Election Report, foreseen for the 17 October 2024 council meeting. The Chair of the ccNSO will inform the ICANN Secretary and the respective Supporting Organization or Advisory Committee of the appointment. Background * ccNSO Guideline: Liaison and Observers https://ccnso.icann.org/sites/default/files/file/field-file-attach/2017-04/… Best regards, Claudia Ruiz Claudia.ruiz(a)icann.org<mailto:Claudia.ruiz@icann.org>

1 0

Reminder | Call for nominations Board Seat 12 closes tomorrow
by Joke Braeken Sept. 26, 2024

Sept. 26, 2024

Dear ccNSO members. This is a reminder that the call for nominations for Board Seat 12 closes tomorrow, Friday 27 September 2024 at 23:59 UTC. The deadline for accepting nominations is Friday, 4 October 2024 (23:59 UTC): the nomination process manager will reach out to all nominees with instructions on how to do so. The election will take place in February 2025, following the completion of due diligence on the nominee(s) by a professional firm. A virtual question and answer session with the candidate(s) will be held in late January. Read more: https://ccnso.icann.org/en/announcements/announcement-09sep24-en.htm Links * Announcements on ccNSO website related to the ongoing nominations: https://ccnso.icann.org/en/about/nominations.htm * Archive for nominations and secondments: https://lists.icann.org/hyperkitty/list/ccnso-boardnominations@icann.org/ * ICANN Bylaws: https://www.icann.org/resources/pages/governance/bylaws-en * ccNSO Internal Rules: https://ccnso.icann.org/sites/default/files/field-attached/internal-members… * ccNSO Guideline Board seat 11 and seat 12 nominations: https://ccnso.icann.org/sites/default/files/field-attached/ccnso-nomination… * Timeline as adopted by ccNSO Council: https://ccnso.icann.org/sites/default/files/field-attached/timeline-nominat… Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 0

REMINDER: call for presenters ccTLD News
by Joke Braeken Sept. 25, 2024

Sept. 25, 2024

Dear All, This is a reminder about the call for presenters for the ICANN81 ccTLD News Session. The ccNSO Meetings Programme Committee still welcomes proposals! SUBMISSION GUIDELINES | Presentation proposals should include a title, abstract (few sentences), and the name, ccTLD affiliation and contact details of the presenter. SUBMISSION DEADLINE | Please submit your presentation proposals no later than 27 September 2024 (23:59 UTC) via https://forms.gle/JAYGApb2gMoEDH3a8 Read more: https://ccnso.icann.org/en/announcements/announcement-22aug24-en.htm Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 0

REMINDER | ccNSO seeks 2 liaisons: to ALAC & GNSO | Join webinar on 25 Sep at 14 UTC
by Joke Braeken Sept. 25, 2024

Sept. 25, 2024

Dear All, This is a reminder that the ccNSO is looking for two members of the ccTLD community to be appointed as liaisons: 1/ ccNSO liaison to the ALAC Read more: https://ccnso.icann.org/en/announcements/announcement-2-12sep24-en.htm 2/ ccNSO liaison to GNSO Council Read more: https://ccnso.icann.org/en/announcements/announcement-12sep24-en.htm To learn more about the role and this call for volunteers, you are warmly invited to a webinar on Wednesday, 25 September 2024 at 14:00 UTC. There will be an opportunity to ask questions and zoom recordings will be posted here<https://community.icann.org/x/HBwFBQ>. To join the webinar, please register here: https://icann.zoom.us/meeting/register/tJMtfuyurTsoHNVEaa7KY3ShuyPrCuBx1CoB Both calls for volunteers close on Friday, 27 September 2024 (23:59 UTC). Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 0

NOTES | ccNSO Council meeting 209 | Thursday, 19 September 2024 at 12:00 UTC
by Joke Braeken Sept. 19, 2024

Sept. 19, 2024

NOTES ccNSO Council meeting 209 Thursday, 19 September 2024 at 12:00 UTC 1. Welcome and roll call Welcome by Alejandra Reynoso, ccNSO Chair. Council workspace for this meeting: https://community.icann.org/x/HQEZEw Reminder to current Council members to please add “Council” next to your name in zoom No roll call. Attendance from the zoom room One AOB, regarding IFRT2 a. Establish whether meeting is Quorate Claudia: no apologies, but 3 Council members arriving late. Claudia Ruiz, ccNSO Secretariat, mentioned the meeting was not yet quorate. 2. Updates Statements of Interest Nick: process for election of a replacement for Katrina. I have been nominated to stand in that process. I will not take part in any of those discussions. Alejandra: new format of the agenda. Use wiki as the one source for all materials. To avoid confusion with materials in your inbox. Background and supporting documents * Council workspace for this meeting: https://community.icann.org/x/HQEZEw * ccNSO correspondence: statements and responses: https://ccnso.icann.org/en/about/statements.htm 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 The prior meeting's minutes are approved. 1. Action items All action items from the previous meeting are completed. No questions or comments were raised regarding these agenda items. Action Items 208-04 to 208-08 are discussed during the meeting today. * 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. No questions or comments were raised regarding this agenda item. UPDATES 7. Update ECA, IFRT & CSC (written updates) Written updates were provided. No questions or comments were raised regarding this agenda item. 8. Update WGs (written updates) 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 Written updates were provided. No questions or comments were raised regarding this agenda item. 9. Update liaisons (written updates) a. Update ALAC Liaison b. Update GNSO Liaison c. Update UASG Liaison Written updates (if any) were provided. No questions or comments were raised regarding this agenda item. Ongoing call for volunteers for 1 ccNSO liaison to ALAC, and one 1 ccNSO liaison to GNSO Council Webinar next week. Council members are not eligible. Claudia: we are quorate. 10. Update ccNSO Website redesign No questions or comments were raised regarding this agenda item. Alejandra: meetings with the ICANN team. Wireframes created. Analysis pending, and more info on timeline to follow. 11. Update Chair, Vice-chairs, Councillors, Regional Organisations and Secretariat a. Update on “How we meet”-initiative by ICANN org Alejandra: received email from Mary. additional info requested by me. More analysis needed by icann. Delay. Info was not easy to collect. b. Heads up: Council leadership meeting with ICANN President and CEO on 2 October More to come at next Council meeting c. Request to appoint a representative to IANA CCG Letter sent to SO/AC chairs. 3 from names community needed and we only have 2 to date. (Greg, ALAC, Maarten Simon, ccNSO), plus 3 from the numbers community. One vacancy. GNSO seems logical SO to appoint an additional person. Ongoing. d. Update on progress by WSIS+20 discussion group Bart: Jordan wants to alert you to the email circulated. A call for a meeting. First meeting. Group has been formed, and they are awaiting the first opportunity to meet. e. Council Vice Chair update to APTLD Jordan provided the update. No questions or comments. He informed Alejandra all went well. Joke: did you like surveymonkey for the ranking of the candidates? No comments. Alejandra likes it. Shall we continue using it? Mostly green ticks Nick: admin burden for staff. Easy to collate answers. Free and good. Harder to see who responded. 100% in favour of tools that make life easier. Is the data properly secure? Confidential basis. Do the tools have the right level of security and confidentiality? Our org underwent privacy assessments. Before we use these tools, we need to be sensitive to the way it is handled. How long is data kept? Data protection law perspective. Be conscious about the issues. Microsoft forms has excellent privacy policies. Making this comment in the spirit is being delivered. Alejandra: sent to individual email addresses of the councillors. Joke: ICANN org approved surveymonkey for use. Legal assessments made. Happy to delete the survey after a certain time, if required to do so Peter: There is a potential data protection issue (regarding the candidates) to be deferred to ICANN legal, I believe. Bart: what are you referring to? Peter: Clarified by Joke in response to Nick 12. Update Board Seat 12 Nomination Process by the Nomination Process Manager Joke: 4 sept heads up that a vacancy needs to be filled. Timeline was included there Call for nominations distributed on 9 Sept. nominations started 10 sept and end 27 sep. 3 candidates to date, all nominated and seconded. 4 oct deadline for acceptance nominations. Then due diligence can start. To be completed by the start of December. List of candidates will be communicated to the public. Virtual Q&A at the end of January, elections in February. 13. Update Council Election Process by the Election Process Manager Term end for Biyi, Jordan, Nick, Demi, Pablo at conclusion of icann82. Webinar on 26 Sep at 14 UTC to inform potential candidates and community. Councillors are invited to join. Nominations start 1 oct. end 22 oct. Q&A at icann 81 with candidates. Wed, block 5. Candidates can join remote or in person ADMINISTRATIVE MATTERS & DECISIONS 14. Appointment members to committees and working groups, if any Move: Sean Second: Pablo Questions or comments? None All in favour 15. Adoption proposed ccNSO Travel Support Guideline Peter: proposed guideline was circulated to council. Following minor refinements, guideline sent to community. No comments received. We propose the adoption of the revised guideline. Move: Pablo Second: Sean Questions or comments? None All in favour 16. Discussion boilerplate text: letter inviting ccTLD managers to become ccNSO members Alejandra: see wiki. Please review and add your suggestions by the end of Wednesday next week. We will clean the draft, and will circulate the proposed final version for an online approval to council mailing list. 17. Discussion template ccNSO DNS Abuse Standing Committee (DASC) review Bart: DASC charter. The ToR and its activities need to be reviewed. Is it valuable to ccnso? Suggest changes. Template follows the format of the CSC effectiveness review. Deliverables, and general questions. See annex. They refer to the ToR of the DASC. general questions regarding the outreach efforts. Review team of 5 members. ToR and RT adopted before ICANN 81, so the RT could meet in person with the DASC members and others, to have a conversation about the DASC itself. Reporting back before ICANN82. Nick: for OISC review. Good for the RT to meet members in person. Regarding the DASC review, good to get this done, sooner rather than later. ToR seems common sense. Sufficient flexibility. Bart: start tomorrow, to review the ToR For the RT, we need at least 2 councillors, who are not part of the DASC. additional 2 volunteers outside of council. 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 Jordan: provides background. Intense effort. Thanks to all councillors and Stephen Deerhake who chaired ccPDP3-RM. Ready to go. Looking forward to interesting and useful conversation with the board. Alejandra: ccPDP3 indeed. It got split in two parts. Move: Jordan Second: Pablo Questions or comments? None All in favour 1. Adoption proposed cover letter for the response to the Board Caucus on ccPDP3-RM Jordan: draws attention to responses. Group of councillors prepared the draft. Not the same group that provide answer to the questions Questions or comments? None Move: Peter Second: Olga All in favour Action item: please contact board ops once the resolution is effective, to check on the modalities and date for the proposed meeting. 19. Tentative ccNSO Block Schedule ICANN 81 Alejandra: no changes compared to last time Joke: ccNSO schedule for ICANN81: go to https://community.icann.org/x/IgDyF a. Council preparatory meeting b. Council workshop c. Council meeting d. Joint meeting: ccNSO and ICANN Board i.Topics for discussion Alejandra: no format, or board questions to date. Better be prepared. Please use mailing list for suggestions 1. Joint meeting: ccNSO and GAC i.Topics for discussion Alejandra: scheduled 1. Working Group and Committee meetings 1. Tech Day 1. ccNSO Members Meeting sessions 1. Plenary Session Claudia: TLD-OPS Table Top Excercise. (TTX) DRBRP. For the playbook see wiki: Disaster Recover and Business Continuity Playbook : https://community.icann.org/x/T6ajBg Translated into 5 languages Similar TTX at ICANN66. Early test of the playbook Sunday block 3 and 4, second DRBC TTX will be held. Focus on ransomware. Cross-section of participants. Closed session. Needs to be registered for. Registrations close at oct 28 or when the spots fill up. Registration link: https://forms.gle/QswLCMG8mud1VAdGA Alejandra: Very nice experience. Please let your peers know and invite them to join Alejandra: communications with RySG. a joint mailing list was created. Ongoing discussion about topics of common interest. their intent to meet informally with ccnso council representatives. They were notified about the IGLC and DASC sessions at ICANN 81. Seeking to plan a joint session for ICANN82. Peter: A common ccNSO RySG topic could be RSSGWG Alejandra: Remind all that the call for presentation proposals for the ccTLD News Sessions is still open. MPC welcomes additional proposals. https://ccnso.icann.org/en/announcements/announcement-22aug24-en.htm 20. AOB Peter: 2 co-chairs letter to ccNSO and RySG to ask for a short time slot for our outreach efforts,before request for comments starts. ccTLDs as customers. We are interested in ccTLD feedback and others. Have we missed something? During the review, it occurred that certain complaints mechanisms are described in the contract. We have another set of those. Would appreciate having info from ccPDP4 and ccPDP3 Alejandra: the pdps have not been approved nor implemented. How does that fit in there? Peter: working title. Incidental infinds. Review what happened in the past. Bart: intended date of publication of initial findings? Peter: not there yet. Team did not want to wait for the report. Gather input. Unlikely to happen before Istanbul Bart: in person or a virtual meeting? Better under control. The current block schedule is full. Peter: separate webinar is more overhead. 5 to 10 slot needed. Take it offline. Bart: organising a webinar is not difficult. We can assist for the ccnso part. Alternative approach. To not put too much pressure on the agenda Secondly. Are you referring to the mediation mechanism, and the customer complaint mechanism in the contract? Bart: ccPDP3-RM looked at that. See also the responses to the board caucus. Point to various documents. Based on this, before reaching out. 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 Thank you all. Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

2 1