Dear SPIRT, Please see the following key outcomes, action items, and high-level notes from today’s SPIRT Meeting #5<https://icann-community.atlassian.net/wiki/x/AQAzLw>. Kind regards, Saewon Key Outcomes, Action Items, and Notes from SPIRT Meeting #5<https://icann-community.atlassian.net/wiki/x/AQAzLw> – Thursday, 23 April 2026 at 13:00 UTC.. [KEY OUTCOMES] 1. Re SPIRT Issue for Council Consideration Process Draft Doc.<https://docs.google.com/document/d/1zITIUCB5yvjV_Rj5Z87ljyqajA5VliMSPvPb77AH...>, Item #1 on “at least three days” to be updated to “at least three calendar days” [COMPLETE] 2. GNSO Staff to clean up draft doc. and circulate with SPIRT/document for future use. [ACTION ITEMS] 1. Ongoing: All SPIRT Members to update their SOIs in accordance with the SOP. 2. LT (Council Liaison) to provide clarity to the GNSO Council and receive confirmation form Council on the Response Process 3. GNSO Staff to prepare/update a Process Doc. for Council that is to be documented for this Process. 4. GDS Staff to possibly add a new column within the Change Log for “deadlines.” 5. SPIRT to pay attention to the update in Change Log (1 new Minor Change) and respond by 24 April if any objections. [NOTES] * Retrieve slides from here: https://icann-community.atlassian.net/wiki/x/AQAzLw *Announcement: SPIRT Meeting links will be changed moving forward since observers are NOT allowed to join the meeting and the current meeting link has been compromised. 1. Welcome * New gTLD Program: 2026 Round will be opening in 1 week and today is the last meeting before the Round officially opens. 1. SOI/SOP Updates * See Members List and SOI/SOP updates in the wiki here: https://icann-community.atlassian.net/wiki/x/AQCJHQ [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/AQCJ...> * Per the SOP, SPIRT Members are required to make a statement as to whether they are participating in any fashion in the 2026 Round – participating in the round, either directly or indirectly – without details. After Reveal Day, however, in accordance with both the Charter<https://gnso.icann.org/sites/default/files/policy/2025/draft/version2point0-...> and the new ICANN Code of Conduct<https://www.icann.org/en/system/files/files/adopted-icann-community-particip...>, Members are required to reveal in which terms they are associated with. * Jeff Neuman provided updates to his SOP. 1. GNSO Council Liaison Update * See the Briefing from the Council Liaison that was made to the Council during April’s Council Meeting (2026)<https://icann-community.atlassian.net/wiki/x/agAyJ> re identifying Council response to SPIRT here: https://gnso.icann.org/sites/default/files/policy/2026/draft/council-process... * There were a few questions requesting clarifications on the SPIRT Issue Consideration Process; GNSO Staff has provided a diagram to resolve the confusion (Slides 8-12<https://icann-community.atlassian.net/wiki/x/AQAzLw>). * The extra process may be creating more confusion, but this process is necessary since the SPIRT cannot raise an issue to itself and has to confer with Council. This prohibition for SPIRT raising an issue to itself is intended to prevent any risks associated with lobbying activities. Though complicated and cumbersome, this process is trying to strike a balance where a SPIRT Member, who are experts in this area, can raise an issue and bring it forward. * A question was raised on how the expedited request would be made. Council Liaison explained the current steps of the Expedited Process. Noted that this information is included within the Council Briefing doc. only (pending confirmation) and the request portion can be viewed here: “In the case where the SPIRT has submitted an issue that is time-sensitive to the New gTLD Program for the GNSO Council consideration, the GNSO Council Liaison informs the GNSO Council of the potential change raised by SPIRT members through the GNSO Council mailing list, noting whether the issue is urgent and merits the Council’s consideration through an expedited process. To clarify, this would only allow for the GNSO Council to approve the SPIRT’s discussion of a forwarded issue.” * For clarity related to Policy issues, this is not under the scope of this SPIRT Issue Consideration Process. If the SPIRT LT determines it is policy together with SPIRT, they will go down the route, in accordance with the Charter, NOT through this process, since policy must be addressed to Council (i.e., Per the Charter, “For Type 3, which is considered a policy change, the SPIRT shall confer with the GNSO Council.”) * A question was raised how weekends would be considered for time-sensitive matters. Council Liaison noted that the Expedited Process is to encourage the Council to respond more quickly. If more time is needed from the Council, then the Councilors have an opportunity to object to the issue/request and go through the Standard Process. * Action Items: 1) LT (Council Liaison) to provide clarity to the GNSO Council and receive confirmation form Council on the Response Process; 2) GNSO Staff to prepare/update a Process Doc. for Council that is to be documented for this Process. 1. SPIRT Issue for GNSO Council Consideration Process Update * See the Draft Process Doc. (including comments) here: https://docs.google.com/document/d/1zITIUCB5yvjV_Rj5Z87ljyqajA5VliMSPvPb77AH... * Andrew (GNSO Staff) directed the SPIRT to the latest comments and redlines; Item #1 on “at least three days” to be updated to “at least three calendar days” * The draft doc. will be cleaned up and circulated/documented for future use. * Outcomes: 1) Item #1 on “at least three days” to be updated to “at least three calendar days”; 2) GNSO Staff to clean up draft doc. and circulate with SPIRT/document for future use. 1. Updates from the Next Round Team * See SPIRT Change Log which has also been circulated via the public mailing list: https://icann-community.atlassian.net/wiki/x/LIC9Lg * Jared (GDS Staff) shared updates and any recent highlights: 1 new Type 1 (Minor) Change (shared on 22 April) regarding safeguard assessment in response to BRG. Effective Date of the Change is 24 April. The new updated AGB in pdf will be shared with SPIRT via the public mailing list as well as the link to the redline. * Emphasis that in accordance with the Charter, for Type 0 and 1 Changes, "no more than three (3) calendar days to provide guidance if it disagrees with the decision." Question was raised whether SPIRT gets any notification when something has been added to the change log or if SPIRT is expected to monitor it. Noted that the updates/new Changes are posted to the mailing list. * Question was raised whether there is a unified way of counting down the Change Log post; i.e., when does the 3-day actually begin its countdown? Noted that it should be 3 days from when the SPIRT is notified. The “timing” will be clearer when the Round opens but for now, the 3-day should be effective from when the Change Log is updated and notified to the SPIRT mailing list, which should be the same time. There were suggestions to maybe add a column for when SPRIT should send the deadline by and Jared responded positively that it can be looked into. * Action Items: 1) GDS Staff to possibly add a new column within the Change Log for “deadlines”; 2) SPIRT should pay attention to the update in Change Log (1 new Minor Change) and respond by 24 April if any objections. 1. Next Steps * Upcoming Meeting: 7 May 20:00 UTC * ICANN86 SPIRT Session scheduled and details to come at a later time. 1. AOB * N/A From: Andrew Chen via Gnso-spirt <gnso-spirt@icann.org> Reply-To: Andrew Chen <andrew.chen@icann.org> Date: Tuesday, April 21, 2026 at 1:00 PM To: Saewon Lee via Gnso-spirt <gnso-spirt@icann.org> Cc: GNSO-Secs <gnso-secs@icann.org> Subject: [Gnso-spirt] [SPIRT] AGENDA | SPIRT Meeting | 23 April 2026 at 13:00 UTC Dear SPIRT Members, Please find below the proposed agenda for the Standing Predictability Implementation Review Team (SPIRT) meeting on Thursday, 23 April 2026 at 13:00 UTC. Agenda: 1. Welcome 2. SOI/SOP Updates 3. GNSO Council Liaison Update 4. SPIRT Issue for GNSO Council Consideration Process Update 5. Updates from the Next Round Team 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/