- Ccnso-council - lists.icann.org

Call for Volunteers: ccNSO Study Group on IANA Public Records
by Joke Braeken Nov. 26, 2025

Nov. 26, 2025

Call for Volunteers: ccNSO Study Group on IANA Public Records The ccNSO Council is seeking volunteers to serve on the ccNSO Study Group on IANA Data Accuracy. The Study Group is expected to begin work in January 2026. This call for volunteers closes 12 December 2025 (23:59 UTC). PURPOSE | The Study Group will examine the purpose, accuracy, and potential compliance mechanisms for IANA public records. Its work includes reviewing what data IANA publishes and why, whether current record types remain necessary, and whether new records should be added. The group will also assess the importance and current level of accuracy of these records and consider what should happen when inaccuracies persist. Finally, it will explore possible compliance and enforcement options beyond today’s limited mechanisms. Based on its findings, the Study Group may recommend new policies or practices to the ccNSO Council. Read more: Terms of Reference IANA Public Records Study Group<https://icann-community.atlassian.net/wiki/spaces/ccNSOCWS/pages/103123987/…> (item 17, ccNSO Council meeting 218) MEMBERSHIP & LEADERSHIP | Membership is open to all representatives of ccTLD managers (members and non-members of the ccNSO) who have ongoing commitment to actively participate in the activities of the study group. At least one of the members should be a ccNSO Councilor. The ccNSO Council appoints members, and regional ccTLD organizations can nominate liaisons, who need to be confirmed by Council. The Chair of the study Group may invite other ICANN SOs/ACs, staff, and external experts to participate. Liaisons, Participants, and Experts engage equally with Members. The ccNSO Council will appoint one of its Councilors as chair and invite the Study group to nominate a vice-chair from among its members. The vice-chair must be formally appointed by Council. WORKING METHODS AND TIME COMMITMENTS | The study group relies on active contributions of its members. It is expected that the group will meet every other week throughout the year. The group might meet during ICANN public meetings As per its Terms of Reference, the study group closes at the end of the ccNSO Council meeting the final report has been discussed by the ccNSO Council, but no later than the ccNSO Council meeting at ICANN86 (June 2026). HOW TO APPLY If you are interested in joining the working group, please submit your application by 12 December 2025 (23:59 UTC). To apply, complete the form here https://forms.gle/kkdUyeWoedVGMYBi9 You will be asked to provide your full name and contact details, your ccTLD affiliation, and a brief statement outlining your qualifications and motivation for joining the group. Additionally, all members and participants to this working group will have to complete a Statement of Interest (SOI). Fill out the form here: https://forms.gle/79Jw4wSnNhn5W4Z46 To facilitate your participation in the ccNSO representing your ccTLD, we will require an ICANN Account<https://account.icann.org/help>, which is the ccNSO's and ICANN's platform to manage participation. If you already have an ICANN Account (e.g. for registering at ICANN meetings), please login<https://account.icann.org/login> to your ICANN Account using the email address that you use for your ccNSO work and verify that your profile is up to date. If you do not have an ICANN Account or are unsure, please create an ICANN Account<https://account.icann.org/> at your earliest convenience. NEXT STEPS | Members shall be appointed by the ccNSO Council after closure of the call for volunteers. The first meeting by this study group will be held in January 2026. If you have questions, please contact us at ccnsosecretariat(a)icann.org<mailto:ccnsosecretariat@icann.org> BACKGROUND For background materials and the full Terms of Reference, please visit: * Final Report ccNSO Policy Gap Analysis Working Group<https://icann-community.atlassian.net/wiki/spaces/ccnsowkspc/pages/10841534…> * IANA's Topic Areas for ccTLD Policy Reviews<https://icann-community.atlassian.net/wiki/spaces/ccnsowkspc/pages/10841534…> * Terms of Reference IANA Public Records Study Group<https://icann-community.atlassian.net/wiki/spaces/ccNSOCWS/pages/103123987/…> (item 17, ccNSO Council meeting 218) Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 0

Reminder: Please cast your vote in the ongoing ccNSO/AP-Region election
by Joke Braeken Nov. 26, 2025

Nov. 26, 2025

