2026-07-23 SPIRT

PROPOSED AGENDA

1. Welcome

2. SOI/SOP updates

3. ICANN Org Updates

4. Continuation of Discussion on RSP Issue

5. AOB 

6. Upcoming meetings

BACKGROUND DOCUMENTS

PARTICIPATION

Apologies: Nitin Walia, Jeff Neuman

Open

RECORDINGS

Audio Recording

Zoom Recording (including audio, visual, rough transcript and chat)

Notes/ Action Items

[KEY OUTCOMES]

1. Several Changes were made to Type 0 (#40-#42) and Type 1 (#8-#13) and updated in the Change Log [icann-community.atlassian.net] as of 20 July 2026 that need SPIRT guidance and confirmation by 24 July 2026 at 23:59 UTC.

[ACTION ITEMS]

2. Ongoing: All SPIRT Members to update their SOIs in accordance with the SOP.

3. SPIRT Members to voice objections to the updated redline language provided by ICANN org on Types 0 and 1 by 24 July 2026 at 23:59 UTC.

[High-Level NOTES]

• ICANN org Updates

• Update from ICANN org on the RSP Issue has been sent to the SPIRT mailing list here:https://lists.icann.org/hyperkitty/list/gnso-spirt@icann.org/thread/OQLBUY5K7PK3NTMPV2ZV3D4R4SHQEAYZ/ [lists.icann.org]

• Updates to Types 0 (#40-#42) and 1 (#8-#13) are listed in the Change Log as of 20 July 2024:https://icann-community.atlassian.net/wiki/x/LIC9Lg [icann-community.atlassian.net]

• The cadence of updating the AGB will need to be determined but the plan is to publish an updated AGB soon, notifying the applicants of the changes made. AGB should be updated and modified to match the TAMS.

• Several concerns were raised regarding the revision of the Path 3 text in the Predictability Framework that the flowchart is dictating the text. ICANN org noted that the flowchart is the correct process where the text needs to be updated accordingly and now the new text correctly reflects the proper process. Also, Path 3 is intended to illustrate Flowchart 1 [newgtldprogram-2026-agb.icann.org] for those instances where Council refers an issue to the SPIRT and this is not in conflict with the Charter nor does it need any amendments. A collaborative effort or the meaning of “collaboration” between ICANN org and the SPIRT, if necessary, remains unchanged and this language has not been omitted from the process or the flowcharts.

• RSP Issue Updates

• Question on the next steps and concerns on the 30-day collaborative effort were raised. Accountability Mechanism was also questioned.

• According to the SPIRT, since the current work approach has not been successful or collaborative, there was a suggestion for a few selective experts to work with ICANN org collaboratively to develop a solution. Expectations on the “collaborative” component were discussed – ICANN org responded that it is working diligently to develop a workable solution.