May 2026 - Gnso-spirt - lists.icann.org

Fwd: Acknowledgment of SPIRT Alert Re: Prohibition on Private Resolution of New gTLD Contention Sets
by Heather Diaz May 20, 2026

May 20, 2026

Dear SPIRT Council, In the spirit of transparency, I am sharing the attached Alert that I submitted for consideration on 12 May. In hindsight, I noticed this submission was not shared with the full Council in the same manner as previous alerts, though it was acknowledged by Andrew Chen and the SPIRT Leadership Team (LT). For context, our Chair, Jeff Neuman, responded to the submission by stating that, for openness and transparency, he would recuse himself from offering opinions due to a client conflict. He ultimately deferred handling of the issue to Cheryl and Segunfunmi. Receiving no follow-up questions from Cheryl or Segunfunmi, I anticipated—consistent with our prior submission process—that the group would be openly informed and that we would discuss the matter during our upcoming call on 21 May. However, yesterday I received the following email from Andrew Chen: Thank you for your patience as the SPIRT leadership team (SPIRT LT) deliberated on your submission regarding the Prohibition on Private Resolution of New gTLD Contention Sets. Given the recent GNSO Council discussions on the mailing list concerning the SPIRT alert process, the SPIRT LT believes that this submission should be submitted to the GNSO Council through a GNSO Councilor for further discussion. The SPIRT LT notes that it may be more expedient to request a GNSO Councilor to submit this issue to the GNSO Council for consideration. We apologize for any inconveniences this may have caused. Please let us know if you have any questions. Sincerely, Andrew Exactly 22 minutes after receiving this email, a cancellation notice was issued for our 21 May Council call, stating it was no longer required. I find it disappointing and concerning that this submission was not treated with the same openness and transparency as the one preceding it. Allowing submissions to be handled exclusively by the LT without visibility or clear rationale provided to the full Council undermines our collaborative process. Furthermore, this lack of transparency appears inconsistent with ICANN Bylaws, which require an explicit rationale for decisions to ensure fairness and procedural integrity across all supporting committees, including the SPIRT. As echoed in previous correspondence on this list, we should seek to further formalize the operations of this group—especially around submission handling and communications regarding LT decisions—to ensure we operate with the highest possible level of openness and transparency. Best regards, Heather Diaz Vice President, Compliance and Policy fTLD Registry - .Bank | .Insurance Office: +1 408 316 7202 www.fTLD.com Schedule a meeting with me <https://meetings.hubspot.com/heather-diaz> ---------- Forwarded message --------- From: Andrew Chen <andrew.chen(a)icann.org> Date: Wed, May 13, 2026 at 6:33 PM Subject: Acknowledgment of SPIRT Alert Re: Prohibition on Private Resolution of New gTLD Contention Sets To: heather(a)ftld.com <heather(a)ftld.com> Cc: Jeff Neuman <jeff(a)jjnsolutions.com>, Segunfunmi Olajide < olajidesegunfunmi(a)gmail.com>, Cheryl Langdon-Orr <langdonorr(a)gmail.com>, lawrence(a)microboss.org <lawrence(a)microboss.org>, Olawale-Roberts Lawrence < lawrenceog(a)yahoo.com>, Steve Chan <steve.chan(a)icann.org>, Saewon Lee < saewon.lee(a)icann.org> Dear Heather, Thank you for your SPIRT Alert submission regarding the Prohibition on Private Resolution of New gTLD Contention Sets. We are acknowledging the receipt of this alert submission, which has been shared with the SPIRT Leadership Team. I have attached a copy of your submission for your records. Sincerely, Andrew -- Andrew Chen Policy Development Support Sr. Specialist, Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org/ ---- Secured by Paubox - HITRUST certified https://www.paubox.com ----

2 2

CANCELLATION | SPIRT Meeting | 21 May 2026 at 13:00 UTC
by Andrew Chen May 19, 2026

May 19, 2026