Dear AP Region Members, I am writing to kindly remind you to cast your vote in the ongoing ccNSO/AP-Region election, to select one Council member from the region. To date, only 20 members have voted, and we have not yet reached the required quorum for a valid outcome. Quorum is achieved when more than half of the Emissaries in the region vote. The region counts 57 Emissaries in total. Earlier today, a reminder was sent to all Emissaries who have not yet voted. If you haven’t already done so, please review the election notice and submit your vote. Read more here: https://ccnso.icann.org/en/announcements/announcement-17nov25-en.htm Your participation is important — every vote counts and helps ensure a representative outcome for the Region. Thank you. Sincerely, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 0

Fwd: Notification ICANN Board Director Nominated by the ccNSO Council (Seat 11)
by Alejandra Reynoso Barral Nov. 25, 2025

Nov. 25, 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: Tue, Nov 25, 2025 at 5:02 PM Subject: Notification ICANN Board Director Nominated by the ccNSO Council (Seat 11) To: ECAdmin <ecadmin(a)icann.org> Cc: John Jeffrey <john.jeffrey(a)icann.org>, Tripti Sinha < tripti.sinha(a)board.icann.org>, Patricio Poblete <ppoblete(a)nic.cl>, Kurtis Lindqvist <kurtis.lindqvist(a)icann.org>, ccNSO Secretariat < ccnsosecretariat(a)icann.org> Dear members of the ECA On behalf of the ccNSO Council, please find attached a notification of the ICANN Board Director Nominated by the ccNSO Council for Seat 11. 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

Call for Volunteers: We seek one ccNSO appointee to the Root Zone Evolution Review Committee (RZERC)
by Joke Braeken Nov. 24, 2025

Nov. 24, 2025

Call for Volunteers: Root Zone Evolution Review Committee (RZERC) As the 3-year term of the current ccNSO appointee to the Root Zone Evolution Review Committee (RZERC) has ended, the ccNSO Council seeks one (1) member to RZERC. The call for volunteers will close on Friday, 5 December 2025 (23:59 UTC). ROLE AND ELIGIBILITY This call for volunteers is open to all individuals affiliated with ccTLD managers—regardless of ccNSO membership—who can demonstrate an ongoing commitment to actively contribute to the work of the Committee. Please note that volunteers for the position are expected to have substantial expertise and a deep, demonstrable technical understanding of the DNS and its underlying architecture. ccNSO-appointed members of the CCG serve in their individual capacity. However, the ccNSO appointee to the RZERC is expected to represent ccNSO values in their work, follow specific direction from the ccNSO Council when provided, and seek the Council’s guidance whenever needed. TERM, WORKING METHODS, TIME COMMITMENTS The appointment lasts three years, with the Council checking each year whether the member wishes to continue. As per the RZERC operational procedures, the Committee meets as often as needed, but at least once per year. Regular meetings require 14 days’ notice and may be called by the Chair or any two members. Urgent meetings can be called with the best notice possible. Meetings may be remote or in-person, but email discussions are not considered meetings. A quorum, as defined in the operating procedures, is required for any meeting. HOW TO APPLY If you are interested in joining RZERC, please submit your application by Friday, 5 December 2025 (23:59 UTC). To apply: 1. Complete the form here https://forms.gle/bHo7XCuXwdH2RMcX9 You will be asked to provide your full name and contact details, your ccTLD affiliation, and a brief statement outlining your qualifications and motivation for joining the group. If not employed by a ccTLD manager, proof of active support from one is required: Please send any additional materials to ccnsosecretariat(a)icann.org<mailto:ccnsosecretariat@icann.org>. 1. Fill out the ccNSO Statement of Interest form: https://forms.gle/79Jw4wSnNhn5W4Z46. Once processed by the Secretariat, you can check your SOI here: https://community.icann.org/x/doAFEg  Read here the ccNSO SOI Guideline: https://ccnso.icann.org/sites/default/files/field-attached/ccnso-internal-p… 2. To facilitate your participation in the ccNSO representing your ccTLD, we will require an ICANN Account<https://account.icann.org/help>, which is the ccNSO’s and ICANN’s platform to manage participation. If you already have an ICANN Account (e.g. for registering at ICANN meetings), please login<https://account.icann.org/login> to your ICANN Account using the email address that you use for your ccNSO work and verify that your profile is up to date. If you do not have an ICANN Account or are unsure, please create an ICANN Account<https://account.icann.org/> at your earliest convenience. NEXT STEPS ccNSO Council shall evaluate all applications, select its preferred candidate, and appoint one member to RZERC, after closure of the call for volunteers. The selection is governed by the ccNSO Guideline regarding ccNSO appointment procedures: https://ccnso.icann.org/sites/default/files/field-attached/guidelines-ccnso… The ccNSO Chair shall notify the RZERC Chair, via email, regarding the member it appoints to the Committee. The RZERC Chair shall then notify the Committee and instruct ICANN support staff to add the member to the Committee distribution list. ABOUT RZERC Following the IANA Stewardship Transition, ICANN has established a Root Zone Evolution Review Committee (RZERC). This Committee is tasked to review and provide input regarding proposed architectural and operational changes to the root zone, including both hardware and software components used in executing changes to the DNS root zone, and the mechanisms used for distribution of the DNS root zone. The Committee shall, as determined necessary by its membership, make recommendations related to those changes for consideration by the ICANN Board. Read more: https://www.icann.org/rzerc Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 0

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

