- Gnso-spirt - lists.icann.org

Updated Change Log
by Jared Erwin June 10, 2026

June 10, 2026

Dear SPIRT Members, I’m writing to notify you of three changes that have been posted to the Change Log<https://icann-community.atlassian.net/wiki/x/LIC9Lg>: * One (1) Type 0<https://icann-community.atlassian.net/wiki/spaces/SPIRTS/pages/784171052/6.…> (Typographical) Change (#39) * Two (2) Type 1<https://icann-community.atlassian.net/wiki/spaces/SPIRTS/pages/784171052/6.…> (Minor) Changes (#6, 7) The changes are described in the Change Log, but I’ve attached a redline version of the AGB (PDF) where you can see the changes in context. As noted on the Change Log and in the SPIRT Charter, “the SPIRT shall review the decision through the Change Log and take no more than three (3) calendar days to provide guidance if it disagrees with the decision.” Given the timing of this email, I have put the SPIRT Guidance as due by 14 June 2026 (3 calendar days from 11 June 2026). Time permitting, I will also briefly go over these in our scheduled meeting tomorrow<https://icann86.sched.com/event/2NQRY/gnso-next-round-spirt>, 11 June 2026. Thank you and talk to you tomorrow, Jared -- Jared Erwin Senior Director, New gTLD Program Global Domains & Strategy (GDS) Internet Corporation for Assigned Names and Numbers (ICANN) jared.erwin(a)icann.org<mailto:jared.erwin@icann.org>

1 0

GNSO Council Referral of RSP Issue to the SPIRT
by Lawrence O. Olawale-Roberts June 10, 2026

June 10, 2026

Dear SPIRT Members, In my capacity as GNSO Council Liaison to the SPIRT, I would like to inform the SPIRT that the GNSO Council voted and passed a motion during its meeting today, 10 June 2026, to refer the RSP issue discussed during its May meeting<https://icann-community.atlassian.net/wiki/x/MoA_J> to the SPIRT. Per the Applicant Guidebook Predictability Framework<https://newgtldprogram-2026-agb.icann.org/en/17-appendix-6-predictability-f…>, the SPIRT is now tasked with determining whether a change to the ongoing round is required. We look forward to meeting tomorrow to start discussing this issue and informing the GNSO council of the outcome of our discussions evolve. Do let me know if you have any questions. Sincerely, Lawrence Olawale-Roberts, GNSO Council Liaison to the SPIRT ----- [Image] [Image] Lawrence Olawale-Roberts Global President & Managing Director Mobile: +234 8070892705, (0)8056 3333 97 Lawrence(a)microboss.org<mailto:Lawrence@microboss.org> [Image] [Image] …collaboration to enhance communication. [Image] https://www.microboss.org<https://www.microboss.org/> | [Image]<https://www.facebook.com/microbosstech/> [Image]<https://www.linkedin.com/company/microbosstech/> [Image]<https://mobile.twitter.com/microbosstech> [Image]<https://www.instagram.com/microbosstech/?hl=en> [Image]<https://www.youtube.com/@microboss> This e-mail and any attachments are confidential and may be protected by legal, professional or other privilege. If you are not the intended recipient, you should not store it, copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. The views expressed are those of the sender and his company MicroBoss. Kindly note that whilst we scan all e-mails for viruses, we cannot guarantee that any e-mail is virus-free. | Do consider the environment before printing this email.

2 1

GNSO Council Resolution on Referrals to SPIRT.
by Lawrence O. Olawale-Roberts June 7, 2026

June 7, 2026

Dear Members, At the last council meeting held on the 21st of May 2026, the process by which the GNSO Council would refer a matter to the SPIRT was discussed. Council resolved that there was general agreement that decisions to refer issues to the SPIRT should be taken by a vote of the Council and will include any instructions that the Council wishes to give to the SPIRT. In the case the issue requiring review where to be time-sensitive, Council will use mechanisms such as email process for voting, to make decisions as promptly as possible. Council wishes to thank all SPIRT members for the good job done so far, and for the patience granted Council to evolve its referral process for issues mandating SPIRT’s attention. Warm regards, Lawrence Olawale-Roberts Council Liaison. ----- [Image] [Image] Lawrence Olawale-Roberts Global President & Managing Director Mobile: +234 8070892705, (0)8056 3333 97 Lawrence(a)microboss.org<mailto:Lawrence@microboss.org> [Image] [Image] …collaboration to enhance communication. [Image] https://www.microboss.org<https://www.microboss.org/> | [Image]<https://www.facebook.com/microbosstech/> [Image]<https://www.linkedin.com/company/microbosstech/> [Image]<https://mobile.twitter.com/microbosstech> [Image]<https://www.instagram.com/microbosstech/?hl=en> [Image]<https://www.youtube.com/@microboss> This e-mail and any attachments are confidential and may be protected by legal, professional or other privilege. If you are not the intended recipient, you should not store it, copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. The views expressed are those of the sender and his company MicroBoss. Kindly note that whilst we scan all e-mails for viruses, we cannot guarantee that any e-mail is virus-free. | Do consider the environment before printing this email.

4 3

AGENDA | SPIRT Meeting | 11 June 2026 at 14:30 UTC
by Andrew Chen June 4, 2026

June 4, 2026

Dear SPIRT Members, Please find below the proposed agenda for the Standing Predictability Implementation Review Team (SPIRT) meeting taking place in Seville, Spain at ICANN86 on Thursday, 11 June 2026 at 14:30 UTC. Agenda: 1. Welcome 2. SOI/SOP Updates 3. GNSO Council Liaison Update 4. SPIRT Discussion 5. ICANN org Updates 6. AOB 7. 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/

1 0

ICANN86 Policy Outlook Report / GNSO Chair Blog
by Julie Bisland June 2, 2026

June 2, 2026

Dear All, On behalf of the GNSO Team, I am happy to share the ICANN86 Policy Outlook Report and the GNSO Chair Blog: * GNSO Chair Blog: https://www.icann.org/en/blogs/details/the-gnso-council-welcomes-you-to-ica… * Policy Outlook Report: https://go.icann.org/outlook86 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

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