Dear SPIRT Members, We would like to inform you that the SPIRT meeting scheduled for Thursday, 21 May 2026 at 13:00 UTC has been cancelled. Please note, meetings are to take place every other week and may be cancelled if there are no issues to discuss or updates to the change log. Ad-hoc meetings may take place if necessary. Items pending GNSO Council approval are still being discussed and may be forwarded to the SPIRT at a later date for discussion. The next SPIRT meeting is scheduled to take place on 11 June 2026 at 14:30 UTC. Sincerely, Andrew -- Andrew Chen Policy Development Support Sr. Specialist, Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org/

1 0

ICANN86 GNSO Sessions - How to Get Organized / Remote Participation Details
by Julie Bisland May 13, 2026

May 13, 2026

Dear all, With ICANN86<https://meetings.icann.org/en/meetings/icann86/> just around the corner, please take a moment to read the information below for a seamless and successful meeting. ICANN86 key dates: * Prep Week will take place virtually 20 & 21 May 2026. * Deadline for IN-PERSON registration is 07 June 2026. * ICANN86 will take place in Seville 08 - 11 June 2026. On-site registration will not be available. Registration for ICANN86 does not automatically create a user account on sched.com. Instructions and guides to register as well as personalize your schedule can be found on these pages: * Visit this page to REGISTER: https://meetings.icann.org/en/meetings/icann86/ * General information about Seville, hotels, transportation and rates, and links to food options can also be found here * The ICANN86 Schedule: https://icann86.sched.com/ * Instructions for personalizing your schedule can also be found here There will be no calendar invitations sent, as the meeting schedule allows you to download all sessions of interest to your individual calendars A reminder to review the Participation Tools page and update Zoom * All sessions that use Zoom rooms, access details will be available 24hrs prior. * Visit the Participation Tools page<https://meetings.icann.org/en/remote-participation> for links to download the latest version of Zoom for access to the ICANN Meeting sessions. * Please see the ICANN Meeting VIRTUAL AND IN-PERSON PARTICIPATION GUIDES in the blue box on the right side of the Participation Tools page for more information on how to get the most out of the virtual meeting tools. * If participating on-site, please read the Frequently Asked Questions here<https://meetings.icann.org/en/meetings/icann86/#faq>. Links to Bookmark ICANN86 Meeting Schedule<https://icann86.sched.com/> ICANN86 GNSO Remote Participation Wiki Page<https://icann-community.atlassian.net/wiki/x/AQB0Og> GNSO Session agendas<https://icann-community.atlassian.net/wiki/x/AYBUOg> For all GNSO meeting-related queries, please email us at: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team -- 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

Re: SPIRT Notification re ASP Financial Need Eligibility Criteria
by Andrew Chen May 13, 2026

May 13, 2026

Dear SPIRT Members, Thank you for reviewing the Applicant Support Program Financial Need Eligibility Criteria issue shared with the SPIRT on 4 May 2026<https://lists.icann.org/hyperkitty/list/gnso-spirt@icann.org/thread/524PYBR…> and discussed during the 7 May 2026 SPIRT meeting<https://icann-community.atlassian.net/wiki/x/KAAvLw>. As noted in the SPIRT Charter<https://gnso.icann.org/sites/default/files/policy/2025/draft/version2point0…>, “When ICANN org notifies the SPIRT of the type of change considered by ICANN org, the SPIRT shall endeavor to provide guidance, if any, within seven (7) calendar days or as otherwise required to maintain the operation of the Program if it disagreed with the Decision”. As 7 calendar days have passed since the change request was shared by ICANN org and no objections or additional guidance has been received, the SPIRT Leadership Team notes that the change request regarding ASP Financial Need Eligibility Criteria has been approved. Sincerely, Andrew on behalf of the SPIRT Leadership Team -- Andrew Chen Policy Development Support Sr. Specialist, Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org/ From: Jared Erwin via Gnso-spirt <gnso-spirt(a)icann.org> Reply-To: Jared Erwin <jared.erwin(a)icann.org> Date: Monday, May 4, 2026 at 11:40 AM To: "gnso-spirt(a)icann.org" <gnso-spirt(a)icann.org> Cc: Kristy Buckley <kristy.buckley(a)icann.org>, Samantha Mancia <samantha.mancia(a)icann.org> Subject: [Gnso-spirt] SPIRT Notification re ASP Financial Need Eligibility Criteria Dear SPIRT Members, On behalf of the Applicant Support Program (ASP) team, please find attached a notification for a proposed solution regarding the ASP Financial Need Eligibility Criteria. As requested in the paper, please provide guidance within 7 calendar days, including whether the SPIRT believes additional time is needed to come to an agreement on the proposed solution. ICANN requests that the SPIRT provide any feedback on list by 11 May 2026. Thank you, Jared — Jared Erwin Senior Director, New gTLD Program ICANN jared.erwin(a)icann.org

