March 2025 - ALAC - lists.icann.org

GNSO Council 10 April 2025 meeting agenda is out
by Justine Chew April 13, 2025

April 13, 2025

Dear all, Just a note to inform you that the agenda for the GNSO Council meeting on 10 April 2025 is out. For a curated version of the highlighted agenda items, please visit the *MATTERS OF INTEREST* sub-menu at this link <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/99708540/GN…> . *GNSO Council Meeting #4 of 2025 held on 10 Apr 2025 <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/99708540/GN…>* *Full Agenda <https://icann-community.atlassian.net/wiki/x/EKafBg> | Documents <https://icann-community.atlassian.net/wiki/x/yKefBg> | Motions <https://icann-community.atlassian.net/wiki/x/GaifBg>* - *Item 1: Administrative Matters* - Item 2: Opening Remarks / Review of Projects Action List - 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List <https://gnso.icann.org/en/council/project> and Action Item List <https://community.icann.org/x/RgZlAg> - *Item 3: Consent Agenda* - GNSO Review of the GAC Communiqué - *Recommendations Report for the Transfer Policy Review PDP* - *Item 4: COUNCIL VOTE - Confirmation of EPDP on Temporary Specification Team’s Intent to Modify RAA Requirements Related to Billing Contact* - Item 5: COUNCIL DISCUSSION - Aspirational Statement Review - *Item 6: COUNCIL DISCUSSION - Han Script Single Character gTLDs (Recommendation 3.17)* - *Item 7: COUNCIL UPDATE: Registration Data Request Service* - *Item 8: COUNCIL DISCUSSION: Next Steps for Whois Implementation Advisory Group* - *Item 9: Any Other Business* - 9.1 - Update on ICANN83 Planning and GNSO Draft Schedule - 9.2 - WSIS+20 <https://docs.google.com/document/d/1fM5b8tZX1APSUhEovc0qHWXc_wg3HzJ8__mJuvZ…> and internet governance discussions - *9.3 - Latin Diacritics PDP Working Group - Review of Project Plan <https://gnso.icann.org/sites/default/files/policy/2025/presentation/project…>* - 9.4 - Standing Committee on Continuous Improvements - Review of Project Plan - *9.5 - Council review of Assignment Forms for DNS Abuse and Accuracy Small Teams* This Council meeting will take place on *10 Apr 2025 **at 21:00 UTC*: https://tinyurl.com/5bsuykt5 for 2 hours and is open to observers remotely in listen-only mode via Zoom. To access the Zoom link for this meeting, please visit the *MEETING DETAILS* sub-menu at this link <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/99708540/GN…> . Thanks for reading / considering. Justine Chew ALAC Liaison to the GNSO GNSO Liaison Report Workspace <https://icann-community.atlassian.net/wiki/x/fG7xBQ?atlOrigin=eyJpIjoiNDI1Y…> ------

1 1

Summary Report on ICANN82 ccNSO Council meeting, working groups and sessions
by Laura Margolis April 1, 2025

April 1, 2025

