December 2025 - council - lists.icann.org

Motion - DNS Abuse PDP1 Charter
by jen＠dot.asia Jan. 7, 2026

Jan. 7, 2026

Dear All, Please find attached the Motion for the DNS Abuse PDP1 Charter. Please note that the Charter Drafting small team is currently resolving editorial comments on the charter, and the current linked charter represents the clean version received by the 23:59 UTC deadline today. When this gets resolved, this will be updated in the link in the motion as well. Wishing all a restful holiday season. Best, Jen

4 3

Thank you
by Prudence Malinki Jan. 5, 2026

Jan. 5, 2026

Dear GNSO Council, Staff and Team, The sale of the Markmonitor business to Com Laude has officially closed as of a few moments ago. As a result of this, I shall need to step down from my role as RrSG Rep, effective immediately. I wanted to take a few moments to thank you all, it has genuinely been a joy to work alongside you and you have supported, encouraged, and handled all of my questions with great kindness and good nature. I wish Susan and the new leadership of Council all of the very best! Now that I am stepping down, I shall leave as a gift a wonderful position of liaison to one of the most efficient and effective PDPs to date (ok I might be biased here) the LD PDP- which I hope one of you shall kindly take the reins of and lead it to its successful completion. Although gone from Council I shall remain at ICANN meetings, where I hope to still see you all (however I'll miss our dinners)! Thank you again everyone, it really has been a pleasure. Wishing you all the warmest and happiest of New Years. I hope to see you in 2026. Best, Prudence Malinki Head of Industry Relations, Markmonitor Signal: PMalinki.92 T +44 207 433 4869 Time zone: GMT/BST [cid:image001.png@01DC7AA0.00164DD0]

7 6

RDRS Action Items and Next Steps
by Susan Payne Dec. 29, 2025

Dec. 29, 2025

Dear Council colleagues, During our December meeting, the Council voted to “accept the RDRS SC Findings Report<https://gnso.icann.org/sites/default/files/policy/2025/draft/rdrs-sc-findin…> as helpful empirical input to inform future deliberations within the GNSO regarding the next steps on the EPDP Phase 2 SSAD Recommendations”. (emphasis added) Action Items: 1. All councilors to please review the Standing Committee’s recommendation for next steps re: SSAD recommendations for the Board-Council dialogue and determine if the SC’s recommendation for the Board to non-adopt the recommendations and allow the Council to put forward supplemental recommendations that take into account the lessons learned from the RDRS pilot is the right path. (See SC Rec. #5) 2. If any councilor(s) disagrees with the above path, they are asked to share their views and reasoning over the list. Additional Context and High-Level Next Steps for SSAD Recommendations (Board + GNSO Council Dialogue) As noted during the meeting, the SSAD recommendations are currently with the ICANN Board, who asked ICANN org to launch a two-year pilot program to gather usage and demand data intended to inform the ICANN Board’s decision on next steps (what we now refer to as the Registration Data Request Service or RDRS). The Board acknowledged the main purpose of the RDRS is to collect data about system usage, which would be used to inform future discussions between the GNSO Council and the ICANN Board on the pending Recommendations 1–18. The RDRS Standing Committee was specifically asked to provide “suggestions to the Council for a proposed recommendation(s) to the ICANN Board in relation to the consideration of the SSAD recommendations.” While the RDRS Standing Committee members may have had a difference of opinion as to specific SSAD recommendations, all members agreed that the recommendations need to be adjusted based on the learnings from the RDRS before the Board can adopt them. Specifically, the RDRS Standing Committee is recommending that the Council request the Board to non-adopt the SSAD recommendations in order to kick off the supplemental recommendation process. The Standing Committee envisioned a similar process to the SubPro Small Team+, wherein a dedicated small team (with additional members of the community) work on creating supplemental recommendations for the Council’s (and eventually Board’s) consideration. As noted during the meeting, the Standing Committee was comprised of a representative group who took into account input from many groups (including public comments), considered the available options, and ultimately recommended the Supplemental Recommendation path, noting that this option proved successful with respect to the SubPro recommendations that were non-adopted by the Board. Councilors should therefore consider the following, when reflecting on the action items: * The Standing Committee provides, in Rec. 5, “the SC further recommends that when the GNSO Council and ICANN Board engage in a dialogue, the Council should recommend that the ICANN board reject the SSAD recommendations (as a package) and send them back to the GNSO Council for further action and Supplemental Recommendation.” It is important to note that in recommending the path of non-adoption, the Standing Committee did not intend to throw the SSAD recommendations away. Instead, the Standing Committee believed the recommendations needed some important changes before the Board could adopt them. Although there are a small number of recommendations which the Standing Committee considers should be kept, even in the case of some of these the Standing Committee also identifies possible minor modifications. * If the Council is in agreement with the Standing Committee’s recommendation for the Council to suggest that the Board non-adopt the recommendations to begin the supplemental recommendation path, there is no need to form an informal small team at this stage (as the other recommendations contained in the Standing Committee’s report would eventually be reviewed and considered by the group developing supplemental recommendations, such as a Small Team +). Instead, the Council can discuss proposed Board dialogue talking points and/or takeaways from the ongoing public comment period on the Policy Alignment Analysis in a plenary session during the January Council meeting and/or the upcoming SPS. * If, however, Councilors believe an informal small team is needed, please let us know if you would like to volunteer to be a part of the discussion, and Support Staff will be happy to assist. Many thanks Susan Payne Head of Legal Policy [cid:image001.png@01DC741E.2539FB30]<https://comlaude.com/> 28 Little Russell Street, London WC1A 2HN, UK T +44 (0) 20 7421 8250 Ext 255 comlaude.com<http://comlaude.com> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAAFJfAADw_RQA0> and YouTube<https://t-uk.xink.io/Tracking/Index/bhkAAFJfAADw_RQA0> [cid:image002.png@01DC741E.2539FB30]<https://www.linkedin.com/company/com-laude> [cid:image003.png@01DC741E.2539FB30] <https://twitter.com/comlaude?lang=en> [cid:image004.png@01DC741E.2539FB30] <https://www.facebook.com/ComLaude/> [cid:image005.png@01DC741E.2539FB30] <https://www.youtube.com/@comlaude> [cid:image006.jpg@01DC741E.2539FB30] HOLIDAYS AND NEW YEAR OPENING (24 December 2025 to 2 January 2026) The Com Laude Group UK offices will close at 4.00pm GMT on Wednesday 24 December 2025, reopening on 2 January 2025. We will continue to provide assistance with urgent requests such as domain registrations and technical changes GMT: 09:00 – 17:30) except for 25-26 December and 1 January, when our UK offices are observing public holidays; our Spanish office (GMT +1), US office (GMT -8) and our Japanese office (GMT+9 hours) will be available on 26-30 December 2025 to provide such assistance. Please note that our Edinburgh office will remain closed until 5 January. Please send any urgent requests to admin(a)comlaude.com as this is the email box which the team providing cover will be monitoring and don't forget to copy in your Domain Strategists. We will also continue to provide 24/7 monitoring of our services and servers and emergency cover in the event that you have a critical requirement outside of our "follow the sun" office hours. Please call our emergency helpline on one of the following numbers in such circumstances - UK: +44. (0) 208 213 5922, USA: +1 2064877683 Meanwhile, Ben, Hayath and everyone at Com Laude Group, wish you a happy and peaceful festive season. 🎄 ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com>

2 2

FW: [CORRESPONDENCE] Tripti Sinha to Susan Payne RE: Submission of GNSO Council Review of the ICANN84 Dublin GAC Communiqué
by Susan Payne Dec. 23, 2025

Dec. 23, 2025

Hi all Sharing the below and attached acknowledgment from the Board of our GAC Communique review. Once again, with thanks to the small team who worked on this. Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 Ext 255 [cid:image001.png@01DC7431.1F522950] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAAGVfAADw_RQA0> and YouTube<https://t-uk.xink.io/Tracking/Index/bhkAAGVfAADw_RQA0> From: Wendy Profit via Gnso-chairs <gnso-chairs(a)icann.org> Sent: 22 December 2025 23:47 To: gnso-chairs(a)icann.org; GNSO-Secs <gnso-secs(a)icann.org> Cc: Tripti Sinha <tripti.sinha(a)board.icann.org> Subject: [gnso-chairs] [CORRESPONDENCE] Tripti Sinha to Susan Payne RE: Submission of GNSO Council Review of the ICANN84 Dublin GAC Communiqué Dear Susan Payne, Please find the attached letter from ICANN Board Chair Tripti Sinha in response to the GNSO Council’s review of the ICANN84 Dublin GAC Communiqué. Thank you and best regards, Wendy Profit Board Operations Senior Manager ICANN ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com>

1 0

FW: [Gnso-sc-budget] ICANN FY27-31 Operating & Financial Plan; ICANN/IANA FY27 Op Plans & Budgets; Draft PTI FY27 Operating Plan and Budget
by Steve Chan Dec. 23, 2025

Dec. 23, 2025

Dear Councilors, Below, please see an email just sent to the Budget & Operations Townhall (BOT) group. A Councilor had asked about the Council potentially submitting a public comment to the ICANN FY27–31 Operating & Financial Plan, ICANN/IANA FY27 Op Plans & Budgets proceeding that is currently open. Please note that the BOT is merely a discussion forum, established to help with understanding and disseminating relevant information. Any decision by an SG/C or the Council to submit a public comment would generally be made outside of the context of the BOT, by the respective group. Best, Steve From: Steve Chan via Gnso-sc-budget <gnso-sc-budget(a)icann.org> Reply-To: Steve Chan <steve.chan(a)icann.org> Date: Tuesday, December 23, 2025 at 9:10 AM To: "gnso-sc-budget(a)icann.org" <gnso-sc-budget(a)icann.org> Subject: [Gnso-sc-budget] ICANN FY27-31 Operating & Financial Plan; ICANN/IANA FY27 Op Plans & Budgets; Draft PTI FY27 Operating Plan and Budget Dear Budget and Operations Townhall (BOT) Members, There are two budget related public comment proceedings currently open: * ICANN FY27-31 Operating & Financial Plan, ICANN/IANA FY27 Op Plans & Budgets<https://www.icann.org/en/public-comment/proceeding/icann-fy2731-operating-f…> – Close date of 12 February 2026 * Draft PTI FY27 Operating Plan and Budget<https://www.icann.org/en/public-comment/proceeding/draft-pti-fy27-operating…> – Close date also 12 February 2026 The GNSO’s ICANN Budget and Operations Townhall (BOT), previously known as the Standing Committee ICANN’s Budget & Operations (SCBO), has been in operation for a few years now. As can be seen from the BOT’s charter [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…>, the focus of this group is “to coordinate and facilitate dialogue to fully understand ICANN's strategic and operational planning and budgetary processes” by interfacing “with ICANN Finance to gather information and ask questions as needed.” This is in contrast to the SCBO, which preceded the BOT, and was centered around formulating the Council’s comment specifically. Beyond reviewing the materials in the public comment proceeding page, I would encourage you all to start by reviewing the Informational Webinar on ICANN's and PTI’s Draft FY27 Plans if you have not already done so: https://icann-community.atlassian.net/wiki/spaces/projfinadhocws/pages/3940… [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/space…> Please note that there is an opportunity for community members to seek clarification for either of the draft plans by submitting their questions to planning(a)icann.org<mailto:planning@icann.org> and/or participating during an upcoming interactive webinar, scheduled for 14 January 2026. There is currently no BOT meeting scheduled. If after reviewing the materials and the webinar, you believe that there is a need to schedule a dialogue amongst each other, or potentially with ICANN Finance, please let us know. Best, Steve Steven Chan  VP, Policy Development Support & GNSO Relations Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org<mailto:steve.chan@icann.org> Mobile: +1.310.339.4410

1 0

Re: Motion re: IRT on IGO-INGO Curative Rights
by Terri Agnew Dec. 23, 2025

Dec. 23, 2025

Hi Damon, We confirm receipt of this motion and it will be posted on the motion wiki page for the 15 Jan 2026 Council meeting: https://icann-community.atlassian.net/wiki/x/QYA0J GNSO Council, this will need someone to second it. Please email the full GNSO Council mailing list to do so: council(a)icann.org<mailto:council@icann.org> Thank you. Kind regards, Terri Policy Team Supporting the GNSO From: "Ashcraft, Damon via council" <council(a)icann.org> Reply-To: "Ashcraft, Damon" <dashcraft(a)swlaw.com> Date: Friday, December 19, 2025 at 10:01 AM To: "council(a)icann.org" <council(a)icann.org> Subject: [council] Motion re: IRT on IGO-INGO Curative Rights Dear Fellow Councilors, As you may know, I am the Council liaison to the IRT on IGO-INGO Curative Rights project. One of the principal issues that this IRT is working on is how UDRPs are handled when the complainant is an IGO/IGNO. These organizations are not always subject to court jurisdiction so the other option for dispute resolution is an arbitration proceeding. Specifically, we are looking at the issue of when can parties exit a UDRP proceeding and proceed to arbitration. The Final Report could be interpreted in a manner that would limit when parties could proceed to arbitration but the IRT generally thinks the approach should be that parties can exit the UDRP at any time and proceed to arbitration if they so choose. This would make these UDRPs for IGO/IGNOs have the same provisions as regular UDPRs whereby parties can pretty much opt out at any time for another dispute resolution proceeding. The IRT has requested Council’s input on this issue and along those lines, I will be submitting a motion for a vote at our January meeting. A draft motion is attached along with a letter that explains this issue. On a personal level, I think the IRT is absolutely correct in their interpretation. It wouldn’t make sense to have UDRP and URS proceedings for NGO/INGOs have significantly different mechanisms to exit them for alternative dispute resolution proceedings. Finally, I want to reiterate that this is NOT an issue of ICANN staff and the IRT having a significant disagreement as to what the final report says. Rather, the IRT recognizes that this is a significant issue and we wanted Council to be aware of it and the provide guidance on the desired interpretation. Please see the attached and let me know if you have any questions. Thanks, Damon J. Damon Ashcraft , P.C. O: 602.382.6389<tel:602.382.6389> | M: 602.510.1640<tel:602.510.1640> dashcraft(a)swlaw.com<mailto:dashcraft@swlaw.com> SNELL & WILMER swlaw.com [us.content.exclaimer.net]<https://urldefense.com/v3/__https:/us.content.exclaimer.net?url=https*3A*2F…> | LinkedIn [us.content.exclaimer.net]<https://urldefense.com/v3/__https:/us.content.exclaimer.net?url=https*3A*2F…> One East Washington Street | Suite 2700 | Phoenix, AZ 85004‑2556 Albuquerque | Boise | Dallas | Denver | Las Vegas | Los Angeles | Los Cabos | Orange County | Palo Alto | Phoenix | Portland | Reno-Tahoe | Salt Lake City | San Diego | Seattle | Tucson | Washington, D.C. This email and any attachments may be confidential and protected by legal privilege. If you have received this message in error, please do not disclose the contents to anyone. Please notify the sender by return email and delete this email as well as any attachments from your system.

3 2

FW: [Ext] NEW: Review of Reviews Cross Community Group Progress/Status Update
by Julie Bisland Dec. 22, 2025

Dec. 22, 2025

FYI: From: ICANN Community Digest <digest(a)icann.ccsend.com> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Monday, December 22, 2025 at 10:05 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] NEW: Review of Reviews Cross Community Group Progress/Status Update [https://danh45uab.cc.rs6.net/on.jsp?ca=1d33fedc-2025-4c45-abc2-7509568863fa…] Monday, 22 December 2025 ICANN Community Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The Digest will resume publication in the new year on 05 January 2026. Click here to learn more about the New gTLD Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> Applicant Support Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> Registry Service Provider Evaluation Program [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> The ICANN organization Policy Development Support function publishes this twice-weekly digest to help ICANN community groups track requests and follow updates. Do you have any ideas for improving the ICANN Community Digest? Write to us at policyinfo(a)icann.org!<mailto:policyinfo@icann.org> Table of Contents ICANN85 · Register now · CLOSES TODAY: Sign up for the session slot for "Get To Know ICANN Community" Onboarding Program for Newcomers, including ICANN85 Fellowship and NextGen@ICANN Programs Participants · ICANN85 Community Childcare Grants Program: Apply Now Information Sharing · NEW: Review of Reviews Cross Community Group Progress/Status Update · NEW: ICANN Seeks Feedback on Trademark Clearinghouse Requirements · NEW: SSAC in 2025: Technical Insight and Global Policy Impact · NEW: Reflecting on One Year as ICANN Ombuds · NEW: Working Together: A Landmark Year for ICANN and the LAC Community Webinars · Register to Attend: Informational Webinar on ICANN's and PTI’s Draft FY27 Plans Next Round · ICANN Materials Provide Prospective New gTLD Applicants Clarity on Key Topics · Next Round Champions Toolkit Available in the Six ICANN Languages · Call for ASP Mentors 🚨 Action Items 🚨 · CLOSING SOON: ICANN Initiates RFP for Asset Management and Custodial Services · CLOSING SOON: ICANN Community Excellence Award: Now Accepting Nominations · CLOSING SOON: Call for Applications: NextGen@ICANN86 · ICANN Request for Proposal: New gTLD Program: 2026 Round Background Screening Services · Invitation to Provide Input for the 2026 ICANN Nominating Committee Cycle · ICANN Request for Proposal: 2026 Round Safeguard Assessment · Call for Nominations for ICANN Fellowship Program Mentors · ICANN Request for Proposal: Evaluator Panels for String Similarity and Variant Strings for the new gTLD Program: 2026 Round · Apply Now for ICANN and PTI Leadership Positions · ICANNWiki Seeking Volunteers Public Comment · NEW: Public Comment Summary Report: Updated GNSO Stakeholder Group and Constituency Charter Amendment Process · NEW: Public Comment Summary Report: String Similarity Evaluation Data for New gTLD Program: Next Round · NEW: Proposed Updates to the Trademark Clearinghouse Requirements · CLOSES TODAY: Name Collision IPv6 Research Study · Proposed GNSO Process for ICANN Board to Reverse Adoption of GNSO Policy Recs · String Similarity Evaluation Guidelines for New gTLD Program: 2026 Round · Proposed Next Round Base gTLD Registry Agreement - Spec 14 (Variant TLDs) · ICANN FY27–31 Operating & Financial Plan, ICANN/IANA FY27 Op Plans & Budgets · Draft PTI FY27 Operating Plan and Budget Events · These events occur in December 2025 and January 2026. ICANN85 Register now [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> CLOSES TODAY: Sign up for the session slot for "Get To Know ICANN Community" Onboarding Program for Newcomers, including ICANN85 Fellowship and NextGen@ICANN Programs Participants Want to introduce your group’s work to ICANN85 Community Forum newcomers, including Fellowship and NextGen@ICANN Programs Participants? Sign up for a 30 minute session on 7-8 March, 2026. These outreach sessions are part of the ""Get To Know ICANN Community"" Onboarding Program for Newcomers and are an opportunity for every SO/AC to share information with the ICANN Meeting newcomers and highlight the important work that your group does within ICANN. The link to sign up for available slots is as follows: https://docs.google.com/spreadsheets/d/1TAxTUrE0ZkODdrend9OClQ5I_1r5Rs_BHSQ… [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…>. For any additional questions, please contact ICANN Fellowship Program Manager, Siranush Vardanyan at siranush.vardanyan(a)icann.org<mailto:siranush.vardanyan@icann.org>. The deadline to sign up for a slot is December 22, 2025 ICANN85 Community Childcare Grants Program: Apply Now The program facilitates the in-person participation of community members with children who are 12 years old or younger at ICANN Public Meetings and eligible ICANN events. DEADLINE: Friday, 16 January 2026, at 23:59 UTC Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> Information Sharing NEW: Review of Reviews Cross Community Group Progress/Status Update As 2025 concludes, find out more about the Reviews CCG progress, [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> status and planned next steps leading up to ICANN85. NEW: ICANN Seeks Feedback on Trademark Clearinghouse Requirements The TMCH Requirements describe the detailed requirements for registry operators in relation to their Sunrise and Trademark Claims periods. Announcement. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> Public Comment. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> NEW: SSAC in 2025: Technical Insight and Global Policy Impact SSAC is grateful to all members and invited experts whose volunteer contributions fuel our impact. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> NEW: Reflecting on One Year as ICANN Ombuds A year goes by very quickly when you're doing work you love for an organization whose mission grows increasingly more vital each day. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> NEW: Working Together: A Landmark Year for ICANN and the LAC Community The year's accomplishments highlight the region's growing readiness, strong community collaboration, and shared commitment to a secure, stable, and multilingual Internet. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> Webinars Register to Attend: Informational Webinar on ICANN's and PTI’s Draft FY27 Plans The webinar will provide an overview of the draft plans for ICANN and Public Technical Identifiers (PTI) which will be posted for separate, concurrent Public Comments. The webinar will be presented at two different times, and community members can register for one or both of the sessions: 14 January 2026 at 00:00 UTC Read more and register. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> Next Round ICANN Materials Provide Prospective New gTLD Applicants Clarity on Key Topics ICANN org is developing supplemental, complementary materials to aid prospective generic top-level domain (gTLD) applicants in understanding the Next Round application requirements, and how to navigate the application and evaluation processes. Blog [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…>. Key Topic Overview Documents. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> Next Round Champions Toolkit Available in the Six ICANN Languages ICANN is working with the community to identify potential Applicant Support Program (ASP) applicants – especially in regions that are currently under-represented in ICANN. If you are interested in helping to raise awareness among your own contacts or communities, please use the materials in the Next Round Champions Toolkit [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…>. To stay up to date on the New gTLD Program: Next Round and ASP, join the mailing list: nextroundinfo(a)icann.org. ASP leads, targets, and ideas can be sent to engagement.newgTLDprogram(a)icann.org<mailto:engagement.newgTLDprogram@icann.org>. Call for ASP Mentors ICANN is seeking volunteer mentors who would like to offer their expertise to supported applicants as part of the ASP in the new gTLD Program: Next Round [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…>. ICANN is looking for mentors who can share insights and experience across ICANN Languages (Arabic, Chinese, English, French, Russian, or Spanish) to support diverse gTLD applicants. Mentors may play a role in: advising applicants on navigating the gTLD application process and DNS industry; identifying resources; providing guidance; sharing experiences as appropriate; and helping supported applicants navigate the ICANN community and Public Meetings. If you or someone in your network might be interested, please refer to the mentor registration announcement [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> for more information. Questions about the ASP or becoming a supported applicant Mentor can be sent to globalsupport(a)icann.org<mailto:globalsupport@icann.org>. Action Items CLOSING SOON: ICANN Initiates RFP for Asset Management and Custodial Services Firms may respond to this RFP to provide asset management services only, custody services only, or both asset management and custody services. DEADLINE: 23:59 UTC on 31 December 2025 Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> CLOSING SOON: ICANN Community Excellence Award: Now Accepting Nominations The Community Excellence Award recognizes ICANN community members who have deeply invested in consensus-based solutions and contributed substantively to the ICANN multistakeholder model. DEADLINE: 8 January 2026 at 23:59 UTC Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> CLOSING SOON: Call for Applications: NextGen@ICANN86 ICANN wants to hear from university students living and studying in the European region who are interested in the future of the Internet and participating in the Public Meeting. DEADLINE: 9 January 2026 Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> ICANN Request for Proposal: New gTLD Program: 2026 Round Background Screening Services Its purpose is to safeguard registrants and the public interest by ensuring that corporations, organizations, and institutions are in good standing and eligible to operate a gTLD. DEADLINE: 23:59 UTC on 16 January 2026 Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> Invitation to Provide Input for the 2026 ICANN Nominating Committee Cycle Specifically, it seeks feedback on the guidance and candidate job descriptions provided by the receiving bodies, as well as additional qualities, skills, or considerations that should be prioritized in candidate selection. DEADLINE: 21 January 2026 Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> ICANN Request for Proposal: 2026 Round Safeguard Assessment The safeguard assessment provider will determine whether an applied-for string fits into one of the risk-based groups that will require specific safeguard public interest commitments (PICs) as contractual obligations in the 2026 Round registry agreement. DEADLINE: 22 January 2026 Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> Call for Nominations for ICANN Fellowship Program Mentors Interested SOs/ACs should select their respective Fellowship Program mentor representative to serve for the ICANN87–ICANN89 meetings, and notify ICANN Fellowship Program Manager Siranush Vardanyan via email at siranush.vardanyan(a)icann.org<mailto:siranush.vardanyan@icann.org> no later than 10 February, 2026. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> ICANN Request for Proposal: Evaluator Panels for String Similarity and Variant Strings for the new gTLD Program: 2026 Round The selected provider(s) will also be required to collaborate with ICANN on the development of evaluation guides for the work conducted by the panels, ensuring that the evaluation processes are transparent, consistent, and repeatable across all gTLD applications. DEADLINE: Wednesday 18 February, 23:59 UTC Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> Apply Now for ICANN and PTI Leadership Positions The selected individuals will have a unique opportunity to work with accomplished colleagues from around the globe to help shape the policy development and technical coordination of the Internet's unique identifiers. DEADLINE: 18 February 2026 Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> ICANNWiki Seeking Volunteers ICANNWiki is seeking volunteers to assist with creating and editing articles and content for the site. Do you want to help? Getting started is as simple as requesting an account [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…>. Then, make sure to read the short content guide [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> to get a feel for what belongs in the wiki. Also, feel free to take a look at some data [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…>source suggestions [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> on where to find reliable data. Happy editing! Public Comment NEW: Public Comment Summary Report: Updated GNSO Stakeholder Group and Constituency Charter Amendment Process [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> NEW: Public Comment Summary Report: String Similarity Evaluation Data for New gTLD Program: Next Round [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> NEW: Proposed Updates to the Trademark Clearinghouse Requirements [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> Open for Submissions Date: Tuesday, 18 December 2025 Closed for Submissions Date: Thursday, 27 January 2026 CLOSES TODAY: Name Collision IPv6 Research Study [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> Submissions Opening Date: Monday, 20 October 2025 Submissions Closing Date: Monday, 22 December 2025 Proposed GNSO Process for ICANN Board to Reverse Adoption of GNSO Policy Recs [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> Submissions Opening Date: Thursday, 20 November 2025 Submissions Closing Date: Thursday, 22 January 2026 String Similarity Evaluation Guidelines for New gTLD Program: 2026 Round [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> Submissions Opening Date: Wednesday, 26 November 2025 Submissions Closing Date: Thursday, 22 January 2026 Proposed Next Round Base gTLD Registry Agreement - Spec 14 (Variant TLDs) [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> Submissions Opening Date: Wednesday, 10 December 2025 Submissions Closing Date: Tuesday, 27 January 2026 ICANN FY27–31 Operating & Financial Plan, ICANN/IANA FY27 Op Plans & Budgets [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> Open for Submissions Date: Tuesday, 16 December 2025 Closed for Submissions Date: Thursday, 12 February 2025 Draft PTI FY27 Operating Plan and Budget [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> Open for Submissions Date: Tuesday, 16 December 2025 Closed for Submissions Date: Thursday, 12 February 2025 See upcoming proceedings [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…>. See other public consultations [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…>. Events These events occur in December 2025 and January 2026. To learn more, please visit our community engagement calendar [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…>. · Libyan School on IG 2025 · ICANN Webinar: DNS101 · ICANN's Training on Advanced DNS · DNSSEC Workshop Jordan 2026 · PTC'26 · (MN)NUG · ICANN Webinar Series for EMEA: Charting the Path Ahead for ICANN's DNS Abuse Mitigation Efforts Volume 7, Issue 91 | Archive [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…> | Next Issue: Monday, 05 January 2026 STAY INFORMED: Subscribe here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001gwFsRDh…>

1 0

REMINDER | Document and Motion deadline | Monday, 05 January 2026 at 23:59 UTC for GNSO Council Meeting 15 January 2026 at 05:00 UTC
by Terri Agnew Dec. 19, 2025

Dec. 19, 2025

Dear all, Reports, motions, and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday, 05 January 2026 at 23:59 UTC) for the GNSO Council Meeting on Thursday, 15 January 2026 at 05:00 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Motions Wiki at: https://icann-community.atlassian.net/wiki/x/QYA0J Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