1 0

Potential improvements for consideration
by Nefertiti Marquez May 9, 2026

May 9, 2026

Dear Team, Thank you for the recent meeting and the discussions that took place. I would like to raise a few points for consideration regarding potential improvements to certain mechanisms within the group, and I welcome any comments or feedback on these suggestions. 1. The Process of Support and Voting There is no doubt that the group may benefit from considering more structured methods of expressing support beyond chat messages or document comments, as these can later be misunderstood, particularly when several items are being addressed simultaneously. It could be beneficial for supportive comments to be collected in a single, clearly accessible place. Possible solutions might include “aye” voting or voting “on behalf of,” similar to the practices used within the Council, although this may prove challenging given the attendance observed so far. Another option could involve the use of polling mechanisms. At the same time, comments or objections should continue to be welcomed when openly expressed during meetings or directly within the documents. 2. Forwarding Team Issues to the Council Based on my observations, I believe there may be a need for a ratification process for documents before they are forwarded to the Council. The SPIRIT issues Consideration Process might therefore need a clarification expressed between the points 3 and 4 related to the process of document phrasing acceptance. Certain statements may require a final team review to ensure that the wording is appropriate and to avoid potential objections or misunderstandings. The Team should therefore have the opportunity to provide concrete feedback on the final documentation before it is submitted to the Council. While this may require additional time, it would help ensure a smoother process and reduce the likelihood of concerns and objections arising from the wording of the final document. My intentions are based solely on observations of the group dynamics and are offered in the spirit of helping the Team find common ground and supporting smooth cooperation. Any comments or suggestions are, of course, more than welcome. Best regards, Nefertiti Sent from Outlook for iOS<https://aka.ms/o0ukef>

2 2

SPIRT Notification re ASP Financial Need Eligibility Criteria
by Jared Erwin May 9, 2026

May 9, 2026

Dear SPIRT Members, On behalf of the Applicant Support Program (ASP) team, please find attached a notification for a proposed solution regarding the ASP Financial Need Eligibility Criteria. As requested in the paper, please provide guidance within 7 calendar days, including whether the SPIRT believes additional time is needed to come to an agreement on the proposed solution. ICANN requests that the SPIRT provide any feedback on list by 11 May 2026. Thank you, Jared — Jared Erwin Senior Director, New gTLD Program ICANN jared.erwin(a)icann.org

2 2

Issue #1 under SPIRT Issues Consideration Process - RSP Evaluation Change Request
by Jeff Neuman May 8, 2026

May 8, 2026

