The proposal on the process for SPIRT Issue for Council Consideration can be found here. https://docs.google.com/document/d/1zITIUCB5yvjV_Rj5Z87ljyqajA5VliMSPvPb77AH...The document shared prior to the last council meeting has been updated with clear flowcharts that describe how the different stakeholders engaged in apply the Predictability Framework carry out their roles. 


As to the Council path, the first option which is the standard processis how the GNSO Council currently conducts its business, so adapting this for the SPIRT should be a breeze and there shouldn’t be any issue with this track.


The expedited process to be used in bringing alerts on SPIRT issues before Council is a fast-track means to securing Council's approval to meet up with real-time timelines and dead lines as the SPIRT works to resolve issues emernating from a live ongoing program. Should more comfort be provided, the Councils adoption process can be modified to issuing ballots for members voting within the 72 hour Conscent period. 


LOR

 -----

Image

Image

Lawrence Olawale-Roberts
Global President & Managing Director

Mobile: +234 8070892705, (0)8056 3333 97
Lawrence@microboss.org

Image

Image

…collaboration to enhance communication. 

Image

https://www.microboss.org | 

Image

Image

Image

Image

Image

 

 

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: Anne ICANN <anneicanngnso@gmail.com>
Sent: Saturday, May 9, 2026 8:08:38 PM
To: farzaneh badii <farzaneh.badii@gmail.com>
Cc: Lawrence O. Olawale-Roberts <lawrence@microboss.org>; GNSO council <council@icann.org>
Subject: Re: [council] Re: GNSO Council Motion for SPIRT Alerts
 
Well I hope we can do so at this May meeting and that is why I asked the two questions below about the "no objection after 72 hours consent process".  If Council does not agree to that process, then I don't know what would bar the Council from approving referring an issue to the SPIRT for consultation purposes on a case-by-case basis?   I think Council can certainly do that right now as the supervisor of the SPIRT under its Charter.

Agree the process should be clarified but if Council does not approve it at the May meeting (as may be modified by friendly amendment), then I think that under our Operating Procedures,  there can still be an email vote on a Motion to send the RSP issue to the SPIRT for further deliberation.  We would not want to hold this one up based on the fact that Council has not approved a process for allowing the SPIRIT to have issues referred to it by Council.  The reason is that this directly affects RSP approval processes ongoing right now at ICANN.
Anne

Anne Aikman-Scalese
GNSO Councilor
NomCom Non-Voting 2022-2026


On Sat, May 9, 2026 at 8:59 AM farzaneh badii <farzaneh.badii@gmail.com> wrote:
Hi Anne

In order to do this we need a process. I raised my concerns with the process Lawrence provided. We should address those concerns, approve the process then attend to the matter that they want to bring. At the moment, we don’t have a process to authorize them. 


Farzaneh 

On Sat, May 9, 2026 at 11:33 AM Anne ICANN <anneicanngnso@gmail.com> wrote:
Hi Farzaneh,
There may be some urgency for the SPIRT to consider the RSP issue since it relates to ICANN's process for RSP qualification and applicants are currently identifying qualified RSPs.  After reviewing the May 7 SPIRT meeting, I agree it's appropriate for Council to authorize the SPIRT to look into this issue.  I don't actually think we need to approve a 72 hour consent by non-objection process in order to do this but that is how the Motion has been framed so that is why I asked the questions below.
Anne


Anne Aikman-Scalese
GNSO Councilor
NomCom Non-Voting 2022-2026


On Sat, May 9, 2026 at 7:17 AM farzaneh badii <farzaneh.badii@gmail.com> wrote:
Hi there

We haven’t yet agreed to the process and the motion hasn’t addressed all the concerns. Shouldn’t we first work on the process?


Farzaneh 

On Sat, May 9, 2026 at 10:03 AM Anne ICANN via council <council@icann.org> wrote:
Thanks Lawrence.  Could you please clarify the following:

1.  In the proposed 72 hour non-objection process that has the effect of sending an issue to the SPIRT for deliberation, what level of objection or raising the issue to the Council level for discussion is required?  Is it objection by one Councilor.  Objection by Leadership?  Is this specified in the Motion?

2.  Where in the Motion or in the form advising Council of the issue does it specify that the SPIRT will bring a recommendation back to Council for its consideration?  Or do we intend for the SPIRIT to resolve the issue itself once the Council has given the 72 hour "consent by non-objection" to the SPIRT?  

I apologize if I have missed the above points in the Motion or in the form submitted which summarizes the important RSP qualification issue.  Thanks again for all your hard work.  

Anne

Anne Aikman-Scalese
GNSO Councilor
NomCom Non-Voting 2022-2026


On Sat, May 9, 2026 at 4:26 AM Lawrence O. Olawale-Roberts via council <council@icann.org> wrote:
Dear Councilors,

 

I submit for your approval and secondment a motion for the GNSO Council Consideration of SPIRT Alert Request process at our meeting for the 21st May, 2026.


Motion: 


On Council's approval of the Consideration Request for SPIRT Alerts in the motion above, the SPIRT would like to be permitted by the GNSO Council to discuss a matter on RSP Applications brought before the SPIRT by the Registry Stakeholder Group through a member.

 

Link to SPIRT Issue Submission Form:


The GNSO Council approval sort aligns with the SPIRT charter and adopted process.


Brief of Issue - RSP APPLICATIONS 


The Registry Service Provider (RSP) Handbook sets out the evaluation process for providers seeking qualification to offer services to new generic top-level domain (gTLD) applicants in the New gTLD Program and currently  mandates prospective RSP's to attest that all Extensible Provisioning Protocol (EPP) extensions they intend to use are registered with IANA in accordance with RFC 7451 and indicate whether they do, or will, refrain from using any EPP extensions that are not registered with IANA pursuant to RFC 7451.


As ICANN agreed to remove the requirement that Registry Operators limit their use to EPP extensions reflected in the IANA registry, the RSP Handbook has not updated to reflect this change and as a result, pre-evaluated RSPs are still required to commit to using only IANA-registered EPP extensions in order to pass evaluation. Thus RSPs must make commitments that their Registry Operators are no longer required to make under the Base Registry Agreement. Accordingly, the RySG requests that SPIRT and ICANN org consider revising the RSP Handbook to align it with the Base Registry Agreement. 

 -----

Image

Image

Lawrence Olawale-Roberts
Global President & Managing Director

Mobile: +234 8070892705, (0)8056 3333 97
Lawrence@microboss.org

Image

Image

…collaboration to enhance communication. 

Image

https://www.microboss.org | 

Image

Image

Image

Image

Image

 

 

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
To unsubscribe send an email to 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
To unsubscribe send an email to 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.