- Gnso-spirt - lists.icann.org

CANCELLATION NOTICE for 18 June 2026
by Saewon Lee June 17, 2026

June 17, 2026

Dear SPIRT Members, Further to Jeff's email on informing ICANN org of the RSP issue determination by the SPIRT, this is to inform you that the meeting scheduled for tomorrow, 18 June 2026 at 13:00 UTC, has been CANCELLED. Accordingly, meeting cancellations have been sent out already. Please note that pursuant to Action Item 3 from the SPIRT session during ICANN86, more updates concerning meeting cancellations or invitations for July will be communicated as soon as feasible. Kind regards, Saewon Get Outlook for Mac<https://aka.ms/GetOutlookForMac>

1 0

ICANN Org ACTION REQUIRED: FORMAL NOTIFICATION - RSP Issue Referred by GNSO Council
by Jeff Neuman June 17, 2026

June 17, 2026

Dear Jared and Marika, On 10 June 2026, the GNSO Council referred to SPIRT an issue concerning a misalignment between the RSP Pre-evaluation process and the new base Registry Operator Agreement (Base RA) for the 2026 round of new gTLDs. Specifically, while the Base RA no longer requires registry operators to use only EPP extensions registered with IANA, the RSP Pre-evaluation questions still require RSP applicants to attest that they will use only IANA-registered EPP extensions, a requirement that is also tested during Registry System Testing. As a result, the obligation currently placed on RSPs is misaligned with the obligation under the Base RA. After initial discussion, SPIRT concluded on 11 June 2026, at ICANN 86, that this issue must be addressed by ICANN org and SPIRT under the Predictability Framework set forth in the 2026 final Applicant Guidebook. SPIRT further concluded that addressing the issue requires a non-minor change to the New gTLD Program, consistent with existing Board-approved policy recommendations, and that such a change would have a material impact on Applicants, meaning ICANN org and SPIRT "have to agree on a permanent solution." Per Appendix 6 of the Applicant Guidebook, "If an agreement is not reached within 30 days, or more urgent action is necessary to the operation of the program, ICANN can implement a temporary solution to be replaced with the solution of ICANN and SPIRT once agreed." SPIRT members had until 23:59:59 UTC on 16 June 2026, to register support or objection to two questions: (1) whether addressing this issue requires a non-minor operational change to the Program, and (2) whether such a change would have a material impact on Applicants. All members who responded confirmed agreement with the June 11 conclusions, and no member objected. Accordingly, in accordance with the Predictability Framework, SPIRT is formally notifying ICANN org "that a change to the ongoing round of the New gTLD Program may be required." The supporting rationale is set out in SPIRT leadership's original request of May 5, 2026 (available here <https://lists.icann.org/hyperkitty/list/gnso-spirt@icann.org/thread/FWYNI2R…> ). Under the Predictability Framework, the question now before ICANN org is: "Does org determine that a change to the ongoing round of the Program is indeed required?" If the answer is yes, SPIRT will Collaborate with ICANN org to develop a solution. At its June 11 meeting, SPIRT requested that ICANN org provide this answer no later than July 3, 2026, so that at least a temporary solution can be developed and announced before the RSP application window closes on 12 August 2026. Please let us know as soon as possible whether ICANN org will be able to respond by 3 July. If not, please propose an alternate date, bearing in mind that RSP Applicants are best served by receiving notice as early as possible ahead of the close of the RSP Application Window. A draft timeline for resolving this issue is attached for your reference. *PROPOSED TIMELINE* 17 June 2026: ICANN org provided notice that a change to the ongoing round may be required 03 July 2026: ICANN org responds to SPIRT stating that a change is indeed required 6 July 2026 – 31 July 2026: ICANN org and SPIRT collaborate on solution (temporary if necessary) 05 Aug. 2026 – ICANN announces change to ongoing round implementing temporary/permanent solution 12 Aug. 2026 – Application Window closes for both RSP applicants and Registry Operator Applicants Best Regards, Jeff Neuman, SPIRT Chair ***Please Note that JJN Solutions, LLC is now JJN Solutions Law, PLLC*** * Jeffrey J. Neuman* Founder & CEO *JJN Solutions Law, PLLC* +1.202.549.5079 *Jeff(a)jjnsolutions.com <Jeff(a)jjnsolutions.com>* *https://www.jjnsolutions.com <https://www.jjnsolutions.com>*

