Dear all, I hope you are all doing well. This report is divided into two main sections: The first part includes a few updates I’d like to highlight regarding Working Groups and Committees, and the second part is a summary of the last ccNSO Council Meeting held on Thursday, April 17th. *AGENDA* <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/99711461/ALA...> <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/99711461/ALAC+Liaison+to+the+ccNSO+Reports?preview=/99711461/216236033/AGENDA%20%20_%20ccNSO%20Council%20Meeting%20216%20_%2017%20April%202025.pdf>*and DOCUMENTS* <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/99711461/ALA...> <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/99711461/ALA...> *MARCH* <https://ccnso.icann.org/en/about/council/decisions-resolutions/2025> <https://ccnso.icann.org/en/about/council/decisions-resolutions/2025>*2025* <https://ccnso.icann.org/en/about/council/decisions-resolutions/2025> <https://ccnso.icann.org/en/about/council/decisions-resolutions/2025> *RESOLUTIONS* <https://ccnso.icann.org/en/about/council/decisions-resolutions/2025> <https://ccnso.icann.org/en/about/council/decisions-resolutions/2025> *Statements and Responses* <https://ccnso.icann.org/en/about/statements.htm> <https://ccnso.icann.org/en/about/statements.htm> *LIAISONS REPORTS * Report ccNSO Liaison to GNSO <https://icann-community.atlassian.net/wiki/spaces/ccNSOCWS/pages/103123979/1...> <https://icann-community.atlassian.net/wiki/spaces/ccNSOCWS/pages/103123979/1...> Report ccNSO Liaison to UASG <https://icann-community.atlassian.net/wiki/spaces/ccNSOCWS/pages/103123979/1...> <https://icann-community.atlassian.net/wiki/spaces/ccNSOCWS/pages/103123979/1...> *UPDATES on Working Groups and Committees * *DASC* <https://icann-community.atlassian.net/wiki/spaces/ccnsowkspc/pages/108411197...> <https://icann-community.atlassian.net/wiki/spaces/ccnsowkspc/pages/108411197/DNS+Abuse+Standing+Committee+DASC>– DNS Abuse Standing Committee The group checked in on a few ongoing items—like reminders about the repository and the survey subgroup taking a break until 2026. Most of the meeting focused on follow-up from ICANN82, with a lot of interest in tackling *online financial fraud and scams*. There’s talk of turning it into a broader community initiative, starting in Prague and maybe continuing in Oman. Planning also kicked off for a DASC session on AI at ICANN83, with a call for volunteers and a few prep meetings lined up. *PGA WG* <https://icann-community.atlassian.net/wiki/spaces/ccnsowkspc/pages/108415223...> <https://icann-community.atlassian.net/wiki/spaces/ccnsowkspc/pages/108415223/Policy+Gap+Analysis+Working+Group+PGA+WG>– Policy Gap Analysis Working Group Final Report PGA WG (draft) https://docs.google.com/document/d/1ouZnDqzikDxnuhlz5VPw0uWvqdCxX2Giy5mEGN4c... <https://docs.google.com/document/d/1ouZnDqzikDxnuhlz5VPw0uWvqdCxX2Giy5mEGN4c...> /edit?tab=t.0#heading=h.v6zxp4ty30x2 <https://docs.google.com/document/d/1ouZnDqzikDxnuhlz5VPw0uWvqdCxX2Giy5mEGN4c...> <https://docs.google.com/document/d/1ouZnDqzikDxnuhlz5VPw0uWvqdCxX2Giy5mEGN4c...> During the last PGA WG meeting (April 15th.), the draft final report <https://docs.google.com/document/d/1ouZnDqzikDxnuhlz5VPw0uWvqdCxX2Giy5mEGN4c...> <https://docs.google.com/document/d/1ouZnDqzikDxnuhlz5VPw0uWvqdCxX2Giy5mEGN4cW_A/edit?tab=t.0#heading=h.v6zxp4ty30x2>was introduced, with the suggestion to include it as Annex B to the full report, and Annex A containing the main document. There was a discussion on whether to include a reference to the latest letter on the retirement policy, as well as outcomes from conversations with ICANN org, the board caucus, and the drafting committee. No additional comments were made regarding the draft recommendation to Council. The group emphasized keeping recommendations concise, suggesting not to delve into too much detail, and advised using the experience from the .lb case for future scenarios. The .lb case serves as an important reference point for understanding the challenges faced by certain domain organizations, particularly regarding their governance and policy discussions. By using this case, the group hopes to learn from past experiences and better structure future recommendations. After consultation, 2 identified recommendations: *Recommendation 1: * *Overview policies, related guidance, and practices relevant for ccTLDs * The ccNSO Council is recommended to adopt the Overview of policies, related guidance, and practices relevant to ccTLDs as presented. This Overview is intended to inform ccTLD Managers and other stakeholders of the key elements that form the framework for how ICANN/PTI and ccTLDs relate to each other and may structure their relationship. After adoption, the ccNSO Council should keep the document up to date by amending the overview: - Each time a new policy arising from a PDP is submitted to or adopted by the ICANN Board - Each time the Council is informed of any other guidance, interpretation or practice. For avoidance of doubt, the overview does not replace, amend, supersede or change the interpretation of any original documentation. *Recommendation 2: **Study Groups IANA Public Records and Disaster Recovery* Following community consultation, the working group recommends that the ccNSO Council establish Study Groups for each of the identified topics, starting with two: IANA Public Records and IANA’s Role in Disaster Recovery. The working group further recommends that the Council determine the order in which the remaining four topics are to be addressed, in consultation with the community. This prioritization should take place once one of the two initial Study Groups is nearing completion of its work. *Disaster recovery* Generally, disaster recovery for a ccTLD is considered wholly the responsibility for the ccTLD manager and its local community to address. However, when it isn’t addressed, the parties often look to IANA for mechanisms to address it, and IANA is expected to do what it reasonably can to address threats to the operation of a ccTLD. What, if any, requirements should be established around disaster recovery and/or the ability to sustain ongoing operations of the domain in the case of disaster or non-compliance with global policies? Another area of disaster recovery is where ccTLD managers have sought to make private arrangements with IANA on special procedures to perform in such emergencies. *IGLC* <https://icann-community.atlassian.net/wiki/spaces/ccnsowkspc/pages/108404474...> <https://icann-community.atlassian.net/wiki/spaces/ccnsowkspc/pages/108404474/Internet+Governance+Liaison+Committee+IGLC>– Internet Governance Liaison Committee The group is preparing a session for ICANN83 on the *Future of Internet Governance*. The session will explore how the principles established in the WSIS process have been implemented over the past two decades and the specific ways in which ccTLDs have contributed to this implementation, through their engagement in national and regional IGFs. Also, the group introduced the new working plan for 2025. <https://docs.google.com/document/d/1DGqqze3TWT0oLZv--gkRMBIAPZtysZ7oaJ0pP3PP...> <https://docs.google.com/document/d/1DGqqze3TWT0oLZv--gkRMBIAPZtysZ7oaJ0pP3PP...> *How we Meet * There were 3 sessions during ICANN82 regarding this topic: 1. ICANN82 Prep Week session <https://sched.co/1udkH> https://sched.co/1udkH <https://sched.co/1udkH> 2. ICANN82 Plenary session <https://sched.co/1vpaT> https://sched.co/1vpaT <https://sched.co/1vpaT> 3. ICANN82 ccNSO Members Meeting <https://sched.co/1vpcE> https://sched.co/1vpcE <https://sched.co/1vpcE> The ccNSO Council is planning to provide feedback to this public comment proceeding. There was a special meeting on April 16th. about this topic and there is a small group working in a draft document. Summary of ccNSO Council Meeting 216 – 17th. April 2025 *Correspondence and Intermeeting Decisions: * • Several important communications were reviewed: o A *request for clarification* was received from *Kim Davies* (VP of IANA Services & President of PTI) regarding the *ccTLD Retirement Policy*. The Council responded to the specific question, and any further steps now rest with ICANN Org. o A *letter from the co-chairs of the Pilot Holistic Review (PHR)* was acknowledged. o A letter was sent to the *Empowered Community Administration (ECA)* confirming the appointment of *Alejandra Reynoso* to the ECA. o Another letter was addressed to the *ICANN Board Chair*, touching on reviews and related governance matters. *Intermeeting Council Decisions (since Meeting 215, March 2025):* o Adoption of a letter *to the NomCom*, providing additional considerations for the selection of future ccNSO Council appointees. o Adoption of a letter *clarifying the scope of trigger events in the retirement policy*, responding to Kim Davies’ inquiry. o Adoption of a letter *to the ICANN Board*, discussing next steps on the *Pilot Holistic Review (PHR)*, *ATRT4*, and broader review frameworks. o These decisions were made between formal meetings and documented for transparency. No objections or additional decisions were raised during the meeting. • The *Triage Committee* reported *no intermeeting decisions* for this period. *Action Items: * • Most action items from meetings 214 and 215 were completed, including appointments, survey reminders, and procedural communications. • Ongoing items include: o Preparation of Council comments for the *IFRT2 consultation*. o Finalization of a response to the *“How We Meet”* public comment process. *Updates: * • Written updates on *ECA, IFRT, CSC*, liaison roles, and working groups were noted. • Progress continues on the *ccNSO website redesign*, with a high-level timeline expected in the next month. Council acknowledged volunteer contributions as vital to this process. • The leadership team met with the ICANN CEO to raise issues regarding the *Playbook*, *bylaw changes*, and the need to defer the *third CSC review*, pending GNSO alignment. *Council 360 Review: * Despite reminders and extended deadlines, the review process did not meet quorum. The Council will revisit whether to continue with the process, considering its usefulness but low participation. *Special Council Election (European Region): * A call for nominations was reopened due to a February resignation. *Nigel Roberts* was nominated and accepted, and as there were no competing candidates, he will be seated without an election. A Q&A is scheduled for *29 April*. *Effectiveness Reviews of Working Groups and Committees:* • A schedule limiting committee/working group reviews to *two per year* was adopted, balancing effectiveness with council workload. • The first group to undergo review under this approach will be the *MPC*, with terms of reference to be drafted before the next meeting. A call for volunteers is open, excluding active MPC members. *Appointments:* Several new members were welcomed into key groups: *IGLC*: Pablo Rodríguez (.pr) *SOPC*: Frank Ogochukwu (.ng) *U**AC*: Andrew Lewela (.ke), Frank Ogochukwu (.ng) *GRC*: Erdem Bayrak (.tr), Francis Alaneme (.ng), Patrick Nyongeza Sungura (.tz), Nicholas Lisse (.na) *DASC*: Vadim Mikhaylov (.ru), Francis Alaneme (.ng), Igor Mkrtumyan (.am),Khaled Khelifi (.tn), Landi Ahmed (.ke), Jake Vincet (.uk), Harsha Saparamadu (.lk), Peter Koch (.de) *CSC Alternate*: Erwin Lansing (.dk) *"How We Meet" Process: * A response to the draft report is being prepared by a team. Aiming for a *1 May* draft. The Council noted the usefulness of a preparatory call held the day prior. *PHR and CIP Letter: * The *PHR/CIP* response letter was already sent to the ICANN Board. No further input or objections were noted. *ICANN83 Planning: * • Meetings are set from *Monday to Thursday*, starting with *Tech Day*. All sessions will be held in the *ccNSO meeting room*, except the Council meeting on Thursday, which will use a *smaller U-shaped room* for better engagement. • A *casual welcome session for newcomers* is also planned. • Planning is underway for a *joint session with the RySG* (Registries Stakeholder Group), aiming to foster dialogue on shared goals, avoid narrow focus on committees, and instead explore thematic cooperation. If you have any questions or would like more details on any of the topics mentioned, feel free to reach out—I’ll be happy to provide more information. Thank you for taking the time to read through the update. See you in the ALAC meeting! Kindest Regards, *Laura Margolis* ALAC Liaison to ccNSO margolisl@gmail.com +59899690992 skype: lauri.margolis ccNSO Liaison Workspace <https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Report...>