October 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

Re: Caller Volunteers DASC Effectiveness review team ( was Approval Terms of Reference DASC review )
by Bart Boswinkel Nov. 9, 2024

Nov. 9, 2024

Dear all, The terms of Reference for the review of the DASC have now been adopted. As indicated in the email from 26 September Per terms of reference 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. The latter implies that Olga, Nick, and Chris are not expected to review the DASC effectiveness. To make maximum use of the in-person meeting in Istanbul, please don’t hesitate to volunteer! Thank you, kind regards, Bart From: Bart Boswinkel via Ccnso-council <ccnso-council(a)icann.org> Reply to: Bart Boswinkel <bart.boswinkel(a)icann.org> Date: Thursday, 26 September 2024 at 16:45 To: "ccnso-council(a)icann.org" <ccnso-council(a)icann.org> Subject: [ccnso-council] Approval Terms of Reference DASC review 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

ccNSO Council 2025 Elections: Candidate List and Upcoming Steps
by Joke Braeken Oct. 31, 2024

Oct. 31, 2024

ccNSO Council 2025 Elections: Candidate List and Upcoming Steps The nomination period for the 2025 ccNSO Council elections closed on 22 October 2024 at 23:59 UTC. The following candidates have been nominated, seconded, and accepted their nominations in line with the established rules and timeline: * Africa: Biyi Oladipo (.ng) * Asia/Australia/Pacific: Jordan Carter (.au), Nguyen Thi Thu Thuy (.vn) * Europe: Nicklas Pousette (.se) * Latin America/Caribbean: Everton Teles Rodrigues (.br), Diego Ernesto Luna Quevedo (.co) * North America: Pablo Rodriguez (.pr) To view the nomination archives, click here. Candidate statements, if provided, are attached. Candidate Q&A Session Date: Wednesday, 13 November 2024 Time: 13:15-14:30 local (10:15-11:30 UTC) Location: ICANN81 This Question-and-Answer session offers ccNSO members a chance to engage with the candidates before the election. Barrack Otieno (AFTLD) will moderate the session. Background on ccNSO Council Elections The ccNSO Council consists of 18 Councillors, representing 5 ICANN geographical regions. Each region has 3 Councillors, with 15 elected by ccNSO members within their respective regions and 3 appointed by the ICANN Nominating Committee. * If a region has the same number of nominees as available seats at the nomination deadline, those nominees are elected by default, and no election will be held for that region. * Regions without elections: Africa, Europe, North America. * Regions with elections: Asia/Australia/Pacific and Latin America/Caribbean. Election Timeline for Regions requiring Elections * Start: Wednesday, 27 November 2024, 00:01 UTC * End: Wednesday, 18 December 2024, 23:59 UTC Ballots will be emailed to the ccNSO emissaries before voting begins. The election process concludes seven days after the ccNSO Council publishes the Election Report. New Council terms will commence at the end of ICANN82 in March 2025. For all election-related materials, visit the ccNSO Council Elections page<https://ccnso.icann.org/en/about/elections.htm>. Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Read more about the ccNSO at ICANN81: https://community.icann.org/x/IgDyF

1 0

ICANN 81 | ccNSO Council Links Library.
by Joke Braeken Oct. 31, 2024

Oct. 31, 2024

Hello All, Welcome to the ICANN81 | ccNSO Council Links Library - your one-stop resource for all council-related links at ICANN81! 😊 Thanks for the suggestion, Jordan. https://docs.google.com/document/d/1SUvvXe1mUXnplB7fgxBNTu4Nusk7SE98CVrVpK1… Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Read more about the ccNSO at ICANN81: https://community.icann.org/x/IgDyF

1 0

NOTES | Council prep | 31 October 2024 (noon UTC)
by Joke Braeken Oct. 31, 2024

Oct. 31, 2024