3 2

Key Outcomes and Action Items from SPIRT Session during ICANN86
by Saewon Lee June 16, 2026

June 16, 2026

Dear SPIRT, Please see the following key outcome and action items from today’s SPIRT Meeting during ICANN86<https://icann86.sched.com/event/2NQRY/gnso-next-round-spirt>. [KEY OUTCOME] * SPIRT Members to review the Registry Service Provider (RSP) issue that has been referred by the GNSO Council and respond within 5 calendar days if any objections. * [ACTION ITEMS] 1. Ongoing: All SPIRT Members to update their SOIs in accordance with the SOP. 2. SPIRT Members to review the RSP issue and voice objections or concerns via the SPIRT mailing list by Tuesday, 16 June 2026, at 23:59 UTC (5 calendar days) if they determine that a change to the ongoing round is not required. 3. GNSO Support Staff to reorganize the next set of SPIRT Meetings for June-July and send calendar invites, as necessary. Safe travels back home! Kind regards, Saewon Get Outlook for Mac<https://aka.ms/GetOutlookForMac>

12 15

Re: Key Outcomes and Action Items from SPIRT Session during ICANN86
by Nitin Walia June 16, 2026

June 16, 2026

+1 I support the change required to the next Round Base Registry Agreement. Warm RegardsNitin WaliaDirectorData Ingenious Globalnitin(a)data.in | नितिन(a)xn--c2bd1gb.xn--h2brj9c www.data.in--------------------------------------------------------------The content of this email is confidential and intended only for the recipient specified.If you received this message in error, please delete it and inform the sender. From: Saewon Lee via Gnso-spirt Sent: 15 June 2026 04:00 To: gnso-spirt(a)icann.org Subject: [Gnso-spirt] Re: Key Outcomes and Action Items from SPIRT Session during ICANN86 Dear SPIRT, It has been brought to my attention that the notes below may not align with the information communicated in Jeff`s Call for Support message and may therefore have caused some confusion. Please see the updated language below (yellow highlights) and we look forward to hearing more from the members by Tuesday, 16 June 2026. Kind regards, Saewon Get Outlook for Mac From: Saewon Lee Date: Thursday, June 11, 2026 at 4:28 PM To: gnso-spirt(a)icann.org Subject: Key Outcomes and Action Items from SPIRT Session during ICANN86 Dear SPIRT, Please see the following key outcome and action items from today&rsquos SPIRT Meeting during ICANN86. [KEY OUTCOME] SPIRT Members to review the Registry Service Provider (RSP) issue that has been referred by the GNSO Council and respond within 5 calendar days if any objections.whether you support or object to the determination that a change is required to the New gTLD Program. [ACTION ITEMS] Ongoing: All SPIRT Members to update their SOIs in accordance with the SOP. SPIRT Members to review the RSP issue and voice your support or objectionsobjections or concerns via the SPIRT mailing list by Tuesday, 16 June 2026, at 23:59 UTC (5 calendar days) ifwhether they determine that a change to the ongoing round is not required. GNSO Support Staff to reorganize the next set of SPIRT Meetings for June-July and send calendar invites, as necessary. Safe travels back home! Kind regards, Saewon Get Outlook for Mac _______________________________________________Gnso-spirt mailing list -- gnso-spirt(a)icann.orgTo unsubscribe send an email to gnso-spirt-leave(a)icann.orgDo not Remove:[HID]20260615192025637[-HID] [XGENFOOTER] [-XGENFOOTER]

1 0

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