Nov. 21, 2025

Dear Councillors As agreed, below you will find the response sent regarding the Draft Bylaw Change Playbook. 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: Alejandra Reynoso Barral <alejandra.reynoso(a)gmail.com> Date: Fri, Nov 21, 2025 at 2:59 PM Subject: Re: [soac-chairs] Draft Bylaw Change Playbook To: Russ Weinstein <russ.weinstein(a)icann.org> Cc: Soac-chairs(a)icann.org <Soac-chairs(a)icann.org>, 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 Russ After having a conversation with the ccNSO Council I want to express my appreciation for the proposed playbook, and I believe it is a sound basis to understand the complexities inherent in ICANN Bylaw changes. From reading the Playbook, it is our understanding that the Bylaw amendment process can be divided in two phases: - Phase one: The procedures to develop a proposed Bylaw change, starting with a request for a Bylaw change and ending with the Initiation of the Bylaw amendment process by the Board (directing a public comment) - Phase two: The procedures and actions as defined in the ICANN Bylaw amendment procedures starting with the public comment period and ending a Board decision to stop the process or ending with EC rejection or approval action process. After an initial evaluation of the playbook, we believe that focusing on the mapping and documenting of the first phase is most helpful to explain how a Bylaw amendment should be proposed by (a part of) the community, and to understand what to expect after an amendment is proposed. Since 2016, when the Empowered Community was established, various Bylaw amendments have been initiated and concluded, and the community has gained an understanding of its role and the procedures. Looking at the Bylaw Change Playbook we have identified the following basic flow for phase one (see overview below). 1. Originating Request. 2. Addressee. 3. Assessment of need and scope of the requested Bylaw amendment. 4. Coordination and detailing of proposals with requesting entities. 5. Consistency Check. 6. Board Initiation (Milestone): End of Phase 1 and Start of Phase 2. Assuming this flow is correct, we have the following questions and observations: - Does it make a difference how a Bylaw proposal originates? For example, through a PDP, a Bylaw mandated review, or a community working group? If so, what is the impact? - Are there Bylaw change requests that by definition can not result in an amendment, for example if a Bylaw amendment is only suggested as part of comment in a public comment procedure and this suggestion is not accepted? In the past the ccNSO Council suggested a Bylaw change through a public comment. This part of the public comments was not accepted by the relevant committee, i.e not included as recommendation by the review team. Does a request for a Bylaw change need to meet any formalities and/or format? - Who is the addressee of a Bylaw amendment? Board, CEO & President, other (for example both)? - Once a request is received, it is unclear from the Playbook, who from staff will be designated to assess the need and scope, who will be informed about the outcome, what is a reasonable timeline, and how to escalate matters if needed. We believe that providing clarity will add significantly to the predictability of the amendment process and cooperation of entities involved in the process. To date the ccNSO had varying experiences with respect to this and the next steps of Phase 1 ( Coordination with requester and Consistency check) . Finally, the Council would like to understand when a request fails? Who decides? Will the requesting party be informed and by whom? Kind regards, Alejandra Reynoso Overview of Phase 1 - Requesting a Bylaw amendment [image: image.jpeg] ******************************************* 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. ******************************************* On Thu, Oct 23, 2025 at 4:25 PM Russ Weinstein via soac-chairs < soac-chairs(a)icann.org> wrote: > 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

proposed written updates, November 2025 edition
by Joke Braeken Nov. 20, 2025

Nov. 20, 2025

1 0

NOTES | ccNSO Council meeting 223 | Thursday, 20 November 2025 | noon UTC
by Joke Braeken Nov. 20, 2025

Nov. 20, 2025