NOTES | Council prep | 31 October 2024 (noon UTC) 1. Welcome Welcome by chair Alejandra. 2. Admin matters 1. SoI 2. Attendance ICANN81 3. Prep joint meetings with Board and GAC: https://docs.google.com/document/d/1Obev-6U_cu2nISM1pk2JIbUHi22Ob5kj/edit Bart: request from Board, directed at SOPC regarding the current financial stress. Irina and Andreas invited. Irina sent her apologies. Main message to the Board? Private capacity, or on behalf of the SOPC? SOPC consultation is challenging at the moment Nick: lots of comments on record regarding ICANN’s finances. Many statements on the record to be cautious. No need to go back to SOPC again. We need to get the tone right. But: “we told you so”. The wage bill and the number of staff have increased scarily quickly. Bart: clear. Do you have a suggestion going forward? Nick: there are better and cheaper processes these days. Also, the length of the processes. E.g. new gTLD process. The world has changed. The EU can legislate quicker than ICANN can make policy. Andreas: new gTLD round. No staff left from the 1st round. We should be more straightforward. Not say “ reduce the headcount “. but postpone future hiring. Look into AI. could help with translation etc. Alejandra: agree with jordan Jordan: maybe we simply need to be more pointed and more public at time. While remaining respectful. I am not sure how many people know how long our critique has gone on - and basically been ignore. so I think 'I told you so' isn't helpful, but 'we want you to account to us for why you have ignored our repeated warnings' Alejandra: been ongoing for a long time. For those things we needed processed. Not worth to be that formal. The question asks more for an opinion Bart: refer to the comments over the years. Pablo: cut down on meetings. Not getting together is not a good answer. It always facilitates conversation. Another meeting in PR soon. Headcount Jordan: not responding or ignoring the advice. What we said would happen, has happened. Why did you decide not to follow that advice? Why didn’t you act? Chris: what process did you follow to evaluate our advice? You made a decision not to follow our advice. Did you read our input, and carried on nonetheless? Stephen: Review Mechanism. Ridiculous. Public forum Chris: there is none Nick: Thursday morning. Bart: progress ccPDP3 and ccPDP4 is a separate topic. Andreas: all relevant points. Agree with Chris. We mentioned it for many years. Tell them what we identified in the past. How will you respond in future? Clear KPI’s. We need to get their answers. How do they deal with our input? Most important point for us. >> Bart: Andreas and Irina take the initiative to speak to this topic. Followed by others, such as what happened today. Put comments on record. >> Regarding messaging: Chris will take that topic. The question is self-explanatory. It became obvious when Katrina stepped down. Chris: hard to plan for surprises. Nick: succession planning and continuity is important regarding term ends. Bart: kick off with the board question, and further discussion on duration of processed and continuity issues. >> Bylaw change. Alejandra will speak to this. Alejandra: what do we expect? Should i ask for a timeline? Bart: rather a workflow. They need to go through workflow. So that people know what is happening and who is responsible for which part? How to get to the decision to start the public comment period? Who initiates the public comment on a bylaw change, and when? >> progress board consideration ccPDP3 and ccPDP4 Stephen: zero action. Delay is not in bylaws. How d we nudge them? Chris: empathize with Stephen. Ccpdp on retirement is done Bart: review mechanism (ccPDP3) and ccPDP4. Chris: are they in the same disarray? If we are worried about ccPDP3, let’s leave it at that. Only ccpdpd3 is in the board’s hands. Understand why stephen is annoyed. They are entitled to ask their questions. Did it take long to ask the questions? Does it take long to answer? Stephen: bylaws do not foresee the option to ask questions. Chris: trying to get a win out of this. Those questions came from legal. Legal consequences to the policy. What lawyers will do, is seeking clarity. That it is not the issue. But the time it took to answer them and that we have no clarity on what happens with our answers. Jordan: they lost the person that leads this work and have our answers since a month. Not reasonable for us to ask them to answer. They learned how crappy that process was. They learned for future PDPs. There is a structure for the GNSO policies. Board readiness something. We could look at that. We could also look at how we write the reports. What can you commit to when the next steps will happen? Bart: mechanism of board caucuses. Stephen: happy that Becky stepped in. 3 topics with GAC * WSIS+20: Chris, Peter * Iana policy gap: Jordan * DNS abuse survey: Nick Bart: GAC has appointed a liaison to ccNSO. From Australia. 4. Overview of session and assignment of rapporteurs: https://docs.google.com/document/d/1Ura8spCLbiRxqRYE0SK1EuInzs-wy7hM/edit Chris: non commercial stakeholder group. Changes re DNS abuse might have human rights impact. They will explain during a session. That is what that is about. Would be good for someone from DASC to attend. Olga: volunteered Chris: clash with Council workshop. Nick: freedom of expression. Chris: what if i went? Alejandra: prefer not. Rather a report afterwards Nick: let’s ask Bruce. Bart: yes. done. 5. Prep Council work session Sunday 10 November, 10.30 local time, Room: Hamidiye - Briefing document included. Nick: hard to find all links Jordan: "ccNSO Google Doc Links - ICANN81" or something 6. AOB 7. Adjourn Thanks all. Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Read more about the ccNSO at ICANN81: https://community.icann.org/x/IgDyF

1 0

Re: Agenda prep call 31 October 2024
by Joke Braeken Oct. 31, 2024

Oct. 31, 2024

