October 2025 - Ccnso-council

Update on ccNSO Council Nominations
by Joke Braeken Oct. 27, 2025

Oct. 27, 2025

Dear All, The three-year terms for five members of the ccNSO Council will conclude in March 2026. In September 2025, the Council launched a call for nominations to fill these upcoming vacancies. The only nominee from the African region did not accept their nomination. Council will meet on Thursday, 30 October 2025, during ICANN84: One of the agenda<https://docs.google.com/document/d/1OK-3geB4TbkfZxUPnumk2wHLbPkqsmJM0JqARJS…> items will be to launch a new call for nominations for the African region seat. Proposed timeline: * Call for nominations: 13 November – 4 December 2025 * Nomination acceptance period: 5 – 12 December 2025 * Election period (if applicable): 22 January – 4 February 2026 Current status of accepted nominations: * AP region: Boyoung Kim, Sami Mohamed Ali * EU region: Chris Disspain * LAC region: Alejandra Reynoso * NA region: Charles Noir During a question-and-answer session held on Wednesday, 29 October 2025 | 15:00-16:00 UTC at ICANN84, the ccNSO Membership will have the opportunity to engage with candidates for the upcoming ccNSO Council elections. Participants may ask questions to all Council candidates<https://ccnso.icann.org/about/councilelections.htm>, as well as the candidate for ICANN Board Seat 11<https://ccnso.icann.org/en/about/nominations.htm>. Candidate statements have been included here: * POBLETE_BoardSeat11_CandidateStatement_2025.pdf<https://drive.google.com/file/d/1-I9ElxvCddmxBvmkeWfbv0lq862SBNau/view?usp=…> * ALI_Council_CandidateStatement_2025.pdf<https://drive.google.com/file/d/1lWeFau2e0wPD4C2BYJaqKhrqGyZSU4Bo/view?usp=…> * REYNOSO_Council_CandidateStatement_2025.pdf<https://drive.google.com/file/d/1m8rt6dZf3M2F3DbdlylM1B_2TX6UR3h0/view?usp=…> * KIM_Council_CandidateStatement_2025.pdf<https://drive.google.com/file/d/18Ev3wM0JFjl3xAJO3-o3DT-tFLviHnNr/view?usp=…> * DISSPAIN_Council_CandidateStatement_2025.pdf<https://drive.google.com/file/d/1HhXOX34CF2l3ld-Hr-FyTSx86ev5eI5K/view?usp=…> * NOIR_Council_CandidateStatement_2025.pdf<https://drive.google.com/file/d/1J55rYnrzKxfrj-R4bS7kMIGpskfmpvwJ/view?usp=…> ccNSO at ICANN84 For more information about the ccNSO program at ICANN84, consult the ccNSO Session Highlights<https://docs.google.com/document/d/1utmHfAuGntv5HkP8aMLQH2qIlojsaYGZqEeyKnc…>. This document outlines the ccNSO schedule for ICANN84, including session dates and times, along with agenda details. It serves as a reference for attendees to navigate the ccNSO-related meetings and discussions during the event. Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 0

Monday 27 October | ccNSO Related Sessions at ICANN84!
by Claudia Ruiz Oct. 27, 2025

Oct. 27, 2025

Hello, Welcome to Tech Day and Day 3 of ICANN84!! Monday, 27 October 2025 * Welcome Ceremony <https://icann84.sched.com/event/29QIQ> * | block 1 * Tech Day <https://icann84.sched.com/event/29QJv/ccnso-tech-day-1-of-3> * Part 1, Part 2, Part 3 (Tech Day by DASC), Part 4 | 10:45-12:00, 13:15-14:30, 15:00-16:00, 16:30 – 17:30 | Liffey B - Level 1 (ccNSO)<https://icann84.sched.com/venue/Liffey+B+-+Level+1+%28ccNSO%29> Hope to see you there, Claudia Ruiz

1 0

Fwd: AOB for our ccNSO & Board joint meeting
by Alejandra Reynoso Barral Oct. 26, 2025

Oct. 26, 2025

