Dear Anne, Thank you for your questions regarding the SPIRT Issue Consideration process. We, as the staff supporting the GNSO liaison to the SPIRT and the SPIRT Leadership Team, are answering on Lawrence’s behalf below: * As I understand it, what the SPIRT team is trying to address is to develop a mechanism for the SPIRT to raise an issue at Council e.g in the case of a disagreement between the SPIRT and ICANN staff on a change to the program. Is that correct? * Since the SPIRT cannot refer an issue to itself under the Charter, the SPIRT is currently developing a procedure for how a SPIRT Member should raise an issue within the group. Under this process, the matter would first be submitted to the SPIRT LT and could ultimately lead to a request being brought before the Council. * Regarding the submission form to be used to identify the issue, my recollection regarding the Charter is that the SPIRT is required to raise an issue with Council if it considers that a policy change is required. This document would provide a means for SPIRT to raise an issue for Council's attention even where the SPIRT believes there is no policy issue involved, right? * This form is strictly for when a SPIRT Member wishes to raise an issue within the group. As mentioned above, the SPIRT Member would submit the google form to the SPIRT LT for the LT to first determine if the submitted issue is within the SPIRT's scope. * And it says that if the issue is "time-sensitive", SPIRT can use a "no response" time limit to proceed if no objection is raised on the Council list? Do you view that as consistent with the SPIRT Charter? * Since the Charter states that the SPIRT may not refer an issue to itself, this item is not guided within the Charter. Here, we are asking that the GNSO Council confirms the requested method when time-sensitive issues arise. * Is there a cleaner version of the "SPIRT Issue Consideration" document for Council to discuss at this time? Have the comments been resolved or are you asking Council to discuss the comments in the linked document? * A clean copy of the SPIRT Issue Consideration document may be found here<https://docs.google.com/document/d/1xA50mCWIgtCpW4NxZYN069zugw3maYemUX8fXajO...>, however, please note that this document is still pending finalization/confirmation by SPRIT. We hope this is helpful. Please let us know if you have any additional 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/ From: Anne ICANN via council <council@icann.org> Reply-To: Anne ICANN <anneicanngnso@gmail.com> Date: Wednesday, April 15, 2026 at 5:39 PM To: "lawrence@microboss.org" <lawrence@microboss.org> Cc: GNSO-Secs <gnso-secs@icann.org>, "council@icann.org" <council@icann.org> Subject: [council] Re: Council Process for Response to SPIRT Request. HI Lawrence. I note there are a number of comments in the SPIRT Issue Consideration document that is linked in your memo. There is also a suggestion from one member that the draft document be "cleaned up" with agreed edits being accepted. This would be helpful before it is considered by Council as a recommendation for Council deliberations. As I understand it, what the SPIRT team is trying to address is to develop a mechanism for the SPIRT to raise an issue at Council e.g in the case of a disagreement between the SPIRT and ICANN staff on a change to the program. Is that correct? Regarding the submission form to be used to identify the issue, my recollection regarding the Charter is that the SPIRT is required to raise an issue with Council if it considers that a policy change is required. This document would provide a means for SPIRT to raise an issue for Council's attention even where the SPIRT believes there is no policy issue involved, right? And it says that if the issue is "time-sensitive", SPIRT can use a "no response" time limit to proceed if no objection is raised on the Council list? Do you view that as consistent with the SPIRT Charter? Is there a cleaner version of the "SPIRT Issue Consideration" document for Council to discuss at this time? Have the comments been resolved or are you asking Council to discuss the comments in the linked document? Looking forward to more background information during the Council meeting. Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Tue, Apr 7, 2026 at 6:41 AM Lawrence O. Olawale-Roberts via council <council@icann.org<mailto:council@icann.org>> wrote: Dear Justine and All, I would presume that a time-sensitive request would be one where mitigation required would span a number of days to 3-4 months if not more. The goal here is to mandate an instruction from Council to the SPIRT Team in liaising with ICANN staff to proffer alternatives to a change on a process impacting the New gTLD Round - The standard process to secure a Council request to act alone may take 2-3 months (where Councilors seek a deferral in the process), hence any action that may require attention within a 3-6 month timeline should be classified as time-sensitive. The edits to read GNSO Chair and Types of Changes are accepted and effected. LOR. ----- Error! Filename not specified. Error! Filename not specified. Lawrence Olawale-Roberts Global President & Managing Director Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org<mailto:Lawrence@microboss.org> Error! Filename not specified. Error! Filename not specified. …collaboration to enhance communication. Error! Filename not specified. https://www.microboss.org [microboss.org]<https://urldefense.com/v3/__https:/www.microboss.org/__;!!PtGJab4!7-xkO-LtH5...> | Error! Filename not specified.[facebook.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> Error! Filename not specified.[linkedin.com]<https://urldefense.com/v3/__https:/www.linkedin.com/company/microbosstech/__...> Error! Filename not specified.[mobile.twitter.com]<https://urldefense.com/v3/__https:/mobile.twitter.com/microbosstech__;!!PtGJ...> Error! Filename not specified.[instagram.com]<https://urldefense.com/v3/__https:/www.instagram.com/microbosstech/?hl=en__;...> Error! Filename not specified.[youtube.com]<https://urldefense.com/v3/__https:/www.youtube.com/@microboss__;!!PtGJab4!7-...> This e-mail and any attachments are confidential and may be protected by legal, professional or other privilege. If you are not the intended recipient, you should not store it, copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. The views expressed are those of the sender and his company MicroBoss. Kindly note that whilst we scan all e-mails for viruses, we cannot guarantee that any e-mail is virus-free. | Do consider the environment before printing this email. ________________________________ From: Justine Chew <justine.chew.icann@gmail.com<mailto:justine.chew.icann@gmail.com>> Sent: Tuesday, April 7, 2026 4:42:55 AM To: Lawrence O. Olawale-Roberts <lawrence@microboss.org<mailto:lawrence@microboss.org>> Cc: GNSO-Secs <gnso-secs@icann.org<mailto:gnso-secs@icann.org>>; council@icann.org<mailto:council@icann.org> <council@icann.org<mailto:council@icann.org>> Subject: Re: [council] Council Process for Response to SPIRT Request. Dear Lawrence, Thanks for the summary document. I have a question and 2 comments:- 1. Do we have an indication of what is considered "time-sensitive" or not? 2. Consider amending "GNSO Council Chair" to "GNSO Chair" as referenced in the Bylaws Section 11.3(g) 3. Consider amending "Types of Change Request" to "Types of Changes" just to avoid confusion with Application Change Request Kind regards, Justine On Tue, 7 Apr 2026 at 04:24, Lawrence O. Olawale-Roberts via council <council@icann.org<mailto:council@icann.org>> wrote: Dear Council Colleagues, On the council agenda for our upcoming meeting is an agenda item under AOB to resolve the Council Process for Response to SPIRT Requests. Seeing that the time for this segment is packed I elected to provide a brief summary on our request to Council via the attached document. I am open to reviewing ideas or answering any questions you may have before our meeting. Lawrence. ----- Error! Filename not specified. Error! Filename not specified. Lawrence Olawale-Roberts Global President & Managing Director Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org<mailto:Lawrence@microboss.org> Error! Filename not specified. Error! Filename not specified. …collaboration to enhance communication. Error! Filename not specified. https://www.microboss.org [microboss.org]<https://urldefense.com/v3/__https:/www.microboss.org/__;!!PtGJab4!7-xkO-LtH5...> | Error! Filename not specified.[facebook.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> Error! Filename not specified.[linkedin.com]<https://urldefense.com/v3/__https:/www.linkedin.com/company/microbosstech/__...> Error! Filename not specified.[mobile.twitter.com]<https://urldefense.com/v3/__https:/mobile.twitter.com/microbosstech__;!!PtGJ...> Error! Filename not specified.[instagram.com]<https://urldefense.com/v3/__https:/www.instagram.com/microbosstech/?hl=en__;...> Error! Filename not specified.[youtube.com]<https://urldefense.com/v3/__https:/www.youtube.com/@microboss__;!!PtGJab4!7-...> This e-mail and any attachments are confidential and may be protected by legal, professional or other privilege. If you are not the intended recipient, you should not store it, copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. The views expressed are those of the sender and his company MicroBoss. Kindly note that whilst we scan all e-mails for viruses, we cannot guarantee that any e-mail is virus-free. | Do consider the environment before printing this email. _______________________________________________ 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. _______________________________________________ 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.