Thank you, Terri. For consideration by Lawrence as the maker of the Motion, I would propose a friendly amendment (specifically in relation to the time sensitive issues raised by SPIRT) along the following lines: - 7 day non-objection period yields consent (rather than 72 hours) and all Councilors are copied (gives some time for Councilors to consult SGs and Cs if needed.) - Council Leadership has the Objection authority if needed (Councilors provide input to Leadership and lets them call it.) - SPIRT agrees to make recommendation back to Council before proceeding to resolve the issue If accepted by Lawrence, I am prepared to second the Motion. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com On Mon, May 11, 2026 at 6:31 AM Terri Agnew via council <council@icann.org> wrote:
Hello all,
This motion has been added on the wiki page: https://icann-community.atlassian.net/wiki/x/kgA3J
Thank you.
Kind regards,
Terri
Policy Team Supporting the GNSO
*From: *"Lawrence O. Olawale-Roberts via council" <council@icann.org> *Reply-To: *"lawrence@microboss.org" <lawrence@microboss.org> *Date: *Saturday, May 9, 2026 at 6:26 AM *To: *GNSO council <council@icann.org> *Subject: *[council] GNSO Council Motion for SPIRT Alerts
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: *
· https://docs.google.com/document/d/1_5rUrQrAPRZmhcMQsE7bnzRULJEiNHZrmc5NPSOu... [docs.google.com] <https://urldefense.com/v3/__https:/docs.google.com/document/d/1_5rUrQrAPRZmh...>
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:*
- https://docs.google.com/document/d/1CPtqQL9hZvoIkQsh6Z3bwzDxGgRdXgiYlW_0BMAq... [docs.google.com] <https://urldefense.com/v3/__https:/docs.google.com/document/d/1CPtqQL9hZvoIk...>
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 removed by sender. Image]
[image: Image removed by sender. Image]
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
[image: Image removed by sender. Image]
[image: Image removed by sender. Image]
*…collaboration to enhance communication*.
[image: Image removed by sender. Image]
https://www.microboss.org [microboss.org] <https://urldefense.com/v3/__https:/www.microboss.org/__;!!PtGJab4!4Po1IC4Uci...> |
[image: Image removed by sender. Image][facebook.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
[image: Image removed by sender. Image][linkedin.com] <https://urldefense.com/v3/__https:/www.linkedin.com/company/microbosstech/__...>
[image: Image removed by sender. Image][mobile.twitter.com] <https://urldefense.com/v3/__https:/mobile.twitter.com/microbosstech__;!!PtGJ...>
[image: Image removed by sender. Image][instagram.com] <https://urldefense.com/v3/__https:/www.instagram.com/microbosstech/?hl=en__;...>
[image: Image removed by sender. Image][youtube.com] <https://urldefense.com/v3/__https:/www.youtube.com/@microboss__;!!PtGJab4!4P...>
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.