March 2025 - Ccnso-council - lists.icann.org

September ccNSO Council Teleconference (221) | 18 September at 21:00 UTC
by ccNSO Calendar March 24, 2025

March 24, 2025

Dear Council, The September ccNSO Council Teleconference (221) is scheduled for 18 September at 21: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/93270112566?pwd=KdqqFEcYmnF3OgQUrtSMLWGE63HWYd.1 Meeting ID: 932 7011 2566 Passcode: ccNSO-0221 Wiki page: https://icann-community.atlassian.net/wiki/x/H4wlBg Thank you!

1 0

August ccNSO Council Teleconference (220) | 21 August at 12:00 UTC
by ccNSO Calendar March 24, 2025

March 24, 2025

Dear Council, The August ccNSO Council Teleconference (220) is scheduled for 21 August 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/95747045146?pwd=ILoiqnlevEnsaEdm9bbwhhwrwJ6pec.1 Meeting ID: 957 4704 5146 Passcode: ccNSO-0220 Wiki page: https://icann-community.atlassian.net/wiki/x/G4wlBg

1 0

July ccNSO Council Teleconference (219) | 17 July at 18:00 UTC
by ccNSO Calendar March 24, 2025

March 24, 2025

Dear Council, The July ccNSO Council Teleconference (219) is scheduled for 17 July at 18: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/94487607246?pwd=kyhimjuamFaul8rETFBpqiTEbRGqnP.1 Meeting ID: 944 8760 7246 Passcode: ccNSO-0219 Wiki page: https://icann-community.atlassian.net/wiki/x/F4wlBg

1 0

May ccNSO Council Teleconference (217) | 15 May at 12:00 UTC
by ccNSO Calendar March 24, 2025

March 24, 2025

Dear Council, The May ccNSO Council Teleconference (217) is scheduled for 15 May 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/94742071601?pwd=5bYDGW1ZUJNMdeLPbeOeoHmANjhWYl.1 Meeting ID: 947 4207 1601 Passcode: ccNSO-0217 Wiki page: https://icann-community.atlassian.net/wiki/x/D4wlBg

1 0

April ccNSO Council Teleconference (216) | 17 April at 21:00 UTC
by ccNSO Calendar March 24, 2025

March 24, 2025

Dear Council, The April ccNSO Council Teleconference (216) is scheduled for 17 April at 21: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/93623172289?pwd=V5uUIve1jBRLTAPjRMGdqcONKHko7V.1 Meeting ID: 936 2317 2289 Passcode: ccNSO-0216 Wiki page: https://icann-community.atlassian.net/wiki/x/C4wlBg

1 0

Rejection Action period ICANN's FY26-30 Strategic Plan
by Bart Boswinkel March 21, 2025

March 21, 2025

Dear members of the ccTLD Community, First, apologies for cross-posting. I am writing, in my capacity as the ccNSO Rejection Action Process Manager, to inform you that on 13 March 2025, the ICANN Board of Directors adopted the Strategic Plan for Fiscal Years 2026–2030. The resolution is available here<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…>. To view the plan, click here<https://www.icann.org/en/system/files/files/strategic-plan-2026-2030-13mar2…>. On 20 March 2025, the ccNSO, one of the Decisional Participants, received a notice from the ICANN Secretary under Section 22.5(b)(v) of the ICANN Bylaws. This notice initiated a 21‑day Rejection Action Petition Period for the community, closing on 11 April 2025 at 6.59 UTC Should you wish to submit a Rejection Action Petition concerning the adopted Operating Plan and Budget, please review Section 2 of Annex D<https://www.icann.org/resources/pages/governance/bylaws-en/#annexD> of the ICANN Bylaws for the mandatory requirements. Rejection Action Petitions must be submitted to the ccNSO role account (ccnso-petions(a)icann.org<mailto:ccnso-petions@icann.org>) by 06:59 UTC on 11 April 2025. Please be advised that per Annex D Section 2.2(a)(i)(A) the Rejection Action Petition must be: “…based on one or more significant issues that were specifically raised in the applicable public comment period(s) relating to perceived inconsistencies with the Mission, purpose and role set forth in ICANN's Articles of Incorporation and Bylaws, the global public interest, the needs of ICANN's stakeholders, financial stability, or other matter of concern to the community.” Please see also our internal ccNSO Guideline<https://ccnso.icann.org/about/guideline-rejection-actions-procedure-24may18…>: ccNSO Procedure for the Exercise of the Empowered Community's rights to Reject Specific Actions. According to this Guideline, the ccNSO will consider Rejection Action Petitions submitted by the following constituents: * ccTLD managers, * Individual(s) directly related to a ccTLD manager, * ccNSO working groups or committees mandated to submit such a pe//on, * Regional ccTLD organisations (as defined in sec/on 10.5 of the ICANN Bylaws), * the ccNSO Council. All relevant information will be published at: https://community.icann.org/display/ccnsowkspc/Rejection+actions Kind Regards, on behalf of Sean Copeland, ccNSO Rejection Action Process Manager, Bart Boswinkel ccNSO secretariat

