NOTES | Council prep | Sunday, 26 Oct 2025 (9 UTC)
Council prep | Sunday, 26 Oct 2025 (9 UTC) https://sched.co/29QKD ________________________________ 1. Welcome Welcome by Alejandra. 2. Overview of sessions and assigning rapporteurs Overview will be circulated closer to the session ccNSO Council: ICANN84 session assignments<https://docs.google.com/document/d/1hW-U5ofKGW-Kg3TMLW4_IU5PQqtDDttDQCR0gApb...> Notes taken directly in this doc 3. Preparing meeting with the Board: assign speakers
Council Topics:
· Unresolved issue from previous joint meetings – Playbook for Bylaw Amendments Resolved in the meanwhile. It took a long time. Linked to efficiency of icann processes. · MSM and ccNSO - In the context of ICANN’s multi-stakeholder model and ICANN’s current Strategic Plan, is there anything the ccNSO could do in your view to enhance the model and contribute to ICANN’s mission? Peter: do more? Refrained from commenting on some of the proposals. See what ASO is doing with ICP2. Bart: confusion with Board topic? Peter: was referring to our topic. Nigel: peter is right. We do need to have an internal decision on what peter described. Founding principles of ccnso. What does the bylaw say we need to do? Entire membership needs to approve if we go beyond that. If we are going to get involved in policy making, we need to interact. Jordan: jumping the shark. are there any unmet needs from icann’s side? Does not mean we automatically do what they suggest. Just trying to find out, if they wish us to do anything. Alejandra: we can take the answer. And not commit to anything, and then have a conversation, if needed. · Becky Burr’s reflection on relation ccNSO, ICANN and the broader community going forward. Saying goodbye to Becky Burr on the Board. Good to have her reflections. Would be good to keep this for the end. Bart: suggestion prior to session with Tripti to keep this for the end
Board Topic:
* “What does the ccNSO believe should be the Board’s and the ICANN organization’s policy priorities in 2026, taking into consideration the new Five-Year Strategic Plan, the WSIS+20 review, and the recently launched Cross Community Group on the Review of Reviews?” We want to know what “policy priorities” refer to? Nigel: confused. Icann org? Or the wider organisation? Chris: they mean the wider organisation. “Org” is a term invented by Göran to refer to staff. Jordan: community policy developed through icann system. Review policy to be adopted asap. ccNSO should not offer an opinion on the GNSO policy framework. How can icann do its work more nimbly, effectively, efficiently? Ignore the world “policy”. Chris as member of the policy priority framework. Have they met Chris: no Bart: you have the priority framework established. Now you have this again.. Alejandra: SO/AC chairs spoke about back and forth between board and community. Bouncing back takes time. Just take action. It does not help. Chris: GNSO has some policy priorities. Far less aimed at us. We are concerned about WSIS. hopefully over by the end of the year. The review of reviews also affects us. Make the process more effective and efficient. Alejandra: hope they adopt the IDN one too Bart: it is slow. But there are meetings in between. Prep time for the caucus. Variant management was a complicated matter. Alejandra: we can expect it soon-ish. By March we have this on the board’s agenda. Bart: who sets icann’s priorities? The group met every year. They went through the policies and all other priorities. You have this group, and then you have the question from the board …. Chris: check with Irina, she is the lead. Bart; they normally meet in May Jordan: Here is a link to the framework: https://icann-community.atlassian.net/wiki/spaces/projfinadhocws/pages/10662... 4. External appointments 2026 (https://docs.google.com/spreadsheets/d/1NdPoBTmQUVlPhMy1PsoZr6rUxUxHzRDQ/edi...) Bart: official appointment for 1 year. Preference for 2 years. Jordan: nomcom having a vice chair for the second time in a row on the board? Chris: expression opinions about the way the nomcom operates. Let’s call for a meeting with the leadership and express our concern The new chair was the last vice chair. Now there is a new vice chair. Real concerns about this. Also raise this with the board. Everton: if we have an appointee, let;s listen to her too. Not just the leadership. Permanent ongoing conversation. Not just a one-off. Nigel: i agree with Chris. Whatever concerns we have, bring to the board. The nomcon has been an issue a long time. Fundamental thing. Bart: nomcom asked for a meeting with the leadership team. Why not schedule a meeting at every AGM? Structural part, standard part of your work. Alejandra: yes. Let’s meet mid november nonetheless. Chris: to be most effective, talking to the board here would be good. Alejandra: nomcom supposed to be independent. Why address the board? Is that realistic? Pablo: agree with Bart’s proposal. Agree also with Everton. Speak to our liaison. Chris: the board is uncomfortable with what is happening. It is good for them to know the community feels uncomfortable too. Nigel: NomCom is an odd beast. Broken election system. In commercial organisations, a nomcom is a subcommittee of the board. Our NomCom has that role, but also has other roles. Balancing different parties of the community, diversity… but you do not want diversity in competence. The board needs to know we have these issues. Alejandra: first talk to nomcom leadership and our appointee? And then to board? So we do not mention it yet to the board. Let’s wait until Mumbai, or write a letter? Chris: huge value in delivering the message now. If we leave it is, it outside of the results of what they have done. If we do it, it should be here. Peter: focus on appointee. How far is our appointee aware? We should make sure she is aware. We cannot give the liaison concrete marching orders on the appointments. Patterns in the NomCom that appear non-worthy. Talk to our liaison first. I was an appointee during the pandemic. Pattern-wise, there might be interesting things. Extension of the mandate by the effectiveness review team was not helpful. Bart: use this meeting with the board. This is not directed to the board. Going forward you want to have the improved relation. We have been invited by the nomcom. But there is a concern. If you put it in the records now, it can feed into the review of reviews Alejandra: we can talk to our appointee here. Joint meeting or public form? Council prefers joint meeting Chris: we should let them know beforehand we have an AOB Alejandra: we will let Patricio, Byron, Tripti know. Alejandra: call for volunteers to happen. Peter: my term ended. Call for volunteers: RZERC. 5. Prep Council meeting Thursday 30 October No additional comments by Councillors to draft agenda that was circulated Draft Agenda | ccNSO Council meeting 222 | Thursday, 30 October 2025<https://docs.google.com/document/d/1OK-3geB4TbkfZxUPnumk2wHLbPkqsmJM0JqARJSQ...> 6. AOB Bylaw amendment Reviews. Paused for the moments. No time to study them yet. 2 alternatives: one is shorter in time. Both have a specific end date. Idea is to pause everything while work is ongoing. Cannot be extended forever. Fixed end date. Preference for the first one, in the conversations by the chairs ccNSO cocktail with the RySG to celebrate Becky’s journey in ICANN. She will get a present. Just a heads up. Stephen: personal note to council and secretariat. I did not stand for reelection. Charles will be on Council for NA. way past my time to go. I am resigning from Council at the conclusion of the meeting this Thursday. 25 years. Bart broke my arm years ago. If you have complaints, you know who to see 🙂 Alejandra: thank your for your hard work. More on Thursday. Chris: small speech for becky. Alejandra: Thanks for the remote councillors to join Biyi: session with Fellows this afternoon. Please join us. 7. Adjourn Joke Braeken joke.braeken@icann.org<mailto:joke.braeken@icann.org>
participants (1)
-
Joke Braeken