February 2026 - council - lists.icann.org

DNS Abuse PDP Chair
by Susan Payne Feb. 25, 2026

Feb. 25, 2026

Hi All I probably won't pick up on everything but did want to clarify a few points on the process. Although it certainly was the case in the past that PDP WGs selected their chair, we moved away from that some time ago, I believe, as part of the PDP3.0 improvements. When WGs select, we often saw co-chairs appointed, rather than a single chair, and sometimes multiple co-chairs due to an apparent inability or unwillingness of the WG members to select a single candidate when multiple volunteers come forward. The template PDP charter now states that "The GNSO Council leadership and Standing Selection Committee leadership will jointly review the responses and will propose a Chair to the GNSO Council which will then either affirm the selection or reject the selection and send the process back to the GNSO Council leadership and Standing Selection Committee leadership." This is the language in the DNS Abuse PDP1 charter, was used in the charter for Latin Diacritics, and was included in PDP Charters at least as early 2018 for the EPDP Temp Spec. While the SSC is not tasked specifically with selecting PDP chairs, its charter tasks it in more general terms with making selections for ICANN structures such as Review Teams, as requested by Council. The PDP charter does however signal a possible role for the SSC. Under the PDP charter, Council Leadership could have made this selection ourselves and recommended the candidate to Council for approval. For a number of reasons, we felt that it was preferable to seek the assistance of the SSC, including that it's a high community-interest topic, there were multiple candidates, rather than only a single clearly-eligible candidate, and the SSC route would allow representatives from each SG/C to have a voice in the process. This is not the only PDP chair selection that has been referred to the SSC. Most recently, the SSC conducted the selection of the chair for the Latin Diacritics PDP, where again there were multiple candidates. It is, I believe, always the case that SSC recommendations must be voted-on by Council, as will be the case here. Council is not required to follow the SSC recommendation, but given the representative nature of that group and the expectation that it will recommend a candidate with full consensus, it seems likely to be an unusual occurrence where Council does not feel able to support that recommendation. Again, for the avoidance of doubt, the first communication to the PDP WG members stated clearly that the chair candidate selected by the SSC was subject to approval by Council but that pending that approval they would be starting work in preparing for the ICANN 85 meetings, to ensure smooth progress and a timely start of the PDP work. I don't hear anyone saying that they do not intend to support the recommended candidate in the upcoming vote, but if that is the case it would be helpful if Councillors could flag that as early as possible. Many thanks Susan Payne Head of Legal Policy [cid:image001.png@01DCA637.E302DCE0]<https://comlaude.com/> 28 Little Russell Street, London WC1A 2HN, UK T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 comlaude.com<http://comlaude.com> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAAA98AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAAA98AADw_RQA0> [cid:image002.png@01DCA637.E302DCE0]<https://www.linkedin.com/company/com-laude> [cid:image003.png@01DCA637.E302DCE0] <https://twitter.com/comlaude?lang=en> [cid:image004.png@01DCA637.E302DCE0] <https://www.facebook.com/ComLaude/> [cid:image005.png@01DCA637.E302DCE0] <https://www.youtube.com/@comlaude> [cid:image006.jpg@01DCA637.E302DCE0] ________________________________ 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

Questions for GNSO meeting with the Board D/L 25 february
by Susan Payne Feb. 24, 2026

Feb. 24, 2026