NOTES ccNSO Council meeting 223 Thursday, 20 November 2025 | noon UTC Apologies Received Jordan, Olga, Ali, Nacho Background and supporting documents * Council workspace for this meeting: https://icann-community.atlassian.net/wiki/x/J4wlBg * ccNSO correspondence: statements and responses: https://ccnso.icann.org/en/about/statements.htm Agenda ADMINISTRATIVE MATTERS 1. Welcome Alejanra: 3 AOB * Closure of GAC-ccNSO meeting and world cafe * meeting/ invite RySG to cooperate with respect to GNSO PDP ( see email Beth) * Tentative Blockschedule ICANN85 a. SOI updates Consult the ccNSO SOI Guideline<https://ccnso.icann.org/en/about/ccnso-internal-procedure-general-soi-coi-2…> Complete the SOI template<https://docs.google.com/forms/d/e/1FAIpQLSfRpehiCw2ty2PYRiaPG0K3lZSKk9LrLPQ…> Check the ccNSO Statements of Interest<https://community.icann.org/x/doAFEg> Alejandra: any updates? none b. Meeting quorum Apologies: Jordan, Olga, Ali 2. Relevant Correspondence 3. Minutes & Action Items a. Minutes Meeting 222 Circulated to the Council mailing list on 14 November 2025. Alejandra: questions? none b. Action Items: Alejandra: All action items either completed, pending, or awaiting launch of the new website. Regarding item 222-02 (pending items tracker) are completed. In Dublin we felt that issue needs to be addressed and it still has to. More matter is ccNSO Council and secretariat the most appropriate group to set-up and maintain the joint tracker. Needs further discussion. Will keep this as an action item agenda, with the caveat that preliminary questions need to be resolved first. Any comments? None · Action item 222-01 The ccNSO Secretariat is requested to schedule a call for volunteers for a small group to review the Bylaw Change Playbook and prepare a response to be adopted by the Council at Meeting 223 in November (See agenda item 16) · Action item 222-02 The ccNSO Secretariat is requested to create a joint tracker in a google doc for all SO/ACs to add any pending requested items to the Board. (Pending, awaiting clarification and confirmation by other SO/AC) · Action item 222-03 Following the conclusion of the candidate Q&A, the Nomination Process Manager is requested to prepare the Nomination Process report for discussion by Council at meeting 223.(Completed, see item 13) · Action item 222-04 The Council Election Process Manager is requested to launch a call for nominations for one seat on the ccNSO Council, for the African region.(Completed) · Action item 222-05 The ccNSO Secretariat is requested to publish the updated ccNSO FY26-27 Portfolio of Activities and quarterly overview (Pending, awaits launch of new website). · Action item 222-06 The ccNSO Chair is requested to inform the RySG and CSC about the adoption by ccNSO of the changes to the CSC Charter. The secretariat is requested to inform ICANN legal and other relevant ICANN staff, and publish this resolution (Completed). · Action item 222-07 The secretariat is requested to publish the updated overview of the policies, guidance and practices for ccTLDs, and to archive the previous version. The secretariat is also requested to publish this resolution regarding the adoption of the updated overview. (Pending, awaits launch of new website). · Action item 222-08 The secretariat is requested to inform the leadership teams of the various working groups and committees and persons appointed, of appointments and enable their participation in the respective teams. This also includes the nominees for the 2026 ICANN leadership Program. (Completed) · Action item 222-09 The ccNSO Secretariat is requested to launch calls for volunteers for the SOPC, IANA Whois Accuracy Study Group and RZERC.(Completed). 4. Intermeeting Council Decisions (since meeting 222, October 2025) None 5. Intermeeting Decisions Triage Committee since Council meeting 222 None UPDATES Written updates - if any - are published on the wiki space for this meeting. Written updates for items 6, 7, 8 are available or will be coming soon to our inboxes. In the meantime does anyone have any pressing comments? none 6. Update ECA & CSC (written updates) 7. Update Working Groups (written updates) a. ccPDP4-IDN (Dormant) b. DASC c. GRC d. IGLC e. MPC f. OMC g. SOPC h. Tech WG i. TLD-OPS SC j. Triage Committee (reported) k. UAC l. CIP-CCG m. Planning Prioritization Process group n. RZERC o. RSS GWG p. CCG Review of Reviews (item 11) 8. Update Liaisons (written updates) a. Update ccNSO Liaison to ALAC b. Update ccNSO Liaison to GNSO Council 9. Progress Board Consideration ccPDP4-IDN Informational No update since meeting 222 10. Progress Review of Reviews Informational Alejandra: in fact-finding mode. Webinars on Tuesday. Chris: later one was better attended. Review on past reviews. Straightforward discussion. Well worth having. Next CCG call is next Tuesday. We will talk about possible solutions. Focus initially on the A bucket. To be followed up in the annual reports and the strategic plan, as boundaries for the reviews. Alejandra: all according to schedule? No concerns regarding progress? Chris: not at the moment Alejandra: do we need a session with ccNSO at ICANN85. Chris: at least one plenary, probably Thursday morning. We want to meet during the week with each SO/AC, for at least 1 hour. You will receive a letter soon. Background ICANN's bylaws require periodic reviews of its supporting organizations, advisory committees, and other structures to ensure accountability and effectiveness. Past reviews have faced institutional lethargy, missed deadlines, and a failure to fully implement recommendations before the next review cycle begins. The current effort, formally initiated in May 2025 with a proposed Cross-Community Group (RoR CCG), seeks to break this cycle by addressing the procedural challenges within the review process itself. 11. Progress “How we meet” CCG No update since Council meeting 222 12. Update Chair, Vice-chairs, Councillors, Regional Organisations, Secretariat Alejandra: attended Mumbai planning webinar. Two topics which need follow-up: * The planning of Smart Africa capacity building against Tech Day. Need to avoid these scheduling in future. Both myself and Eberhard expressed concerns. To be followed-up * Board-Community session was proposed to be held at ICANN85, as a result from “how we meet”. Suggested to start the experiment at Policy Forum. We suggested to start with this experiment at ICANN86 instead, since there are no sessions with the Board at the policy forum * Likely the new ccnso website will go live mid December. ADMINISTRATIVE MATTERS & DECISIONS 13. Adoption Nomination process Board seat 11 Report For discussion and decision Joke: The Nomination Report is in your inboxes and posted on the Council wiki for this meeting. It contains details about the nomination, the results, link to the reference materials etc (guideline, candidate statement, recording Q&A etc). Two observations: * The ccNSO Board Seat Nomination guideline – in contrast to the ccNSO Council Election guideline - does not include explicit reference regarding “Eligibility to Nominate and Second”, and “Eligibility to Vote”. Furthermore, the ccNSO Council Election Guideline specifies that only the Representative from a ccNSO member will be able to nominate and second candidates to serve as a ccNSO Councillor. Recommendation : The Council is advised to request the Guideline Review Committee to verify if and how the ccNSO Guidelines should be adjusted, to ensure alignment across all nomination procedures. * As per ccNSO Council decision 219-02, if there is only one candidate, no election is required. The ccNSO Board Seat Nomination guideline – in contrast to the ccNSO Council Election guideline – requires elections, even if the seat goes uncontested. Recommendation: The Council is advised to request the Guideline Review Committee to verify if and how the ccNSO Guidelines should be adjusted, to ensure alignment across all nomination procedures. Upon adoption of the report, the nomination process will formally conclude, and Patricio Poblete will be nominated for ICANN Board Seat 11. Alejandra: we are not quorate. We will defer the decision to an online decision Bart: any questions regarding the resolution? Move? Pablo Second? Peter Councillors in favour, no reactions from Jiankang and Biyi. only green ticks Alejandra: thank you for staying with us for another term Patricio: thanks again! I hope to live up to the expectations Alejandra: i will send the note to ECA. this concludes the process Background The current term of Patricio Poblete, the ccNSO-nominated Director for ICANN Board Seat 11, will conclude at the ICANN87 Annual General Meeting in October 2026. To ensure sufficient time for due diligence and the bylaw requirements regarding appointments, the Council initiated the nomination process in July 2025. This timeline allows the community to engage with the candidate during a Question-and-Answer session at the ICANN84 Annual General Meeting in Dublin. Patricio Poblete was duly nominated, seconded, and accepted his nomination before the deadline, in full compliance with the applicable rules. In accordance with ccNSO Council decision 219-02, an election is not required when only one candidate is nominated. Draft Resolution Decision The ccNSO Council adopts the Board seat 11 Nomination Process report as proposed, including its recommendations, and formally nominates Patricio Poblete - the selected candidate - as outlined in Section 10.3(i) of the ICANN Bylaws. With this adoption, the Board Seat 11 Nomination Process is now closed. The Council congratulates Patricio on his nomination. The ccNSO Guidelines Review Committee (GRC) is requested to review the Board Nomination Process Guideline, taking into account the recommendations from the Nomination Process Manager. The secretariat is requested to publish this resolution as soon as possible and inform the GRC. The ccNSO Chair is requested to inform the Empowered Community Administration (ECA) and ICANN's Secretary of the nomination results. This decision takes effect upon publication of the resolution. 14. Progress Council selection process a. Update on election process Joke: The seats for the EU, LAC and NA regions are uncontested, so no elections will be held for those regions. A Q&A was held at ICANN84 Secondly, for the AP region: * since there are 2 nominees that accepted their nomination, an election needed to be held. A Q&A was held at ICANN84, voting started earlier this week, and closes on 9 December. Prior to ICANN84, the Emissaries from the AP region received a personalised heads up, as well as a heads up via the ccnso mailing list. The RO helped to spread the word. * New voting tool. All is working well. * To meet quorum, at least a majority of all Emissaries entitled to vote in the ICANN Geographic Region must have cast a vote. The ccNSO currently counts 58 members from the Asia/Australia/Pacific region, corresponding to 57 Territories, and therefore 57 Emissaries. To date, 12 Emissaries cast their vote. * Secretariat is in touch with the regional organisation and ICANN GSE to promote the vote, and where needed, to ensure the Emissary gets updated. Background Five ccNSO Council seats with terms ending in March 2026 opened for nominations from 9–30 September 2025, with nominees required to accept by 10 October 2025. The following candidates accepted their nominations: · AP: Boyoung Kim, Sami Mohamed Ali · EU: Chris Disspain · LAC: Alejandra Reynoso · NA: Charles Noir A candidate Q&A took place on 29 October 2025 during ICANN84. The seats for the EU, LAC and NA regions are uncontested, so no elections will be held for those regions, in accordance with the ccNSO Council Election Guideline. Elections for the AP region will be held post ICANN84. b. Update call for Nomination African region Informational Joke: · AF region: the sole nominee did not accept their nomination. · At ICANN84, Council decided to launch a new nomination process, which started last week, and closes 4 December. · One candidate has been nominated as per the guideline. The secondment was not submitted by the Representative of the ccTLD manager. Secretariat reached out to the Representative, to seek confirmation. After closure of the various nomination and election rounds, a report will be submitted to Council for consideration and eventually adoption. It will contain nomination and election details, including any issues and observations. Candidates takes their seat at the end of ICANN85 Pablo: regarding item a, Emissaries not voting Would it be helpful to reach out to RO’s? Joke: that is ongoing. Since prior to ICANN84. GSE also involved Background Five ccNSO Council seats will become vacant when current three-year terms end in March 2026. A call for nominations was launched in September 2025. However, the sole nominee from the African region did not accept, leaving that regional seat without an eligible candidate. As a result, the Council has initiated a new call for nominations specifically for the African region seat, following the ICANN Bylaws, the ccNSO Council Selection Guideline, and the Council-adopted timeline. New Nomination Timeline (Africa region only): · Opens: Thursday, 13 November 2025 at 00:01 UTC · Closes: Thursday, 4 December 2025 at 23:59 UTC 15. Appointment members, or chairs/vice chairs to committees or working groups, if any The Council needs to agree on appointment of various persons to external groups. · ccNSO Nominees to various external groups (https://docs.google.com/spreadsheets/d/1NdPoBTmQUVlPhMy1PsoZr6rUxUxHzRDQ/ed…) Alejandra: since we are not quorate, this is deferred to an online decision Draft resolution Decision The ccNSO Council appoints the following people to the respective roles as specified: · Members of the following committees, study groups or working groups: o Kristian Ørmen (.se), member of DASC o Hsuping Tang (.tw), member of DASC o Siphokazi Simandla (.za), member of IGLC The secretariat is requested to inform the leadership teams of the various working groups and committees and persons appointed and enable their participation in the respective teams. This resolution becomes effective upon publication. Move? Everton Second? Wafa Any questions? None Only green ticks, this has been approved Alejandra: welcome to the new volunteers. Our engagement efforts are working 16. Review Bylaw change Playbook For discussion and decision Alejandra: As you may recall the SO/AC chairs group finally received the first version of the Bylaw change Playbook just before the roundtable in Dublin, with a request to provide feedback. The Playbook was forwarded to you, and one of the action items for today’s meeting was to prepare a response which could be adopted at this meeting. First I want to handle the process and then deal with the content of the comment. The playbook was sent to the SO/AC chairs by Russ Weinstein just prior to the Dublin Roundtable with a request to provide feedback and comments. As this is not a formal process, suggest that I send the observation as an informal response to Russ. So no formal resolution is needed. Any questions or concerns? None. green ticks in zoom With respect to the content, let me introduce the document In preparing the response we looked at the Playbook and tried to understand the flow and timelines. We also tried to understand the roles and responsibilities of the various groups: community group, staff, board and the roles each of them played, including oversight. Finally we looked at the instances we have requested a Bylaw change, and why they did not result in a change. The proposed comment focuses on these instances. Some of these instances were: * Change of Article 18 in preparation of 1st IANA Function Review to adjust the composition of the IFRT, it was not acceptable to the board at that time, although the community supported the request to change. As a result the 1st IFR started almost a year too late. * Change of Article 10 membership of ccNSO, which was completed relatively smoothly * Suggestion in public comment to change frequency of IANA Function Review * Request to change Article 17: frequency of CSC effectiveness review, following recommendation of the 2nd CSC effectiveness review team in June 2023. (in process) * At the suggestion of the ccNSO request of 2nd IFR to change frequency of the IFRs (in process). Any questions on observations and questions raised on the playbook? None Alejandra: ok, will send it to Russ after this meeting, and see how it evolves SUBSTANTIVE MATTERS & DECISIONS None 17. Any Other Business (AOB) Alejandra: 3 items * Item 1. Closure world Cafe sessions: o joint GAC-ccNSO: GAC-ccNSo organizing have received summaries. They will be made available to broader community next week (published on ICANN84 schedule for future reference) Alejandra: was a request from the previous world cafe. Scribes took notes Bart: consolidated report sent to station hosts and scribes. Following their approval. o GRC Continuous Improvement Program session. Participants received the summaries per station GRC has taken on to further review, and details the criteria and indicators emerging from the session. To be presented in Mumbai. Alejandra: GRC Continuous Improvement Program session Participants received the summaries per station GRC has taken on to further review, and details the criteria and indicators emerging from the session. To be presented in Mumbai. Sean: we looked at practical ways to measure. We welcome feedback. How are people feeling? Measurement system, within world of KPIs. we will bring these together for you. As council members and community to see what a number means to the membership, to the people involved. How do we try to improve as an organisation. Significant change. Think you will enjoy the result. You have to be seen, to be doing, and the other way around Bart: qualitative and quantitative indicators. Joint effort that defines them. What is relevant for the stakeholders? * Item 2. Cooperation GNSO PDP DNS Abuse / Meeting with RySG o First: Note from Beth - Soon gNSO Council will have an updated Issues Report and Charter that reflects the Public Comments. o Suggestion not to participate as ccNSO in PDP (out of scope, and bandwidth). Inform individual ccTLD and check with DASC members whether they want to participate (not as DASC, not mandated) Second: could be the topic of a joint session organized by DASC and RySG DNS Abuse group. Alejandra: they invites us and DASC to participate in the PDP. my suggestions is to - like we always do with GNSO PDPs - to share it with individuals. ccNSO, not DASC, is mandated to do so. They can always collaborate and provide feedback Chris: that is fine. But should we at least consider? Given the topic of abuse, and given the cooperation. Should we consider a slightly different approach? Might be warranted in these circumstances. IDN fast track PDP: matter that crossed boundaries. Alejandra: people to join in their individual capacity. Not as ccNSO. Cooperation with RySG: DASC session at ICANN85 with RySG? Gather feedback from the ccTLD community during this session? Chris: that is fine. But this is a GNSO matter, not just RySG. testing, to make sure we cover all basis. The way the gTLD registries are mandated to deal with DNS abuse. Pivoting. Cross-community PDP. may have an effect on individual ccTLDs being pressured. Their own LIC to push them in future? So, is it sensible for the ccNSO to have a voice? This is an important set of PDPs coming up. Suspect they will have an effect on ccTLDs. Not pushing, but asking the question for us to consider this carefully Peter: I like thinking. Chris his suggestion to have a conversation? Useful. We get dragged into gTLD precedent. Often the GAC does not fully grasp the difference. We cannot just stick our heads in the sand. Having a conversation is good. When and where? Not sure. Mumbai might be too late Chris: Australia as an example. Following a new RyRr policy, the Australian gvt might say “you should be doing it in .au”. If the ccTLD does not have a voice in the gTLD policy setting, and that policy is being used to put pressure on the ccTLD back home, that is not good. Bart: this might be timely. There is a discussion in the GNSO on the issues report. Has not been launched yet. Invites will come later. Suggestion to involve leadership of DASC prior to the next council meeting. Have an informal conversation first. More extensive topic at the next Council meeting Alejandra: great idea. Also supported by Chris and Peter. First have that call. Open to all interested councillors. * Item 3, ICANN85 Block schedule We will be briefly discussing our blockschedule for ICANN85, as we will have only the upcoming 4 weeks to get ready. The secretariat has to submit the schedule into ICANN’s scheduling tool starting 5 January and be done by 16 January. Taking into account the seasonal break at the end of the year we as a community will have only 4 weeks (until 19 December) to plan the sessions. Joke: proposed high level block schedule. WG/C meetings over the weekend. Bart: either DASC or IGLC on Tuesday. DASC only, if there is no joint RySG-ccNSO DASC session on Wednesday Peter: WSIS+20? Bart: IGLC session on Tuesday. IGLC still to determine the need. Regarding the market trends: discussed by MPC. They wanted regional diverse ccTLD contributions and perspectives. How do ccTLDs deal with these trends? cross-regional , global function of the ccNSO Bart: does that work for you. Wed block 5? Chris: fine. Bart: council prep meeting on saturday, block 1 on council roles and responsibilities. Also discussion on chair and vice chair selection. Any concerns? Alejandra: i see no objections. 18. Next Council Meetings · 18 December 2025 | 18:00 UTC, Meeting 224 · 22 January 2026 | 12:00 UTC, Meeting 225 · 19 February 2026 | 21:00 UTC, Meeting 226 · 12 March 2026 | ICANN85 - Mumbai, Meeting 227 · 16 April 2026 | 12:00 UTC, Meeting 228 · 21 May 2026 | 18:00 UTC, Meeting 229 · 11 June 2026 | ICANN86 - Sevilla, Meeting 230 · 16 July 2026 | 12:00 UTC, Meeting 231 · 13 August 2026 | 21:00 UTC, Meeting 232 · 17 September 2026 | 12:00 UTC, Meeting 233 · 22 October 2026 | ICANN87 - Muscat, Meeting 234 · 19 November 2026 | 18:00 UTC, Meeting 235 · 17 December 2026 | 12:00 UTC, Meeting 236 19. Adjourn Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 0