Dear SPIRT, Please find attached an issue submitted by a member of the SPIRT for the Leadership Teams review and consideration. A short summary is below: *Summary of submission* - *Submitted by:* Jeff Neuman on behalf of the RySG - *Aspect of the New gTLD Program Impacted*: Registry Service Provider Evaluation - *Change Type*: Non-minor Operational Change (Type 2) - *GNSO Council Urgency*: Non-Urgent (i.e. Standard Response) - *Material Impact*?: Yes - *Type of Material Impact*: Has a non-trivial monetary or operational impact on applicants In accordance with the SPIRT Issues Consideration Process <https://docs.google.com/document/d/1zITIUCB5yvjV_Rj5Z87ljyqajA5VliMSPvPb77A…>, the Leadership team met today and discussed the proposed issue. We determined that the issue* is within scope *for the SPIRT with one small exception. In the "Note" section at the end of the "Summary of the Issue impacting this New gTLD Program" (Page 3 of 6), the RySG asks the SPIRT to consider recommending that the requested changes apply retroactively to RSPs that have already undergone RSP Pre-Evaluation. SPIRT Leadership did not believe that looking at issues requiring retroactive changes was within the scope of the SPIRT, but we wanted to bring that issue to the full working group to see if there is consensus on that point. This topic will be added to Thursday's agenda (May 7th). The hope *is to refer this issue to the GNSO Council by May 8th at the latest.* We understand the tight turnaround, but remember that at the meeting, we are only trying to determine if we should send the issue to the Council so it can officially "raise the issue" with the SPIRT, allowing us to commence our work. We will only discuss the substance of the issue to ensure that the SPIRT members understand the topic, not to discuss solutions for the issues presented. That said, this email intends to kick off those discussions. Sincerely, Jeff Neuman SPIRT Chair -- ***Please Note that JJN Solutions, LLC is now JJN Solutions Law, PLLC*** [image: image.png] Jeffrey J. Neuman Founder & CEO JJN Solutions Law, PLLC +1.202.549.5079 Jeff(a)jjnsolutions.com https://www.jjnsolutions.com *This email and any attachments are intended only for the person or entity to which they are addressed and may contain confidential and/or privileged information. If you are not the intended recipient, you may not review, use, disclose, or distribute this message. If you received this email in error, please notify the sender immediately and delete it from your system.* *Nothing in this email is intended to create, and receipt does not establish, an attorney-client relationship unless expressly agreed in writing by JJN Solutions Law, PLLC. Any legal advice contained in this communication is provided solely for the client identified and may not be relied upon by any other person.*

3 3

Notes and Action Items | SPIRT Meeting | 07 May 2026 at 20:00 UTC
by Saewon Lee May 8, 2026

May 8, 2026