1 0

ccNSO information for NomCom - draft letter to review
by Jordan Carter March 20, 2025

March 20, 2025

Hi all This is a note and a short letter to read for discussion at Thursday’s council meeting. Coming up to this icann meeting, the NomCom asked Alejandra, Biyi and I to meet with them to talk about the role description for the appointees they select as Council members. The idea is to answer any queries NomCom may have, and help them understand a bit about how the role works in practice. We joined NomCom on Saturday for a half hour. The conversation identified some areas that they asked us to communicate to them in writing. Here’s the draft, please feel welcome to add any comments or questions or discuss it by email. https://docs.google.com/document/d/10T-sfeZUqqhbPO8D8mWsclZMCt3TlobqVt4b2n9… Cheers Jordan _______ Jordan Carter jordan.carter(a)auda.org.au<mailto:jordan.carter@auda.org.au> +61 417 243 647

3 4

REMINDER | Share Your Feedback on the ccNSO Members Meeting at ICANN82: Help Shape Future ccNSO Meetings
by Joke Braeken March 19, 2025

March 19, 2025

Dear All, Here is a reminder to please complete the ICANN82 satisfaction survey. Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Read more about the ccNSO at ICANN82: https://bit.ly/4h4E8Ot From: Joke Braeken <joke.braeken(a)icann.org> Date: Thursday, 13 March 2025 at 00:50 To: ccnso-council <ccnso-council(a)icann.org>, "ccnso-members(a)icann.org" <ccnso-members(a)icann.org>, "ccTLDcommunity(a)cctld-managers.org" <ccTLDcommunity(a)cctld-managers.org> Subject: Share Your Feedback on the ccNSO Members Meeting at ICANN82: Help Shape Future ccNSO Meetings Dear All, We hope the ICANN82 ccNSO Members Meeting was a rewarding experience for you, whether you joined us in person or remotely. The ccNSO Meetings Programme Committee (MPC) values your input and is seeking feedback on this ccNSO Members Meeting. Which sessions did you find particularly engaging? How can we improve? What topics would you like to see addressed at the ICANN83 Policy Forum? Your feedback is crucial in shaping future ccNSO Members Meetings. How to provide your feedback: https://www.surveymonkey.com/r/WJDNQFN The survey will be open until Tuesday, 25 March 2025, 23:59 UTC. Thank you for sharing your insights! Best regards. Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Read more about the ccNSO at ICANN82: https://bit.ly/4h4E8Ot

1 0

NOTES | ccNSO Council meeting 215 | 13 Feb 2025 at ICANN82
by Joke Braeken March 13, 2025

March 13, 2025