Motion re: IRT on IGO-INGO Curative Rights
by Ashcraft, Damon Dec. 19, 2025

Dec. 19, 2025

Dear Fellow Councilors, As you may know, I am the Council liaison to the IRT on IGO-INGO Curative Rights project. One of the principal issues that this IRT is working on is how UDRPs are handled when the complainant is an IGO/IGNO. These organizations are not always subject to court jurisdiction so the other option for dispute resolution is an arbitration proceeding. Specifically, we are looking at the issue of when can parties exit a UDRP proceeding and proceed to arbitration. The Final Report could be interpreted in a manner that would limit when parties could proceed to arbitration but the IRT generally thinks the approach should be that parties can exit the UDRP at any time and proceed to arbitration if they so choose. This would make these UDRPs for IGO/IGNOs have the same provisions as regular UDPRs whereby parties can pretty much opt out at any time for another dispute resolution proceeding. The IRT has requested Council’s input on this issue and along those lines, I will be submitting a motion for a vote at our January meeting. A draft motion is attached along with a letter that explains this issue. On a personal level, I think the IRT is absolutely correct in their interpretation. It wouldn’t make sense to have UDRP and URS proceedings for NGO/INGOs have significantly different mechanisms to exit them for alternative dispute resolution proceedings. Finally, I want to reiterate that this is NOT an issue of ICANN staff and the IRT having a significant disagreement as to what the final report says. Rather, the IRT recognizes that this is a significant issue and we wanted Council to be aware of it and the provide guidance on the desired interpretation. Please see the attached and let me know if you have any questions. Thanks, Damon J. Damon Ashcraft , P.C. O: 602.382.6389<tel:602.382.6389> | M: 602.510.1640<tel:602.510.1640> dashcraft(a)swlaw.com<mailto:dashcraft@swlaw.com> SNELL & WILMER swlaw.com<https://us.content.exclaimer.net?url=https%3A%2F%2Fwww.swlaw.com%2F&tenanti…> | LinkedIn<https://us.content.exclaimer.net?url=https%3A%2F%2Fwww.linkedin.com%2Fcompa…> One East Washington Street | Suite 2700 | Phoenix, AZ 85004‑2556 Albuquerque | Boise | Dallas | Denver | Las Vegas | Los Angeles | Los Cabos | Orange County | Palo Alto | Phoenix | Portland | Reno-Tahoe | Salt Lake City | San Diego | Seattle | Tucson | Washington, D.C. This email and any attachments may be confidential and protected by legal privilege. If you have received this message in error, please do not disclose the contents to anyone. Please notify the sender by return email and delete this email as well as any attachments from your system.