Dear SPIRT, Please see the following key outcomes, action items, and high-level notes from today’s SPIRT Meeting #6<https://icann-community.atlassian.net/wiki/x/KAAvLw>. Kind regards, Saewon Key Outcomes, Action Items, and Notes from SPIRT Meeting #6<https://icann-community.atlassian.net/wiki/x/KAAvLw> – Thursday, 7 May 2026 at 20:00 UTC. [KEY OUTCOME] * General Support from the SPIRT Members on ICANN org’s categorization (Type 2: Non-minor operational change) and proposed solution regarding the ASP Financial Need Eligibility Criteria [To be confirmed by 11 May] [ACTION ITEMS] 1. Ongoing: All SPIRT Members to update their SOIs in accordance with the SOP. 2. LT to issue a 24-hour objection call to the mailing list on the issue regarding RSP submitted by Jeff Neuman. [COMPLETE] 3. SPIRT Members to review the issue regarding RSP submitted by Jeff Neuman and share any suggestions or concerns, objections or support in the next 24 hours (by Friday, 8 May 2026 at 22:00 UTC) via mailing list. 4. SPIRT Members to further weigh in on the ICANN org issue regarding ASP Financial Need Eligibility Criteria. [NOTES] * Retrieve slides from here: https://icann-community.atlassian.net/wiki/x/KAAvLw 1. Welcome o TLD Application Management System (TAMS) is now open and running – congratulations to all! 1. SOI/SOP Updates o See Members List and SOI/SOP updates in the wiki here: https://icann-community.atlassian.net/wiki/x/AQCJHQ [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/AQC…> 1. SPIRT Issue for Consideration * See the SPIRT Issue Consideration Process here: https://icann-community.atlassian.net/wiki/x/AYCJHQ 1. RySG issue for consideration by SPIRT: Summary of issue in slide 7<https://icann-community.atlassian.net/wiki/x/KAAvLw> (re RSP Evaluation/Type 2 – Non-minor Operational Change/Non-urgent/has a non-trivial monetary or operational impact) and original (updated) message here<https://docs.google.com/document/d/1CPtqQL9hZvoIkQsh6Z3bwzDxGgRdXgiYlW_0BMA…> – We are testing out the SPIRT Issue Consideration Process for the first time. LT discussed the issue and considered it to be within scope and thus, forwarded it to the SPIRT for discussion. * High-level summary of requested change: Revising the RSP Handbook to align it with the Base RA; clarifying that any response does not impact the evaluation and to update the corresponding RST requirements to reflect this change. Also, SPIRT to also consider whether it should be applied retroactively to RSPs that have already passed the RSP Evaluation. * SPIRT LT believes that the SPIRT may not have jurisdiction to make retroactive changes to the New gTLD Program; only to consider changes moving forward. * This issue can be forwarded to the GNSO Council in the absence of non-objection within the SPIRT. * Feedback from SPIRT Members: * Christabel Mebaghandu: Question and Objection based on the Council Response process not having been confirmed by Council – only would like to move forward with this when and once this is confirmed by Council, since it may not be within the remit of SPIRT at this time. LT noted that there are 2 points/paths to consider – distinguishing the difference between the process that has been confirmed by the SPIRT and the response mechanism that the Council will be voting on in May – and that Council’s approval issue should not affect the SPIRT from discussing this issue today and/or alerting Council of this issue. Agreed to respond back to this point and any further objections via text/language on mailing list. * Phil Buckingham: No issue with sending the issue to Council through the SPIRT Issue Consideration Process which is a "proactive" alert mechanism. Council’s response is out of remit for SPIRT. * Heather Diaz: Agree with the discussion to move ahead within SPIRT. However, objects to the “outcome-based solutions” approach since this may be a step too far at this point. Noted that the request could be reframed. * Maxim Alzoba: Raised a suggestion to create an “objection” method seeking text/language from SPIRT Members specifying the rationale and how to mitigate the issue. * SPIRT Members to review the current issue regarding RSP submitted by Jeff Neuman and to share any suggestions or concerns, objections or support in the next 24 hours (by Friday, 8 May 2026 at 22:00 UTC) via mailing list. * Action Item: SPIRT Members to review the issue regarding RSP submitted by Jeff Neuman and share any suggestions or concerns, objections or support in the next 24 hours (by Friday, 8 May 2026 at 22:00 UTC) via mailing list. 1. ICANN org Issue for SPIRT Consideration – Non-minor Operational Change (Type 2): Summary of Issue is uploaded in Change Log<https://icann-community.atlassian.net/wiki/x/LIC9Lg> and shared via mailing list on 4 May (re ASP Financial Need Eligibility Criteria). * Proposed solution: Considering different funding environments and inflation, to include a buffer to the financial need not to exceed $5 mill. and provide guidance to the Support Applicant Review Panel (SARP) to allow for allowance of up to 15% above the threshold. To date, there is no impact on any outcomes since no applicants have been disqualified due to not meeting the criteria. * Seeking guidance from SPIRT within 7 calendar days (by 11 May) and get a decision as soon as possible so as not to hold up the Program. * If SPIRT opposed to this proposed change, the alternative that could be considered is to default back to the original rule. * Question on $5mill. limit. Noted that the ASP IRT set the number. No global standard existed at the time and was set as a compromise after considering various numbers. * Question on the type of change category, i.e., why not policy? Noted that the $ amount was not guided within the SubPro Report, but this was specified during implementation and AGB, which went through Public Comment. * Feedback from SPIRT Members: * Alan Greenberg: Agree to the change and proposed solution which sounds reasonable; the number was probably set as to what may be reasonable, thus flexibility is allowed to not exclude an entity from support. GDS Staff noted that exchange rate was in consideration. * Heather Diaz: Support the change. * Phil Buckingham: Support the increase in the buffer. * Other supports: Mark Wilson, Denise Hochbaum, Henry Chan, Maxim Alzoba, Nefertiti Marquez, Anil Kumar Jain. * A suggestion was raised that with all members of the SPIRT not represented today that all feedback should be considered within the 7-day period. The SPIRT LT noted that this issue has already been shared through the mailing list since 4 May and posted on the Change Log. Either way, if via the list members request extra time, this can be discussed with ICANN org. * LT asks the SPIRT Members to weigh in by providing feedback via mailing list as well. * Outcome: General Support from the SPIRT Members on ICANN org’s categorization (Type 2: Non-minor operational change) and proposed solution regarding the ASP Financial Need Eligibility Criteria [To be confirmed by 11 May] * Action Item: SPIRT Members to further weigh in on the ICANN org issue regarding ASP Financial Need Eligibility Criteria. 1. Updates from the Next Round Team * A line has been added to the Change Log<https://icann-community.atlassian.net/wiki/x/LIC9Lg> per Justine’s suggestion on which version of the AGB the items are incorporated into. 1. AOB o The 2026 Round is currently running smoothly. 1. Upcoming Meetings and Close of Meeting o Upcoming Meeting: 21 May 13:00 UTC o Council’s May Meeting is on the same day – 21 May 05:00 UTC – but earlier than SPIRT Meeting where we will get to know the result of the Council vote regarding the response mechanism. o SPIRT will have a session in ICANN86 in Seville. From: Andrew Chen via Gnso-spirt <gnso-spirt(a)icann.org> Reply-To: Andrew Chen <andrew.chen(a)icann.org> Date: Tuesday, May 5, 2026 at 1:00 PM To: Jared Erwin via Gnso-spirt <gnso-spirt(a)icann.org> Cc: GNSO-Secs <gnso-secs(a)icann.org> Subject: [Gnso-spirt] [SPIRT] AGENDA | SPIRT Meeting | 07 May 2026 at 20:00 UTC Dear SPIRT Members, Please find below the proposed agenda for the Standing Predictability Implementation Review Team (SPIRT) meeting on Thursday, 07 May 2026 at 20:00 UTC. Agenda: 1. Welcome 2. SOI/SOP Updates 3. SPIRT Issue for Consideration 4. Updates from the Next Round Team 5. AOB 6. Upcoming Meetings and Close of Meeting We would like to remind participants that to ensure transparency of participation in ICANN's multistakeholder model, we ask that you sign in to Zoom sessions using your full name. For example, First Name and Last Name or Surname. You may be removed from the session if you do not sign in using your full name. Please do not hesitate to contact us should you have any questions. Sincerely, Andrew -- Andrew Chen Policy Development Support Sr. Specialist, Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org/