FYI ******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. ******************************************* ---------- Forwarded message --------- From: Alejandra Reynoso Barral <alejandra.reynoso(a)gmail.com> Date: Sun, Oct 26, 2025 at 2:06 PM Subject: AOB for our ccNSO & Board joint meeting To: Tripti Sinha <tripti.sinha(a)board.icann.org> Cc: Patricio Poblete <ppoblete(a)nic.cl>, Byron Holland <byron.holland(a)cira.ca>, Board Ops Team <board-ops-team(a)icann.org>, ccNSO Secretariat < ccnsosecretariat(a)icann.org> Dear Tripti Today the ccNSO Council had its preparatory meeting and one of the topics we discussed was the result of this year’s NomCom appointment process. As a heads-up we will raise this during the AOB of our joint session on Tuesday. We don’t expect you to comment or respond, unless you wish to. Additionally, would it be ok that we leave our suggested topic on Becky's reflection to be the last one in the agenda (after the AOB)? It would be a nice closure. Best regards, Alejandra ******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. *******************************************

1 0

Fwd: [Soac-chairs-vice-chairs] FOLLOW UP: Update on Bylaw Changes re: Reviews
by Alejandra Reynoso Barral Oct. 26, 2025

Oct. 26, 2025

Dear Councillors As mentioned in our prep call, please find below the alternatives proposed as bylaw amendments to acknowledge the pause of specific reviews while the Review of Reviews Cross Community Group (CCG) is ongoing. Just as a little bit of background, the ccNSO has remained neutral to the need of this bylaw amendment, and we agree with the SO/AC Chairs that alternative 1 felt the best way forward with the following observations: 1. The conditions for extending the period should remain objective, if conditions are met, extension will proceed, otherwise not. 2. We are aiming at the shortest time possible, to be closer with the current CCG timeline, to prove that in ICANN work can be done in a reasonable time frame. 3. Our task is to suggest the best options in brackets [ ] for the language to go into the Bylaw Amendment process. Best regards, Aleajndra ******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. ******************************************* ---------- Forwarded message --------- From: Mary Wong via Soac-chairs-vice-chairs < soac-chairs-vice-chairs(a)icann.org> Date: Thu, Oct 16, 2025 at 11:03 PM Subject: [Soac-chairs-vice-chairs] FOLLOW UP: Update on Bylaw Changes re: Reviews To: soac-chairs-vice-chairs(a)icann.org <soac-chairs-vice-chairs(a)icann.org> Cc: Policy Team Leaders <policy-team-leaders(a)icann.org>, Kurtis Lindqvist < kurtis.lindqvist(a)icann.org>, Theresa Swinehart <theresa.swinehart(a)icann.org>, John Jeffrey <john.jeffrey(a)icann.org>, Russ Weinstein < russ.weinstein(a)icann.org>, Sam Eisner <Samantha.Eisner(a)icann.org> Dear SOAC Leaders, Please see the message below from Russ as well as the attached draft proposals for a Bylaws amendment relating to reviews. Thank you, we are looking forward to welcoming you all to ICANN84 in Dublin and our discussions there! As I committed to doing in the note I sent to you on Monday 13 October, I am attaching a document with two alternative proposals for a Bylaws amendment that we’d like to explore with the community. We hope that you will view these as a strong starting point for further community discussion on how to ensure that ICANN adheres to its obligations under Sections 4.4 and 4.6 of the Bylaws, while the Review of Reviews Cross Community Working Group is working concurrently to address the question of how Bylaws-mandated reviews should be considered in the future. The two alternatives, as outlined below, were drafted to achieve the overarching principle that any relief of ICANN’s obligations to conduct Specific Reviews should only last for a fixed period of time, and not require special action by ICANN or the community to restart. The difference between the two is that one sets forth a shorter timeframe for the relief in question and defines the conditions for which the ICANN community could agree that more time is needed to conduct their work, while still defining a maximum duration for the pause. The second alternative is more straightforward, and sets out a single, unextendible duration for the pause, based upon the same maximum duration set out in the first alternative. In both alternatives, the proposed addition of a Transition Article would be a Standard Bylaws Amendment. We are interested in hearing your thoughts on what might be a reasonable and successful path forward. We hope that the Roundtable next week in Dublin can provide an opportunity to begin this discussion. Some of the questions we may wish to discuss could be: - Do either or both of the proposals address the community’s concern in bringing ICANN back into compliance with its Bylaws obligations? - If not, what are the issues that are not addressed? What ideas and alternatives do you suggest for addressing these issues? - What is the likely period of time that the community and ICANN will need to complete the work to get to a new form of reviews? What is a reasonable duration for the pause? - Is a shorter period for a pause that is coupled with the ability to extend preferable to a single, longer period? - If we proceed with the shorter pause, have we captured the right conditions for allowing an extension? - What level of socialization do you think is needed with your groups prior to moving to a formal Bylaws amendment process? To help prepare for our discussion, we have included further rationale for each of the proposed alternatives. *The Proposals: Common Elements* Both alternatives have the following common factors: 1. Use a Transition Article to pause, for a defined period of time, ICANN’s obligation to conduct the Specific Reviews as defined through Article 4, Section 4.6; 2. Set a workable schedule for reviews to be re-initiated under Article 4, Section 4.6 in a manner that will not replicate the overlap of reviews that led in part to the issues ICANN currently experiences with reviews; and 3. Do not define the one-time process of the Reviews CCG as the mechanism through which updates to Specific Reviews must be achieved. For both alternatives: 1. The defined time for the pause would not go into effect until the Bylaws Amendment has been approved by the ICANN Board and the Empowered Community process has been completed. This is estimated to be approximately four months from the time the Board initiates a Standard Bylaws Amendment Process. 2. As soon as the relevant Bylaws regarding reviews are amended, the pause ends because ICANN’s obligations regarding reviews will have changed. In each case, the Transition Article includes a re-initiation of the Bylaws-mandated reviews in the event that no changes are made during the pause. Another discussion point relates to the restarting of the Competition, Consumer Trust and Consumer Choice (CCT) review. In each alternative, we propose a different trigger for the initiation of that review than is currently found in the Bylaws. The proposed language is *“when the next round of new gTLDs has been in operation for two years, such operation being measured from the time that 500 gTLDs applied for within that round have been delegated into the root zone.”* This reflects the ATRT3 recommendation that the timing for the next CCT review be extended from one to two years from the round being in operation. In addition, and based on the evolution of the domain name market as a result of the 2012 Round, ICANN org is concerned that triggering the data collection activities to measure the impact on the operation of a new gTLD round based on a single new gTLD delegation will not collect or measure enough data about the impact of that round. We therefore propose that a more significant sample be required. We are happy to discuss the appropriate number of delegated TLDs that should be required to be in the root before the initiation of the CCT review. *Alternative 1: Pause with ability to extend * 1. Includes bracketed alternatives for discussion regarding the appropriate duration of a pause (e.g., should it be for 12 months, extendable to 24 months, or for 18 months, extendable to 30 months? Are different timeframes appropriate?) 2. Sets out a few conditions for the extension of the pause, including: 1. ICANN Board acceptance of a community recommendation on the modification of Specific Reviews, which is proceeding to implementation; 2. A pending Bylaws amendment process to update or replace Article 4, Section 4.6 of the ICANN Bylaws; or 3. Four of the seven SOs and ACs issue a statement supporting a further pause of Specific Reviews. 3. Defines a staged schedule if the Specific Reviews are not changed to address the issue of overlapping reviews, with 18 months proposed between the initiation of each new review, and an updated requirement for kicking off the CCT (as discussed above). *Alternative 2: The “Simple” Version* Alternative 2 sets out a pause of 24 or 30 months, with no ability to extend the pause. Alternative 2 takes the maximum pause as proposed within Alternative 1, and sets that as the baseline. If ICANN’s obligations to conduct reviews have not changed by the end of the pause, then the Specific Reviews will proceed based on the same staggered schedule presented within the Alternative 1. This creates a simple, straightforward pause with no need to identify if conditions exist to extend the pause. Best regards, Russ *From: *Russ Weinstein <russ.weinstein(a)icann.org> *Date: *Monday, October 13, 2025 at 12:31 PM *To: *Susie Johnson via Soac-chairs-vice-chairs < soac-chairs-vice-chairs(a)icann.org> *Cc: *Policy Team Leaders <policy-team-leaders(a)icann.org>, Kurtis Lindqvist <kurtis.lindqvist(a)icann.org>, Theresa Swinehart <theresa.swinehart(a)icann.org>, John Jeffrey <john.jeffrey(a)icann.org> *Subject: *Update on Bylaw Changes re: Reviews Dear SOAC Leaders I hope this finds you well. As we discussed in the several meetings following ICANN83 related to reviews, the Org would work with this group and the Board on a proposal to amend the Bylaws to bring to the community for consideration. The objective of the proposal is to address the ICANN community’s request to bring ICANN back into compliance with its Bylaws obligations on conducting Specific Reviews while the Review of Reviews Cross Community Working Group (Reviews CCG) is addressing the question of how reviews should be considered in the future. I am pleased to report, we have made good progress on the drafting. As noted in Tripti’s recent blog <https://www.icann.org/en/blogs/details/chairs-blog-recap-of-the-september-b…> about the Board’s workshop in Madrid, the Board discussed and provided feedback on a proposal from staff. We have made updates to address the feedback and are socializing the updated proposal with the Board. I must caveat, this socialization with the Board is to ensure they are comfortable with the proposal, but not a commitment that they would approve it. From a procedural perspective the process would follow the requirements set out in the Bylaws, Article 25 Section 25.1: · Board Action to Initiate the Bylaws Amendment · Public Comment · Summary & Analysis of Comments · Updates to the proposal as needed · Board Action · Empowered Community Rejection Action Period As we have previously shared, particularly with the December holidays intervening, we anticipate that these steps could be completed and come into effect in as quickly as ~ 4 months. We suggest that ensuring alignment with the SOAC leaders that the proposal addresses the spirit of the community’s original request and generally meets expectations before proceeding to the formal process above will help us meet or beat this 4 month timeline. As a next step we plan to provide the proposal to the SOAC leadership by end of my day 16 October. We suggest discussing it at the SOAC leadership roundtable in Dublin to gather any additional feedback and ensure alignment. When it is shared, we will provide more context for how and why the proposal is organized and designed in relation to the community’s requests. Thanks, Russ _______________________________________________ Soac-chairs-vice-chairs mailing list -- soac-chairs-vice-chairs(a)icann.org To unsubscribe send an email to soac-chairs-vice-chairs-leave(a)icann.org