All Further to the email shared with the Board's questions to us, and our discussion during the Prep Webinar last week, we need to finalise our questions for the Board by 25 February. Below are various suggestions for views, improvement, rejection, etc: 1. Review of Reviews: As discussed, we will respond to the Board question, and ask the Board for their own thoughts on the direction that the CCG is taking. 2. Prioritisation: The GNSO Council is currently engaging in an exercise to develop a more formal process for prioritising our workload. Are there any internal or external factors that the Board would like us to take into consideration? For example, are there specific future risks that the Board has identified as likely to require policy work? 3. ICANN Grant Program: recipients were announced at the start of 2025. Many were for 2-year projects but some were of shorter duration. All Grant recipients are expected to complete interim reports throughout the duration of the grant to document the progress of the project and the use of the funds. A final report will also be due at the conclusion of the project and should detail achievement of goals and objectives and final expenditures for the project. When will we start seeing such reports? 4. WSIS+20: Now that the WSIS+20 process has moved on to the development of the implementation roadmap by UNGIS, does ICANN have any involvement in or visibility on that process? Do you envisage any impact on the current or future policy landscape? If there are additional, or alternative questions you feel we should be asking please feed them back. Again, just a reminder that we plan to answer both of the Board questions, with the FY 26-30 Strategic Plan question giving an opportunity for us to update on our PDP efficiency & effectiveness measures in the work on Board Readiness, and an update on the Board non-adoption process following the recent public comment period. Susan Payne Head of Legal Policy [cid:image001.png@01DCA5DC.A37BCCE0]<https://comlaude.com/> 28 Little Russell Street, London WC1A 2HN, UK T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 comlaude.com<http://comlaude.com> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAAA98AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAAA98AADw_RQA0> [cid:image002.png@01DCA5DC.A37BCCE0]<https://www.linkedin.com/company/com-laude> [cid:image003.png@01DCA5DC.A37BCCE0] <https://twitter.com/comlaude?lang=en> [cid:image004.png@01DCA5DC.A37BCCE0] <https://www.facebook.com/ComLaude/> [cid:image005.png@01DCA5DC.A37BCCE0] <https://www.youtube.com/@comlaude> [cid:image006.jpg@01DCA5DC.A37BCCE0] ________________________________ 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>

3 2

DNS Abuse PDP Chair
by Bruna Martins dos Santos Feb. 24, 2026

Feb. 24, 2026

Dear all, Hope this email finds you well. I understand we are all under a lot of pressure due to the forthcoming start of the DNS Abuse PDP and Mumbai meeting, but I would like to share my discomfort as to how the chair selection and PDP communications has been handled so far. As of now, we have had an announcement made on the list on behalf of a preliminary chair. And, as per our understanding, Council leadership has made a request for SSC to make a recommendation of a chair and this recommendation needs to be confirmed by council and hasn't been yet. Therefore, I would like to kindly request that Council leadership informs us of the next steps in this process, especially because I have the following doubts: *1. Will there be a motion confirming Paul as PDP Chair in Mumbai we need to vote on ? 2. How can a preliminary chair host the first meeting of the PDP if he hasn't been formally confirmed on the role ? In this case, shouldn't we ask Staff to chair the first meeting? (im invoking gnso working group guidelines that foresee the possibility of staff performing admin coordination until a chair is appointed) * *3. How can a preliminary chair select his vice-chair if he hasn't been confirmed yet ? * Again, I understand we're all doing our best and my email is by no means a question about Paul's abilities. But the way we have been dealing with this process has been a tad frustrating and I wish we had more information from leadership. Kind regards, Bruna -- *Bruna Martins dos Santos * Policy and Advocacy Manager | WITNESS <https://www.witness.org/> German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von Humboldt Foundation <https://www.humboldt-foundation.de/> Member | Coalizão Direitos na Rede <https://direitosnarede.org.br/> Twitter: @boomartins <https://twitter.com/boomartins> // Skype: bruna.martinsantos Email: bruna.mrtns(a)gmail.com

3 4

REMINDER | Document and Motion deadline | Sunday, 01 March 2026 at 23:59 UTC for GNSO Council Meeting 11 March 2026 at 07:45 UTC (13:15 IST)
by Terri Agnew Feb. 23, 2026

Feb. 23, 2026

Dear all, Reports, motions, and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Sunday, 01 March 2026 at 23:59 UTC) for the GNSO Council Meeting on Wednesday, 11 March 2026 at 07:45 UTC (13:15 IST) 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/pYAtJ Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

Re: Urgent Requests/LEA
by Anne ICANN Feb. 23, 2026

Feb. 23, 2026