Dear All, I hope this message finds you well. Attached is my report on the ICANN82 Meeting in Seattle. To make it easier to follow, I have divided the report into three sections: 1. Highlights from Council Meeting #215 in Seattle. 2. Updates on Working Groups and Committees. 3. ICANN82 Sessions. *AGENDA <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/99711461/AL…> Council meeting #215 – March 13th., 2025 * *BACKGROUND AND DOCUMENTS <https://ccnso.icann.org/en/about/statements.htm>* 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 *1.- HIGHLIGHTS FROM COUNCIL MEETING #215 IN SEATTLE* *Some News in the Council about Councilors:* Alejandra Reynoso was reelected as a Chair, starting her term at the end of ICANN82 and until ICANN85. Biyi Oladipo (.ng) and Jordan Carter (.au) were re elected as Vice Chairs, starting at the end of ICANN82 and until ICANN85. Byron Holland (.ca) started his position #12 at the Board, replacing Katrina Sataki who resigned. Everton Rodrigues (.br) started as a new Councilor, elected for LAC Region. *Election Process for European Region Vacancy – Meeting Report Summary* The ccNSO Council approved an extraordinary election process to fill the European Region vacancy after Nicklas Pousette declined his term. The timeline includes nominations (26 March – 22 April 2025) and elections if needed (30 April – 21 May 2025), with results announced on 23 May 2025. Joke Braeken was appointed Election Process Manager, and the decision took effect upon publication. *Some Decisions made during the Council Meeting #215 in Seattle* *Council 360 Review* Suggestion: Extend deadline Background: The ccNSO Council 360 feedback process requires at least 10 CouncilLors to respond within a two-week period. In the first 2025 review (11 Feb – 3 Mar 2025), only 6 Councillors responded, failing to meet quorum. Decision: The ccNSO Council has extended the 360 review process until 21 March 2025. Results will be shared with individual Councillors starting 25 March 2025. *Blueprint Review Process – ccNSO Working Groups and Committees* Decision Summary: Following the successful review of the DNS Abuse Standing Committee (DASC) in January 2025, the ccNSO Council approved a standardized review method for other committees and working groups. The Council adopted the review blueprint and requested the ccNSO Chair and Secretariat to develop a review schedule in consultation with the committees, considering workload and necessity. The timeline is expected by Meeting 216 to ensure the launch of a review before ICANN83 in Prague. The resolution will take effect seven days after publication, and the Chair will inform the relevant working groups accordingly. *Update on Pilot Holistic Review (PHR) and ATRT4 Next Steps* An update was provided on the Board’s discussions regarding the Pilot Holistic Review (PHR) and its future direction. The Board has engaged with the PHR co-chairs, SO/AC chairs, and the broader community to determine whether the premises of the review are acceptable. The continuation of the PHR remains subject to both community and Board approval. Concerns were raised about the review process, questioning its necessity and suggesting a return to the drawing board. While there was some opposition, At-Large members largely supported continuing the work. It was suggested that the group should first communicate with the Board before making decisions. The importance of clarity on the Board’s intent regarding ATRT4 and other reviews was emphasized. A note to the Board will be drafted to inquire about their plans. There were discussions about systemic issues within ICANN’s review processes, with a proposal to pause all reviews, including PHR, and consider appointing a design team to improve the overall review system. A drafting team was formed to prepare a communication to the Board. Caution was advised against halting all bylaw reviews, emphasizing the need for a balanced approach. *2.- SOME UPDATES ON THE WORKING GROUPS AND COMMITTEES* *IGLC <https://ccnso.icann.org/en/workinggroups/iglc.htm> – Internet Governance Liaison Committee* The group adopted the New Action Plan <https://docs.google.com/document/d/1DGqqze3TWT0oLZv--gkRMBIAPZtysZ7oaJ0pP3P…> during ICANN82 Meeting, which includes the update of the heatmap <https://drive.google.com/file/d/16p_pqHKkeFjWfXBAdOYDMW4i4-9kALso/view> (is a brainstorming of ideas on the hot Internet Governance topics in the different regions) and the napkin pitch exercise, which requests the views of the IGLC members on a topic identified on the heatmap. - The IGLC will monitor key policy trends and regulatory developments that relate to ccTLDs. - When needed the IGLC will inform and share information to the broader ccTLD community to assist community members to assess trends and developments by: Providing written reports for inclusion in the ccNSO newsletter Hosting sessions at ICANN public meetings Arranging intersessional webinars and roundtable discussions Coordinating with other (ccNSO) working groups and committees to discuss and present views on a central topic from different perspectives The New Action Plan also included an impact-effort analysis which concluded the need to prioritize the following topics: 1. The Future of Internet Governance 2. Resilience 3. Artificial Intelligence The IGLC recognizes *Resilience* as a multifaceted topic involving various ccNSO groups. To prevent overlap, it suggests coordinating with other ccNSO working groups to present diverse perspectives, potentially leading to a shared approach for similar topics. Regarding *Artificial Intelligence,* the IGLC will monitor key policy trends and regulations, informing the ccTLD community via the ccNSO Newsletter when relevant. The IGLC is planning for ICANN83 a session on the *Future of Internet Governance.* *PGA WG <https://icann-community.atlassian.net/wiki/spaces/ccnsowkspc/pages/10841522…> – Policy Gap Analysis Working Group* The group ended its first part in January and created an overview document with policies and guidance related to ccTLDs. <https://docs.google.com/document/d/1Jp2WLD6ZfF1nVY3p0xSNkCeo1E4fKIdL/edit> 2 recommendations came out after discussion in the working group. Recommendation is for two ccNSO Study Groups, to look in depth at: 1. IANA Public Records for ccTLDs - what is the purpose, data accuracy and maintenance. 2. IANA role (if any) in disaster recovery for ccTLDs. The ccNSO Council will decide on the next steps in the next few months. Session during ICANN82: https://icann82.sched.com/event/1vpcS *DASC <https://ccnso.icann.org/en/workinggroups/dasc.htm> – DNS Abuse Standing Committee* The session focused on the accuracy of domain name registration data and its role in mitigating DNS abuse. The discussion covered proactive and reactive monitoring strategies designed to improve data accuracy. Early findings suggest a correlation between unverified registration details and potentially harmful domain activity. It was also highlighted that registrant verification can support law enforcement investigations and help ensure that domain owners retain control over their domains. However, verification alone is not considered a complete solution for preventing abuse. Measures implemented by a ccTLD registry to enhance data accuracy were discussed, including incentives for registrars that adopt electronic identification (eID) verification and the launch of a new system in May 2025 to flag domains with inaccurate registration details and set deadlines for correction. The session concluded with a vote to gather participants' perspectives on the effectiveness of accurate registration data in combating online abuse. The group agreed to broaden its scope of discussion to encompass a wider range of topics, including spam, phishing, malware, and other related issues. Additionally, they considered renaming the group to avoid limiting its focus solely to DNS abuse. Session during ICANN82 in Seattle: https://icann82.sched.com/event/1vpcW *TLD-OPS <https://ccnso.icann.org/en/workinggroups/tld-ops-standing.htm> Standing Committee* The purpose of the Standing Committee is to govern the daily operation of the TLD-OPS email list; and, when deemed necessary, to develop and implement progress plans for future improvements and developments of the TLD-OPS email list, including its ecosystem. A new workshop will be held during ICANN84 on concrete demonstration on security software for registries. <https://ccnso.icann.org/sites/default/files/field-attached/tld-monitoring-t…> *3.- SESSIONS DURING ICANN82 – SEATTLE* *ccTLDs NEWS SESSION* The ccTLD News Sessions have been an integral part of the ccNSO Members Meetings for several years, serving as a global forum where both seasoned professionals and newcomers can exchange insights and discuss key issues related to country-code Top-Level Domains (ccTLDs). At ICANN82, the session covered several significant topics, including: - *Proactive Measures Against Domain Abuse in .us* – Crystal Peterson (.us) introduced the Registry Threat Mitigation Service (RTMS), a centralized platform aimed at enhancing domain security by facilitating the detection, blocking, investigation, and reporting of domain abuse threats. - *Research on Next-Generation DNS by APTLD* – Sameer Gahlot (.in) presented findings from two case studies conducted by APTLD. The research explored how registries can integrate emerging technologies to improve security, privacy, and efficiency within the DNS ecosystem, highlighting the necessity of adapting to global technological advancements. - *Updates on the Ukrainian ccTLD* – Dmytro Kohmanyuk (.ua) provided an overview of recent developments in Ukraine's ccTLD, addressing challenges and progress in the context of the ongoing geopolitical situation. - *Lusophone Community Initiatives* – Marta Moreira Dias (.pt) shared insights into projects and initiatives aimed at fostering collaboration and development within the Lusophone ccTLD community. These discussions underscored the evolving landscape of ccTLD management and the importance of collaborative efforts in addressing both technical and strategic challenges. Session during ICANN82: https://icann82.sched.com/event/1vpcH *ccNSO with GAC SESSION* The session was divided into two parts. The first item focused on identifying policy and procedural gaps in IANA's policies related to country-code top-level domains (ccTLDs), conducted in a plenary format. The second item was an interactive engagement session where participants were split into breakout groups to discuss various ccTLD models. This networking session offered an opportunity for meaningful dialogue and idea exchange. The session was both interesting and productive, fostering deeper insights into the challenges and opportunities facing ccTLDs. More information and presentations: https://gac.icann.org/sessions/icann82-session-20-gac-meeting-with-the-ccnso *SIDS - Small Island Developing States within the ICANN Ecosystem* ICANN82 hosted the first official session on Small Island Developing States (SIDS) following informal discussions at previous meetings. The open mic session covered ICANN initiatives for SIDS, improvements in training and engagement, and regional collaboration. Key highlights included ICANN’s capacity-building efforts in Oceania and the LAC Regions. The importance of technical training, collaboration with the SIDS technical community, and anycast deployment for reliable root service was emphasized. Participants proposed enhancing regional cooperation, conducting assessments for tailored training, and addressing financial constraints. LACTLD presented two Caribbean ccTLD initiatives: the Unified Domain Search Engine and LACTLD's Anycast Cloud, used by six regional ccTLDs. The session concluded with a brainstorming, agreeing to revive a mailing list for continued discussions. Session during ICANN82: https://icann82.sched.com/event/1vpeC Please feel free to reach out if you have any questions or need some more information on any of the topics, —I’ll be happy to answer. Thank you. Best Regards, -- *Laura Margolis* ALAC Liaison to ccNSO margolisl(a)gmail.com +59899690992 skype: lauri.margolis ccNSO Liaison Workspace <https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Repor…>