1 0

Fwd: [soac-chairs] Draft Bylaw Change Playbook
by Alejandra Reynoso Barral Oct. 26, 2025

Oct. 26, 2025

Dear Councillors Please find below the Bylaws playbook I mentioned today at our prep meeting. Best regards, Alejandra ******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. ******************************************* ---------- Forwarded message --------- From: Russ Weinstein via soac-chairs <soac-chairs(a)icann.org> Date: Thu, Oct 23, 2025 at 3:25 PM Subject: [soac-chairs] Draft Bylaw Change Playbook To: Soac-chairs(a)icann.org <Soac-chairs(a)icann.org> Cc: Policy Team Leaders <policy-team-leaders(a)icann.org>, Kurtis Lindqvist < kurtis.lindqvist(a)icann.org>, John Jeffrey <john.jeffrey(a)icann.org>, Sam Eisner <Samantha.Eisner(a)icann.org> Dear SO AC Leaders, I hope your travel has gone smoothly (or is going smoothly). The team and I am looking forward to seeing you soon here in Dublin! Based on a previous request for information on how the community can raise the need for Bylaws amendments and the expected processes from start to finish for such amendment processes, attached please find a discussion draft of a Bylaws Playbook. We have been working on a draft that shares meaningful information, with the hope that it is useful to the community. While the procedural requirements from the ICANN Bylaws Article 25, Sections 25.1 and 25.2 are defined, those procedural requirements only start once there is language upon which the Bylaws amendment processes can be formally initiated. As documented in the Playbook, there are a variety of situations from which community could identify the possible need for a Bylaws amendment. The Bylaws Playbook therefore is more example-based than forward looking, exploring how Bylaws amendments have been raised in the past. The Playbook then discusses how, once there is appropriate language for consideration, the formal Section 25.1 or 25.2 processes move forward. We are looking for your feedback on the utility of this document and whether there are modifications or enhancements that might serve the community’s needs. If it would be helpful, we would be happy to schedule some time next month to hear your initial thoughts. Thanks, Russ Russ Weinstein Senior Vice President, Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) _______________________________________________ soac-chairs mailing list -- soac-chairs(a)icann.org To unsubscribe send an email to soac-chairs-leave(a)icann.org _______________________________________________ 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.