Hi all, For notes today, go to https://docs.google.com/document/d/1OesDGU5ck96L5BywXwjaqA6QqB8sCx3u3fgXb4D… Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Read more about the ccNSO at ICANN81: https://community.icann.org/x/IgDyF From: ccnso-council <ccnso-council(a)icann.org> Reply to: Bart Boswinkel <bart.boswinkel(a)icann.org> Date: Wednesday, 30 October 2024 at 15:42 To: ccnso-council <ccnso-council(a)icann.org>, Andreas Musielak <musielak(a)denic.de>, Irina Danelia <irina.danelia(a)gmail.com> Subject: [ccnso-council] Agenda prep call 31 October 2024 Dear all, Please find included agenda and material for the upcoming prep call: 1. Welcome 2. Admin matters * SoI * Attendance ICANN81 3. Prep joint meetings with Board and GAC: https://docs.google.com/document/d/1Obev-6U_cu2nISM1pk2JIbUHi22Ob5kj/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1Obev-6U_cu2n…> 4. Overview of session and assignment of rapporteurs: https://docs.google.com/document/d/1Ura8spCLbiRxqRYE0SK1EuInzs-wy7hM/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1Ura8spCLbiRx…> 5. Prep Council work session Sunday 10 November, 10.30 local time, Room: Hamidiye - Briefing document included. 6. AOB 7. Adjourn Kind regards, Bart

1 0

Agenda prep call 31 October 2024
by Bart Boswinkel Oct. 30, 2024

Oct. 30, 2024

Dear all, Please find included agenda and material for the upcoming prep call: 1. Welcome 2. Admin matters * SoI * Attendance ICANN81 3. Prep joint meetings with Board and GAC: https://docs.google.com/document/d/1Obev-6U_cu2nISM1pk2JIbUHi22Ob5kj/edit 4. Overview of session and assignment of rapporteurs: https://docs.google.com/document/d/1Ura8spCLbiRxqRYE0SK1EuInzs-wy7hM/edit 5. Prep Council work session Sunday 10 November, 10.30 local time, Room: Hamidiye - Briefing document included. 6. AOB 7. Adjourn Kind regards, Bart

1 0

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

REMINDER | Join the ccNSO webinar for newcomers tomorrow. Wednesday, 30 October at 12 UTC
by Joke Braeken Oct. 29, 2024

Oct. 29, 2024

https://ccnso.icann.org/en/announcements/announcement-24oct24-en.htm Hi All, Are you new to the ccNSO, or would like to learn more? Perhaps you know about colleagues or peers who would benefit from an introductory session to the ccNSO? Join ccNSO Council Vice Chair Biyi Oladipo (.ng) for a 1-hour ccTLD Webinar for newcomers. Biyi will help you to gain an understanding of the work of the ccNSO, what to expect from the ccNSO at the ICANN81 Annual General Meeting, as well as how ccTLD community representatives can participate in the important work that affects you and your region. When? Thursday, 30 October 2023 | 12:00 (noon) UTC How to participate? Register in advance for this meeting: https://icann.zoom.us/meeting/register/tJckdeqtrDgvH9I7QmC5ajhhTn3CY72HdBeH After registering, you will receive a confirmation email containing information about joining the meeting. Recordings will become available here: https://community.icann.org/x/ooNJD Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Read more about the ccNSO at ICANN81: https://community.icann.org/x/IgDyF

1 0

(Correct link ) You're Invited! Registration for ccNSO Cocktail in Istanbul
by Claudia Ruiz Oct. 25, 2024

Oct. 25, 2024

ccNSO Cocktail and Networking Event You are invited to the ccNSO Cocktail in Istanbul! Date: Tuesday, 12 November Time: 6:00pm Location: Veranda Pera [verandapera.com]<https://urldefense.com/v3/__https:/www.verandapera.com/__;!!PtGJab4!95goEHw…> Vişnezade, Gümüşsuyu, Asker Ocağı Cd. No:6, 34367 Şişli/İstanbul – Süzer Plaza Registration: https://forms.gle/ZaMDpMBbGRJJpcFk9 All participants must register by Friday, 01 November 2024 ccNSO related session schedule: https://community.icann.org/x/IgDyF *** A huge thank you to .auDA [auda.org.au]<https://urldefense.com/v3/__https:/www.auda.org.au/__;!!PtGJab4!95goEHwNX8e…> and nominet.uk [nominet.uk]<https://urldefense.com/v3/__https:/www.nominet.uk/__;!!PtGJab4!95goEHwNX8en…> for sponsoring this event *** Please let me know if you have any questions or concerns.

1 0