November ccNSO Council Teleconference (223) | 20 November at 12:00 UTC
by ccNSO Calendar Nov. 20, 2025

Nov. 20, 2025

Meeting starts at top of the hour ***REMINDER*** Dear Council, The November ccNSO Council Teleconference (223) is scheduled for 20 November at 12:00 UTC. The agenda will be circulated prior to the call. Please find the call details below: Join Zoom Meeting https://icann.zoom.us/j/96095269567?pwd=aV3V56a07eWL5h3BHyvQRkALD7s7Ci.1 Meeting ID: 960 9526 9567 Passcode: ccNSO-0223 Wiki page: https://icann-community.atlassian.net/wiki/x/J4wlBg Thank you!

1 0

Output GRC Word Cafe developing criteria and indicators ccNSO Continuous Improvement Program
by Bart Boswinkel Nov. 20, 2025

Nov. 20, 2025

Dear all, On behalf of Sean, first, thank you for your interest in the ccNSO GRC World Café working session. In Dublin. Included you’ll find the outcome of the World Café discussions per principle/station of the conversations on developing criteria and indicators per principle. The outcome has been shared with the ccNSO GRC. The GRC will use this as basis for further design of the ccNSO CI Program. On behalf of Sean, thank you for participating and your contributions. Kind regards, Bart

1 0

November ccNSO Council Teleconference (223) | 20 November at 12:00 UTC
by ccNSO Calendar Nov. 20, 2025

Nov. 20, 2025

***REMINDER*** Dear Council, The November ccNSO Council Teleconference (223) is scheduled for 20 November at 12:00 UTC. The agenda will be circulated prior to the call. Please find the call details below: Join Zoom Meeting https://icann.zoom.us/j/96095269567?pwd=aV3V56a07eWL5h3BHyvQRkALD7s7Ci.1 Meeting ID: 960 9526 9567 Passcode: ccNSO-0223 Wiki page: https://icann-community.atlassian.net/wiki/x/J4wlBg Thank you!

4 3