1 0

NOTES | Council prep | Sunday, 26 Oct 2025 (9 UTC)
by Joke Braeken Oct. 26, 2025

Oct. 26, 2025

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_IU5PQqtDDttDQCR0gAp…> 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/1066… 4. External appointments 2026 (https://docs.google.com/spreadsheets/d/1NdPoBTmQUVlPhMy1PsoZr6rUxUxHzRDQ/ed…) 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-3geB4TbkfZxUPnumk2wHLbPkqsmJM0JqARJS…> 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(a)icann.org<mailto:joke.braeken@icann.org>

1 0

ROOM CORRECTION | Sunday 26 October | ccNSO Related Sessions at ICANN84!
by Claudia Ruiz Oct. 26, 2025

Oct. 26, 2025

Dear all, Apologies for the typo, SOPC session will be in Liffey Hall 1 * ccNSO: Strategic and Operational Planning Standing Committee Session [icann84.sched.com]<https://urldefense.com/v3/__https:/icann84.sched.com/event/29QKF/ccnso-stra…>| 13:15 – 14:30 (internal work) | Room Liffey Hall 1 – Level 1 Thank you! From: ccNSO Council <ccnso-council(a)icann.org> Reply-To: Claudia Ruiz <claudia.ruiz(a)icann.org> Date: Sunday, October 26, 2025 at 5:00 AM To: "ccnso-members(a)icann.org" <ccnso-members(a)icann.org>, "ccTLDcommunity(a)cctld-managers.org" <ccTLDcommunity(a)cctld-managers.org> Cc: ccNSO Council <ccnso-council(a)icann.org> Subject: [ccnso-council] Sunday 26 October | ccNSO Related Sessions at ICANN84! Hello, Welcome to Day 2 of ICANN84!! Important: Please note the time change!!! Also, please see that we will be alternating between two different rooms today. Sunday, 26 October 2025 * ccNSO: Council Prep: Roles & Responsibilities [icann84.sched.com]<https://urldefense.com/v3/__https:/icann84.sched.com/event/29QKD/ccnso-coun…> (CLOSED) | 9:00-10:10 | Room Liffey Hall 1 – Level 1 * ccNSO: TLD-OPS [icann84.sched.com]<https://urldefense.com/v3/__https:/icann84.sched.com/event/29QJr/ccnso-tld-…> (CLOSED) | 9:00-10:10 | Room Liffey B – Level 1 (ccNSO Room) * ccNSO: TLD-OPS Work Session [icann84.sched.com]<https://urldefense.com/v3/__https:/icann84.sched.com/event/29QJs/ccnso-tld-…>| 10:30-12:00 | Room Liffey B – Level 1 (ccNSO Room) * ccNSO: Strategic and Operational Planning Standing Committee Session [icann84.sched.com]<https://urldefense.com/v3/__https:/icann84.sched.com/event/29QKF/ccnso-stra…>| 13:15 – 14:30 (internal work) | Room Liffey Hall 1 – Level 1 * ccNSO: Guidelines Review Committee Working Session (1 of 2) [icann84.sched.com]<https://urldefense.com/v3/__https:/icann84.sched.com/event/29QJm/ccnso-guid…> (CLOSED) | 15:00 – 16:00 | Room Liffey B – Level 1 (ccNSO Room) * ccNSO: Guidelines Review Committee Working Session ( 2 of 2 ) [icann84.sched.com]<https://urldefense.com/v3/__https:/icann84.sched.com/event/29QJo/ccnso-guid…> (CLOSED) | 16:30 – 17:30 | Room Liffey B – Level 1 (ccNSO Room) Hope to see you there, Claudia Ruiz

1 0

Re: Zoom link Council prep (closed session)
by Bart Boswinkel Oct. 26, 2025

Oct. 26, 2025

Agenda included as well Bart From: Joke Braeken via Ccnso-council <ccnso-council(a)icann.org> Reply-To: Joke Braeken <joke.braeken(a)icann.org> Date: Sunday, October 26, 2025 at 8:53 AM To: ccnso-council <ccnso-council(a)icann.org> Subject: [ccnso-council] Zoom link Council prep (closed session) All, Here is the zoom link for today’s council Prep meeting. This is a closed session. https://icann.zoom.us/j/95073038756?pwd=pbOGcPTotQr5pX87r0Cacm50V6tNbk.1 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/95073038756?pwd=pbOGcPTo…> Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 0

Council prep
by ccNSO Calendar Oct. 26, 2025

Oct. 26, 2025

https://icann.zoom.us/j/95073038756?pwd=pbOGcPTotQr5pX87r0Cacm50V6tNbk.1

1 0

Zoom link Council prep (closed session)
by Joke Braeken Oct. 26, 2025

Oct. 26, 2025

All, Here is the zoom link for today’s council Prep meeting. This is a closed session. https://icann.zoom.us/j/95073038756?pwd=pbOGcPTotQr5pX87r0Cacm50V6tNbk.1 Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 0