Hi Anne, With regards to the edits to the draft SPIRT Charter<https://gnso.icann.org/sites/default/files/policy/2024/draft/final-charter-s...>, I’m just talking about filling out the TBD items and making sure links are pointing to updated/current documentation, like the link to the Predictability Framework. Maybe better to describe these as administrative updates? For the additional SOI elements, I do not envision a change to the SOI itself. The SPIRT Charter references a Statement of Participation, which is additional to the SOI. Any requirements beyond the standard SOI will be an element of the signup process for members to the SPIRT. And lastly, regarding the Code of Conduct, my understanding is that it will apply broadly to participation in ICANN processes, with nothing specific pertaining to the SPIRT. Accordingly, I’m not clear why the SPIRT would specifically need to mention the Code of Conduct, but am happy to be convinced otherwise. Best, Steve From: Anne ICANN <anneicanngnso@gmail.com> Date: Thursday, September 18, 2025 at 11:04 AM To: Steve Chan <steve.chan@icann.org> Cc: "council@icann.org" <council@icann.org> Subject: [Ext] Re: [council] Standing Predictability Implementation Review Team (SPIRT) - UPDATE Thanks Steve. I'm not aware of any minor and non-substantive changes that would need to be made in the draft, but please do forward with redline as soon as possible. The issue I raised previously is (a) need for a much more detailed SOI form as called for by the Charter (b) the possible effect on the Charter of a Code of Conduct being finalized by the Board and this affecting the SOI and the ability of participants selected to participate in all SPIRT deliberations/communications or not on a case-by-by case basis. In this regard, I think that the Call for Volunteers should reflect the more detailed SOI (which includes full disclosure of interests represented I think) and to create a placeholder in relation to how the Code of Conduct adopted by the Board could affect the SPIRT SOI. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Thu, Sep 18, 2025 at 10:04 AM Steve Chan via council <council@icann.org<mailto:council@icann.org>> wrote: Dear Councilors, As the September Council meeting was action packed and we didn’t manage to get to all of the AOB items, you will see a handful of email updates to cover the items we missed. 9.5 - Initiating the Standing Predictability Implementation Review Team (SPIRT) For Councilors that may be unfamiliar with the SPIRT, it is a GNSO Council mechanism to manage unforeseen change to the New gTLD Program that may occur after the Board’s adoption of Applicant Guidebook (AGB). With the Board potentially adopting the AGB at ICANN84, steps need to be taken to ensure the SPIRT is established and prepared to carry out its role. The Council adopted [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/council/resolutions/202...> the draft SPIRT Charter in August 2024. That tiny bit of background aside, the update is: * The Call for Volunteers for the SPIRT will be published soon; we expect the Call for Volunteers will remain open through mid-October. The SPIRT will likely kick-off shortly after ICANN84, presuming that the AGB is adopted by the Board during ICANN84. * As noted in the background above, the Council adopted the SPIRT Charter in draft form. This was because the Predictability Framework, upon which the SPIRT relies upon, was still subject to potential change. As far as staff is aware, there has not been any significant change to the Predictability Framework and as a result, staff plans to make minor and non-substantive adjustments to migrate the SPIRT Charter from draft to final. Please let us know if you have any questions. Best, Steve Steven Chan VP, Policy Development Support & GNSO Relations Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 Email: steve.chan@icann.org<mailto:steve.chan@icann.org> Mobile: +1.310.339.4410 _______________________________________________ council mailing list -- council@icann.org<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto:council-leave@icann.org> _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.