2 2

GNSO Council 12 March 2025 meeting agenda is out
by Justine Chew March 18, 2025

March 18, 2025

Dear all, Please find following the agenda for the GNSO Council's 12 March 2025 meeting during ICANN82. Owing to the ongoing migration work for the ICANN wiki, I am unable to point to the relevant wiki page per my usual practice. Instead, I am including highlights within this email. *GNSO Council Meeting #3 of 2025 held on 12 Mar 2025 * - *Item 1: Administrative Matters* - *Minutes <https://gnso.icann.org/sites/default/files/policy/2025/minutes/minutes-gnso…> of the GNSO Council Meeting on 09 January 2025 were posted on 26 January 2025.* - *Minutes <https://gnso.icann.org/sites/default/files/policy/2024/minutes/minutes-gnso…> of the GNSO Council Meeting on 13 February 2025 will be posted on 03 March 2025* - Item 2: Opening Remarks / Review of Projects Action List - 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List <https://gnso.icann.org/en/council/project> and Action Item List <https://community.icann.org/x/RgZlAg> - Item 3: Consent Agenda - Confirm the GNSO Standing Committee on Continuous Improvement (SCCI) Leadership Team - Acknowledgment of the appointment of Greg DiBiase to seat 13 on the ICANN Board. - *Item 4: COUNCIL VOTE - Final Report from the Transfer Policy Review (“TPR”) Policy Development Process (“PDP”) Working Group* - The TPR PDP WG which Council initiated <https://gnso.icann.org/en/council/resolutions/2020-current#20210218-2> on 18 Feb 2021 to review the Transfer Policy <https://www.icann.org/resources/pages/transfer-policy-2016-06-01-en>, the policy that governs the process of transferring a domain name from one registrar to another, was tasked to determine if changes to the policy are needed to improve the ease, security, and efficacy of inter-registrar and inter-registrant transfers. - Having started work in May 2021, the TPR PDP WG delivered a comprehensive Initial Report <https://community.icann.org/pages/viewpage.action?pageId=347734037&preview=…>, which it published on 1 August 2024, and delivered its Final Report <https://gnso.icann.org/sites/default/files/policy/2025/correspondence/tpr-t…> to Council in February 2025. - The Initial Report covers all topics in the working group’s charter, including inter-registrar transfers, change of registrant, the Transfer Dispute Resolution Policy, ICANN-approved transfers, and others. - The Final Report contains 47 policy recommendations. - The TPR Working Group introduced a new format to its Initial and Final Report, where it endeavors to indicate the “Policy Impact Level” of each policy recommendation. The Policy Impact Indicator is a new feature to help the reader understand the degree of change being proposed by the Working Group, i.e., how much does this recommendation differ from the current Transfer Policy? - Council will vote on the Final Report (voting threshold: supermajority) - *Item 5: COUNCIL DISCUSSION - Next Steps for Registration Data Accuracy * - *During Council’s July 2024 meeting <https://gnso.icann.org/sites/default/files/policy/2024/minutes/minutes-gnso…>, it was agreed that restarting the Scoping Team at this time is not recommended. However, during the August meeting <https://gnso.icann.org/sites/default/files/policy/2024/minutes/minutes-gnso…>, some Councilors suggested potentially convening a small team to discuss how to make progress on this topic. * - *Council Leadership distributed a proposal <https://lists.icann.org/hyperkitty/list/council@icann.org/thread/DPFGXG6WTL…> of how to solicit additional feedback from ICANN org and GNSO groups with directed questions, in order to receive information from which Council can decide how to handle the important topic of accuracy. Following full Council review and feedback, the Council distributed these questions to Supporting Organizations and Advisory Committees. * - *Council received feedback from the following groups: ALAC, BC, GAC, IPC, ISPCP, NCSG, RrSG, and RySG.* - *Separately, Council Leadership sent a communication re: RDS-WHOIS2 Recommendation CC.1 <https://www.icann.org/en/system/files/files/resolutions-board-action-rds-wh…> from 2020. This recommendation deals with the accuracy of RDS data, particularly names suspended due to inaccurate data. The recommendation essentially recommends that registrars note in the RDS record that the name is suspended due to incorrect data and also recommends the name should not be “unsuspended” until the data is corrected. As this recommendation also falls under the topic of accuracy, Leadership noted that folding Recommendation CC.1 into the broader discussion of accuracy (when that takes place) may make sense. * - *Council will discuss the feedback received and determine next steps for making progress on registration data accuracy. * - *Item 6: COUNCIL DISCUSSION - EPDP Phase 1 on the Temporary Specification - Implementation Question re: Billing Contact* - *During the ICANN81 GNSO Council Wrap-Up <https://icann81.sched.com/event/1p2Gu/gnso-council-wrap-up>, Thomas Rickert provided an update regarding the implementation of EPDP Temp Spec Phase 1 recommendations. Thomas is the current GNSO Council Liaison to the EPDP Temp Spec Phase 1 Implementation Review Team (IRT). Thomas noted that the IRT expressed the view that the absence of a reference to billing contact data was a drafting error, and the EPDP Team intended for the collection of billing contact data to be optional and not mandatory.* - *The Registration Data Policy <https://www.icann.org/resources/pages/registration-data-policy-2024-02-21-en> was published on 21 February 2024, and the policy has an effective date of 21 August 2025. The EPDP Phase 1 policy recommendations <https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-gtld…> do not reference billing contact data, and the Registration Data Policy <https://www.icann.org/resources/pages/registration-data-policy-2024-02-21-en> also makes no reference to billing contact data.* - *In the interest of transparency, Thomas requested that all Councilors consult with their respective groups to ensure that others are properly informed and agree with the interpretation raised by the IRT. Accordingly, Councilors were asked to consult with their groups. Council discussed this topic during its meeting on 19 December 2024 <https://icann.zoom.us/rec/play/wMLdawWw7g5mSvuAbgKmzJKUiRDCBU1sSYKHcwg3nb8O…> and asked for additional background information on the topic. * - * During its February meeting, the Council considered the questions below:* * 1. Does the Council confirm billing contact was in scope for the EPDP on the Temp Spec - Phase 1 Team? 2. Does the Council confirm:* a. the collection of billing contacts by registrars should continue to be required as per current RAA requirements because EPDP Phase 1, by being silent on this, did not mean to change this requirement, OR *b. the collection of billing contacts by registrars should become optional because EPDP Phase 1, by being silent on this, meant to change the RAA requirement?* - *Council will continue discussing at ICANN82 options for resolving this Billing Contact question. * - *Item 7: COUNCIL DISCUSSION: Update on Trilateral Meeting on Urgent Requests * - *ICANN org convened an Implementation Review Team to assist ICANN in implementing the EPDP on the Temporary Specification Phase 1 Final Report <https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-gtld…>, which began meeting in May 2019. ICANN org published the draft Registration Data Policy for public comment <https://www.icann.org/en/public-comment/proceeding/registration-data-consen…> on 24 August 2022. Several commenters expressed dissatisfaction with the implementation of Recommendation 18, specifically around the issue of the response timeline for urgent requests. The relevant portion of Recommendation 18 reads, “A separate timeline of [less than X business days] will considered for the response to ‘Urgent’ Reasonable Disclosure Requests, those Requests for which evidence is supplied to show an immediate need for disclosure [time frame to be finalized and criteria set for Urgent requests during implementation].”* - *On 3 June 2024 <https://gnso.icann.org/sites/default/files/policy/2024/correspondence/tsinh…>, the Board wrote to Council, noting concerns with the proposed urgent request timeline of business days as not fit for purpose, as truly urgent requests should be responded to within minutes or hours rather than business days. Recognizing this, the Board also noted there is no universal mechanism for registrars to authenticate law enforcement entities. Council responded on 29 August 2024 <https://gnso.icann.org/sites/default/files/policy/2024/correspondence/dibia…>, agreeing with the Board’s concerns and suggesting a trilateral meeting between the Board, Council, and GAC to discuss a potential path forward in light of the concerns. * - *A trilateral meeting was held on 4 November 2024 <https://community.icann.org/display/gnsocouncilmeetings/Dialogue+with+GAC%2…> and the Board, GAC, and GNSO Council discussed next steps, including potentially resuming discussions with the IRT. The Council discussed this issue in detail during its meeting on 19 December 2024 <https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agen…> and responded to the GAC on 15 January 2025 <https://gnso.icann.org/sites/default/files/policy/2025/correspondence/dibia…>. A second trilateral meeting was held on 12 February 2025 <https://community.icann.org/display/gnsocouncilmeetings/Dialogue+with+GAC%2…>. * - *Council will hear an update from that trilateral meeting and discuss next steps. * - *Item 8: COUNCIL DISCUSSION: Outcomes of Strategic Planning Session* - *Item 9: Any Other Business * - *9.1 - GNSO Chair Election Timeline <https://gnso.icann.org/sites/default/files/file/field-file-attach/proposed-…> Announcement* - *9.2 - Update from the GNSO Informal Internet Governance Tracking Group\* - *9.3 - Accuracy Scoping Deferral Expiration* - *9.4 - Open Mic* This Council meeting will take place on 12 March at 20:15 UTC: https://tinyurl.com/ym7f48uc for 2 hours and is open to observers either in-person ICANN registered participants, or remotely in listen-only mode via Zoom (except for the Open Mic session). Please check *https://icann82.sched.com/event/1vpbt/gnso-council-meeting* <https://icann82.sched.com/event/1vpbt/gnso-council-meeting> for the designated meeting room and the Zoom room link. The Zoom room link will only be published 24 hours prior to the meeting. Thanks for reading / considering. Justine Chew ALAC Liaison to the GNSO GNSO Liaison Report Workspace <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…>

