Dear SPIRT,

 

Please see the following key outcomes, action items, and high-level notes from today’s SPIRT Meeting #6.

 

Kind regards,

Saewon

 

 

Key Outcomes, Action Items, and Notes from SPIRT Meeting #6 – Thursday, 7 May 2026 at 20:00 UTC.

 

[KEY OUTCOME]

 

[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]

  

  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]

 

  1. SPIRT Issue for Consideration

 

 

  1. RySG issue for consideration by SPIRT: Summary of issue in slide 7 (re RSP Evaluation/Type 2 – Non-minor Operational Change/Non-urgent/has a non-trivial monetary or operational impact) and original (updated) message here – 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.

 

 

  1.  ICANN org Issue for SPIRT Consideration – Non-minor Operational Change (Type 2): Summary of Issue is uploaded in Change Log 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:

 

  1. Updates from the Next Round Team
  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@icann.org>
Reply-To: Andrew Chen <andrew.chen@icann.org>
Date: Tuesday, May 5, 2026 at 1:00 PM
To: Jared Erwin via Gnso-spirt <gnso-spirt@icann.org>
Cc: GNSO-Secs <gnso-secs@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/