Dear SPIRT,

Please see the following key outcome, action items, and high-level notes from today’s SPIRT Meeting on Thursday, 09 July 2026 at 20:00 UTC.

Kind regards,

Saewon

Please find below the Key Outcomes, Action Items, and High-Level Notes from the SPIRT Meeting on Thursday, 09 July 2026 at 20:00 UTC:

[KEY OUTCOMES]

1. SPIRT determined that it does not need to confer with the GNSO Council regarding the RSP Issue at this stage, per the Predictability Framework and the relevant discussions.
2. SPIRT LT, on behalf of SPIRT, will respond to ICANN org with anticipated next steps, including a request for a timeline.
3. SPIRT determined next steps to help solve the RSP issue, suggesting a phased approach, with communication to RSP applicants and gTLD applicants as priority, followed by system updating, coding change, etc.
4. SPIRT Meetings are scheduled for the next 3 Thursdays until the end of July to resolve the RSP Issue. Ad hoc meetings may take place.

[ACTION ITEMS]

1. Ongoing: All SPIRT Members to update their SOIs in accordance with the SOP.
2. SPIRT LT to communicate the following to ICANN org, including: 1) anticipated next steps and request for a timeline; and 2) SPIRT’s willingness and readiness to collaborate with ICANN org to solve the issue in time.
3. ICANN org Staff to address SPIRT’s questions and concerns raised from the call today internally, also checking with Gustavo and team, and provide feedback, as necessary.

[High-Level NOTES]

• Jeff Neuman disclosed a new disclosure statement regarding a new client that is in the process of application.

• SPIRT Discussion on RSP Issue Referred by GNSO Council

• Next Steps regarding the Predictability Framework
  • ICANN org, through its response, noted “conferring with the GNSO” as the next step, but SPIRT believes that according to the text in the Predictability Framework (Path 3), which prevails over the flow chart, this step is unnecessary.
  • Jeff, as SPIRT Chair, proposes to respond the following to ICANN org, including: 1) that there is no need to discuss with or go back to Council at this point since this step does not apply to the current issue; and 2) that the SPIRT is ready and available to discuss the solution with ICANN org by 3 August, requesting for a suggested timeline from ICANN org.
    • ICANN org is aware of the 30-day timeline and is in the process of developing a preliminary solution to come back to SPIRT asap.

• Expectations for ICANN org Solution

• There are a few areas that need to be addressed to resolve this RSP issue, including: 1) notifying RSP applicants and those that have already passed that the attestation will not be enforced; 2) updating the application system (bright red alert when selecting “no”); and 3) checking code within the RSP evaluation test suite.
• ICANN org must: 1) inform the RSP applicants and gTLD applicants, update FAQs/Applicant Guidebook as well as the RSP handbook; 2) update the application system or make it manually possible; and 3) check that during the RSP testing, if RSP fails due to that one issue, they can be manually overridden.
• Since there is not much time until the application window closes (5-6 weeks), SPIRT suggests a phased-approach where communication and outreach to RSP applicants, gTLD applicants, and dissemination of information related to the overall program are prioritized – Predictability is paramount.
• For those more difficult items to solve, including coding changes, SPIRT had no concerns if they were not addressed within 12 August (application window) – as long as notification is out in time, more difficult items can be addressed after 12 August.
  • FYI. By 12 August, applicants only need to submit an application. They do not need to choose RSPs before the application window and will still have time to select the RSPs after. ICANN org’s goal is to have RSP evaluation by the end of year.