3 2

[Review Requested] 24 Hour review of SPIRT issue concerning RSP
by Andrew Chen May 7, 2026

May 7, 2026

Dear SPIRT Members As discussed on today’s call (07 May 2026<https://icann-community.atlassian.net/wiki/x/KAAvLw>), please review the SPIRT issue concerning RSP submitted by Jeff Neuman. Please share any concerns, objections, support, or suggestions by tomorrow, 08 May 2026 at 22:00 UTC. SPIRT Issue Submission: https://docs.google.com/document/d/1CPtqQL9hZvoIkQsh6Z3bwzDxGgRdXgiYlW_0BMA… Thank you for your review and consideration. Sincerely, Andrew on behalf of the SPIRT Leadership Team -- Andrew Chen Policy Development Support Sr. Specialist, Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org/

1 0

Post Call | Standing Predictability Implementation Review Team (SPIRT) | Thursday, 07 May 2026
by Julie Bisland May 7, 2026

May 7, 2026

Dear all, All recordings for the Standing Predictability Implementation Review Team (SPIRT) call held on Thursday, 07 May 2026 at 20:00 UTC can be found on the agenda wiki page <https://icann-community.atlassian.net/wiki/x/KAAvLw> . You can also access via the GNSO Calendar 2026<https://gnso.icann.org/en/group-activities/calendar/2026>. Agenda wiki page includes: * Attendance * Audio recording * Zoom recording (including audio, visual, rough transcript, and chat.) * Agenda and Notes/Action Items For additional information, you may consult the mailing list archives<https://lists.icann.org/hyperkitty/list/gnso-spirt@icann.org/> and the main wiki page<https://icann-community.atlassian.net/wiki/x/nwB2HQ>. Thank you. Kind regards, Julie Policy Team Supporting the GNSO

1 0