3 5

Final Results of the ccNSO DNS Abuse Survey
by Laura Margolis March 1, 2025

March 1, 2025

Dear All, I would like to share with you the final results of the DNS Abuse survey conducted by the ccNSO DNS Abuse Standing Committee (DASC) <https://ccnso.icann.org/en/workinggroups/dasc.htm>. You can access the full report here: 🔗 DNS Abuse Survey Results <https://ccnso.icann.org/sites/default/files/field-attached/ccnso-dasc-surve…> Additionally, if you are interested in the presentation of the results, I have included the link to the webinar recording from last Wednesday, February 26th: 🔗 Webinar Recording <https://community.icann.org/display/ccnsowkspc/ccNSO+Webinars> (currently and during this weekend out of service for website maintenance) The 2024 survey results highlight important trends in the ccTLD community’s approach to DNS abuse. Notably, awareness of abuse levels has improved, with a significant drop in respondents unsure about their domain abuse rates (from 35% in 2022 to 21% in 2024). The majority of ccTLDs continue to report low levels of abuse, with 69% indicating rates below 0.1%, a notable improvement from 49% in the previous survey. Additionally, while there remains no clear correlation between domain pricing and abuse levels, ccTLDs are increasingly adopting AI and machine learning for detection. The survey also provides valuable insights into the adoption of ICANN gTLD contract DNS abuse clauses and the ongoing efforts in abuse mitigation. Thank you! Best regards, -- *Laura Margolis* ALAC Liaison to ccNSO margolisl(a)gmail.com +59899690992 skype: lauri.margolis ccNSO Liaison Workspace <https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Repor…>

2 1