Ashley, As far as I know (and I may not be current since some extenuating circumstances here in Tucson have forced a delay in my participation and response), the PSWG Authentication Group is looking at the terminology involved in a set of questions developed by Gabriel Andrews of the FBI that seek to address concerns we all expressed about the proposed short term solution to authentication, i.e. Law Enforcement Agencies to supply email addresses they consider valid to ICANN and to attest to their view of the validity of these Requestor email addresses. ICANN would then supply these email addresses to registrars as a first step to supply additional information that a registrar can consider when evaluating an Urgent Request. I remember emphasizing a need to understand how each LEA acquires, validates, reviews and purges these addresses since some in the practitioners group have pointed out that email addresses can be fabricated but still have the appearance of being official. Farzi and I and others have been asking to be able to understand these email list practices on an LEA-by-LEA basis; ever since the initiation of the PSWG meetings on this topic. I also suggested that in the short term solution proposed by Gabe, Interpol, and Europol, appropriate disclaimers may have to be made as to the accuracy of the email addresses provided since many registrars (especially smaller ones) might not have the resources to conduct an independent investigation of authenticity of the Requestor email address on an urgent timeline. Gabe recently sent around the following list of questions representing his understanding of the questions the group still has and several members commented on the terminology. I cannot update you as to any changes to terminology which may have been made. Farzi may be more current than I. I would expect that Gabe will be presenting a slide on this at the GAC-Council meeting but I don't know for certain. - *At a high level, what is the proposed mechanism for Law Enforcement Agencies (LEAs) to authenticate users of ICANN’s Registration Data Request Service?* - *Who is expected to serve as an Identity Provider for LEAs?* - *How does each LEA Identity Provider determine (or verify) that an agency is or isn’t a LEA? How do they verify that the user is an actual member of that law enforcement agency? * - *How many agencies and/or users are expected to have access to authenticated connections to RDRS via the law enforcement portals?* - *How frequently is the status (or employment) of a LEA user validated?* - *What information is expected to be passed to the data holder when an authenticated LEA requestor submits an RDRS request?* - *Are there any technical requirements expected of a data holder?* - *Is the LEA request logged? By whom? For how long?* - *What rules govern how a LEA requestor uses the authentication portal? (i.e. what commitments are made in regards to responsible use?)* - *What recourse exists to a data holder if a LEA requestor is suspected of abuse/misuse of the RDRS?* - *Does an authenticated request carry any additional obligation to disclose data vs a non-authenticated request? * - *What documentation is expected to exist, and where can it be found?* *Jurisdictional Issues* As to the subject of jurisdiction, we have made the point in the PSWG meetings that not every registrar is subject to the jurisdiction of every LEA. So, as Farzi noted in a meeting last week, the question whether the registrar is actually legally required or able to respond to an LEA request is one each registrar must determine for itself even in advance of evaluating whether the request meets the Urgent Request definition in the existing policy. As you know, the IRT on this topic noted in its request for public comment that the registrar should respond accordingly to the LEA if jurisdictional issues form the basis for a denial of disclosure in a case that would potentially qualify as an Urgent Request. I assume public comment would have favored this recommended approach from the IRT in recognition of the fact that the jurisdictional issues are very real. These jurisdictional issues were covered extensively in Thomas Rickert's presentation to the GAC in Dublin on this topic. It would be a good idea to review the zoom on that meeting since some theories on the reach of jurisdiction were explored in addition to a discussion regarding EU interpretation of the applicability of MLAT provisions. This is pretty complex stuff but I know the European Commission representative on the GAC has some knowledge on this topic and made a comment in response to Thomas' summary of the jurisdictional topic. *Policy Process* As to whether a policy process is necessary to define "Authenticated Requestor", as outlined in the material put out by the IRT for public comment, I do not know if the staff summary is available but I would certainly expect it will be before Mumbai. My recollection is there were comments in support of a policy process and other comments saying it was not necessary, including of course by the GAC, but at least one registrar agreed no policy process was necessary. In this regard, I think it would be better to revise the slide to state "the Policy process anticipated by the IRT" rather than saying "the anticipated Policy process" as if this were a Council official position. Again, I am not certain of being up to date on the above topics. Wish you well in facilitating the discussion with the GAC. I will not be in Mumbai but will be participating remotely. Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso(a)gmail.com On Wed, Feb 18, 2026 at 8:14 AM farzaneh badii <farzaneh.badii(a)gmail.com> wrote: > Hi Ashley, > > The practitioner group is putting all sorts of questions together, I > wonder if we should pose those during our meeting. Another thing is as Anne > and I have been consistently saying, we need to know which protocols law > enforcement use to authenticate their emails and what policies they have > for requesting disclosure. I just don't know if we should put those > questions forward. > > I'd like to discuss more about GAC opinion that urgent request should not > go through a round of policy and understand them better but I don't know > if the council wants to pose that question. > > Farzaneh > > > On Tue, Feb 17, 2026 at 2:54 PM aheineman(a)godaddy.com < > aheineman(a)godaddy.com> wrote: > >> Hi guys. I volunteered to be the spokesperson for the Urgent Request/LEA >> discussion with the GAC in Mumbai. Below is the start of talking points >> from Seb, even thought this will largely be a GAC lead. That being said, >> since you guys participate on the LEA group, could you kindly let me know >> if you think there is anything we should proactively add or question during >> the dialogue? Thanks in advance! >> >> >> >> - Urgent Request/LEA Agencies >> >> >> - TOPIC LEAD - Ashley Heineman >> - The GNSO expects the GAC/PSWG to lead this discussion. >> - The Practice Group had a question over jurisdiction [get >> question from Lawrence, Farzaneh or Anne who were there... I was too but >> frankly I don't remember] >> - We acknowledge the agreed need for discretion over this topic in >> public/on the mic and understand the limited disclosures PSWG will be able >> to offer on the topic. >> - We nevertheless hope to be able to get enough of an >> understanding to be able to, for example, assess the anticipated Policy >> work to frame the outcomes. >> >> >> >

2 4

FW: [Ext] NEW: A Preview of the ICANN85 Community Forum
by Julie Bisland Feb. 23, 2026

Feb. 23, 2026

FYI-- From: ICANN Community Digest <digest(a)icann.ccsend.com> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Monday, February 23, 2026 at 10:03 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] NEW: A Preview of the ICANN85 Community Forum [https://danh45uab.cc.rs6.net/on.jsp?ca=02c9a4ec-6ced-478e-90d7-fdecda32db81…] Monday, 23 February 2026 ICANN Community Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] 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=001ut5rJcx…> 2026 Round Applicant Guidebook [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ut5rJcx…> 2026 Round Vendor Sourcing Timeline [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ut5rJcx…> 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 · Prep Week Schedule · ICANN85 Schedule Now Available · PRSP Pre-ICANN85 Briefing · NEW: A Preview of the ICANN85 Community Forum Information Sharing · NEW: Press Release: ICANN CEO Highlights 2026 Domain Expansion Opportunities During Türkiye Visit · NEW: Chair’s Blog: Recap of the January Board Workshop · NEW: Kicking Off the Annual Strategy Review: Your Voice Matters 2026 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 🚨 · ICANN Request for Proposal: Geographic Names and Reserved Names Panelss · ICANNWiki Seeking Volunteers Public Comment · · TODAY: Latin Script Diacritics PDP Initial Report · Name Collision Procedure Documentation · Fundamental Bylaws Amendments on IANA-Related Reviews and CSC Charter Update · Standard Bylaws Amendment – Transition Article on Specific Reviews · Proposed Root KSK Algorithm Rollover Events · These events occur in February 2026. ICANN85 Register now [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ut5rJcx…> Prep Week Schedule [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ut5rJcx…> PRSP Briefing [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ut5rJcx…> ICANN85 Schedule [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ut5rJcx…> NEW: A Preview of the ICANN85 Community Forum Whether you are a longtime ICANN community member, an occasional contributor, or joining us for the first time, I encourage you to take an active role. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ut5rJcx…> Information Sharing NEW: Press Release: ICANN CEO Highlights 2026 Domain Expansion Opportunities During Türkiye Visit The discussion spanned Internet security, stability, and resilience, as well as the broader policy environment in which the Domain Name System operates. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ut5rJcx…> NEW: Chair’s Blog: Recap of the January Board Workshop The ICANN Board of Directors held its first workshop of 2026, marking a productive start to the year. We convened in Singapore from 23 to 25 January. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ut5rJcx…> NEW: Kicking Off the Annual Strategy Review: Your Voice Matters The annual strategy review is the process through which we ensure that the assumptions underpinning the Strategic Plan still hold, and to stay alert to emerging trends. Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ut5rJcx…> 2026 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=001ut5rJcx…>. Key Topic Overview Documents. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ut5rJcx…> 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=001ut5rJcx…>. 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=001ut5rJcx…>. 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=001ut5rJcx…> 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 ICANN Request for Proposal: Geographic Names and Reserved Names Panels Interested providers are invited to submit proposals that ICANN will then evaluate for capability and expertise. Because the work related to both panels is similar, ICANN intends to consolidate the work with a single provider. Deadline: 13 March 2026 Read more. [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ut5rJcx…> GNSO’s DNS Abuse Mitigation PDP-1 Observer Enrollment While the PDP membership is structured as a representative model, all of the ICANN community are also free to enroll as an Observer to follow the deliberations of the PDP. To enroll as an Observer, enrollments will be fielded through ICANN Join. If you have not used ICANN Join before, please follow the first-time user instructions below. Accessing ICANN Join does require having an ICANN Account. ICANN Join Instructions [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ut5rJcx…> 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=001ut5rJcx…>. 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=001ut5rJcx…> 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=001ut5rJcx…>source suggestions [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ut5rJcx…> on where to find reliable data. Happy editing! Public Comment TODAY: Latin Script Diacritics PDP Initial Report [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ut5rJcx…> Open for Submissions Date: Monday, 12 January 2026 Closed for Submissions Date: Monday, 23 February 2026 Name Collision Procedure Documentation [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ut5rJcx…> Open for Submissions Date: Thursday, 29 January 2026 Closed for Submissions Date: Monday, 16 March 2026 Fundamental Bylaws Amendments on IANA-Related Reviews and CSC Charter Update [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ut5rJcx…> Open for Submissions Date: Wednesday, 11 February 2026 Closed for Submissions Date: Monday, 30 March 2026 Standard Bylaws Amendment – Transition Article on Specific Reviews [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ut5rJcx…> Open for Submissions Date: Wednesday, 11 February 2026 Closed for Submissions Date: Monday, 30 March 2026 Proposed Root KSK Algorithm Rollover [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ut5rJcx…> Open for Submissions Date: Tuesday, 3 February 2026 Closed for Submissions Date: Monday, 6 April 2026 See upcoming proceedings [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ut5rJcx…>. See other public consultations [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ut5rJcx…>. Events These events occur in February 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=001ut5rJcx…>. · Virtual School on Internet Governance Course - Session on WISIS+20 · Connected Africa Summit 2026-Partners Breakfast Meeting · Domain Summit Africa 2026 · ITU-ATU-ICANN regional technical information session (online) dedicated to strengthening digital infrastructure in Africa · ICANN Webinar Series for EMEA: The Rise and Fall of Undelegated TLDs · Unlocking the Power of the Internet with a .Brand Domain Name · (NY)NUG · IX Fórum Regional Edição Sudeste - Ribeirão Preto / SP Volume 8, Issue 15 | Archive [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ut5rJcx…> | Next Issue: Thursday, 26 February 2026 STAY INFORMED: Subscribe here [danh45uab.cc.rs6.net]<https://urldefense.com/v3/__https:/danh45uab.cc.rs6.net/tn.jsp?f=001ut5rJcx…>

1 0

Draft letter summarizing recent SSAD dialogue with ICANN Board
by Caitlin Tubergen Feb. 23, 2026

Feb. 23, 2026

Dear Councilors, During the February 2026 GNSO Council meeting, Support Staff captured the following action item re: Next Steps for SSAD Recommendations: Council Leadership to propose a draft letter to send to the Board, summarizing the dialogue and emphasizing the message that the Council, in recommending the Board consider non-adoption of the SSAD recommendations, does not intend to throw any recommendations away, that it will complete the work in a timely manner (e.g., less than one year), and provide brief rationale for why the suggested path is preferable. Council Leadership is proposing this draft letter, which endeavors to include the above points, to be sent to the Board early next week prior to ICANN85: https://docs.google.com/document/d/1c3sgy18x3TR0VjOznwfRJVXns6dvAlHUM92L51B…. Deadline for review: If you have any comments or concerns on the draft, please provide them by Thursday, 26 February. Thank you. Best regards, Caitlin on behalf of Council Leadership

1 0

ICANN85 Policy Outlook Report
by Julie Bisland Feb. 23, 2026

Feb. 23, 2026

Dear All, I am happy to share the ICANN85 Policy Outlook report is now available for download! * Policy Outlook Report: https://go.icann.org/outlook85 Happy reading! With kind regards, Julie -- Julie Bisland Policy Operations Analyst (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

1 0

Review of Reviews update to GNSO
by Susan Payne Feb. 21, 2026

Feb. 21, 2026

Hi all further to Osvaldo's email of Monday, please see the below update from Osvaldo and Sophie. This has gone to SG/C chairs, so either they, o you, can share with your respective groups. Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:image001.png@01DCA0E7.196744C0] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0> From: Terri Agnew via GNSO-SG-C-Leadership <gnso-sg-c-leadership(a)icann.org> Sent: 18 February 2026 13:17 To: gnso-sg-c-leadership(a)icann.org Cc: Sophie Hey <sophie.hey(a)comlaude.com>; GNSO-Secs <gnso-secs(a)icann.org> Subject: [GNSO-SG-C-Leadership] Review of Reviews update to GNSO **Sent on behalf of Sophie Hey and Osvaldo Novoa, GNSO Reps on the Review of Reviews Team Dear all, We have set out an update on the work of the Review of Reviews Cross Community Group (CCG) ahead of ICANN85 and Prep Week. Please share this with your respective memberships. The work of the CCG is progressing well. We are on schedule to present a draft proposal of a future Reviews Program at ICANN85 for community input and feedback. As a reminder, our work plan has us presenting a final proposal to the community at ICANN86, so now is the time to start paying attention and sharing input if you haven't already! As of now, the CCG will be proposing five reviews: CIP Assessment, Structural Review, Review of Reviews, Ad Hoc Review, and Accountability & Transparency/Bucket A. Please note, there are options for the objectives of the Accountability & Transparency/Bucket A, and Structural Review, and the CCG will be specifically seeking input on whether the community has a preference between these options. For those that are interested, the early version of our draft proposal is available here https://docs.google.com/document/d/1bNrRxa2-BuO5SOjg9-mAfKmj8VhKydrBu3Kfq-J… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1bNrRxa2-BuO5…>. We ask that you do not provide comments directly into the document, as it is a working document for the CCG. Rather, please share any input you have via the inputonreviews(a)icann.org<mailto:inputonreviews@icann.org> mailing list. We have already received some input via the mailing list, from both individuals and groups, which we have been considering during our regular meetings - you can view the mailing list archives here https://lists.icann.org/hyperkitty/list/inputonreviews@icann.org/ [lists.icann.org]<https://urldefense.com/v3/__https:/lists.icann.org/hyperkitty/list/inputonr…>. This has also included the sender of the input speaking to the CCG, which we are also using to remind you all that the CCG has a very flexible Observer policy (sign up here https://icann-community.atlassian.net/wiki/spaces/CDOR/pages/464355519/Obse… [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/space…>). As a reminder, if you don't share your input with the CCG, it can't be considered by the CCG. In preparation for ICANN85, we suggest that you and your groups consider the following questions: 1. Do you agree with the objectives and purpose of the proposed reviews set out in the table? Would you suggest any changes or clarifications? 1. Are any reviews missing from the table, or is a review included that should not be? 1. Is there anything in the table that does not make sense to you, and you want more clarity on? Note, these questions are not exhaustive but are intended to serve as prompts for your analysis and feedback on the draft to the CCG. If you would like either of us (or one of the CCG co-chairs) to join your SG/C meetings at ICANN85 to discuss the proposal in more detail and answer questions, please let us know. Osvaldo and Sophie ________________________________ 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 1

Draft Minutes of the GNSO Council Meeting 12 February 2026
by John Emery Feb. 21, 2026

Feb. 21, 2026

Dear Councilors, Attached, please find the draft minutes of the GNSO Council Meeting held on 12 February 2026. If there are no comments, these minutes will be published on the website as approved, according to the GNSO Rules of Procedure <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> section 3.5: "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting" on 3 March. Thank you, John R. Emery, Ph.D. Policy Development Support Senior Specialist Generic Names Supporting Organization (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0