ccNSO Council meeting 215 Thursday 13 February 2025 ICANN82 Background and supporting documents * Council workspace for this meeting: https://icann-community.atlassian.net/wiki/x/-4slBg * ccNSO correspondence: statements and responses: https://ccnso.icann.org/en/about/statements.htm Agenda Welcome by Alejandra Reynoso Council members are asked to add “Council” to their names in Zoom We are quorate Remote: Ali, Wafa, Jiankang Any SOI updates? None Any AOB? Alejandra: e-mail from ICANN org. We will discuss in AOB ADMINISTRATIVE MATTERS 1. Relevant Correspondence No relevant correspondence 2. Minutes & Action Items a. Minutes Meeting 214: not yet circulated You may expect the minutes soon. Action items as taken from the notes b. Action Items (preliminary, as taken from the meeting notes. Pending distribution and approval meeting minutes) · Action item 214-01 (ongoing) GRC to prepare a draft response to the request for comments on the Proposed Updates to the Operating Standards for Specific Reviews. · Action item 214-02 (ongoing) Secretariat and Peter Koch to draft input for Council’s discussion and consideration, regarding input for the work by the RSS GWG. Skipping to item 5 3. Intermeeting Decisions (since meeting 214, February 2025) a. Adoption Board Seat 12 Nomination Report and formal nomination by Council of Byron Holland to Board Seat 12 4. Intermeeting Decisions Triage Committee None UPDATES 5. Update ECA, IFRT & CSC (from the ICANN82 sessions) CSC: Need for alternate to replace Nicklas Pousette for remainder of term (until 1 October 2015) Suggested action item: Chair and secretariat to propose alternate for formal appointment by the Council Alejandra: need to find replacement for an alternate on the CSC Current members (Federico and Pablo), to seek an alternate for the remaining term of Nicklas, until start of October. Role: CSC shadow, alternate. In case one of the members is not avalaible 6. Update Working Groups (from the ICANN82 sessions) a. ccPDP3-Review Mechanism - Dormant b. ccPDP4-IDN - Dormant c. DASC d. FIN2 WG e. GRC f. IGLC g. MPC h. OMC i. PGA WG j. SOPC k. Tech WG l. TLD-OPS SC m. Triage Committee n. UAC o. CIP-CCG p. Planning Prioritization Process group q. RZERC r. RSS GWG s. ICANN How We Meet Group 7. Update Liaisons (written updates) Written updates - if any - are published on the wiki space for this meeting. a. Update ccNSO Liaison to ALAC b. Update ccNSO Liaison to GNSO Council c. Update ccNSO Liaison to UASG 8. Update ccNSO Website redesign No meeting since Council meeting 214 9. Progress Board Consideration ccPDP4-IDN and ccPDP3-RM Update taken from the meeting ccPDP3: see update from Becky during Q&A. board consideration by or at icann83 ccPDP4: proceeding well No questions or comments 10. Update Chair, Vice-chairs, Councillors, Regional Organisations and Secretariat a. pre-ICANN82 SO/AC Round Tabl The “How we meet” process and Reviews were the major topics. As you may note these two topics are on the agenda, and we will discuss in more detail later on the agenda. Additional Meeting: Biyi, Jordan and I met with ICANN org staff this week on the retirement policy. I’ll address this in more detail under the AOB. We also met with other SO/AC on the next steps Pilot Holistic Review, we will discuss this further under item 17. Leadership and OMC met with newcomers. We intend to turn this into a recurring (informal) event. It was a great opportunity for us to learn from them how we can improve the onboarding process and build a mentoring program. Meeting with RySG to find common topics of interest, and gather feedback from respective communities. Suggestion to hold a session at ICANN83 Peter: * IFRT public comment. ccNSO represented by Olga, Sami, myself. 40 day comment period starting end March. March 20th. Alejandra: action item for us to draft a statement * Root server system governance WG. Council to look at suggestions and ccTLD representation Biyi: more engagement with fellows and newcomers needed. Not just OMC, but all of us. Pablo: yesterday meeting in LAC space. Hope for more engagement with/by ccTLDs from caribbean region b. Update Councillors from various sessions they attended during ICANN82 11. Update Council 360 Review Suggestion to extend deadline Alejandra: only 6 provided feedback. Minimum 10 needed Draft Resolution Background According to the ccNSO Council 360 feedback process (https://ccnso.icann.org/sites/default/files/field-attached/ccnso-council-36…) the review process should be open two-weeks, and at least 10 Councillors should have responded during this period. During the first 2025 process, which ran from Tuesday 11 February 2025 to 3 March 2025, only 6 Councillors responded, and hence the quorum was not met. Decision The ccNSO Council extends the 360 review process until 21 March 2023. The results will be shared with the Councillors. The results will be shared with the individual Councillors starting 25 March 2025. Alejandra: Assuming they have not done so, and although Nick and Demi will step down at the end of this meeting, I suggest that both of them do provide their feedback as if they are still Council. Move: Olga Second: Stephen Any questions regarding the resolution? Biyi: please send reminder with links to the survey Bart: will do Peter abstains Other councillors approve, resolution is adopted ADMINISTRATIVE MATTERS & DECISIONS 12. Roles and Responsibilities Councillors Alejandra: Before moving into the formal part of this section I want to thank all of you for an amazing year. A lot of what we have achieved since March 2024 is captured in our annual achievement report. However that report does not do justice to your contributions and what we collectively have achieved and our collegiality. I think this is reflected in how we handled the assignment of roles and responsibilities for the upcoming year. We will formally adopt the assignments under item c of this agenda item. Bart explains the process. First chair election. Nick will ask for a nomination/secondments. Candidates whether they accept. A secret vote only if more than 2 candidate Chairs and vice chairs need to reside in different icann regions, to ensure geo diversity. According to the Guideline: ccNSO Council Roles and Responsibilities (https://ccnso.icann.org/sites/default/files/field-attached/roles-responsibi…) the ccNSO Council elects is chair and vice-chairs annually, at the first ICANN meeting of the calendar year. The chair will be elected first and the vice-chairs selected afterwards. The section of the meeting where the Chair gets elected shall be chaired by Vice-Chair who is not standing for chair. According to the Guideline the chair and vice-chairs need to be from different ICANN regions. Chair election After nomination and secondment, a candidate has to accept her/his nomination. If only one candidate stands, the Councillors will appoint the candidate by a public vote. If two or more candidates have accepted the nomination, the Councillors will elect the Chair by a secret vote. Vice-Chair elections To be nominated as vice-chairs the following procedural requirements are relevant: The candidates should not be from the same ICANN regions nor from the Chair’s ICANN Geographic region, Has been nominated and seconded, and has accepted her/his nomination. If there are as many valid candidates as there are open Vice-chair seats and each candidate is from a different ICANN Geographic Region, the Vice-chairs will be appointed by a public vote. a. Election of the ccNSO Council Chair The ccNSO Council is expected to elect its chair from its members at this meeting. Draft Resolution Decision In accordance with the procedure to select its chair and vice-chairs, as included in the Guideline ccNSO Roles and Responsibilities<https://ccnso.icann.org/sites/default/files/field-attached/roles-responsibi…> adopted on 26 February 2018, [insert name] was duly nominated and seconded as candidate Chair of the ccNSO, and accepted her /his nomination and the ccNSO Council elects [insert name] to serve as its Chair starting at the end of the ICANN82 until the end of ICANN85. The secretariat is requested to inform the ICANN secretary accordingly and post an announcement on the ccNSO Website. This resolution becomes effective upon publication. Nick: thanks for explanation Asking for nominations for the chair Pablo: i nominate Alejandra Reynoso Seconded by Demi Any other nominations? None Do you accept? Alejandra: yes Nick: thank you and congratulations Alejandra: LAC region b. Election of the ccNSO Council vice-chairs The ccNSO Council is expected to elect its vice- chairs from its members at this meeting. Draft Resolution Decision In accordance with the procedure to select its chair and vice-chairs, as included in the Guideline ccNSO Roles and Responsibilities<https://ccnso.icann.org/sites/default/files/field-attached/roles-responsibi…> adopted on 26 February 2018, [insert names] were duly nominated and seconded, and accepted their nominations. It is noted that the Chair, and Vice-Chairs are all residing in different ICANN regions. The ccNSO Council elects [insert names ] to serve as its Vice-Chairs starting at the end of the ICANN82 meeting until the end of the ICANN85 meeting. The secretariat is requested to inform the ICANN secretary accordingly and post an announcement on the ccNSO Website. This resolution becomes effective upon publication. Nominations for Vice chair Molehe: i nominate Biyi Second: pablo Biyi: i accept Other nominations? There are 2 vice chair roles Sean: i nominate Jordan Chris: second Jordan: i accept Further nominations? None Thank you all Alejandra: thank you. Honour to do this Regarding the process: all clear? Bart: we will add the names to the resolution. Jordan: quick reflection. 3 of us have a good dynamic. Pleasure to work with. Enjoy Alejandra’s leadership style Biyi: alejandra knows how to make you work ;-) c. Adoption of Assignment of roles and responsibilities of Council members By adopting the overview of roles and responsibilities of Councillors, individual Councillors are appointed to the various committees and liaison roles. The overview was provided on 12 March 2025. Draft Resolution Decision The ccNSO Council adopts the March 2025 overview of roles and responsibilities and their assignment to Councillors, including those of the Council Chair and Vice-Chair as decided under a. and b. above. The secretariat is requested to publish this resolution and the overview on the ccNSO website as soon as possible. This resolution becomes effective upon publication. Alejandra: We have assigned roles and responsibilities last Sunday. The overview was circulated. By adopting the overview of roles and responsibilities of Councillors, individual Councillors are appointed to the various committees and liaison roles. The overview was provided on 12 March 2025. Move? Jenifer Second? Chris Any questions regarding the resolution? None Green ticks Adopted. Alejandra: working with Jordan and Biyi is smooth. Happy to continue one extra year. 13. Blueprint Review Process ccNSO Working Groups and Committees Draft Resolution Background After the successful conclusion (January 2025) of the review of the DNS Abuse Standing Committee (DASC), the Council requested the chair of the Council and chair of the GRC to document the method that was used to review the effectiveness and efficiency of the DASC. The intention was that the method will be used to review the purpose, effectiveness and efficiency of other ccNSO Committees and long standing working groups, which are subject to a regular review. According to their charters/ terms of reference, the following committees will need to be reviewed over time: · Meeting Program Committee (MPC), once every 3 years, starting November 2022 · Internet Governance Liaison Committee (IGLC), once every 2 years, starting March 2023 · Universal Acceptance Committee (UAC), every 2 years, starting July 2023 · Strategic and Operational Planning Standing Committee (SOPC), once every 3 years, starting August 2022 · Guideline Review Committee (GRC), once every 2 years, starting February 2022 · TLD-Opc Steering Committee, once every 2 years, starting July 2017 · Technical Working Group, once every 3 years, starting July 2022 Decision The ccNSO Council adopts the Template/ Blueprint for review. The ccNSO Chair and secretariat are requested to develop a schedule and timeline for review of the various groups, after consulting the various committees and taking into account the workload to conduct a review and need for a review. The schedule and timeline are expected by meeting 216. This would allow the Council to launch a review well before the Prague meeting (ICANN83). The secretariat is requested to publish this resolution as soon as possible. This resolution becomes effective 7 days after publication. The chair is requested to inform the various working groups as soon as possible after the resolution becomes effective. Alejandra: After the successful conclusion of the review of the DNS Abuse Standing Committee (DASC) in January this year, the Council requested the chair of the Council and chair of the GRC to document the method that was used to review the effectiveness and efficiency of the DASC. The intention was that the method will be used to review the purpose, effectiveness and efficiency of other ccNSO Committees and long standing working groups. The document was shared with you a few days ago. I also want to alert you to the overview of the reviews, in particular to the aggregate effect. When looking at a review from an individual committee perspective, it makes sense to do a review once every 2 or 3 years. However if you combine all the reviews, we are constantly reviewing the effectiveness and efficiency of committees. With this in mind we suggest that before embarking on reviews, we prioritize the reviews, and devise a plan to do a maximum 2 reviews per year. Move? Stephen Second? Ali Any questions regarding resolution? None Green marks in zoom, adopted 14. Adoption Election Time Special European region selection and appointment Council election process manager Draft Resolution Background In February, Nicklas Pousette, the Councillor-elect, from the European Region announced that he will not start his term on the ccNSO Council starting at the end of ICANN83 (13 March 2025). To fill this anticipated vacancy as soon as possible, the Council will launch an extraordinary European Region selection process, and therefore has to adopt a timeline and appoint the Selection process manager. The proposed timeline was circulated separately. The main dates are: · Nomination period: 26 March - 22 April · Election, if needed: 30 April - 21 May 2025 · Announcement 23 May 2025 In addition the Council needs to appoint the Election Process Manager Decision The ccNSO Council adopts the proposed timeline for the extraordinary ccNSO Council European election. The ccNSO Council appoints Joke Braeken, ccNSO secretariat, as Election Process Manager. The secretariat is requested to publish this resolution as soon as possible. The decision becomes effective upon publication. Alejandra: Nicklas Pousette, councillor Elect EU region. His term was supposed to start at conclusion of ICANN82. He resigned Other councillors from the EU region wanted to have the seat filled asap. Not wait for the review of the council selection guideline Move? Peter Seconded? Wafa No questions Green ticks in zoom. adopted. 15. Appointment members or chairs/vice chairs to committees and working groups, if any Draft Resolution Decision The following persons are appointed: · Alishah Shariff to the IGLC · Ann Ibrahim (InternetNZ) to the UAC The secretariat is requested to inform the appointees and chairs of the committees accordingly. The secretariat is also requested to publish this resolution as soon as feasible. This resolution becomes effective upon publication. Joke: typo in Anne’s name Move? Olga Second? Jenifer All in favour SUBSTANTIVE MATTERS & DECISIONS 16. Update “How we meet” process and next steps For discussion Jordan: concerns regarding icann’s presentation. It was straightforward by the community. That it was suggestions for cost-savings. ccTLD managers to offer their thoughts, through the public comments. Ccnso session, aggregate comments from the ccTLD community Alejandra: molehe and Jodi to review outcomes of the session We will prepare a statement 17. Update Pilot Holistic Review and CIP and next steps For discussion Any action required by the Council? Chris: board weas thinking to review this. Co-chairs of PHR had conversations with Board and community members. Meeting with SO/AC chairs. And Cherlyn LOE. chair ATRT3. Way to deal with PHR, provide that the community can accept the premises on which the review is going to be build. SO/AC chairs and Board effectiveness community. As long as you accept what we will do, we will build it. Subject to all accepting it, and subject to the board accepting to continue. Tripti mentioned a few times: go back to drawing board. Stop what we are doing. Why do we do this. ATRT4. Unanimity, waste of time. At-large mostly thinks it is not a waste of time. Alejandra: occurred to me. Write to board first? Chris: what we say to them will have some effect to what they decide. We need to write to them first. Alejandra: we will wait for the letter to arrive and will reply Alejandra: regarding ATRT4. Should we do sth? It was deferred to april, discussed in the reviews. Cascading effect it has. Chris: no harm to draft a note to the board. We need to write them: do you intent to move forward with ATRT4? Alejandra: and all other reviews? Chris: board might have sent it already by the time we decide Jordan: entire review system is broken. Intended as sth useful. Need to look as icann system as a whole. Holistic review. All other reviews are not in scope. Pause all reviews? Incl PHR? Stop all bylaw reviews? Appoint a design team to design a good review process? Chris: yes. Sort of what Tripti said. When Fadhi and Larry agreed what the review should be about. NTIA to plug topics out. If we wanted to write to board and say that, it would be helpful. Right path forward. Chris, Jordan, Sean, Peter volunteered to drafting team Peter: not all bylaw reviews are equal. Be careful. Do not throw away the baby with the bathwater Chris: by next council meeting Bart: mid April 18. Any Other Business (AOB) Alejandra: Retirement policy: we have just received a note from ICANN. I have shared this to the council, and I suggest that we do not respond directly, but by our next council meeting in April at the latest. From my perspective this request ends all other conversations we had and we only focus on the response. I also urge everyone not to respond to any questions regarding .su case in your capacity as Councillor, and note that the retirement working group was formally closed at our 22 September 2022 meeting. May I ask Jordan, Biyi, Chris and Peter, together with the secretariat to prepare a response, to be circulated to the list. They agree Questions, comments? None AOB? none 19. Next Council Meetings * 17 April 2025 | 21:00 UTC, Meeting 216 * 15 May 2025 | 12:00 UTC, Meeting 217 * 12 June 2025 | time TBC, Meeting 218 (ICANN83) * 17 July 2025 | 18:00 UTC, Meeting 219 * 21 August 2025 | 12:00 UTC (Meeting 220) * 18 September 2025 | 21:00 UTC (Meeting 221) * 30 October 2025 | time TBC, Meeting 222 (ICANN84) * 20 November 2025 | 12:00 UTC, Meeting 223 * 18 December 2025 | 18:00 UTC, Meeting 224 20. Thank you and Adjourn * Congratulation to Stephen Deerhake for winning the Community Excellence Award * Thank you to .us for the outstanding ccNSO Cocktail. * Thank you Demi Getschko * Thank you Nick Wenban-Smith, appreciation for willingness to continue to contribute to the work of the ccNSO (DASC) * Welcome Everton T. Rodriguez, as incoming LAC region Councillor. * Thank you to the volunteers for organising sessions * Thank you to secretariat, in-room staff and interpreters * Thank you for participating either in person or remotely. Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Read more about the ccNSO at ICANN82: https://bit.ly/4h4E8Ot