1 0

Council AOB - Internet Governance Tracking Team - WSIS+20
by Anne ICANN Dec. 19, 2025

Dec. 19, 2025

Dear Councilors, Regarding the AOB Update for today's Council meeting on the WSIS+20 process, attached please find the current draft (Revision 2) of the Outcome Document. The Informal Multistakeholder Sounding Board (IMSB) - of which Jen is a member- conducted consultations on this version this past Monday December 8. ICANN has participated actively in the consultations and provided comment on this version via Alexey Trepykhalin, Senior Manager of IGO and Government Engagement, including support for continuation and funding of the Internet Governance Forum (IGF) and asking that the reference to fragmentation of the Internet in the document be revised to refer to "Internet architecture" in order to more precisely reflect the nature of the concern. The attached Rev 2 document is not final. Discussions among the governments who will be voting next week in New York are continuing and will result in a third Revision. ICANN will have a presence in New York, including Alexey and Theresa Swinehart, who has also been participating actively as an ICANN Rep and a member of the IMSB. Chris Buckridge is also an IMSB member. In general, everyone has been very pleased with the UN's receptivity to soliciting the views of multiple stakeholders and the IMSB has been a great tool for this purpose. My understanding is that UN General Assembly deliberations will be live-streamed in case you are interested. Scroll down on this page for the livestream links: https://publicadministration.desa.un.org/wsis20/GA%20High-Level-Meeting In the event we do not have time for this AOB item in the meeting today, please feel free to raise any questions you may have by responding to this email. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso(a)gmail.com

2 2