1 0

Fwd: New clarification request on ccTLD Retirement Policy
by Alejandra Reynoso Barral March 13, 2025

March 13, 2025

Dear Councillors Please find below correspondence from Kim Davies. Best regards, Alejandra ---------- Forwarded message --------- From: Kim Davies <kim.davies(a)iana.org> Date: Thu, Mar 13, 2025, 10:33 Subject: New clarification request on ccTLD Retirement Policy To: Alejandra Reynoso Barral <alejandra.reynoso(a)gmail.com> Cc: Becky Burr <becky.burr(a)board.icann.org>, Sam Eisner < Samantha.Eisner(a)icann.org> Dear Alejandra: We appreciate your willingness to discuss the ccNSO Retirement Policy earlier this week, and wanted to put a new request for clarification in writing. Section 3 of the ccNSO Retirement Policy states that the policy applies to all entries in the Root Zone database that are identified as ccTLD and subject to a Trigger. For 2-letter ASCII ccTLDs, there are two potential Triggering Events identified in the Retirement Policy. We understand the first trigger applies to 2 letter ascii ccTLDs that correspond to an ISO 3166-1 Alpha-2 Code Element. We further understand that a Triggering Event occurs when the corresponding Alpha-2 Code Element is deleted from the ISO 3166-1 Standard by the ISO 3166-1 Maintenance Agency (“ISO 3166/MA”). See Retirement Policy Section 3, p. 15. To break this down a bit, the language suggests that a “Triggering Event” occurs when: (i) an ascii entry identified as a ccTLD in the Root Zone database (ii) that corresponds to any ISO 3166-1 Alpha 2 Code Element (iii) is deleted from the ISO 3166-1 standard by the ISO 3166-1 Maintenance Agency. Further, based on the ISO 3166-1 Maintenance Organization’s website, it appears that the Alpha-2 Code Elements include, among others, “officially assigned code elements,” “unassigned code elements,” “transitionally assigned code elements,” and “exceptionally reserved code elements.” Under this interpretation, a ccTLD corresponding to any ISO 3166-1 Alpha-2 code element would never be subject to retirement until it has been fully deleted from anywhere within the ISO 3166-1 Standard, which incorporates unassigned codes, Reserved Codes, Exceptionally Reserved Codes, etc. ( https://www.iso.org/glossary-for-iso-3166.html [iso.org] <https://urldefense.com/v3/__https:/www.iso.org/glossary-for-iso-3166.html__…> )? Can the ccNSO confirm that this is the correct interpretation of the ccNSO Retirement Policy? If we have misunderstood the intent of the Retirement Policy, would it be possible for the ccNSO to clarify the circumstances under which a Triggering Event specified in item 1 above would occur? Kindest regards, kim Kim Davies VP, IANA Services, ICANN President, PTI

2 1