Re: GNSO Council Motion for SPIRT Alerts
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 removed by sender. Image] [Image removed by sender. Image] Lawrence Olawale-Roberts Global President & Managing Director Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org<mailto:Lawrence@microboss.org> [Image removed by sender. Image] [Image removed by sender. Image] …collaboration to enhance communication. [Image removed by sender. Image] https://www.microboss.org [microboss.org]<https://urldefense.com/v3/__https:/www.microboss.org/__;!!PtGJab4!4Po1IC4Uci...> | [Image removed by sender. Image][facebook.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> [Image removed by sender. Image][linkedin.com]<https://urldefense.com/v3/__https:/www.linkedin.com/company/microbosstech/__...> [Image removed by sender. Image][mobile.twitter.com]<https://urldefense.com/v3/__https:/mobile.twitter.com/microbosstech__;!!PtGJ...> [Image removed by sender. Image][instagram.com]<https://urldefense.com/v3/__https:/www.instagram.com/microbosstech/?hl=en__;...> [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.
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.
Thanks to Lawrence for bringing this to Council in his capacity as the liaison to the SPIRT, and to Anne and Farzi for their comments. I wanted to just make a couple of comments, for the benefit of Councillors, particularly those who perhaps are not so familiar with the detail as yet. As a reminder, the SPIRT operates under the oversight of Council. Where an issue comes to the attention of the SPIRT which may require a change to the New gTLD Program, the SPIRT cannot consider that issue of its own volition, since the SPIRT cannot refer an issue to itself. Council may refer the issue to the SPIRT, however, and ask the SPIRT to look at it. What we are doing here is trying to set out a process for how that happens, including some timing expectations since such issues may be quite time-sensitive. Under the SPIRT Charter, the first task of the SPIRT is to determine whether the issue can be resolved in a manner that is consistent with existing policy recommendations. If SPIRT concludes that it cannot (in other words, that a policy change would be needed), then the SPIRT is already required under its Charter to confer with the Council on a path forward. But, with an issue that the SPIRT is aware of (but which has not been referred to it) it cannot even make that assessment because it is not empowered to act. By this process, Council will only be giving the SPIRT permission to evaluate the issue, we are not signing off on a proposed solution. Nothing in this process supersedes the SPIRT Charter. It is merely a pathway that allows the SPIRT to put something on Council’s radar and get permission from Council to look at it. I hope that we can work collaboratively to agree a timeline that allows Councillors time to confer with their groups, and allows the SPIRT to be put to work, where appropriate, as quickly as possible in time-sensitive situations. Input from others on what that timing might be – whether 72 hours, 7 days, or other – would be welcome. Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:image001.png@01DCE169.8DA1A930] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0> From: Anne ICANN via council <council@icann.org> Sent: 11 May 2026 15:51 To: Terri Agnew <terri.agnew@icann.org> Cc: GNSO council <council@icann.org> Subject: [council] Re: GNSO Council Motion for SPIRT Alerts 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<mailto:anneicanngnso@gmail.com> On Mon, May 11, 2026 at 6:31 AM Terri Agnew via council <council@icann.org<mailto: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<mailto:council@icann.org>> Reply-To: "lawrence@microboss.org<mailto:lawrence@microboss.org>" <lawrence@microboss.org<mailto:lawrence@microboss.org>> Date: Saturday, May 9, 2026 at 6:26 AM To: GNSO council <council@icann.org<mailto: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. ----- Lawrence Olawale-Roberts Global President & Managing Director Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org<mailto:Lawrence@microboss.org> …collaboration to enhance communication. https://www.microboss.org [microboss.org]<https://urldefense.com/v3/__https:/www.microboss.org/__;!!PtGJab4!4Po1IC4Uci...> | [facebook.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> [linkedin.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> [mobile.twitter.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> [instagram.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> [youtube.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> 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,<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> 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.<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> 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.<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> _______________________________________________ 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.<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/>
Dear Susan and Anne, Thank you for your inputs and contribution to the subject matter. @Susan your submission is spot on and am sure it provides some further clarity. where the Council adopts a 7 day timeframe in providing its consent over referring an issue to SPIRT, on a case-by-case basis I am hopeful the Council can beat this deadline in providing its conscent where needed. @ Anne i consider your first two proposals friendly and have gone ahead to update the motion before the Council in line with your suggestions - That the time for a consent be extended to 7 days and that Council leadership make the call for an objection. 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 your third request, the SPIRT charter explicitly recommends they come back to council on an issue that revolves around developing new policy (Type 3 Process)- Note that the SPIRT is a team of experts that are deemed to have the required competence to work along ICANN Org. In resolving any Type 2 issue that may arise. Mandating that they revert back to council at every point a decision needs to be made nullifies the intent behind how they are currently chatered, saddles the council with the same task they are to resolve and i believe isn’t the spirt behind the Predictability framework. I would urge that the council aligns with the PF and SPIRT Charther. Hopefully, this gets us all moving towards a consensus on the issue. Lawrence. ----- [Image] [Image] Lawrence Olawale-Roberts Global President & Managing Director Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org<mailto:Lawrence@microboss.org> [Image] [Image] …collaboration to enhance communication. [Image] https://www.microboss.org<https://www.microboss.org/> | [Image]<https://www.facebook.com/microbosstech/> [Image]<https://www.linkedin.com/company/microbosstech/> [Image]<https://mobile.twitter.com/microbosstech> [Image]<https://www.instagram.com/microbosstech/?hl=en> [Image]<https://www.youtube.com/@microboss> 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: Susan Payne via council <council@icann.org> Sent: Monday, May 11, 2026 5:44:15 PM To: GNSO council <council@icann.org> Subject: [council] Re: GNSO Council Motion for SPIRT Alerts Thanks to Lawrence for bringing this to Council in his capacity as the liaison to the SPIRT, and to Anne and Farzi for their comments. I wanted to just make a couple of comments, for the benefit of Councillors, particularly those who perhaps are not so familiar with the detail as yet. As a reminder, the SPIRT operates under the oversight of Council. Where an issue comes to the attention of the SPIRT which may require a change to the New gTLD Program, the SPIRT cannot consider that issue of its own volition, since the SPIRT cannot refer an issue to itself. Council may refer the issue to the SPIRT, however, and ask the SPIRT to look at it. What we are doing here is trying to set out a process for how that happens, including some timing expectations since such issues may be quite time-sensitive. Under the SPIRT Charter, the first task of the SPIRT is to determine whether the issue can be resolved in a manner that is consistent with existing policy recommendations. If SPIRT concludes that it cannot (in other words, that a policy change would be needed), then the SPIRT is already required under its Charter to confer with the Council on a path forward. But, with an issue that the SPIRT is aware of (but which has not been referred to it) it cannot even make that assessment because it is not empowered to act. By this process, Council will only be giving the SPIRT permission to evaluate the issue, we are not signing off on a proposed solution. Nothing in this process supersedes the SPIRT Charter. It is merely a pathway that allows the SPIRT to put something on Council’s radar and get permission from Council to look at it. I hope that we can work collaboratively to agree a timeline that allows Councillors time to confer with their groups, and allows the SPIRT to be put to work, where appropriate, as quickly as possible in time-sensitive situations. Input from others on what that timing might be – whether 72 hours, 7 days, or other – would be welcome. Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:image001.png@01DCE169.8DA1A930] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0> From: Anne ICANN via council <council@icann.org> Sent: 11 May 2026 15:51 To: Terri Agnew <terri.agnew@icann.org> Cc: GNSO council <council@icann.org> Subject: [council] Re: GNSO Council Motion for SPIRT Alerts 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<mailto:anneicanngnso@gmail.com> On Mon, May 11, 2026 at 6:31 AM Terri Agnew via council <council@icann.org<mailto: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<mailto:council@icann.org>> Reply-To: "lawrence@microboss.org<mailto:lawrence@microboss.org>" <lawrence@microboss.org<mailto:lawrence@microboss.org>> Date: Saturday, May 9, 2026 at 6:26 AM To: GNSO council <council@icann.org<mailto: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. ----- Lawrence Olawale-Roberts Global President & Managing Director Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org<mailto:Lawrence@microboss.org> …collaboration to enhance communication. https://www.microboss.org [microboss.org]<https://urldefense.com/v3/__https:/www.microboss.org/__;!!PtGJab4!4Po1IC4Uci...> | [facebook.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> [linkedin.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> [mobile.twitter.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> [instagram.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> [youtube.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> 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,<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> 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.<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> 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.<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> _______________________________________________ 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.<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/>
Hello all, We have updated the motion wiki page with the **Friendly amendment submitted by Anne Aikman-Scalese and accepted by Lawrence Olawale-Roberts. https://icann-community.atlassian.net/wiki/x/kgA3J @Anne, please let us know if you would like to second what is proposed. All the best, Terri From: "Lawrence O. Olawale-Roberts via council" <council@icann.org> Reply-To: "lawrence@microboss.org" <lawrence@microboss.org> Date: Monday, May 11, 2026 at 3:04 PM To: Susan Payne <susan.payne@comlaude.com>, GNSO council <council@icann.org> Subject: [council] Re: GNSO Council Motion for SPIRT Alerts Dear Susan and Anne, Thank you for your inputs and contribution to the subject matter. @Susan your submission is spot on and am sure it provides some further clarity. where the Council adopts a 7 day timeframe in providing its consent over referring an issue to SPIRT, on a case-by-case basis I am hopeful the Council can beat this deadline in providing its conscent where needed. @ Anne i consider your first two proposals friendly and have gone ahead to update the motion before the Council in line with your suggestions - That the time for a consent be extended to 7 days and that Council leadership make the call for an objection. 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 your third request, the SPIRT charter explicitly recommends they come back to council on an issue that revolves around developing new policy (Type 3 Process)- Note that the SPIRT is a team of experts that are deemed to have the required competence to work along ICANN Org. In resolving any Type 2 issue that may arise. Mandating that they revert back to council at every point a decision needs to be made nullifies the intent behind how they are currently chatered, saddles the council with the same task they are to resolve and i believe isn’t the spirt behind the Predictability framework. I would urge that the council aligns with the PF and SPIRT Charther. Hopefully, this gets us all moving towards a consensus on the issue. Lawrence. ----- [Image removed by sender. Image] [Image removed by sender. Image] Lawrence Olawale-Roberts Global President & Managing Director Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org<mailto:Lawrence@microboss.org> [Image removed by sender. Image] [Image removed by sender. Image] …collaboration to enhance communication. [Image removed by sender. Image] https://www.microboss.org [microboss.org]<https://urldefense.com/v3/__https:/www.microboss.org/__;!!PtGJab4!6xR1MswdAG...> | [Image removed by sender. Image][facebook.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> [Image removed by sender. Image][linkedin.com]<https://urldefense.com/v3/__https:/www.linkedin.com/company/microbosstech/__...> [Image removed by sender. Image][mobile.twitter.com]<https://urldefense.com/v3/__https:/mobile.twitter.com/microbosstech__;!!PtGJ...> [Image removed by sender. Image][instagram.com]<https://urldefense.com/v3/__https:/www.instagram.com/microbosstech/?hl=en__;...> [Image removed by sender. Image][youtube.com]<https://urldefense.com/v3/__https:/www.youtube.com/@microboss__;!!PtGJab4!6x...> 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: Susan Payne via council <council@icann.org> Sent: Monday, May 11, 2026 5:44:15 PM To: GNSO council <council@icann.org> Subject: [council] Re: GNSO Council Motion for SPIRT Alerts Thanks to Lawrence for bringing this to Council in his capacity as the liaison to the SPIRT, and to Anne and Farzi for their comments. I wanted to just make a couple of comments, for the benefit of Councillors, particularly those who perhaps are not so familiar with the detail as yet. As a reminder, the SPIRT operates under the oversight of Council. Where an issue comes to the attention of the SPIRT which may require a change to the New gTLD Program, the SPIRT cannot consider that issue of its own volition, since the SPIRT cannot refer an issue to itself. Council may refer the issue to the SPIRT, however, and ask the SPIRT to look at it. What we are doing here is trying to set out a process for how that happens, including some timing expectations since such issues may be quite time-sensitive. Under the SPIRT Charter, the first task of the SPIRT is to determine whether the issue can be resolved in a manner that is consistent with existing policy recommendations. If SPIRT concludes that it cannot (in other words, that a policy change would be needed), then the SPIRT is already required under its Charter to confer with the Council on a path forward. But, with an issue that the SPIRT is aware of (but which has not been referred to it) it cannot even make that assessment because it is not empowered to act. By this process, Council will only be giving the SPIRT permission to evaluate the issue, we are not signing off on a proposed solution. Nothing in this process supersedes the SPIRT Charter. It is merely a pathway that allows the SPIRT to put something on Council’s radar and get permission from Council to look at it. I hope that we can work collaboratively to agree a timeline that allows Councillors time to confer with their groups, and allows the SPIRT to be put to work, where appropriate, as quickly as possible in time-sensitive situations. Input from others on what that timing might be – whether 72 hours, 7 days, or other – would be welcome. Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:image001.png@01DCE159.2333F9A0] [comlaude.com]<https://urldefense.com/v3/__https:/comlaude.com/__;!!PtGJab4!6xR1MswdAG9azUg...> Follow us on LinkedIn [t-uk.xink.io]<https://urldefense.com/v3/__https:/t-uk.xink.io/Tracking/Index/pRkAABB8AADw_...> and Youtube [t-uk.xink.io]<https://urldefense.com/v3/__https:/t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_...> From: Anne ICANN via council <council@icann.org> Sent: 11 May 2026 15:51 To: Terri Agnew <terri.agnew@icann.org> Cc: GNSO council <council@icann.org> Subject: [council] Re: GNSO Council Motion for SPIRT Alerts 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<mailto:anneicanngnso@gmail.com> On Mon, May 11, 2026 at 6:31 AM Terri Agnew via council <council@icann.org<mailto:council@icann.org>> wrote: Hello all, This motion has been added on the wiki page: https://icann-community.atlassian.net/wiki/x/kgA3J [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/kgA3...> Thank you. Kind regards, Terri Policy Team Supporting the GNSO From: "Lawrence O. Olawale-Roberts via council" <council@icann.org<mailto:council@icann.org>> Reply-To: "lawrence@microboss.org<mailto:lawrence@microboss.org>" <lawrence@microboss.org<mailto:lawrence@microboss.org>> Date: Saturday, May 9, 2026 at 6:26 AM To: GNSO council <council@icann.org<mailto: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. ----- Lawrence Olawale-Roberts Global President & Managing Director Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org<mailto:Lawrence@microboss.org> …collaboration to enhance communication. https://www.microboss.org [microboss.org]<https://urldefense.com/v3/__https:/www.microboss.org/__;!!PtGJab4!4Po1IC4Uci...> | [facebook.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> [linkedin.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> [mobile.twitter.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> [instagram.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> [youtube.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> 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,<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> 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.<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> 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.<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> _______________________________________________ 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.<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com [comlaude.com]<https://urldefense.com/v3/__https:/comlaude.com/__;!!PtGJab4!6xR1MswdAG9azUg...>
Dear Councilors, Thank you for the summary and all for the constructive discussion regarding the proposed Council Process for Response to SPIRT Request and the role of the SPIRT under the Predictability Framework. I appreciate the thoughtful feedback provided by Councilors and concur that a 7-day consent period seems more reasonable. *@Terri:* I noticed a discrepancy in the agenda item text under the expedited process description. The paragraph still references a “72-hour consent period”. Can you please reflect that to a 7-day consent period as discussed in this thread ? Final+Proposed+Agenda+2026-05-21 <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...> Thank you all again for the collaborative engagement on this matter. Regards Gaurav Vedi GNSO CPH NCA On Mon, May 11, 2026 at 4:16 PM Terri Agnew via council <council@icann.org> wrote:
Hello all,
We have updated the motion wiki page with the ***Friendly amendment submitted by Anne Aikman-Scalese and accepted by* *Lawrence Olawale-Roberts.*
https://icann-community.atlassian.net/wiki/x/kgA3J
@Anne, please let us know if you would like to second what is proposed.
All the best,
Terri
*From: *"Lawrence O. Olawale-Roberts via council" <council@icann.org> *Reply-To: *"lawrence@microboss.org" <lawrence@microboss.org> *Date: *Monday, May 11, 2026 at 3:04 PM *To: *Susan Payne <susan.payne@comlaude.com>, GNSO council < council@icann.org> *Subject: *[council] Re: GNSO Council Motion for SPIRT Alerts
Dear Susan and Anne,
Thank you for your inputs and contribution to the subject matter.
@Susan your submission is spot on and am sure it provides some further clarity. where the Council adopts a 7 day timeframe in providing its consent over referring an issue to SPIRT, on a case-by-case basis I am hopeful the Council can beat this deadline in providing its conscent where needed.
@ Anne i consider your first two proposals friendly and have gone ahead to update the motion before the Council in line with your suggestions - That the time for a consent be extended to 7 days and that Council leadership make the call for an objection.
*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 your third request, the SPIRT charter explicitly recommends they come back to council on an issue that revolves around developing new policy (Type 3 Process)- Note that the SPIRT is a team of experts that are deemed to have the required competence to work along ICANN Org. In resolving any Type 2 issue that may arise. Mandating that they revert back to council at every point a decision needs to be made nullifies the intent behind how they are currently chatered, saddles the council with the same task they are to resolve and i believe isn’t the spirt behind the Predictability framework. I would urge that the council aligns with the PF and SPIRT Charther.
Hopefully, this gets us all moving towards a consensus on the issue.
Lawrence.
-----
[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!6xR1MswdAG...> |
[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!6x...>
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:* Susan Payne via council <council@icann.org> *Sent:* Monday, May 11, 2026 5:44:15 PM *To:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
Thanks to Lawrence for bringing this to Council in his capacity as the liaison to the SPIRT, and to Anne and Farzi for their comments.
I wanted to just make a couple of comments, for the benefit of Councillors, particularly those who perhaps are not so familiar with the detail as yet.
As a reminder, the SPIRT operates under the oversight of Council. Where an issue comes to the attention of the SPIRT which may require a change to the New gTLD Program, the SPIRT cannot consider that issue of its own volition, since the SPIRT cannot refer an issue to itself. Council may refer the issue to the SPIRT, however, and ask the SPIRT to look at it. What we are doing here is trying to set out a process for how that happens, including some timing expectations since such issues may be quite time-sensitive.
Under the SPIRT Charter, the first task of the SPIRT is to determine whether the issue can be resolved in a manner that is consistent with existing policy recommendations. If SPIRT concludes that it cannot (in other words, that a policy change would be needed), then the SPIRT is already required under its Charter to confer with the Council on a path forward. But, with an issue that the SPIRT is aware of (but which has not been referred to it) it cannot even make that assessment because it is not empowered to act. By this process, Council will only be giving the SPIRT permission to evaluate the issue, we are not signing off on a proposed solution.
Nothing in this process supersedes the SPIRT Charter. It is merely a pathway that allows the SPIRT to put something on Council’s radar and get permission from Council to look at it.
I hope that we can work collaboratively to agree a timeline that allows Councillors time to confer with their groups, and allows the SPIRT to be put to work, where appropriate, as quickly as possible in time-sensitive situations. Input from others on what that timing might be – whether 72 hours, 7 days, or other – would be welcome.
Susan Payne Head of Legal Policy Com Laude *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
[comlaude.com] <https://urldefense.com/v3/__https:/comlaude.com/__;!!PtGJab4!6xR1MswdAG9azUg...>
*Follow us on **LinkedIn* [t-uk.xink.io] <https://urldefense.com/v3/__https:/t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0__;!!PtGJab4!6xR1MswdAG9azUgoz97RynfF-0yQsJ10HdYaCx5ReyDT7VBPmjPm-WDsquObrdWgzJLmOdEZdNmkIJQxtuW0iRE$>* and **Youtube* [t-uk.xink.io] <https://urldefense.com/v3/__https:/t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_...>
[image: Image removed by sender.]
*From:* Anne ICANN via council <council@icann.org> *Sent:* 11 May 2026 15:51 *To:* Terri Agnew <terri.agnew@icann.org> *Cc:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
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 [icann-community.atlassian.net] <https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/kgA3...>
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.
-----
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
*…collaboration to enhance communication*.
https://www.microboss.org [microboss.org] <https://urldefense.com/v3/__https:/www.microboss.org/__;!!PtGJab4!4Po1IC4Uci...> |
[facebook.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
[linkedin.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
[mobile.twitter.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
[instagram.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
[youtube.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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, <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
_______________________________________________ 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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
------------------------------
The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com [comlaude.com] <https://urldefense.com/v3/__https:/comlaude.com/__;!!PtGJab4!6xR1MswdAG9azUg...> _______________________________________________ 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.
-- Regards, Gaurav Vedi
Hi Susan, According to AGB "Policy changes for ongoing rounds would only occur in extraordinary circumstances where the Program’s continuation is at risk if the change were not executed. If a policy change is necessary, the Board, ICANN org, and the GNSO Council in consultation with the SPIRT will identify an appropriate solution that secures the Program’s continuation and establishes a suitable implementation process. 8. Any collaboration between the Council and the SPIRT in this context is outside this Framework and is governed by the SPIRT Charter." So SPIRT shouldn't really be able to bring policy change proposals single handedly. And that’s not how I read the charter. As to the motion ... I feel like this is a premature motion. The process needs to be discussed before we actually have a motion. But I can bring my concerns as amendments: My concern is that the current process does not clearly distinguish between: - identifying and characterizing an issue; - deliberating operational impacts; and - developing substantive remediation pathways that may themselves implicate policy considerations. For example, an issue may initially appear operational, but the eventual proposed solution may no longer fit neatly within a Type 2 framework. That is why I think the motion should more clearly provide that: - issue alerts are intended to identify and characterize issues rather than embed proposed solutions at the alert stage; (this was even raised during the meeting last SPIRT had) - SPIRT alerts should come from SPIRT and not just a member or a stakeholder, the alert should include areas of agreement and disagreement within SPIRT regarding characterization and escalation; - urgency should remain subject to Council determination on a case-by-case basis; and - if, during deliberations, SPIRT or the council determine that either the issue itself or the proposed remediation pathway may constitute a Policy Change under the Predictability Framework, the matter should immediately return to Council for further consideration consistent with the SPIRT Charter and Predictability Framework. And this part is not in the process: At all times, SPIRT should bring the outcome of the process and the solution to the council for review and approval. I do not think these clarifications undermine the role of SPIRT or the Predictability Framework. Rather, they help preserve the distinction between operational deliberation and policy development that the Framework itself is trying to maintain. Farzaneh On Mon, May 11, 2026 at 4:16 PM Terri Agnew via council <council@icann.org> wrote:
Hello all,
We have updated the motion wiki page with the ***Friendly amendment submitted by Anne Aikman-Scalese and accepted by* *Lawrence Olawale-Roberts.*
https://icann-community.atlassian.net/wiki/x/kgA3J
@Anne, please let us know if you would like to second what is proposed.
All the best,
Terri
*From: *"Lawrence O. Olawale-Roberts via council" <council@icann.org> *Reply-To: *"lawrence@microboss.org" <lawrence@microboss.org> *Date: *Monday, May 11, 2026 at 3:04 PM *To: *Susan Payne <susan.payne@comlaude.com>, GNSO council < council@icann.org> *Subject: *[council] Re: GNSO Council Motion for SPIRT Alerts
Dear Susan and Anne,
Thank you for your inputs and contribution to the subject matter.
@Susan your submission is spot on and am sure it provides some further clarity. where the Council adopts a 7 day timeframe in providing its consent over referring an issue to SPIRT, on a case-by-case basis I am hopeful the Council can beat this deadline in providing its conscent where needed.
@ Anne i consider your first two proposals friendly and have gone ahead to update the motion before the Council in line with your suggestions - That the time for a consent be extended to 7 days and that Council leadership make the call for an objection.
*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 your third request, the SPIRT charter explicitly recommends they come back to council on an issue that revolves around developing new policy (Type 3 Process)- Note that the SPIRT is a team of experts that are deemed to have the required competence to work along ICANN Org. In resolving any Type 2 issue that may arise. Mandating that they revert back to council at every point a decision needs to be made nullifies the intent behind how they are currently chatered, saddles the council with the same task they are to resolve and i believe isn’t the spirt behind the Predictability framework. I would urge that the council aligns with the PF and SPIRT Charther.
Hopefully, this gets us all moving towards a consensus on the issue.
Lawrence.
-----
[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!6xR1MswdAG...> |
[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!6x...>
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:* Susan Payne via council <council@icann.org> *Sent:* Monday, May 11, 2026 5:44:15 PM *To:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
Thanks to Lawrence for bringing this to Council in his capacity as the liaison to the SPIRT, and to Anne and Farzi for their comments.
I wanted to just make a couple of comments, for the benefit of Councillors, particularly those who perhaps are not so familiar with the detail as yet.
As a reminder, the SPIRT operates under the oversight of Council. Where an issue comes to the attention of the SPIRT which may require a change to the New gTLD Program, the SPIRT cannot consider that issue of its own volition, since the SPIRT cannot refer an issue to itself. Council may refer the issue to the SPIRT, however, and ask the SPIRT to look at it. What we are doing here is trying to set out a process for how that happens, including some timing expectations since such issues may be quite time-sensitive.
Under the SPIRT Charter, the first task of the SPIRT is to determine whether the issue can be resolved in a manner that is consistent with existing policy recommendations. If SPIRT concludes that it cannot (in other words, that a policy change would be needed), then the SPIRT is already required under its Charter to confer with the Council on a path forward. But, with an issue that the SPIRT is aware of (but which has not been referred to it) it cannot even make that assessment because it is not empowered to act. By this process, Council will only be giving the SPIRT permission to evaluate the issue, we are not signing off on a proposed solution.
Nothing in this process supersedes the SPIRT Charter. It is merely a pathway that allows the SPIRT to put something on Council’s radar and get permission from Council to look at it.
I hope that we can work collaboratively to agree a timeline that allows Councillors time to confer with their groups, and allows the SPIRT to be put to work, where appropriate, as quickly as possible in time-sensitive situations. Input from others on what that timing might be – whether 72 hours, 7 days, or other – would be welcome.
Susan Payne Head of Legal Policy Com Laude *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
[comlaude.com] <https://urldefense.com/v3/__https:/comlaude.com/__;!!PtGJab4!6xR1MswdAG9azUg...>
*Follow us on **LinkedIn* [t-uk.xink.io] <https://urldefense.com/v3/__https:/t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0__;!!PtGJab4!6xR1MswdAG9azUgoz97RynfF-0yQsJ10HdYaCx5ReyDT7VBPmjPm-WDsquObrdWgzJLmOdEZdNmkIJQxtuW0iRE$>* and **Youtube* [t-uk.xink.io] <https://urldefense.com/v3/__https:/t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_...>
[image: Image removed by sender.]
*From:* Anne ICANN via council <council@icann.org> *Sent:* 11 May 2026 15:51 *To:* Terri Agnew <terri.agnew@icann.org> *Cc:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
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 [icann-community.atlassian.net] <https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/kgA3...>
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.
-----
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
*…collaboration to enhance communication*.
https://www.microboss.org [microboss.org] <https://urldefense.com/v3/__https:/www.microboss.org/__;!!PtGJab4!4Po1IC4Uci...> |
[facebook.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
[linkedin.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
[mobile.twitter.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
[instagram.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
[youtube.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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, <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
_______________________________________________ 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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
------------------------------
The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com [comlaude.com] <https://urldefense.com/v3/__https:/comlaude.com/__;!!PtGJab4!6xR1MswdAG9azUg...> _______________________________________________ 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.
Hi Farzaneh. As you know, I concur with your statement at the end of the email below where the SPIRT has alerted an issue to Council *on its own initiative* (as opposed to the case where the SPIRT is operating in accordance with its Charter.). "At all times, SPIRT should bring the outcome of the process and the solution to the council for review and approval." Interesting to note that the SPIRT has a session in Seville on Thursday at the end of the meeting day. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com On Mon, May 11, 2026 at 8:56 PM farzaneh badii via council < council@icann.org> wrote:
Hi Susan, According to AGB "Policy changes for ongoing rounds would only occur in extraordinary circumstances where the Program’s continuation is at risk if the change were not executed. If a policy change is necessary, the Board, ICANN org, and the GNSO Council in consultation with the SPIRT will identify an appropriate solution that secures the Program’s continuation and establishes a suitable implementation process. 8. Any collaboration between the Council and the SPIRT in this context is outside this Framework and is governed by the SPIRT Charter."
So SPIRT shouldn't really be able to bring policy change proposals single handedly. And that’s not how I read the charter.
As to the motion ... I feel like this is a premature motion. The process needs to be discussed before we actually have a motion. But I can bring my concerns as amendments:
My concern is that the current process does not clearly distinguish between:
-
identifying and characterizing an issue; -
deliberating operational impacts; and -
developing substantive remediation pathways that may themselves implicate policy considerations.
For example, an issue may initially appear operational, but the eventual proposed solution may no longer fit neatly within a Type 2 framework. That is why I think the motion should more clearly provide that:
-
issue alerts are intended to identify and characterize issues rather than embed proposed solutions at the alert stage; (this was even raised during the meeting last SPIRT had) -
SPIRT alerts should come from SPIRT and not just a member or a stakeholder, the alert should include areas of agreement and disagreement within SPIRT regarding characterization and escalation; -
urgency should remain subject to Council determination on a case-by-case basis; and -
if, during deliberations, SPIRT or the council determine that either the issue itself or the proposed remediation pathway may constitute a Policy Change under the Predictability Framework, the matter should immediately return to Council for further consideration consistent with the SPIRT Charter and Predictability Framework.
And this part is not in the process: At all times, SPIRT should bring the outcome of the process and the solution to the council for review and approval.
I do not think these clarifications undermine the role of SPIRT or the Predictability Framework. Rather, they help preserve the distinction between operational deliberation and policy development that the Framework itself is trying to maintain.
Farzaneh
On Mon, May 11, 2026 at 4:16 PM Terri Agnew via council <council@icann.org> wrote:
Hello all,
We have updated the motion wiki page with the ***Friendly amendment submitted by Anne Aikman-Scalese and accepted by* *Lawrence Olawale-Roberts.*
https://icann-community.atlassian.net/wiki/x/kgA3J
@Anne, please let us know if you would like to second what is proposed.
All the best,
Terri
*From: *"Lawrence O. Olawale-Roberts via council" <council@icann.org> *Reply-To: *"lawrence@microboss.org" <lawrence@microboss.org> *Date: *Monday, May 11, 2026 at 3:04 PM *To: *Susan Payne <susan.payne@comlaude.com>, GNSO council < council@icann.org> *Subject: *[council] Re: GNSO Council Motion for SPIRT Alerts
Dear Susan and Anne,
Thank you for your inputs and contribution to the subject matter.
@Susan your submission is spot on and am sure it provides some further clarity. where the Council adopts a 7 day timeframe in providing its consent over referring an issue to SPIRT, on a case-by-case basis I am hopeful the Council can beat this deadline in providing its conscent where needed.
@ Anne i consider your first two proposals friendly and have gone ahead to update the motion before the Council in line with your suggestions - That the time for a consent be extended to 7 days and that Council leadership make the call for an objection.
*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 your third request, the SPIRT charter explicitly recommends they come back to council on an issue that revolves around developing new policy (Type 3 Process)- Note that the SPIRT is a team of experts that are deemed to have the required competence to work along ICANN Org. In resolving any Type 2 issue that may arise. Mandating that they revert back to council at every point a decision needs to be made nullifies the intent behind how they are currently chatered, saddles the council with the same task they are to resolve and i believe isn’t the spirt behind the Predictability framework. I would urge that the council aligns with the PF and SPIRT Charther.
Hopefully, this gets us all moving towards a consensus on the issue.
Lawrence.
-----
[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!6xR1MswdAG...> |
[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!6x...>
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:* Susan Payne via council <council@icann.org> *Sent:* Monday, May 11, 2026 5:44:15 PM *To:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
Thanks to Lawrence for bringing this to Council in his capacity as the liaison to the SPIRT, and to Anne and Farzi for their comments.
I wanted to just make a couple of comments, for the benefit of Councillors, particularly those who perhaps are not so familiar with the detail as yet.
As a reminder, the SPIRT operates under the oversight of Council. Where an issue comes to the attention of the SPIRT which may require a change to the New gTLD Program, the SPIRT cannot consider that issue of its own volition, since the SPIRT cannot refer an issue to itself. Council may refer the issue to the SPIRT, however, and ask the SPIRT to look at it. What we are doing here is trying to set out a process for how that happens, including some timing expectations since such issues may be quite time-sensitive.
Under the SPIRT Charter, the first task of the SPIRT is to determine whether the issue can be resolved in a manner that is consistent with existing policy recommendations. If SPIRT concludes that it cannot (in other words, that a policy change would be needed), then the SPIRT is already required under its Charter to confer with the Council on a path forward. But, with an issue that the SPIRT is aware of (but which has not been referred to it) it cannot even make that assessment because it is not empowered to act. By this process, Council will only be giving the SPIRT permission to evaluate the issue, we are not signing off on a proposed solution.
Nothing in this process supersedes the SPIRT Charter. It is merely a pathway that allows the SPIRT to put something on Council’s radar and get permission from Council to look at it.
I hope that we can work collaboratively to agree a timeline that allows Councillors time to confer with their groups, and allows the SPIRT to be put to work, where appropriate, as quickly as possible in time-sensitive situations. Input from others on what that timing might be – whether 72 hours, 7 days, or other – would be welcome.
Susan Payne Head of Legal Policy Com Laude *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
[comlaude.com] <https://urldefense.com/v3/__https:/comlaude.com/__;!!PtGJab4!6xR1MswdAG9azUg...>
*Follow us on **LinkedIn* [t-uk.xink.io] <https://urldefense.com/v3/__https:/t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0__;!!PtGJab4!6xR1MswdAG9azUgoz97RynfF-0yQsJ10HdYaCx5ReyDT7VBPmjPm-WDsquObrdWgzJLmOdEZdNmkIJQxtuW0iRE$>* and **Youtube* [t-uk.xink.io] <https://urldefense.com/v3/__https:/t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_...>
[image: Image removed by sender.]
*From:* Anne ICANN via council <council@icann.org> *Sent:* 11 May 2026 15:51 *To:* Terri Agnew <terri.agnew@icann.org> *Cc:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
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 [icann-community.atlassian.net] <https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/kgA3...>
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.
-----
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
*…collaboration to enhance communication*.
https://www.microboss.org [microboss.org] <https://urldefense.com/v3/__https:/www.microboss.org/__;!!PtGJab4!4Po1IC4Uci...> |
[facebook.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
[linkedin.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
[mobile.twitter.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
[instagram.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
[youtube.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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, <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
_______________________________________________ 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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
------------------------------
The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com [comlaude.com] <https://urldefense.com/v3/__https:/comlaude.com/__;!!PtGJab4!6xR1MswdAG9azUg...> _______________________________________________ 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.
Hi Terri - Lawrence accepted the first two prongs of my proposed friendly amendment, but not the third where the SPIRT should review the proposed solution with Council. We are discussing this on the list. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com On Mon, May 11, 2026 at 1:16 PM Terri Agnew via council <council@icann.org> wrote:
Hello all,
We have updated the motion wiki page with the ***Friendly amendment submitted by Anne Aikman-Scalese and accepted by* *Lawrence Olawale-Roberts.*
https://icann-community.atlassian.net/wiki/x/kgA3J
@Anne, please let us know if you would like to second what is proposed.
All the best,
Terri
*From: *"Lawrence O. Olawale-Roberts via council" <council@icann.org> *Reply-To: *"lawrence@microboss.org" <lawrence@microboss.org> *Date: *Monday, May 11, 2026 at 3:04 PM *To: *Susan Payne <susan.payne@comlaude.com>, GNSO council < council@icann.org> *Subject: *[council] Re: GNSO Council Motion for SPIRT Alerts
Dear Susan and Anne,
Thank you for your inputs and contribution to the subject matter.
@Susan your submission is spot on and am sure it provides some further clarity. where the Council adopts a 7 day timeframe in providing its consent over referring an issue to SPIRT, on a case-by-case basis I am hopeful the Council can beat this deadline in providing its conscent where needed.
@ Anne i consider your first two proposals friendly and have gone ahead to update the motion before the Council in line with your suggestions - That the time for a consent be extended to 7 days and that Council leadership make the call for an objection.
*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 your third request, the SPIRT charter explicitly recommends they come back to council on an issue that revolves around developing new policy (Type 3 Process)- Note that the SPIRT is a team of experts that are deemed to have the required competence to work along ICANN Org. In resolving any Type 2 issue that may arise. Mandating that they revert back to council at every point a decision needs to be made nullifies the intent behind how they are currently chatered, saddles the council with the same task they are to resolve and i believe isn’t the spirt behind the Predictability framework. I would urge that the council aligns with the PF and SPIRT Charther.
Hopefully, this gets us all moving towards a consensus on the issue.
Lawrence.
-----
[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!6xR1MswdAG...> |
[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!6x...>
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:* Susan Payne via council <council@icann.org> *Sent:* Monday, May 11, 2026 5:44:15 PM *To:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
Thanks to Lawrence for bringing this to Council in his capacity as the liaison to the SPIRT, and to Anne and Farzi for their comments.
I wanted to just make a couple of comments, for the benefit of Councillors, particularly those who perhaps are not so familiar with the detail as yet.
As a reminder, the SPIRT operates under the oversight of Council. Where an issue comes to the attention of the SPIRT which may require a change to the New gTLD Program, the SPIRT cannot consider that issue of its own volition, since the SPIRT cannot refer an issue to itself. Council may refer the issue to the SPIRT, however, and ask the SPIRT to look at it. What we are doing here is trying to set out a process for how that happens, including some timing expectations since such issues may be quite time-sensitive.
Under the SPIRT Charter, the first task of the SPIRT is to determine whether the issue can be resolved in a manner that is consistent with existing policy recommendations. If SPIRT concludes that it cannot (in other words, that a policy change would be needed), then the SPIRT is already required under its Charter to confer with the Council on a path forward. But, with an issue that the SPIRT is aware of (but which has not been referred to it) it cannot even make that assessment because it is not empowered to act. By this process, Council will only be giving the SPIRT permission to evaluate the issue, we are not signing off on a proposed solution.
Nothing in this process supersedes the SPIRT Charter. It is merely a pathway that allows the SPIRT to put something on Council’s radar and get permission from Council to look at it.
I hope that we can work collaboratively to agree a timeline that allows Councillors time to confer with their groups, and allows the SPIRT to be put to work, where appropriate, as quickly as possible in time-sensitive situations. Input from others on what that timing might be – whether 72 hours, 7 days, or other – would be welcome.
Susan Payne Head of Legal Policy Com Laude *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
[comlaude.com] <https://urldefense.com/v3/__https:/comlaude.com/__;!!PtGJab4!6xR1MswdAG9azUg...>
*Follow us on **LinkedIn* [t-uk.xink.io] <https://urldefense.com/v3/__https:/t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0__;!!PtGJab4!6xR1MswdAG9azUgoz97RynfF-0yQsJ10HdYaCx5ReyDT7VBPmjPm-WDsquObrdWgzJLmOdEZdNmkIJQxtuW0iRE$>* and **Youtube* [t-uk.xink.io] <https://urldefense.com/v3/__https:/t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_...>
[image: Image removed by sender.]
*From:* Anne ICANN via council <council@icann.org> *Sent:* 11 May 2026 15:51 *To:* Terri Agnew <terri.agnew@icann.org> *Cc:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
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 [icann-community.atlassian.net] <https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/kgA3...>
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.
-----
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
*…collaboration to enhance communication*.
https://www.microboss.org [microboss.org] <https://urldefense.com/v3/__https:/www.microboss.org/__;!!PtGJab4!4Po1IC4Uci...> |
[facebook.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
[linkedin.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
[mobile.twitter.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
[instagram.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
[youtube.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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, <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
_______________________________________________ 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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
------------------------------
The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com [comlaude.com] <https://urldefense.com/v3/__https:/comlaude.com/__;!!PtGJab4!6xR1MswdAG9azUg...> _______________________________________________ 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.
Thanks Lawrence. Re the third issue, the RSP issue is a Categroy 2 issue - non-minor operational with material impact on applicants - but apparently ICANN has asked that this issue be briefed to the Council. Some members of SPIRT thought they could deal with it alone without talking to us. ICANN Org did not agree - presumably because of the nature of the material impact on RSP Qualification. So how is it that Council can agree with you that a Category 2 issue brought to the Council in this manner does not need to come back to Council for the proposed solution? Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com On Mon, May 11, 2026 at 1:04 PM Lawrence O. Olawale-Roberts via council < council@icann.org> wrote:
Dear Susan and Anne,
Thank you for your inputs and contribution to the subject matter.
@Susan your submission is spot on and am sure it provides some further clarity. where the Council adopts a 7 day timeframe in providing its consent over referring an issue to SPIRT, on a case-by-case basis I am hopeful the Council can beat this deadline in providing its conscent where needed.
@ Anne i consider your first two proposals friendly and have gone ahead to update the motion before the Council in line with your suggestions - That the time for a consent be extended to 7 days and that Council leadership make the call for an objection.
*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 your third request, the SPIRT charter explicitly recommends they come back to council on an issue that revolves around developing new policy (Type 3 Process)- Note that the SPIRT is a team of experts that are deemed to have the required competence to work along ICANN Org. In resolving any Type 2 issue that may arise. Mandating that they revert back to council at every point a decision needs to be made nullifies the intent behind how they are currently chatered, saddles the council with the same task they are to resolve and i believe isn’t the spirt behind the Predictability framework. I would urge that the council aligns with the PF and SPIRT Charther.
Hopefully, this gets us all moving towards a consensus on the issue.
Lawrence.
-----
[image: Image]
[image: Image]
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
[image: Image]
[image: Image]
*…collaboration to enhance communication*.
[image: Image]
[image: Image] <https://www.facebook.com/microbosstech/>
[image: Image] <https://www.linkedin.com/company/microbosstech/>
[image: Image] <https://mobile.twitter.com/microbosstech>
[image: Image] <https://www.instagram.com/microbosstech/?hl=en>
[image: Image] <https://www.youtube.com/@microboss>
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:* Susan Payne via council <council@icann.org> *Sent:* Monday, May 11, 2026 5:44:15 PM *To:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
Thanks to Lawrence for bringing this to Council in his capacity as the liaison to the SPIRT, and to Anne and Farzi for their comments.
I wanted to just make a couple of comments, for the benefit of Councillors, particularly those who perhaps are not so familiar with the detail as yet.
As a reminder, the SPIRT operates under the oversight of Council. Where an issue comes to the attention of the SPIRT which may require a change to the New gTLD Program, the SPIRT cannot consider that issue of its own volition, since the SPIRT cannot refer an issue to itself. Council may refer the issue to the SPIRT, however, and ask the SPIRT to look at it. What we are doing here is trying to set out a process for how that happens, including some timing expectations since such issues may be quite time-sensitive.
Under the SPIRT Charter, the first task of the SPIRT is to determine whether the issue can be resolved in a manner that is consistent with existing policy recommendations. If SPIRT concludes that it cannot (in other words, that a policy change would be needed), then the SPIRT is already required under its Charter to confer with the Council on a path forward. But, with an issue that the SPIRT is aware of (but which has not been referred to it) it cannot even make that assessment because it is not empowered to act. By this process, Council will only be giving the SPIRT permission to evaluate the issue, we are not signing off on a proposed solution.
Nothing in this process supersedes the SPIRT Charter. It is merely a pathway that allows the SPIRT to put something on Council’s radar and get permission from Council to look at it.
I hope that we can work collaboratively to agree a timeline that allows Councillors time to confer with their groups, and allows the SPIRT to be put to work, where appropriate, as quickly as possible in time-sensitive situations. Input from others on what that timing might be – whether 72 hours, 7 days, or other – would be welcome.
Susan Payne Head of Legal Policy Com Laude *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
*Follow us on **LinkedIn* <https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0>* and* *Youtube* <https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0>
*From:* Anne ICANN via council <council@icann.org> *Sent:* 11 May 2026 15:51 *To:* Terri Agnew <terri.agnew@icann.org> *Cc:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
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.
-----
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
*…collaboration to enhance communication*.
https://www.microboss.org [microboss.org] <https://urldefense.com/v3/__https:/www.microboss.org/__;!!PtGJab4!4Po1IC4Uci...> |
[facebook.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[linkedin.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[mobile.twitter.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[instagram.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[youtube.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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, <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
_______________________________________________ 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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
------------------------------ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com/> _______________________________________________ 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.
P.S. I should explain again that the Category 2 issue on RSP was actually raised by a SPIRT member on behalf of the RySG. To the extent that we are authorizing the SPIRT to raise an issue itself, It does not seem to me that the logic of just letting the SPIRT proceed to resolve on its own without conferring with Council still applies. (This comment is limited to Category 2 issues raised by the SPIRT itself or one of its members.) Reminder again that the Charter actually prohibits the SPIRT from raising issues. During Charter drafting, it was assumed the SG or C would raise the issue at the Council level if it was not raised by Board, ICANN, or the Council in some other way. So this mechanism for allowing the SPIRT (or in this case an RySG member of the SPIRT) to raise an issue was not contemplated by the Charter. Again, it may be more efficient to allow the SPIRT to do this, if only because it presumably meets more often than Council, but that does not mean that the SPIRT should be authorized to resolve an issue it has raised on its own (either by consensus or by Leadership team of the SPIRT or by an individual member) without coming back to the Council with the proposed solution. The very notion that the SPIRT can raise an issue itself is a new one and we need to be especially careful with a 7 day non-objection/consent process. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com On Tue, May 12, 2026 at 6:29 AM Anne ICANN <anneicanngnso@gmail.com> wrote:
Thanks Lawrence. Re the third issue, the RSP issue is a Categroy 2 issue - non-minor operational with material impact on applicants - but apparently ICANN has asked that this issue be briefed to the Council. Some members of SPIRT thought they could deal with it alone without talking to us. ICANN Org did not agree - presumably because of the nature of the material impact on RSP Qualification. So how is it that Council can agree with you that a Category 2 issue brought to the Council in this manner does not need to come back to Council for the proposed solution?
Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com
On Mon, May 11, 2026 at 1:04 PM Lawrence O. Olawale-Roberts via council < council@icann.org> wrote:
Dear Susan and Anne,
Thank you for your inputs and contribution to the subject matter.
@Susan your submission is spot on and am sure it provides some further clarity. where the Council adopts a 7 day timeframe in providing its consent over referring an issue to SPIRT, on a case-by-case basis I am hopeful the Council can beat this deadline in providing its conscent where needed.
@ Anne i consider your first two proposals friendly and have gone ahead to update the motion before the Council in line with your suggestions - That the time for a consent be extended to 7 days and that Council leadership make the call for an objection.
*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 your third request, the SPIRT charter explicitly recommends they come back to council on an issue that revolves around developing new policy (Type 3 Process)- Note that the SPIRT is a team of experts that are deemed to have the required competence to work along ICANN Org. In resolving any Type 2 issue that may arise. Mandating that they revert back to council at every point a decision needs to be made nullifies the intent behind how they are currently chatered, saddles the council with the same task they are to resolve and i believe isn’t the spirt behind the Predictability framework. I would urge that the council aligns with the PF and SPIRT Charther.
Hopefully, this gets us all moving towards a consensus on the issue.
Lawrence.
-----
[image: Image]
[image: Image]
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
[image: Image]
[image: Image]
*…collaboration to enhance communication*.
[image: Image]
[image: Image] <https://www.facebook.com/microbosstech/>
[image: Image] <https://www.linkedin.com/company/microbosstech/>
[image: Image] <https://mobile.twitter.com/microbosstech>
[image: Image] <https://www.instagram.com/microbosstech/?hl=en>
[image: Image] <https://www.youtube.com/@microboss>
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:* Susan Payne via council <council@icann.org> *Sent:* Monday, May 11, 2026 5:44:15 PM *To:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
Thanks to Lawrence for bringing this to Council in his capacity as the liaison to the SPIRT, and to Anne and Farzi for their comments.
I wanted to just make a couple of comments, for the benefit of Councillors, particularly those who perhaps are not so familiar with the detail as yet.
As a reminder, the SPIRT operates under the oversight of Council. Where an issue comes to the attention of the SPIRT which may require a change to the New gTLD Program, the SPIRT cannot consider that issue of its own volition, since the SPIRT cannot refer an issue to itself. Council may refer the issue to the SPIRT, however, and ask the SPIRT to look at it. What we are doing here is trying to set out a process for how that happens, including some timing expectations since such issues may be quite time-sensitive.
Under the SPIRT Charter, the first task of the SPIRT is to determine whether the issue can be resolved in a manner that is consistent with existing policy recommendations. If SPIRT concludes that it cannot (in other words, that a policy change would be needed), then the SPIRT is already required under its Charter to confer with the Council on a path forward. But, with an issue that the SPIRT is aware of (but which has not been referred to it) it cannot even make that assessment because it is not empowered to act. By this process, Council will only be giving the SPIRT permission to evaluate the issue, we are not signing off on a proposed solution.
Nothing in this process supersedes the SPIRT Charter. It is merely a pathway that allows the SPIRT to put something on Council’s radar and get permission from Council to look at it.
I hope that we can work collaboratively to agree a timeline that allows Councillors time to confer with their groups, and allows the SPIRT to be put to work, where appropriate, as quickly as possible in time-sensitive situations. Input from others on what that timing might be – whether 72 hours, 7 days, or other – would be welcome.
Susan Payne Head of Legal Policy Com Laude *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
*Follow us on **LinkedIn* <https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0>* and* *Youtube* <https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0>
*From:* Anne ICANN via council <council@icann.org> *Sent:* 11 May 2026 15:51 *To:* Terri Agnew <terri.agnew@icann.org> *Cc:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
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.
-----
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
*…collaboration to enhance communication*.
https://www.microboss.org [microboss.org] <https://urldefense.com/v3/__https:/www.microboss.org/__;!!PtGJab4!4Po1IC4Uci...> |
[facebook.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[linkedin.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[mobile.twitter.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[instagram.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[youtube.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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, <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
_______________________________________________ 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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
------------------------------ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com/> _______________________________________________ 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.
Well if we have a group of council members that are more active and monitor SPIRT issues and in touch with their stakeholders and they can bring the issue to the council and then the Council in collaboration with SPIRT sorts it out, I think that’s for the better. For now I can’t say yes to this motion there are too many unknowns and not much clarification and the more I look into it the more complicated it looks. And it will get more complicated. One stakeholder nor SPIRT should bring the issue to the council. This should be in a collaborative way. The more collaborative, the more efficient too! But to address the problem Jeff has submitted on behalf of the registry stakeholder group, I think we can just discuss the issue during next week meeting and ask the council members that want to work with SPIRT to come up with a solution to do so and bring back the result to the council. Farzaneh On Tue, May 12, 2026 at 11:18 AM Anne ICANN via council <council@icann.org> wrote:
P.S. I should explain again that the Category 2 issue on RSP was actually raised by a SPIRT member on behalf of the RySG. To the extent that we are authorizing the SPIRT to raise an issue itself, It does not seem to me that the logic of just letting the SPIRT proceed to resolve on its own without conferring with Council still applies. (This comment is limited to Category 2 issues raised by the SPIRT itself or one of its members.)
Reminder again that the Charter actually prohibits the SPIRT from raising issues. During Charter drafting, it was assumed the SG or C would raise the issue at the Council level if it was not raised by Board, ICANN, or the Council in some other way. So this mechanism for allowing the SPIRT (or in this case an RySG member of the SPIRT) to raise an issue was not contemplated by the Charter. Again, it may be more efficient to allow the SPIRT to do this, if only because it presumably meets more often than Council, but that does not mean that the SPIRT should be authorized to resolve an issue it has raised on its own (either by consensus or by Leadership team of the SPIRT or by an individual member) without coming back to the Council with the proposed solution. The very notion that the SPIRT can raise an issue itself is a new one and we need to be especially careful with a 7 day non-objection/consent process. Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com
On Tue, May 12, 2026 at 6:29 AM Anne ICANN <anneicanngnso@gmail.com> wrote:
Thanks Lawrence. Re the third issue, the RSP issue is a Categroy 2 issue - non-minor operational with material impact on applicants - but apparently ICANN has asked that this issue be briefed to the Council. Some members of SPIRT thought they could deal with it alone without talking to us. ICANN Org did not agree - presumably because of the nature of the material impact on RSP Qualification. So how is it that Council can agree with you that a Category 2 issue brought to the Council in this manner does not need to come back to Council for the proposed solution?
Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com
On Mon, May 11, 2026 at 1:04 PM Lawrence O. Olawale-Roberts via council < council@icann.org> wrote:
Dear Susan and Anne,
Thank you for your inputs and contribution to the subject matter.
@Susan your submission is spot on and am sure it provides some further clarity. where the Council adopts a 7 day timeframe in providing its consent over referring an issue to SPIRT, on a case-by-case basis I am hopeful the Council can beat this deadline in providing its conscent where needed.
@ Anne i consider your first two proposals friendly and have gone ahead to update the motion before the Council in line with your suggestions - That the time for a consent be extended to 7 days and that Council leadership make the call for an objection.
*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 your third request, the SPIRT charter explicitly recommends they come back to council on an issue that revolves around developing new policy (Type 3 Process)- Note that the SPIRT is a team of experts that are deemed to have the required competence to work along ICANN Org. In resolving any Type 2 issue that may arise. Mandating that they revert back to council at every point a decision needs to be made nullifies the intent behind how they are currently chatered, saddles the council with the same task they are to resolve and i believe isn’t the spirt behind the Predictability framework. I would urge that the council aligns with the PF and SPIRT Charther.
Hopefully, this gets us all moving towards a consensus on the issue.
Lawrence.
-----
[image: Image]
[image: Image]
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
[image: Image]
[image: Image]
*…collaboration to enhance communication*.
[image: Image]
[image: Image] <https://www.facebook.com/microbosstech/>
[image: Image] <https://www.linkedin.com/company/microbosstech/>
[image: Image] <https://mobile.twitter.com/microbosstech>
[image: Image] <https://www.instagram.com/microbosstech/?hl=en>
[image: Image] <https://www.youtube.com/@microboss>
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:* Susan Payne via council <council@icann.org> *Sent:* Monday, May 11, 2026 5:44:15 PM *To:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
Thanks to Lawrence for bringing this to Council in his capacity as the liaison to the SPIRT, and to Anne and Farzi for their comments.
I wanted to just make a couple of comments, for the benefit of Councillors, particularly those who perhaps are not so familiar with the detail as yet.
As a reminder, the SPIRT operates under the oversight of Council. Where an issue comes to the attention of the SPIRT which may require a change to the New gTLD Program, the SPIRT cannot consider that issue of its own volition, since the SPIRT cannot refer an issue to itself. Council may refer the issue to the SPIRT, however, and ask the SPIRT to look at it. What we are doing here is trying to set out a process for how that happens, including some timing expectations since such issues may be quite time-sensitive.
Under the SPIRT Charter, the first task of the SPIRT is to determine whether the issue can be resolved in a manner that is consistent with existing policy recommendations. If SPIRT concludes that it cannot (in other words, that a policy change would be needed), then the SPIRT is already required under its Charter to confer with the Council on a path forward. But, with an issue that the SPIRT is aware of (but which has not been referred to it) it cannot even make that assessment because it is not empowered to act. By this process, Council will only be giving the SPIRT permission to evaluate the issue, we are not signing off on a proposed solution.
Nothing in this process supersedes the SPIRT Charter. It is merely a pathway that allows the SPIRT to put something on Council’s radar and get permission from Council to look at it.
I hope that we can work collaboratively to agree a timeline that allows Councillors time to confer with their groups, and allows the SPIRT to be put to work, where appropriate, as quickly as possible in time-sensitive situations. Input from others on what that timing might be – whether 72 hours, 7 days, or other – would be welcome.
Susan Payne Head of Legal Policy Com Laude *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
*Follow us on **LinkedIn* <https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0>* and* *Youtube* <https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0>
*From:* Anne ICANN via council <council@icann.org> *Sent:* 11 May 2026 15:51 *To:* Terri Agnew <terri.agnew@icann.org> *Cc:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
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.
-----
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
*…collaboration to enhance communication*.
https://www.microboss.org [microboss.org] <https://urldefense.com/v3/__https:/www.microboss.org/__;!!PtGJab4!4Po1IC4Uci...> |
[facebook.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[linkedin.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[mobile.twitter.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[instagram.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[youtube.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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, <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
_______________________________________________ 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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
------------------------------ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland <https://www.google.com/maps/search/15+William+Street,+South+West+Lane,+Edinb...>; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2 <https://www.google.com/maps/search/Calle+Barcas+2?entry=gmail&source=g>, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com/> _______________________________________________ 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.
Hi Farzaneh. I'm a bit surprised that you suggest a "small team" of Councilors that want to work with SPIRT to develop the analysis and work on solutions? If the issue is assigned to the SPIRT due to their expertise, I would favor having them bring a proposal back to the full Council. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com On Tue, May 12, 2026 at 9:04 AM farzaneh badii <farzaneh.badii@gmail.com> wrote:
Well if we have a group of council members that are more active and monitor SPIRT issues and in touch with their stakeholders and they can bring the issue to the council and then the Council in collaboration with SPIRT sorts it out, I think that’s for the better. For now I can’t say yes to this motion there are too many unknowns and not much clarification and the more I look into it the more complicated it looks. And it will get more complicated. One stakeholder nor SPIRT should bring the issue to the council. This should be in a collaborative way. The more collaborative, the more efficient too!
But to address the problem Jeff has submitted on behalf of the registry stakeholder group, I think we can just discuss the issue during next week meeting and ask the council members that want to work with SPIRT to come up with a solution to do so and bring back the result to the council.
Farzaneh
On Tue, May 12, 2026 at 11:18 AM Anne ICANN via council <council@icann.org> wrote:
P.S. I should explain again that the Category 2 issue on RSP was actually raised by a SPIRT member on behalf of the RySG. To the extent that we are authorizing the SPIRT to raise an issue itself, It does not seem to me that the logic of just letting the SPIRT proceed to resolve on its own without conferring with Council still applies. (This comment is limited to Category 2 issues raised by the SPIRT itself or one of its members.)
Reminder again that the Charter actually prohibits the SPIRT from raising issues. During Charter drafting, it was assumed the SG or C would raise the issue at the Council level if it was not raised by Board, ICANN, or the Council in some other way. So this mechanism for allowing the SPIRT (or in this case an RySG member of the SPIRT) to raise an issue was not contemplated by the Charter. Again, it may be more efficient to allow the SPIRT to do this, if only because it presumably meets more often than Council, but that does not mean that the SPIRT should be authorized to resolve an issue it has raised on its own (either by consensus or by Leadership team of the SPIRT or by an individual member) without coming back to the Council with the proposed solution. The very notion that the SPIRT can raise an issue itself is a new one and we need to be especially careful with a 7 day non-objection/consent process. Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com
On Tue, May 12, 2026 at 6:29 AM Anne ICANN <anneicanngnso@gmail.com> wrote:
Thanks Lawrence. Re the third issue, the RSP issue is a Categroy 2 issue - non-minor operational with material impact on applicants - but apparently ICANN has asked that this issue be briefed to the Council. Some members of SPIRT thought they could deal with it alone without talking to us. ICANN Org did not agree - presumably because of the nature of the material impact on RSP Qualification. So how is it that Council can agree with you that a Category 2 issue brought to the Council in this manner does not need to come back to Council for the proposed solution?
Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com
On Mon, May 11, 2026 at 1:04 PM Lawrence O. Olawale-Roberts via council < council@icann.org> wrote:
Dear Susan and Anne,
Thank you for your inputs and contribution to the subject matter.
@Susan your submission is spot on and am sure it provides some further clarity. where the Council adopts a 7 day timeframe in providing its consent over referring an issue to SPIRT, on a case-by-case basis I am hopeful the Council can beat this deadline in providing its conscent where needed.
@ Anne i consider your first two proposals friendly and have gone ahead to update the motion before the Council in line with your suggestions - That the time for a consent be extended to 7 days and that Council leadership make the call for an objection.
*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 your third request, the SPIRT charter explicitly recommends they come back to council on an issue that revolves around developing new policy (Type 3 Process)- Note that the SPIRT is a team of experts that are deemed to have the required competence to work along ICANN Org. In resolving any Type 2 issue that may arise. Mandating that they revert back to council at every point a decision needs to be made nullifies the intent behind how they are currently chatered, saddles the council with the same task they are to resolve and i believe isn’t the spirt behind the Predictability framework. I would urge that the council aligns with the PF and SPIRT Charther.
Hopefully, this gets us all moving towards a consensus on the issue.
Lawrence.
-----
[image: Image]
[image: Image]
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
[image: Image]
[image: Image]
*…collaboration to enhance communication*.
[image: Image]
[image: Image] <https://www.facebook.com/microbosstech/>
[image: Image] <https://www.linkedin.com/company/microbosstech/>
[image: Image] <https://mobile.twitter.com/microbosstech>
[image: Image] <https://www.instagram.com/microbosstech/?hl=en>
[image: Image] <https://www.youtube.com/@microboss>
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:* Susan Payne via council <council@icann.org> *Sent:* Monday, May 11, 2026 5:44:15 PM *To:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
Thanks to Lawrence for bringing this to Council in his capacity as the liaison to the SPIRT, and to Anne and Farzi for their comments.
I wanted to just make a couple of comments, for the benefit of Councillors, particularly those who perhaps are not so familiar with the detail as yet.
As a reminder, the SPIRT operates under the oversight of Council. Where an issue comes to the attention of the SPIRT which may require a change to the New gTLD Program, the SPIRT cannot consider that issue of its own volition, since the SPIRT cannot refer an issue to itself. Council may refer the issue to the SPIRT, however, and ask the SPIRT to look at it. What we are doing here is trying to set out a process for how that happens, including some timing expectations since such issues may be quite time-sensitive.
Under the SPIRT Charter, the first task of the SPIRT is to determine whether the issue can be resolved in a manner that is consistent with existing policy recommendations. If SPIRT concludes that it cannot (in other words, that a policy change would be needed), then the SPIRT is already required under its Charter to confer with the Council on a path forward. But, with an issue that the SPIRT is aware of (but which has not been referred to it) it cannot even make that assessment because it is not empowered to act. By this process, Council will only be giving the SPIRT permission to evaluate the issue, we are not signing off on a proposed solution.
Nothing in this process supersedes the SPIRT Charter. It is merely a pathway that allows the SPIRT to put something on Council’s radar and get permission from Council to look at it.
I hope that we can work collaboratively to agree a timeline that allows Councillors time to confer with their groups, and allows the SPIRT to be put to work, where appropriate, as quickly as possible in time-sensitive situations. Input from others on what that timing might be – whether 72 hours, 7 days, or other – would be welcome.
Susan Payne Head of Legal Policy Com Laude *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
*Follow us on **LinkedIn* <https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0>* and* *Youtube* <https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0>
*From:* Anne ICANN via council <council@icann.org> *Sent:* 11 May 2026 15:51 *To:* Terri Agnew <terri.agnew@icann.org> *Cc:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
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.
-----
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
*…collaboration to enhance communication*.
https://www.microboss.org [microboss.org] <https://urldefense.com/v3/__https:/www.microboss.org/__;!!PtGJab4!4Po1IC4Uci...> |
[facebook.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[linkedin.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[mobile.twitter.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[instagram.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[youtube.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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, <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
_______________________________________________ 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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
------------------------------ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland <https://www.google.com/maps/search/15+William+Street,+South+West+Lane,+Edinb...>; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2 <https://www.google.com/maps/search/Calle+Barcas+2?entry=gmail&source=g>, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com/> _______________________________________________ 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.
Hi Anne I said a coordination group. And they only coordinate, they provide briefing, they provide background. If all council members want to focus on it, they can. And I didn’t say don’t bring back to the council. From the beginning I have been insiting council involvement through all the process. I think this is better than having a liaison have to do it and be the messenger, this workload is going to get heavy. Another way is, a stakeholder group provide an issue to their council member, we discuss with the whole council and having SPIRT come to the council and discuss further and come up with a solution. Farzaneh On Tue, May 12, 2026 at 1:06 PM Anne ICANN <anneicanngnso@gmail.com> wrote:
Hi Farzaneh. I'm a bit surprised that you suggest a "small team" of Councilors that want to work with SPIRT to develop the analysis and work on solutions? If the issue is assigned to the SPIRT due to their expertise, I would favor having them bring a proposal back to the full Council. Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com
On Tue, May 12, 2026 at 9:04 AM farzaneh badii <farzaneh.badii@gmail.com> wrote:
Well if we have a group of council members that are more active and monitor SPIRT issues and in touch with their stakeholders and they can bring the issue to the council and then the Council in collaboration with SPIRT sorts it out, I think that’s for the better. For now I can’t say yes to this motion there are too many unknowns and not much clarification and the more I look into it the more complicated it looks. And it will get more complicated. One stakeholder nor SPIRT should bring the issue to the council. This should be in a collaborative way. The more collaborative, the more efficient too!
But to address the problem Jeff has submitted on behalf of the registry stakeholder group, I think we can just discuss the issue during next week meeting and ask the council members that want to work with SPIRT to come up with a solution to do so and bring back the result to the council.
Farzaneh
On Tue, May 12, 2026 at 11:18 AM Anne ICANN via council < council@icann.org> wrote:
P.S. I should explain again that the Category 2 issue on RSP was actually raised by a SPIRT member on behalf of the RySG. To the extent that we are authorizing the SPIRT to raise an issue itself, It does not seem to me that the logic of just letting the SPIRT proceed to resolve on its own without conferring with Council still applies. (This comment is limited to Category 2 issues raised by the SPIRT itself or one of its members.)
Reminder again that the Charter actually prohibits the SPIRT from raising issues. During Charter drafting, it was assumed the SG or C would raise the issue at the Council level if it was not raised by Board, ICANN, or the Council in some other way. So this mechanism for allowing the SPIRT (or in this case an RySG member of the SPIRT) to raise an issue was not contemplated by the Charter. Again, it may be more efficient to allow the SPIRT to do this, if only because it presumably meets more often than Council, but that does not mean that the SPIRT should be authorized to resolve an issue it has raised on its own (either by consensus or by Leadership team of the SPIRT or by an individual member) without coming back to the Council with the proposed solution. The very notion that the SPIRT can raise an issue itself is a new one and we need to be especially careful with a 7 day non-objection/consent process. Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com
On Tue, May 12, 2026 at 6:29 AM Anne ICANN <anneicanngnso@gmail.com> wrote:
Thanks Lawrence. Re the third issue, the RSP issue is a Categroy 2 issue - non-minor operational with material impact on applicants - but apparently ICANN has asked that this issue be briefed to the Council. Some members of SPIRT thought they could deal with it alone without talking to us. ICANN Org did not agree - presumably because of the nature of the material impact on RSP Qualification. So how is it that Council can agree with you that a Category 2 issue brought to the Council in this manner does not need to come back to Council for the proposed solution?
Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com
On Mon, May 11, 2026 at 1:04 PM Lawrence O. Olawale-Roberts via council <council@icann.org> wrote:
Dear Susan and Anne,
Thank you for your inputs and contribution to the subject matter.
@Susan your submission is spot on and am sure it provides some further clarity. where the Council adopts a 7 day timeframe in providing its consent over referring an issue to SPIRT, on a case-by-case basis I am hopeful the Council can beat this deadline in providing its conscent where needed.
@ Anne i consider your first two proposals friendly and have gone ahead to update the motion before the Council in line with your suggestions - That the time for a consent be extended to 7 days and that Council leadership make the call for an objection.
*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 your third request, the SPIRT charter explicitly recommends they come back to council on an issue that revolves around developing new policy (Type 3 Process)- Note that the SPIRT is a team of experts that are deemed to have the required competence to work along ICANN Org. In resolving any Type 2 issue that may arise. Mandating that they revert back to council at every point a decision needs to be made nullifies the intent behind how they are currently chatered, saddles the council with the same task they are to resolve and i believe isn’t the spirt behind the Predictability framework. I would urge that the council aligns with the PF and SPIRT Charther.
Hopefully, this gets us all moving towards a consensus on the issue.
Lawrence.
-----
[image: Image]
[image: Image]
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
[image: Image]
[image: Image]
*…collaboration to enhance communication*.
[image: Image]
[image: Image] <https://www.facebook.com/microbosstech/>
[image: Image] <https://www.linkedin.com/company/microbosstech/>
[image: Image] <https://mobile.twitter.com/microbosstech>
[image: Image] <https://www.instagram.com/microbosstech/?hl=en>
[image: Image] <https://www.youtube.com/@microboss>
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:* Susan Payne via council <council@icann.org> *Sent:* Monday, May 11, 2026 5:44:15 PM *To:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
Thanks to Lawrence for bringing this to Council in his capacity as the liaison to the SPIRT, and to Anne and Farzi for their comments.
I wanted to just make a couple of comments, for the benefit of Councillors, particularly those who perhaps are not so familiar with the detail as yet.
As a reminder, the SPIRT operates under the oversight of Council. Where an issue comes to the attention of the SPIRT which may require a change to the New gTLD Program, the SPIRT cannot consider that issue of its own volition, since the SPIRT cannot refer an issue to itself. Council may refer the issue to the SPIRT, however, and ask the SPIRT to look at it. What we are doing here is trying to set out a process for how that happens, including some timing expectations since such issues may be quite time-sensitive.
Under the SPIRT Charter, the first task of the SPIRT is to determine whether the issue can be resolved in a manner that is consistent with existing policy recommendations. If SPIRT concludes that it cannot (in other words, that a policy change would be needed), then the SPIRT is already required under its Charter to confer with the Council on a path forward. But, with an issue that the SPIRT is aware of (but which has not been referred to it) it cannot even make that assessment because it is not empowered to act. By this process, Council will only be giving the SPIRT permission to evaluate the issue, we are not signing off on a proposed solution.
Nothing in this process supersedes the SPIRT Charter. It is merely a pathway that allows the SPIRT to put something on Council’s radar and get permission from Council to look at it.
I hope that we can work collaboratively to agree a timeline that allows Councillors time to confer with their groups, and allows the SPIRT to be put to work, where appropriate, as quickly as possible in time-sensitive situations. Input from others on what that timing might be – whether 72 hours, 7 days, or other – would be welcome.
Susan Payne Head of Legal Policy Com Laude *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
*Follow us on **LinkedIn* <https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0>* and* *Youtube* <https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0>
*From:* Anne ICANN via council <council@icann.org> *Sent:* 11 May 2026 15:51 *To:* Terri Agnew <terri.agnew@icann.org> *Cc:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
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.
-----
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
*…collaboration to enhance communication*.
https://www.microboss.org [microboss.org] <https://urldefense.com/v3/__https:/www.microboss.org/__;!!PtGJab4!4Po1IC4Uci...> |
[facebook.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[linkedin.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[mobile.twitter.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[instagram.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[youtube.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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, <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
_______________________________________________ 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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
------------------------------ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland <https://www.google.com/maps/search/15+William+Street,+South+West+Lane,+Edinb...>; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2 <https://www.google.com/maps/search/Calle+Barcas+2?entry=gmail&source=g>, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com/> _______________________________________________ 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.
Frankly Farzaneh, this is not how the SPIRT is chartered to work. Your proposal would require re-drafting the SPIRT charter and basically resetting the group without even allowing them or ICANN test the current process. The SPIRT other path through which the can mitigate issues referred to them through ICANN Org. Does not require SPIRT coming back to Council for concurrence or consultations as long as the issue is not determined to be Type 3 - hence over engineering this process of just getting to secure council's approval to look into a matter might subsequently push dependence on staff to initiate issues for the SPIRT to act on. LOR ----- [Image] [Image] Lawrence Olawale-Roberts Global President & Managing Director Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org<mailto:Lawrence@microboss.org> [Image] [Image] …collaboration to enhance communication. [Image] https://www.microboss.org<https://www.microboss.org/> | [Image]<https://www.facebook.com/microbosstech/> [Image]<https://www.linkedin.com/company/microbosstech/> [Image]<https://mobile.twitter.com/microbosstech> [Image]<https://www.instagram.com/microbosstech/?hl=en> [Image]<https://www.youtube.com/@microboss> 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: farzaneh badii via council <council@icann.org> Sent: Tuesday, May 12, 2026 6:41:01 PM To: Anne ICANN <anneicanngnso@gmail.com> Cc: Lawrence O. Olawale-Roberts <lawrence@microboss.org>; GNSO council <council@icann.org> Subject: [council] Re: GNSO Council Motion for SPIRT Alerts Hi Anne I said a coordination group. And they only coordinate, they provide briefing, they provide background. If all council members want to focus on it, they can. And I didn’t say don’t bring back to the council. From the beginning I have been insiting council involvement through all the process. I think this is better than having a liaison have to do it and be the messenger, this workload is going to get heavy. Another way is, a stakeholder group provide an issue to their council member, we discuss with the whole council and having SPIRT come to the council and discuss further and come up with a solution. Farzaneh On Tue, May 12, 2026 at 1:06 PM Anne ICANN <anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com>> wrote: Hi Farzaneh. I'm a bit surprised that you suggest a "small team" of Councilors that want to work with SPIRT to develop the analysis and work on solutions? If the issue is assigned to the SPIRT due to their expertise, I would favor having them bring a proposal back to the full Council. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Tue, May 12, 2026 at 9:04 AM farzaneh badii <farzaneh.badii@gmail.com<mailto:farzaneh.badii@gmail.com>> wrote: Well if we have a group of council members that are more active and monitor SPIRT issues and in touch with their stakeholders and they can bring the issue to the council and then the Council in collaboration with SPIRT sorts it out, I think that’s for the better. For now I can’t say yes to this motion there are too many unknowns and not much clarification and the more I look into it the more complicated it looks. And it will get more complicated. One stakeholder nor SPIRT should bring the issue to the council. This should be in a collaborative way. The more collaborative, the more efficient too! But to address the problem Jeff has submitted on behalf of the registry stakeholder group, I think we can just discuss the issue during next week meeting and ask the council members that want to work with SPIRT to come up with a solution to do so and bring back the result to the council. Farzaneh On Tue, May 12, 2026 at 11:18 AM Anne ICANN via council <council@icann.org<mailto:council@icann.org>> wrote: P.S. I should explain again that the Category 2 issue on RSP was actually raised by a SPIRT member on behalf of the RySG. To the extent that we are authorizing the SPIRT to raise an issue itself, It does not seem to me that the logic of just letting the SPIRT proceed to resolve on its own without conferring with Council still applies. (This comment is limited to Category 2 issues raised by the SPIRT itself or one of its members.) Reminder again that the Charter actually prohibits the SPIRT from raising issues. During Charter drafting, it was assumed the SG or C would raise the issue at the Council level if it was not raised by Board, ICANN, or the Council in some other way. So this mechanism for allowing the SPIRT (or in this case an RySG member of the SPIRT) to raise an issue was not contemplated by the Charter. Again, it may be more efficient to allow the SPIRT to do this, if only because it presumably meets more often than Council, but that does not mean that the SPIRT should be authorized to resolve an issue it has raised on its own (either by consensus or by Leadership team of the SPIRT or by an individual member) without coming back to the Council with the proposed solution. The very notion that the SPIRT can raise an issue itself is a new one and we need to be especially careful with a 7 day non-objection/consent process. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Tue, May 12, 2026 at 6:29 AM Anne ICANN <anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com>> wrote: Thanks Lawrence. Re the third issue, the RSP issue is a Categroy 2 issue - non-minor operational with material impact on applicants - but apparently ICANN has asked that this issue be briefed to the Council. Some members of SPIRT thought they could deal with it alone without talking to us. ICANN Org did not agree - presumably because of the nature of the material impact on RSP Qualification. So how is it that Council can agree with you that a Category 2 issue brought to the Council in this manner does not need to come back to Council for the proposed solution? Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Mon, May 11, 2026 at 1:04 PM Lawrence O. Olawale-Roberts via council <council@icann.org<mailto:council@icann.org>> wrote: Dear Susan and Anne, Thank you for your inputs and contribution to the subject matter. @Susan your submission is spot on and am sure it provides some further clarity. where the Council adopts a 7 day timeframe in providing its consent over referring an issue to SPIRT, on a case-by-case basis I am hopeful the Council can beat this deadline in providing its conscent where needed. @ Anne i consider your first two proposals friendly and have gone ahead to update the motion before the Council in line with your suggestions - That the time for a consent be extended to 7 days and that Council leadership make the call for an objection. 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 your third request, the SPIRT charter explicitly recommends they come back to council on an issue that revolves around developing new policy (Type 3 Process)- Note that the SPIRT is a team of experts that are deemed to have the required competence to work along ICANN Org. In resolving any Type 2 issue that may arise. Mandating that they revert back to council at every point a decision needs to be made nullifies the intent behind how they are currently chatered, saddles the council with the same task they are to resolve and i believe isn’t the spirt behind the Predictability framework. I would urge that the council aligns with the PF and SPIRT Charther. Hopefully, this gets us all moving towards a consensus on the issue. Lawrence. ----- [Image] [Image] Lawrence Olawale-Roberts Global President & Managing Director Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org<mailto:Lawrence@microboss.org> [Image] [Image] …collaboration to enhance communication. [Image] https://www.microboss.org<https://www.microboss.org/> | [Image]<https://www.facebook.com/microbosstech/> [Image]<https://www.linkedin.com/company/microbosstech/> [Image]<https://mobile.twitter.com/microbosstech> [Image]<https://www.instagram.com/microbosstech/?hl=en> [Image]<https://www.youtube.com/@microboss> 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: Susan Payne via council <council@icann.org<mailto:council@icann.org>> Sent: Monday, May 11, 2026 5:44:15 PM To: GNSO council <council@icann.org<mailto:council@icann.org>> Subject: [council] Re: GNSO Council Motion for SPIRT Alerts Thanks to Lawrence for bringing this to Council in his capacity as the liaison to the SPIRT, and to Anne and Farzi for their comments. I wanted to just make a couple of comments, for the benefit of Councillors, particularly those who perhaps are not so familiar with the detail as yet. As a reminder, the SPIRT operates under the oversight of Council. Where an issue comes to the attention of the SPIRT which may require a change to the New gTLD Program, the SPIRT cannot consider that issue of its own volition, since the SPIRT cannot refer an issue to itself. Council may refer the issue to the SPIRT, however, and ask the SPIRT to look at it. What we are doing here is trying to set out a process for how that happens, including some timing expectations since such issues may be quite time-sensitive. Under the SPIRT Charter, the first task of the SPIRT is to determine whether the issue can be resolved in a manner that is consistent with existing policy recommendations. If SPIRT concludes that it cannot (in other words, that a policy change would be needed), then the SPIRT is already required under its Charter to confer with the Council on a path forward. But, with an issue that the SPIRT is aware of (but which has not been referred to it) it cannot even make that assessment because it is not empowered to act. By this process, Council will only be giving the SPIRT permission to evaluate the issue, we are not signing off on a proposed solution. Nothing in this process supersedes the SPIRT Charter. It is merely a pathway that allows the SPIRT to put something on Council’s radar and get permission from Council to look at it. I hope that we can work collaboratively to agree a timeline that allows Councillors time to confer with their groups, and allows the SPIRT to be put to work, where appropriate, as quickly as possible in time-sensitive situations. Input from others on what that timing might be – whether 72 hours, 7 days, or other – would be welcome. Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:ii_19e1c5da1c84cff311] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0> From: Anne ICANN via council <council@icann.org<mailto:council@icann.org>> Sent: 11 May 2026 15:51 To: Terri Agnew <terri.agnew@icann.org<mailto:terri.agnew@icann.org>> Cc: GNSO council <council@icann.org<mailto:council@icann.org>> Subject: [council] Re: GNSO Council Motion for SPIRT Alerts 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<mailto:anneicanngnso@gmail.com> On Mon, May 11, 2026 at 6:31 AM Terri Agnew via council <council@icann.org<mailto: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<mailto:council@icann.org>> Reply-To: "lawrence@microboss.org<mailto:lawrence@microboss.org>" <lawrence@microboss.org<mailto:lawrence@microboss.org>> Date: Saturday, May 9, 2026 at 6:26 AM To: GNSO council <council@icann.org<mailto: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. ----- Lawrence Olawale-Roberts Global President & Managing Director Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org<mailto:Lawrence@microboss.org> …collaboration to enhance communication. https://www.microboss.org [microboss.org]<https://urldefense.com/v3/__https:/www.microboss.org/__;!!PtGJab4!4Po1IC4Uci...> | [facebook.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> [linkedin.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> [mobile.twitter.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> [instagram.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> [youtube.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> 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,<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> 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.<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> 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.<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> _______________________________________________ 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.<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England<https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England<https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England<https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland<https://www.google.com/maps/search/15+William+Street,+South+West+Lane,+Edinb...>; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2<https://www.google.com/maps/search/Calle+Barcas+2?entry=gmail&source=g>, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/> _______________________________________________ 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.
I disagree Lawrence. I came up with that idea based on the SPIRT spirit and the charter. It actually goes pretty well with providing oversight and we don’t have to overengineer processes with deadlines to weigh in etc. Farzaneh On Tue, May 12, 2026 at 2:00 PM Lawrence O. Olawale-Roberts < lawrence@microboss.org> wrote:
Frankly Farzaneh, this is not how the SPIRT is chartered to work. Your proposal would require re-drafting the SPIRT charter and basically resetting the group without even allowing them or ICANN test the current process.
The SPIRT other path through which the can mitigate issues referred to them through ICANN Org. Does not require SPIRT coming back to Council for concurrence or consultations as long as the issue is not determined to be Type 3 - hence over engineering this process of just getting to secure council's approval to look into a matter might subsequently push dependence on staff to initiate issues for the SPIRT to act on.
LOR
-----
[image: Image]
[image: Image]
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
[image: Image]
[image: Image]
*…collaboration to enhance communication*.
[image: Image]
[image: Image] <https://www.facebook.com/microbosstech/>
[image: Image] <https://www.linkedin.com/company/microbosstech/>
[image: Image] <https://mobile.twitter.com/microbosstech>
[image: Image] <https://www.instagram.com/microbosstech/?hl=en>
[image: Image] <https://www.youtube.com/@microboss>
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:* farzaneh badii via council <council@icann.org> *Sent:* Tuesday, May 12, 2026 6:41:01 PM *To:* Anne ICANN <anneicanngnso@gmail.com> *Cc:* Lawrence O. Olawale-Roberts <lawrence@microboss.org>; GNSO council < council@icann.org>
*Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
Hi Anne
I said a coordination group. And they only coordinate, they provide briefing, they provide background. If all council members want to focus on it, they can. And I didn’t say don’t bring back to the council. From the beginning I have been insiting council involvement through all the process. I think this is better than having a liaison have to do it and be the messenger, this workload is going to get heavy.
Another way is, a stakeholder group provide an issue to their council member, we discuss with the whole council and having SPIRT come to the council and discuss further and come up with a solution.
Farzaneh
On Tue, May 12, 2026 at 1:06 PM Anne ICANN <anneicanngnso@gmail.com> wrote:
Hi Farzaneh. I'm a bit surprised that you suggest a "small team" of Councilors that want to work with SPIRT to develop the analysis and work on solutions? If the issue is assigned to the SPIRT due to their expertise, I would favor having them bring a proposal back to the full Council. Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com
On Tue, May 12, 2026 at 9:04 AM farzaneh badii <farzaneh.badii@gmail.com> wrote:
Well if we have a group of council members that are more active and monitor SPIRT issues and in touch with their stakeholders and they can bring the issue to the council and then the Council in collaboration with SPIRT sorts it out, I think that’s for the better. For now I can’t say yes to this motion there are too many unknowns and not much clarification and the more I look into it the more complicated it looks. And it will get more complicated. One stakeholder nor SPIRT should bring the issue to the council. This should be in a collaborative way. The more collaborative, the more efficient too!
But to address the problem Jeff has submitted on behalf of the registry stakeholder group, I think we can just discuss the issue during next week meeting and ask the council members that want to work with SPIRT to come up with a solution to do so and bring back the result to the council.
Farzaneh
On Tue, May 12, 2026 at 11:18 AM Anne ICANN via council <council@icann.org> wrote:
P.S. I should explain again that the Category 2 issue on RSP was actually raised by a SPIRT member on behalf of the RySG. To the extent that we are authorizing the SPIRT to raise an issue itself, It does not seem to me that the logic of just letting the SPIRT proceed to resolve on its own without conferring with Council still applies. (This comment is limited to Category 2 issues raised by the SPIRT itself or one of its members.)
Reminder again that the Charter actually prohibits the SPIRT from raising issues. During Charter drafting, it was assumed the SG or C would raise the issue at the Council level if it was not raised by Board, ICANN, or the Council in some other way. So this mechanism for allowing the SPIRT (or in this case an RySG member of the SPIRT) to raise an issue was not contemplated by the Charter. Again, it may be more efficient to allow the SPIRT to do this, if only because it presumably meets more often than Council, but that does not mean that the SPIRT should be authorized to resolve an issue it has raised on its own (either by consensus or by Leadership team of the SPIRT or by an individual member) without coming back to the Council with the proposed solution. The very notion that the SPIRT can raise an issue itself is a new one and we need to be especially careful with a 7 day non-objection/consent process. Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com
On Tue, May 12, 2026 at 6:29 AM Anne ICANN <anneicanngnso@gmail.com> wrote:
Thanks Lawrence. Re the third issue, the RSP issue is a Categroy 2 issue - non-minor operational with material impact on applicants - but apparently ICANN has asked that this issue be briefed to the Council. Some members of SPIRT thought they could deal with it alone without talking to us. ICANN Org did not agree - presumably because of the nature of the material impact on RSP Qualification. So how is it that Council can agree with you that a Category 2 issue brought to the Council in this manner does not need to come back to Council for the proposed solution?
Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com
On Mon, May 11, 2026 at 1:04 PM Lawrence O. Olawale-Roberts via council < council@icann.org> wrote:
Dear Susan and Anne,
Thank you for your inputs and contribution to the subject matter.
@Susan your submission is spot on and am sure it provides some further clarity. where the Council adopts a 7 day timeframe in providing its consent over referring an issue to SPIRT, on a case-by-case basis I am hopeful the Council can beat this deadline in providing its conscent where needed.
@ Anne i consider your first two proposals friendly and have gone ahead to update the motion before the Council in line with your suggestions - That the time for a consent be extended to 7 days and that Council leadership make the call for an objection.
*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 your third request, the SPIRT charter explicitly recommends they come back to council on an issue that revolves around developing new policy (Type 3 Process)- Note that the SPIRT is a team of experts that are deemed to have the required competence to work along ICANN Org. In resolving any Type 2 issue that may arise. Mandating that they revert back to council at every point a decision needs to be made nullifies the intent behind how they are currently chatered, saddles the council with the same task they are to resolve and i believe isn’t the spirt behind the Predictability framework. I would urge that the council aligns with the PF and SPIRT Charther.
Hopefully, this gets us all moving towards a consensus on the issue.
Lawrence.
-----
[image: Image]
[image: Image]
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
[image: Image]
[image: Image]
*…collaboration to enhance communication*.
[image: Image]
[image: Image] <https://www.facebook.com/microbosstech/>
[image: Image] <https://www.linkedin.com/company/microbosstech/>
[image: Image] <https://mobile.twitter.com/microbosstech>
[image: Image] <https://www.instagram.com/microbosstech/?hl=en>
[image: Image] <https://www.youtube.com/@microboss>
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:* Susan Payne via council <council@icann.org> *Sent:* Monday, May 11, 2026 5:44:15 PM *To:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
Thanks to Lawrence for bringing this to Council in his capacity as the liaison to the SPIRT, and to Anne and Farzi for their comments.
I wanted to just make a couple of comments, for the benefit of Councillors, particularly those who perhaps are not so familiar with the detail as yet.
As a reminder, the SPIRT operates under the oversight of Council. Where an issue comes to the attention of the SPIRT which may require a change to the New gTLD Program, the SPIRT cannot consider that issue of its own volition, since the SPIRT cannot refer an issue to itself. Council may refer the issue to the SPIRT, however, and ask the SPIRT to look at it. What we are doing here is trying to set out a process for how that happens, including some timing expectations since such issues may be quite time-sensitive.
Under the SPIRT Charter, the first task of the SPIRT is to determine whether the issue can be resolved in a manner that is consistent with existing policy recommendations. If SPIRT concludes that it cannot (in other words, that a policy change would be needed), then the SPIRT is already required under its Charter to confer with the Council on a path forward. But, with an issue that the SPIRT is aware of (but which has not been referred to it) it cannot even make that assessment because it is not empowered to act. By this process, Council will only be giving the SPIRT permission to evaluate the issue, we are not signing off on a proposed solution.
Nothing in this process supersedes the SPIRT Charter. It is merely a pathway that allows the SPIRT to put something on Council’s radar and get permission from Council to look at it.
I hope that we can work collaboratively to agree a timeline that allows Councillors time to confer with their groups, and allows the SPIRT to be put to work, where appropriate, as quickly as possible in time-sensitive situations. Input from others on what that timing might be – whether 72 hours, 7 days, or other – would be welcome.
Susan Payne Head of Legal Policy Com Laude *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
*Follow us on **LinkedIn* <https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0>* and* *Youtube* <https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0>
*From:* Anne ICANN via council <council@icann.org> *Sent:* 11 May 2026 15:51 *To:* Terri Agnew <terri.agnew@icann.org> *Cc:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
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.
-----
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
*…collaboration to enhance communication*.
https://www.microboss.org [microboss.org] <https://urldefense.com/v3/__https:/www.microboss.org/__;!!PtGJab4!4Po1IC4Uci...> |
[facebook.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[linkedin.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[mobile.twitter.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[instagram.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[youtube.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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, <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
_______________________________________________ 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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
------------------------------ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland <https://www.google.com/maps/search/15+William+Street,+South+West+Lane,+Edinb...>; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2 <https://www.google.com/maps/search/Calle+Barcas+2?entry=gmail&source=g>, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com/> _______________________________________________ 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.
Hi Lawrence. I can't get over the fact that GDD thought this should be raised with Council but the RySG thought it would be more expedient to address via the SPIRT. I know there are RSPs that have already been qualified based on a promise to abide by the IETF standard (which has now changed). Per SPIRT Leadership, they don't think they have jurisdiction to make a retroactive change for RSPs who have already qualified that is consistent with what they are suggesting going forward as a solution for RSPs that qualify in the future. In that case, how could the SPIRT actually avoid bringing this back to Council for discussion? Again, we don't know what the ICANN view is on this issue. We have not yet heard directly from GDD or from RySG at Council. The good news is we have something more than just a hypothetical issue to help sort out these considerations. Again, the process you describe where Council does not get involved is for issues raised directly by ICANN or the Board which are not policy issues. For whatever reason, ICANN GDD thought it could not just bring the RSP Qualification issue to the SPIRT for resolution with no notice to Council. Any chance we can hear from Lars or Francisco in the Council meeting on May 21? Never mind that this particular issue may not need an "urgent" or "time-sensitive" resolution before August 12. It's very possible that the same set of procedural circumstances could arise in the 7 day "consent via non-objection" scenario and that is why I asked for a friendly amendment requiring SPIRT to review the proposed solution with Council when it has essentially referred an issue to itself via the newly proposed "SPIRT Alert" process. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com On Tue, May 12, 2026 at 11:00 AM Lawrence O. Olawale-Roberts < lawrence@microboss.org> wrote:
Frankly Farzaneh, this is not how the SPIRT is chartered to work. Your proposal would require re-drafting the SPIRT charter and basically resetting the group without even allowing them or ICANN test the current process.
The SPIRT other path through which the can mitigate issues referred to them through ICANN Org. Does not require SPIRT coming back to Council for concurrence or consultations as long as the issue is not determined to be Type 3 - hence over engineering this process of just getting to secure council's approval to look into a matter might subsequently push dependence on staff to initiate issues for the SPIRT to act on.
LOR
-----
[image: Image]
[image: Image]
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
[image: Image]
[image: Image]
*…collaboration to enhance communication*.
[image: Image]
[image: Image] <https://www.facebook.com/microbosstech/>
[image: Image] <https://www.linkedin.com/company/microbosstech/>
[image: Image] <https://mobile.twitter.com/microbosstech>
[image: Image] <https://www.instagram.com/microbosstech/?hl=en>
[image: Image] <https://www.youtube.com/@microboss>
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:* farzaneh badii via council <council@icann.org> *Sent:* Tuesday, May 12, 2026 6:41:01 PM *To:* Anne ICANN <anneicanngnso@gmail.com> *Cc:* Lawrence O. Olawale-Roberts <lawrence@microboss.org>; GNSO council < council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
Hi Anne
I said a coordination group. And they only coordinate, they provide briefing, they provide background. If all council members want to focus on it, they can. And I didn’t say don’t bring back to the council. From the beginning I have been insiting council involvement through all the process. I think this is better than having a liaison have to do it and be the messenger, this workload is going to get heavy.
Another way is, a stakeholder group provide an issue to their council member, we discuss with the whole council and having SPIRT come to the council and discuss further and come up with a solution.
Farzaneh
On Tue, May 12, 2026 at 1:06 PM Anne ICANN <anneicanngnso@gmail.com> wrote:
Hi Farzaneh. I'm a bit surprised that you suggest a "small team" of Councilors that want to work with SPIRT to develop the analysis and work on solutions? If the issue is assigned to the SPIRT due to their expertise, I would favor having them bring a proposal back to the full Council. Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com
On Tue, May 12, 2026 at 9:04 AM farzaneh badii <farzaneh.badii@gmail.com> wrote:
Well if we have a group of council members that are more active and monitor SPIRT issues and in touch with their stakeholders and they can bring the issue to the council and then the Council in collaboration with SPIRT sorts it out, I think that’s for the better. For now I can’t say yes to this motion there are too many unknowns and not much clarification and the more I look into it the more complicated it looks. And it will get more complicated. One stakeholder nor SPIRT should bring the issue to the council. This should be in a collaborative way. The more collaborative, the more efficient too!
But to address the problem Jeff has submitted on behalf of the registry stakeholder group, I think we can just discuss the issue during next week meeting and ask the council members that want to work with SPIRT to come up with a solution to do so and bring back the result to the council.
Farzaneh
On Tue, May 12, 2026 at 11:18 AM Anne ICANN via council <council@icann.org> wrote:
P.S. I should explain again that the Category 2 issue on RSP was actually raised by a SPIRT member on behalf of the RySG. To the extent that we are authorizing the SPIRT to raise an issue itself, It does not seem to me that the logic of just letting the SPIRT proceed to resolve on its own without conferring with Council still applies. (This comment is limited to Category 2 issues raised by the SPIRT itself or one of its members.)
Reminder again that the Charter actually prohibits the SPIRT from raising issues. During Charter drafting, it was assumed the SG or C would raise the issue at the Council level if it was not raised by Board, ICANN, or the Council in some other way. So this mechanism for allowing the SPIRT (or in this case an RySG member of the SPIRT) to raise an issue was not contemplated by the Charter. Again, it may be more efficient to allow the SPIRT to do this, if only because it presumably meets more often than Council, but that does not mean that the SPIRT should be authorized to resolve an issue it has raised on its own (either by consensus or by Leadership team of the SPIRT or by an individual member) without coming back to the Council with the proposed solution. The very notion that the SPIRT can raise an issue itself is a new one and we need to be especially careful with a 7 day non-objection/consent process. Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com
On Tue, May 12, 2026 at 6:29 AM Anne ICANN <anneicanngnso@gmail.com> wrote:
Thanks Lawrence. Re the third issue, the RSP issue is a Categroy 2 issue - non-minor operational with material impact on applicants - but apparently ICANN has asked that this issue be briefed to the Council. Some members of SPIRT thought they could deal with it alone without talking to us. ICANN Org did not agree - presumably because of the nature of the material impact on RSP Qualification. So how is it that Council can agree with you that a Category 2 issue brought to the Council in this manner does not need to come back to Council for the proposed solution?
Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com
On Mon, May 11, 2026 at 1:04 PM Lawrence O. Olawale-Roberts via council < council@icann.org> wrote:
Dear Susan and Anne,
Thank you for your inputs and contribution to the subject matter.
@Susan your submission is spot on and am sure it provides some further clarity. where the Council adopts a 7 day timeframe in providing its consent over referring an issue to SPIRT, on a case-by-case basis I am hopeful the Council can beat this deadline in providing its conscent where needed.
@ Anne i consider your first two proposals friendly and have gone ahead to update the motion before the Council in line with your suggestions - That the time for a consent be extended to 7 days and that Council leadership make the call for an objection.
*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 your third request, the SPIRT charter explicitly recommends they come back to council on an issue that revolves around developing new policy (Type 3 Process)- Note that the SPIRT is a team of experts that are deemed to have the required competence to work along ICANN Org. In resolving any Type 2 issue that may arise. Mandating that they revert back to council at every point a decision needs to be made nullifies the intent behind how they are currently chatered, saddles the council with the same task they are to resolve and i believe isn’t the spirt behind the Predictability framework. I would urge that the council aligns with the PF and SPIRT Charther.
Hopefully, this gets us all moving towards a consensus on the issue.
Lawrence.
-----
[image: Image]
[image: Image]
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
[image: Image]
[image: Image]
*…collaboration to enhance communication*.
[image: Image]
[image: Image] <https://www.facebook.com/microbosstech/>
[image: Image] <https://www.linkedin.com/company/microbosstech/>
[image: Image] <https://mobile.twitter.com/microbosstech>
[image: Image] <https://www.instagram.com/microbosstech/?hl=en>
[image: Image] <https://www.youtube.com/@microboss>
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:* Susan Payne via council <council@icann.org> *Sent:* Monday, May 11, 2026 5:44:15 PM *To:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
Thanks to Lawrence for bringing this to Council in his capacity as the liaison to the SPIRT, and to Anne and Farzi for their comments.
I wanted to just make a couple of comments, for the benefit of Councillors, particularly those who perhaps are not so familiar with the detail as yet.
As a reminder, the SPIRT operates under the oversight of Council. Where an issue comes to the attention of the SPIRT which may require a change to the New gTLD Program, the SPIRT cannot consider that issue of its own volition, since the SPIRT cannot refer an issue to itself. Council may refer the issue to the SPIRT, however, and ask the SPIRT to look at it. What we are doing here is trying to set out a process for how that happens, including some timing expectations since such issues may be quite time-sensitive.
Under the SPIRT Charter, the first task of the SPIRT is to determine whether the issue can be resolved in a manner that is consistent with existing policy recommendations. If SPIRT concludes that it cannot (in other words, that a policy change would be needed), then the SPIRT is already required under its Charter to confer with the Council on a path forward. But, with an issue that the SPIRT is aware of (but which has not been referred to it) it cannot even make that assessment because it is not empowered to act. By this process, Council will only be giving the SPIRT permission to evaluate the issue, we are not signing off on a proposed solution.
Nothing in this process supersedes the SPIRT Charter. It is merely a pathway that allows the SPIRT to put something on Council’s radar and get permission from Council to look at it.
I hope that we can work collaboratively to agree a timeline that allows Councillors time to confer with their groups, and allows the SPIRT to be put to work, where appropriate, as quickly as possible in time-sensitive situations. Input from others on what that timing might be – whether 72 hours, 7 days, or other – would be welcome.
Susan Payne Head of Legal Policy Com Laude *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
*Follow us on **LinkedIn* <https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0>* and* *Youtube* <https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0>
*From:* Anne ICANN via council <council@icann.org> *Sent:* 11 May 2026 15:51 *To:* Terri Agnew <terri.agnew@icann.org> *Cc:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
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.
-----
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
*…collaboration to enhance communication*.
https://www.microboss.org [microboss.org] <https://urldefense.com/v3/__https:/www.microboss.org/__;!!PtGJab4!4Po1IC4Uci...> |
[facebook.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[linkedin.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[mobile.twitter.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[instagram.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[youtube.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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, <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
_______________________________________________ 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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
------------------------------ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland <https://www.google.com/maps/search/15+William+Street,+South+West+Lane,+Edinb...>; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2 <https://www.google.com/maps/search/Calle+Barcas+2?entry=gmail&source=g>, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com/> _______________________________________________ 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.
Dear Farzi, the SPIRT as a body of experts have been chartered through a process approved by the GNSO Council to deliver on its mandate as spelt out in its charter. The council has a role as an arbiter between the SPIRT and ICANN Org whenever there is a diffrence in opinions between both parties - as such inserting the Council as the validator of any decision made by SPIRT makes us an interested party and may cause for the process flow of the Council task to be moved to the Board. A coordination group or small team seating with SPIRIT cannot substitute for receiving approval from the GNSO Council neither can the body refer a Type-3 issue to the Council - hence cannot serve this process. Dear Anne, Once the Council refers an issue to the SPIRT as per the charter, the SPIRT would have to first determine and confirm that it is a Type 2 issue and after collaboration with the GNSO Council, if appropriate, inform ICANN org of a needed change to the program. ICANN org will then determine if a change to the ongoing round is needed and if contrary to the SPIRT’s position ICANN Org determines that No change is needed the SPIRT comes back to confer with the GNSO Council and on determining that a change is needed, the Council engages with the Board, allowing the ICANN Board to ultimately decide if a change is needed, and were they do direct ICANN Org to apply the Predictability framework. I am not aware that ICANN Org. asked that the issue identified around RSP applications be brought as a council belief, rather ICANN staff were approached to see if there was merit refering it to the SPIRT and were advised to use the SPIRT membership route to introduce it as a topic to nurge Council to have referred to SPIRT. Leadership went ahead to review and ask members if they objected to having the issue passed on to Council for referral to SPIRT. Whilst the SPIRT is expected to collaborate with Council, I am not sure they are designed to come back to council for a Solution, otherwise why have them assembled? LOR. ----- [Image] [Image] Lawrence Olawale-Roberts Global President & Managing Director Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org<mailto:Lawrence@microboss.org> [Image] [Image] …collaboration to enhance communication. [Image] https://www.microboss.org<https://www.microboss.org/> | [Image]<https://www.facebook.com/microbosstech/> [Image]<https://www.linkedin.com/company/microbosstech/> [Image]<https://mobile.twitter.com/microbosstech> [Image]<https://www.instagram.com/microbosstech/?hl=en> [Image]<https://www.youtube.com/@microboss> 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: Lawrence O. Olawale-Roberts via council <council@icann.org> Sent: Tuesday, May 12, 2026 7:01 PM To: farzaneh badii <farzaneh.badii@gmail.com>; Anne ICANN <anneicanngnso@gmail.com> Cc: GNSO council <council@icann.org> Subject: [council] Re: GNSO Council Motion for SPIRT Alerts Frankly Farzaneh, this is not how the SPIRT is chartered to work. Your proposal would require re-drafting the SPIRT charter and basically resetting the group without even allowing them or ICANN test the current process. The SPIRT other path through which the can mitigate issues referred to them through ICANN Org. Does not require SPIRT coming back to Council for concurrence or consultations as long as the issue is not determined to be Type 3 - hence over engineering this process of just getting to secure council's approval to look into a matter might subsequently push dependence on staff to initiate issues for the SPIRT to act on. LOR ----- [Image] [Image] Lawrence Olawale-Roberts Global President & Managing Director Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org<mailto:Lawrence@microboss.org> [Image] [Image] …collaboration to enhance communication. [Image] https://www.microboss.org<https://www.microboss.org/> | [Image]<https://www.facebook.com/microbosstech/> [Image]<https://www.linkedin.com/company/microbosstech/> [Image]<https://mobile.twitter.com/microbosstech> [Image]<https://www.instagram.com/microbosstech/?hl=en> [Image]<https://www.youtube.com/@microboss> 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: farzaneh badii via council <council@icann.org> Sent: Tuesday, May 12, 2026 6:41:01 PM To: Anne ICANN <anneicanngnso@gmail.com> Cc: Lawrence O. Olawale-Roberts <lawrence@microboss.org>; GNSO council <council@icann.org> Subject: [council] Re: GNSO Council Motion for SPIRT Alerts Hi Anne I said a coordination group. And they only coordinate, they provide briefing, they provide background. If all council members want to focus on it, they can. And I didn’t say don’t bring back to the council. From the beginning I have been insiting council involvement through all the process. I think this is better than having a liaison have to do it and be the messenger, this workload is going to get heavy. Another way is, a stakeholder group provide an issue to their council member, we discuss with the whole council and having SPIRT come to the council and discuss further and come up with a solution. Farzaneh On Tue, May 12, 2026 at 1:06 PM Anne ICANN <anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com>> wrote: Hi Farzaneh. I'm a bit surprised that you suggest a "small team" of Councilors that want to work with SPIRT to develop the analysis and work on solutions? If the issue is assigned to the SPIRT due to their expertise, I would favor having them bring a proposal back to the full Council. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Tue, May 12, 2026 at 9:04 AM farzaneh badii <farzaneh.badii@gmail.com<mailto:farzaneh.badii@gmail.com>> wrote: Well if we have a group of council members that are more active and monitor SPIRT issues and in touch with their stakeholders and they can bring the issue to the council and then the Council in collaboration with SPIRT sorts it out, I think that’s for the better. For now I can’t say yes to this motion there are too many unknowns and not much clarification and the more I look into it the more complicated it looks. And it will get more complicated. One stakeholder nor SPIRT should bring the issue to the council. This should be in a collaborative way. The more collaborative, the more efficient too! But to address the problem Jeff has submitted on behalf of the registry stakeholder group, I think we can just discuss the issue during next week meeting and ask the council members that want to work with SPIRT to come up with a solution to do so and bring back the result to the council. Farzaneh On Tue, May 12, 2026 at 11:18 AM Anne ICANN via council <council@icann.org<mailto:council@icann.org>> wrote: P.S. I should explain again that the Category 2 issue on RSP was actually raised by a SPIRT member on behalf of the RySG. To the extent that we are authorizing the SPIRT to raise an issue itself, It does not seem to me that the logic of just letting the SPIRT proceed to resolve on its own without conferring with Council still applies. (This comment is limited to Category 2 issues raised by the SPIRT itself or one of its members.) Reminder again that the Charter actually prohibits the SPIRT from raising issues. During Charter drafting, it was assumed the SG or C would raise the issue at the Council level if it was not raised by Board, ICANN, or the Council in some other way. So this mechanism for allowing the SPIRT (or in this case an RySG member of the SPIRT) to raise an issue was not contemplated by the Charter. Again, it may be more efficient to allow the SPIRT to do this, if only because it presumably meets more often than Council, but that does not mean that the SPIRT should be authorized to resolve an issue it has raised on its own (either by consensus or by Leadership team of the SPIRT or by an individual member) without coming back to the Council with the proposed solution. The very notion that the SPIRT can raise an issue itself is a new one and we need to be especially careful with a 7 day non-objection/consent process. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Tue, May 12, 2026 at 6:29 AM Anne ICANN <anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com>> wrote: Thanks Lawrence. Re the third issue, the RSP issue is a Categroy 2 issue - non-minor operational with material impact on applicants - but apparently ICANN has asked that this issue be briefed to the Council. Some members of SPIRT thought they could deal with it alone without talking to us. ICANN Org did not agree - presumably because of the nature of the material impact on RSP Qualification. So how is it that Council can agree with you that a Category 2 issue brought to the Council in this manner does not need to come back to Council for the proposed solution? Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Mon, May 11, 2026 at 1:04 PM Lawrence O. Olawale-Roberts via council <council@icann.org<mailto:council@icann.org>> wrote: Dear Susan and Anne, Thank you for your inputs and contribution to the subject matter. @Susan your submission is spot on and am sure it provides some further clarity. where the Council adopts a 7 day timeframe in providing its consent over referring an issue to SPIRT, on a case-by-case basis I am hopeful the Council can beat this deadline in providing its conscent where needed. @ Anne i consider your first two proposals friendly and have gone ahead to update the motion before the Council in line with your suggestions - That the time for a consent be extended to 7 days and that Council leadership make the call for an objection. 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 your third request, the SPIRT charter explicitly recommends they come back to council on an issue that revolves around developing new policy (Type 3 Process)- Note that the SPIRT is a team of experts that are deemed to have the required competence to work along ICANN Org. In resolving any Type 2 issue that may arise. Mandating that they revert back to council at every point a decision needs to be made nullifies the intent behind how they are currently chatered, saddles the council with the same task they are to resolve and i believe isn’t the spirt behind the Predictability framework. I would urge that the council aligns with the PF and SPIRT Charther. Hopefully, this gets us all moving towards a consensus on the issue. Lawrence. ----- [Image] [Image] Lawrence Olawale-Roberts Global President & Managing Director Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org<mailto:Lawrence@microboss.org> [Image] [Image] …collaboration to enhance communication. [Image] https://www.microboss.org<https://www.microboss.org/> | [Image]<https://www.facebook.com/microbosstech/> [Image]<https://www.linkedin.com/company/microbosstech/> [Image]<https://mobile.twitter.com/microbosstech> [Image]<https://www.instagram.com/microbosstech/?hl=en> [Image]<https://www.youtube.com/@microboss> 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: Susan Payne via council <council@icann.org<mailto:council@icann.org>> Sent: Monday, May 11, 2026 5:44:15 PM To: GNSO council <council@icann.org<mailto:council@icann.org>> Subject: [council] Re: GNSO Council Motion for SPIRT Alerts Thanks to Lawrence for bringing this to Council in his capacity as the liaison to the SPIRT, and to Anne and Farzi for their comments. I wanted to just make a couple of comments, for the benefit of Councillors, particularly those who perhaps are not so familiar with the detail as yet. As a reminder, the SPIRT operates under the oversight of Council. Where an issue comes to the attention of the SPIRT which may require a change to the New gTLD Program, the SPIRT cannot consider that issue of its own volition, since the SPIRT cannot refer an issue to itself. Council may refer the issue to the SPIRT, however, and ask the SPIRT to look at it. What we are doing here is trying to set out a process for how that happens, including some timing expectations since such issues may be quite time-sensitive. Under the SPIRT Charter, the first task of the SPIRT is to determine whether the issue can be resolved in a manner that is consistent with existing policy recommendations. If SPIRT concludes that it cannot (in other words, that a policy change would be needed), then the SPIRT is already required under its Charter to confer with the Council on a path forward. But, with an issue that the SPIRT is aware of (but which has not been referred to it) it cannot even make that assessment because it is not empowered to act. By this process, Council will only be giving the SPIRT permission to evaluate the issue, we are not signing off on a proposed solution. Nothing in this process supersedes the SPIRT Charter. It is merely a pathway that allows the SPIRT to put something on Council’s radar and get permission from Council to look at it. I hope that we can work collaboratively to agree a timeline that allows Councillors time to confer with their groups, and allows the SPIRT to be put to work, where appropriate, as quickly as possible in time-sensitive situations. Input from others on what that timing might be – whether 72 hours, 7 days, or other – would be welcome. Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:ii_19e1c5da1c84cff311] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0> From: Anne ICANN via council <council@icann.org<mailto:council@icann.org>> Sent: 11 May 2026 15:51 To: Terri Agnew <terri.agnew@icann.org<mailto:terri.agnew@icann.org>> Cc: GNSO council <council@icann.org<mailto:council@icann.org>> Subject: [council] Re: GNSO Council Motion for SPIRT Alerts 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<mailto:anneicanngnso@gmail.com> On Mon, May 11, 2026 at 6:31 AM Terri Agnew via council <council@icann.org<mailto: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<mailto:council@icann.org>> Reply-To: "lawrence@microboss.org<mailto:lawrence@microboss.org>" <lawrence@microboss.org<mailto:lawrence@microboss.org>> Date: Saturday, May 9, 2026 at 6:26 AM To: GNSO council <council@icann.org<mailto: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. ----- Lawrence Olawale-Roberts Global President & Managing Director Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org<mailto:Lawrence@microboss.org> …collaboration to enhance communication. https://www.microboss.org [microboss.org]<https://urldefense.com/v3/__https:/www.microboss.org/__;!!PtGJab4!4Po1IC4Uci...> | [facebook.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> [linkedin.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> [mobile.twitter.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> [instagram.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> [youtube.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> 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,<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> 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.<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> 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.<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> _______________________________________________<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> council mailing list -- <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> council@icann.org<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> To unsubscribe send an email to <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> council-leave@icann.org<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> _______________________________________________<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> 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://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJab4!4Po1IC4Uciu-bbgeBNYeGncd1lAX_OSBDktLsJw5HBaInI6BmN8LiLweAm9YyH1VO3HmdodfcMntqNzFA5WX34Q$>https://www.icann.org/privacy/policy<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJab4!4Po1IC4Uciu-bbgeBNYeGncd1lAX_OSBDktLsJw5HBaInI6BmN8LiLweAm9YyH1VO3HmdodfcMntqNzFA5WX34Q$>) and the website Terms of Service (<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJab4!4Po1IC4Uciu-bbgeBNYeGncd1lAX_OSBDktLsJw5HBaInI6BmN8LiLweAm9YyH1VO3HmdodfcMntqNzFA5WX34Q$>https://www.icann.org/privacy/tos<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJab4!4Po1IC4Uciu-bbgeBNYeGncd1lAX_OSBDktLsJw5HBaInI6BmN8LiLweAm9YyH1VO3HmdodfcMntqNzFA5WX34Q$>). 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.<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England<https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England<https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England<https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland<https://www.google.com/maps/search/15+William+Street,+South+West+Lane,+Edinb...>; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2<https://www.google.com/maps/search/Calle+Barcas+2?entry=gmail&source=g>, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/> _______________________________________________ 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.
Lawrence, The Charter empowers the SPIRT to deal with issues other than Policy issues directly without bringing them back to Council WHEN THE ISSUE IS RAISED BY ICANN, the BOARD, or COUNCIL. Its reason for existence is defined accordlngly in the Charter but in this case, apparently no one was comfortable saying the issue could be resolved without Council involvement. You saw the SPIRT resolve an issue re ASP Qualification via the SPIRT change log. Obviously there is a reason for the SPIRT to exist but its' existence is defined by its Charter and the Alert process is not part of that Charter. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com On Tue, May 12, 2026 at 1:54 PM Lawrence O. Olawale-Roberts < lawrence@microboss.org> wrote:
Dear Farzi, the SPIRT as a body of experts have been chartered through a process approved by the GNSO Council to deliver on its mandate as spelt out in its charter. The council has a role as an arbiter between the SPIRT and ICANN Org whenever there is a diffrence in opinions between both parties - as such inserting the Council as the validator of any decision made by SPIRT makes us an interested party and may cause for the process flow of the Council task to be moved to the Board.
A coordination group or small team seating with SPIRIT cannot substitute for receiving approval from the GNSO Council neither can the body refer a Type-3 issue to the Council - hence cannot serve this process.
Dear Anne, Once the Council refers an issue to the SPIRT as per the charter, the SPIRT would have to first determine and confirm that it is a Type 2 issue and after collaboration with the GNSO Council, if appropriate, inform ICANN org of a needed change to the program. ICANN org will then determine if a change to the ongoing round is needed and if contrary to the SPIRT’s position ICANN Org determines that No change is needed the SPIRT comes back to confer with the GNSO Council and on determining that a change is needed, the Council engages with the Board, allowing the ICANN Board to ultimately decide if a change is needed, and were they do direct ICANN Org to apply the Predictability framework.
I am not aware that ICANN Org. asked that the issue identified around RSP applications be brought as a council belief, rather ICANN staff were approached to see if there was merit refering it to the SPIRT and were advised to use the SPIRT membership route to introduce it as a topic to nurge Council to have referred to SPIRT. Leadership went ahead to review and ask members if they objected to having the issue passed on to Council for referral to SPIRT. Whilst the SPIRT is expected to collaborate with Council, I am not sure they are designed to come back to council for a Solution, otherwise why have them assembled?
LOR.
-----
[image: Image]
[image: Image]
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
[image: Image]
[image: Image]
*…collaboration to enhance communication*.
[image: Image]
[image: Image] <https://www.facebook.com/microbosstech/>
[image: Image] <https://www.linkedin.com/company/microbosstech/>
[image: Image] <https://mobile.twitter.com/microbosstech>
[image: Image] <https://www.instagram.com/microbosstech/?hl=en>
[image: Image] <https://www.youtube.com/@microboss>
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:* Lawrence O. Olawale-Roberts via council <council@icann.org> *Sent:* Tuesday, May 12, 2026 7:01 PM *To:* farzaneh badii <farzaneh.badii@gmail.com>; Anne ICANN < anneicanngnso@gmail.com> *Cc:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
Frankly Farzaneh, this is not how the SPIRT is chartered to work. Your proposal would require re-drafting the SPIRT charter and basically resetting the group without even allowing them or ICANN test the current process.
The SPIRT other path through which the can mitigate issues referred to them through ICANN Org. Does not require SPIRT coming back to Council for concurrence or consultations as long as the issue is not determined to be Type 3 - hence over engineering this process of just getting to secure council's approval to look into a matter might subsequently push dependence on staff to initiate issues for the SPIRT to act on.
LOR
-----
[image: Image]
[image: Image]
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
[image: Image]
[image: Image]
*…collaboration to enhance communication*.
[image: Image]
[image: Image] <https://www.facebook.com/microbosstech/>
[image: Image] <https://www.linkedin.com/company/microbosstech/>
[image: Image] <https://mobile.twitter.com/microbosstech>
[image: Image] <https://www.instagram.com/microbosstech/?hl=en>
[image: Image] <https://www.youtube.com/@microboss>
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:* farzaneh badii via council <council@icann.org> *Sent:* Tuesday, May 12, 2026 6:41:01 PM *To:* Anne ICANN <anneicanngnso@gmail.com> *Cc:* Lawrence O. Olawale-Roberts <lawrence@microboss.org>; GNSO council < council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
Hi Anne
I said a coordination group. And they only coordinate, they provide briefing, they provide background. If all council members want to focus on it, they can. And I didn’t say don’t bring back to the council. From the beginning I have been insiting council involvement through all the process. I think this is better than having a liaison have to do it and be the messenger, this workload is going to get heavy.
Another way is, a stakeholder group provide an issue to their council member, we discuss with the whole council and having SPIRT come to the council and discuss further and come up with a solution.
Farzaneh
On Tue, May 12, 2026 at 1:06 PM Anne ICANN <anneicanngnso@gmail.com> wrote:
Hi Farzaneh. I'm a bit surprised that you suggest a "small team" of Councilors that want to work with SPIRT to develop the analysis and work on solutions? If the issue is assigned to the SPIRT due to their expertise, I would favor having them bring a proposal back to the full Council. Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com
On Tue, May 12, 2026 at 9:04 AM farzaneh badii <farzaneh.badii@gmail.com> wrote:
Well if we have a group of council members that are more active and monitor SPIRT issues and in touch with their stakeholders and they can bring the issue to the council and then the Council in collaboration with SPIRT sorts it out, I think that’s for the better. For now I can’t say yes to this motion there are too many unknowns and not much clarification and the more I look into it the more complicated it looks. And it will get more complicated. One stakeholder nor SPIRT should bring the issue to the council. This should be in a collaborative way. The more collaborative, the more efficient too!
But to address the problem Jeff has submitted on behalf of the registry stakeholder group, I think we can just discuss the issue during next week meeting and ask the council members that want to work with SPIRT to come up with a solution to do so and bring back the result to the council.
Farzaneh
On Tue, May 12, 2026 at 11:18 AM Anne ICANN via council <council@icann.org> wrote:
P.S. I should explain again that the Category 2 issue on RSP was actually raised by a SPIRT member on behalf of the RySG. To the extent that we are authorizing the SPIRT to raise an issue itself, It does not seem to me that the logic of just letting the SPIRT proceed to resolve on its own without conferring with Council still applies. (This comment is limited to Category 2 issues raised by the SPIRT itself or one of its members.)
Reminder again that the Charter actually prohibits the SPIRT from raising issues. During Charter drafting, it was assumed the SG or C would raise the issue at the Council level if it was not raised by Board, ICANN, or the Council in some other way. So this mechanism for allowing the SPIRT (or in this case an RySG member of the SPIRT) to raise an issue was not contemplated by the Charter. Again, it may be more efficient to allow the SPIRT to do this, if only because it presumably meets more often than Council, but that does not mean that the SPIRT should be authorized to resolve an issue it has raised on its own (either by consensus or by Leadership team of the SPIRT or by an individual member) without coming back to the Council with the proposed solution. The very notion that the SPIRT can raise an issue itself is a new one and we need to be especially careful with a 7 day non-objection/consent process. Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com
On Tue, May 12, 2026 at 6:29 AM Anne ICANN <anneicanngnso@gmail.com> wrote:
Thanks Lawrence. Re the third issue, the RSP issue is a Categroy 2 issue - non-minor operational with material impact on applicants - but apparently ICANN has asked that this issue be briefed to the Council. Some members of SPIRT thought they could deal with it alone without talking to us. ICANN Org did not agree - presumably because of the nature of the material impact on RSP Qualification. So how is it that Council can agree with you that a Category 2 issue brought to the Council in this manner does not need to come back to Council for the proposed solution?
Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com
On Mon, May 11, 2026 at 1:04 PM Lawrence O. Olawale-Roberts via council < council@icann.org> wrote:
Dear Susan and Anne,
Thank you for your inputs and contribution to the subject matter.
@Susan your submission is spot on and am sure it provides some further clarity. where the Council adopts a 7 day timeframe in providing its consent over referring an issue to SPIRT, on a case-by-case basis I am hopeful the Council can beat this deadline in providing its conscent where needed.
@ Anne i consider your first two proposals friendly and have gone ahead to update the motion before the Council in line with your suggestions - That the time for a consent be extended to 7 days and that Council leadership make the call for an objection.
*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 your third request, the SPIRT charter explicitly recommends they come back to council on an issue that revolves around developing new policy (Type 3 Process)- Note that the SPIRT is a team of experts that are deemed to have the required competence to work along ICANN Org. In resolving any Type 2 issue that may arise. Mandating that they revert back to council at every point a decision needs to be made nullifies the intent behind how they are currently chatered, saddles the council with the same task they are to resolve and i believe isn’t the spirt behind the Predictability framework. I would urge that the council aligns with the PF and SPIRT Charther.
Hopefully, this gets us all moving towards a consensus on the issue.
Lawrence.
-----
[image: Image]
[image: Image]
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
[image: Image]
[image: Image]
*…collaboration to enhance communication*.
[image: Image]
[image: Image] <https://www.facebook.com/microbosstech/>
[image: Image] <https://www.linkedin.com/company/microbosstech/>
[image: Image] <https://mobile.twitter.com/microbosstech>
[image: Image] <https://www.instagram.com/microbosstech/?hl=en>
[image: Image] <https://www.youtube.com/@microboss>
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:* Susan Payne via council <council@icann.org> *Sent:* Monday, May 11, 2026 5:44:15 PM *To:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
Thanks to Lawrence for bringing this to Council in his capacity as the liaison to the SPIRT, and to Anne and Farzi for their comments.
I wanted to just make a couple of comments, for the benefit of Councillors, particularly those who perhaps are not so familiar with the detail as yet.
As a reminder, the SPIRT operates under the oversight of Council. Where an issue comes to the attention of the SPIRT which may require a change to the New gTLD Program, the SPIRT cannot consider that issue of its own volition, since the SPIRT cannot refer an issue to itself. Council may refer the issue to the SPIRT, however, and ask the SPIRT to look at it. What we are doing here is trying to set out a process for how that happens, including some timing expectations since such issues may be quite time-sensitive.
Under the SPIRT Charter, the first task of the SPIRT is to determine whether the issue can be resolved in a manner that is consistent with existing policy recommendations. If SPIRT concludes that it cannot (in other words, that a policy change would be needed), then the SPIRT is already required under its Charter to confer with the Council on a path forward. But, with an issue that the SPIRT is aware of (but which has not been referred to it) it cannot even make that assessment because it is not empowered to act. By this process, Council will only be giving the SPIRT permission to evaluate the issue, we are not signing off on a proposed solution.
Nothing in this process supersedes the SPIRT Charter. It is merely a pathway that allows the SPIRT to put something on Council’s radar and get permission from Council to look at it.
I hope that we can work collaboratively to agree a timeline that allows Councillors time to confer with their groups, and allows the SPIRT to be put to work, where appropriate, as quickly as possible in time-sensitive situations. Input from others on what that timing might be – whether 72 hours, 7 days, or other – would be welcome.
Susan Payne Head of Legal Policy Com Laude *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
*Follow us on **LinkedIn* <https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0>* and* *Youtube* <https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0>
*From:* Anne ICANN via council <council@icann.org> *Sent:* 11 May 2026 15:51 *To:* Terri Agnew <terri.agnew@icann.org> *Cc:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
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.
-----
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
*…collaboration to enhance communication*.
https://www.microboss.org [microboss.org] <https://urldefense.com/v3/__https:/www.microboss.org/__;!!PtGJab4!4Po1IC4Uci...> |
[facebook.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[linkedin.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[mobile.twitter.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[instagram.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[youtube.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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, <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
_______________________________________________ <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> council mailing list -- <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> *council@icann.org* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> To unsubscribe send an email to <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> *council-leave@icann.org* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
_______________________________________________ <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> 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://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> *https://www.icann.org/privacy/policy* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>) and the website Terms of Service ( <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> *https://www.icann.org/privacy/tos* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>). 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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
------------------------------ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland <https://www.google.com/maps/search/15+William+Street,+South+West+Lane,+Edinb...>; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2 <https://www.google.com/maps/search/Calle+Barcas+2?entry=gmail&source=g>, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com/> _______________________________________________ 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.
Dear Anne, In fairness to the SPIRT, they haven't discussed the issue around RSP yet, as they are waiting for council to refer this task to them. The ASP on the other hand was handled by ICANN Org and they reverted to the SPIRT for concurrence. 1, SPIRT is awaiting the Council's formalized process to be adopted and communicated to them via the liaison and 2, SPIRT is requesting that the RSP issue be referred to them for their recommendation, I would await Council's decision and communicate same to the SPIRT in due course. Lawrence. Get Outlook for iOS<https://aka.ms/o0ukef> ________________________________ From: Anne ICANN <anneicanngnso@gmail.com> Sent: Tuesday, May 12, 2026 10:01:47 PM To: Lawrence O. Olawale-Roberts <lawrence@microboss.org> Cc: farzaneh badii <farzaneh.badii@gmail.com>; GNSO council <council@icann.org> Subject: Re: [council] Re: GNSO Council Motion for SPIRT Alerts Lawrence, The Charter empowers the SPIRT to deal with issues other than Policy issues directly without bringing them back to Council WHEN THE ISSUE IS RAISED BY ICANN, the BOARD, or COUNCIL. Its reason for existence is defined accordlngly in the Charter but in this case, apparently no one was comfortable saying the issue could be resolved without Council involvement. You saw the SPIRT resolve an issue re ASP Qualification via the SPIRT change log. Obviously there is a reason for the SPIRT to exist but its' existence is defined by its Charter and the Alert process is not part of that Charter. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Tue, May 12, 2026 at 1:54 PM Lawrence O. Olawale-Roberts <lawrence@microboss.org<mailto:lawrence@microboss.org>> wrote: Dear Farzi, the SPIRT as a body of experts have been chartered through a process approved by the GNSO Council to deliver on its mandate as spelt out in its charter. The council has a role as an arbiter between the SPIRT and ICANN Org whenever there is a diffrence in opinions between both parties - as such inserting the Council as the validator of any decision made by SPIRT makes us an interested party and may cause for the process flow of the Council task to be moved to the Board. A coordination group or small team seating with SPIRIT cannot substitute for receiving approval from the GNSO Council neither can the body refer a Type-3 issue to the Council - hence cannot serve this process. Dear Anne, Once the Council refers an issue to the SPIRT as per the charter, the SPIRT would have to first determine and confirm that it is a Type 2 issue and after collaboration with the GNSO Council, if appropriate, inform ICANN org of a needed change to the program. ICANN org will then determine if a change to the ongoing round is needed and if contrary to the SPIRT’s position ICANN Org determines that No change is needed the SPIRT comes back to confer with the GNSO Council and on determining that a change is needed, the Council engages with the Board, allowing the ICANN Board to ultimately decide if a change is needed, and were they do direct ICANN Org to apply the Predictability framework. I am not aware that ICANN Org. asked that the issue identified around RSP applications be brought as a council belief, rather ICANN staff were approached to see if there was merit refering it to the SPIRT and were advised to use the SPIRT membership route to introduce it as a topic to nurge Council to have referred to SPIRT. Leadership went ahead to review and ask members if they objected to having the issue passed on to Council for referral to SPIRT. Whilst the SPIRT is expected to collaborate with Council, I am not sure they are designed to come back to council for a Solution, otherwise why have them assembled? LOR. ----- [Image] [Image] Lawrence Olawale-Roberts Global President & Managing Director Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org<mailto:Lawrence@microboss.org> [Image] [Image] …collaboration to enhance communication. [Image] https://www.microboss.org<https://www.microboss.org/> | [Image]<https://www.facebook.com/microbosstech/> [Image]<https://www.linkedin.com/company/microbosstech/> [Image]<https://mobile.twitter.com/microbosstech> [Image]<https://www.instagram.com/microbosstech/?hl=en> [Image]<https://www.youtube.com/@microboss> 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: Lawrence O. Olawale-Roberts via council <council@icann.org<mailto:council@icann.org>> Sent: Tuesday, May 12, 2026 7:01 PM To: farzaneh badii <farzaneh.badii@gmail.com<mailto:farzaneh.badii@gmail.com>>; Anne ICANN <anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com>> Cc: GNSO council <council@icann.org<mailto:council@icann.org>> Subject: [council] Re: GNSO Council Motion for SPIRT Alerts Frankly Farzaneh, this is not how the SPIRT is chartered to work. Your proposal would require re-drafting the SPIRT charter and basically resetting the group without even allowing them or ICANN test the current process. The SPIRT other path through which the can mitigate issues referred to them through ICANN Org. Does not require SPIRT coming back to Council for concurrence or consultations as long as the issue is not determined to be Type 3 - hence over engineering this process of just getting to secure council's approval to look into a matter might subsequently push dependence on staff to initiate issues for the SPIRT to act on. LOR ----- [Image] [Image] Lawrence Olawale-Roberts Global President & Managing Director Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org<mailto:Lawrence@microboss.org> [Image] [Image] …collaboration to enhance communication. [Image] https://www.microboss.org<https://www.microboss.org/> | [Image]<https://www.facebook.com/microbosstech/> [Image]<https://www.linkedin.com/company/microbosstech/> [Image]<https://mobile.twitter.com/microbosstech> [Image]<https://www.instagram.com/microbosstech/?hl=en> [Image]<https://www.youtube.com/@microboss> 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: farzaneh badii via council <council@icann.org<mailto:council@icann.org>> Sent: Tuesday, May 12, 2026 6:41:01 PM To: Anne ICANN <anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com>> Cc: Lawrence O. Olawale-Roberts <lawrence@microboss.org<mailto:lawrence@microboss.org>>; GNSO council <council@icann.org<mailto:council@icann.org>> Subject: [council] Re: GNSO Council Motion for SPIRT Alerts Hi Anne I said a coordination group. And they only coordinate, they provide briefing, they provide background. If all council members want to focus on it, they can. And I didn’t say don’t bring back to the council. From the beginning I have been insiting council involvement through all the process. I think this is better than having a liaison have to do it and be the messenger, this workload is going to get heavy. Another way is, a stakeholder group provide an issue to their council member, we discuss with the whole council and having SPIRT come to the council and discuss further and come up with a solution. Farzaneh On Tue, May 12, 2026 at 1:06 PM Anne ICANN <anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com>> wrote: Hi Farzaneh. I'm a bit surprised that you suggest a "small team" of Councilors that want to work with SPIRT to develop the analysis and work on solutions? If the issue is assigned to the SPIRT due to their expertise, I would favor having them bring a proposal back to the full Council. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Tue, May 12, 2026 at 9:04 AM farzaneh badii <farzaneh.badii@gmail.com<mailto:farzaneh.badii@gmail.com>> wrote: Well if we have a group of council members that are more active and monitor SPIRT issues and in touch with their stakeholders and they can bring the issue to the council and then the Council in collaboration with SPIRT sorts it out, I think that’s for the better. For now I can’t say yes to this motion there are too many unknowns and not much clarification and the more I look into it the more complicated it looks. And it will get more complicated. One stakeholder nor SPIRT should bring the issue to the council. This should be in a collaborative way. The more collaborative, the more efficient too! But to address the problem Jeff has submitted on behalf of the registry stakeholder group, I think we can just discuss the issue during next week meeting and ask the council members that want to work with SPIRT to come up with a solution to do so and bring back the result to the council. Farzaneh On Tue, May 12, 2026 at 11:18 AM Anne ICANN via council <council@icann.org<mailto:council@icann.org>> wrote: P.S. I should explain again that the Category 2 issue on RSP was actually raised by a SPIRT member on behalf of the RySG. To the extent that we are authorizing the SPIRT to raise an issue itself, It does not seem to me that the logic of just letting the SPIRT proceed to resolve on its own without conferring with Council still applies. (This comment is limited to Category 2 issues raised by the SPIRT itself or one of its members.) Reminder again that the Charter actually prohibits the SPIRT from raising issues. During Charter drafting, it was assumed the SG or C would raise the issue at the Council level if it was not raised by Board, ICANN, or the Council in some other way. So this mechanism for allowing the SPIRT (or in this case an RySG member of the SPIRT) to raise an issue was not contemplated by the Charter. Again, it may be more efficient to allow the SPIRT to do this, if only because it presumably meets more often than Council, but that does not mean that the SPIRT should be authorized to resolve an issue it has raised on its own (either by consensus or by Leadership team of the SPIRT or by an individual member) without coming back to the Council with the proposed solution. The very notion that the SPIRT can raise an issue itself is a new one and we need to be especially careful with a 7 day non-objection/consent process. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Tue, May 12, 2026 at 6:29 AM Anne ICANN <anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com>> wrote: Thanks Lawrence. Re the third issue, the RSP issue is a Categroy 2 issue - non-minor operational with material impact on applicants - but apparently ICANN has asked that this issue be briefed to the Council. Some members of SPIRT thought they could deal with it alone without talking to us. ICANN Org did not agree - presumably because of the nature of the material impact on RSP Qualification. So how is it that Council can agree with you that a Category 2 issue brought to the Council in this manner does not need to come back to Council for the proposed solution? Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Mon, May 11, 2026 at 1:04 PM Lawrence O. Olawale-Roberts via council <council@icann.org<mailto:council@icann.org>> wrote: Dear Susan and Anne, Thank you for your inputs and contribution to the subject matter. @Susan your submission is spot on and am sure it provides some further clarity. where the Council adopts a 7 day timeframe in providing its consent over referring an issue to SPIRT, on a case-by-case basis I am hopeful the Council can beat this deadline in providing its conscent where needed. @ Anne i consider your first two proposals friendly and have gone ahead to update the motion before the Council in line with your suggestions - That the time for a consent be extended to 7 days and that Council leadership make the call for an objection. 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 your third request, the SPIRT charter explicitly recommends they come back to council on an issue that revolves around developing new policy (Type 3 Process)- Note that the SPIRT is a team of experts that are deemed to have the required competence to work along ICANN Org. In resolving any Type 2 issue that may arise. Mandating that they revert back to council at every point a decision needs to be made nullifies the intent behind how they are currently chatered, saddles the council with the same task they are to resolve and i believe isn’t the spirt behind the Predictability framework. I would urge that the council aligns with the PF and SPIRT Charther. Hopefully, this gets us all moving towards a consensus on the issue. Lawrence. ----- [Image] [Image] Lawrence Olawale-Roberts Global President & Managing Director Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org<mailto:Lawrence@microboss.org> [Image] [Image] …collaboration to enhance communication. [Image] https://www.microboss.org<https://www.microboss.org/> | [Image]<https://www.facebook.com/microbosstech/> [Image]<https://www.linkedin.com/company/microbosstech/> [Image]<https://mobile.twitter.com/microbosstech> [Image]<https://www.instagram.com/microbosstech/?hl=en> [Image]<https://www.youtube.com/@microboss> 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: Susan Payne via council <council@icann.org<mailto:council@icann.org>> Sent: Monday, May 11, 2026 5:44:15 PM To: GNSO council <council@icann.org<mailto:council@icann.org>> Subject: [council] Re: GNSO Council Motion for SPIRT Alerts Thanks to Lawrence for bringing this to Council in his capacity as the liaison to the SPIRT, and to Anne and Farzi for their comments. I wanted to just make a couple of comments, for the benefit of Councillors, particularly those who perhaps are not so familiar with the detail as yet. As a reminder, the SPIRT operates under the oversight of Council. Where an issue comes to the attention of the SPIRT which may require a change to the New gTLD Program, the SPIRT cannot consider that issue of its own volition, since the SPIRT cannot refer an issue to itself. Council may refer the issue to the SPIRT, however, and ask the SPIRT to look at it. What we are doing here is trying to set out a process for how that happens, including some timing expectations since such issues may be quite time-sensitive. Under the SPIRT Charter, the first task of the SPIRT is to determine whether the issue can be resolved in a manner that is consistent with existing policy recommendations. If SPIRT concludes that it cannot (in other words, that a policy change would be needed), then the SPIRT is already required under its Charter to confer with the Council on a path forward. But, with an issue that the SPIRT is aware of (but which has not been referred to it) it cannot even make that assessment because it is not empowered to act. By this process, Council will only be giving the SPIRT permission to evaluate the issue, we are not signing off on a proposed solution. Nothing in this process supersedes the SPIRT Charter. It is merely a pathway that allows the SPIRT to put something on Council’s radar and get permission from Council to look at it. I hope that we can work collaboratively to agree a timeline that allows Councillors time to confer with their groups, and allows the SPIRT to be put to work, where appropriate, as quickly as possible in time-sensitive situations. Input from others on what that timing might be – whether 72 hours, 7 days, or other – would be welcome. Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:ii_19e1dfb280c4cff311] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0> From: Anne ICANN via council <council@icann.org<mailto:council@icann.org>> Sent: 11 May 2026 15:51 To: Terri Agnew <terri.agnew@icann.org<mailto:terri.agnew@icann.org>> Cc: GNSO council <council@icann.org<mailto:council@icann.org>> Subject: [council] Re: GNSO Council Motion for SPIRT Alerts 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<mailto:anneicanngnso@gmail.com> On Mon, May 11, 2026 at 6:31 AM Terri Agnew via council <council@icann.org<mailto: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<mailto:council@icann.org>> Reply-To: "lawrence@microboss.org<mailto:lawrence@microboss.org>" <lawrence@microboss.org<mailto:lawrence@microboss.org>> Date: Saturday, May 9, 2026 at 6:26 AM To: GNSO council <council@icann.org<mailto: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. ----- Lawrence Olawale-Roberts Global President & Managing Director Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org<mailto:Lawrence@microboss.org> …collaboration to enhance communication. https://www.microboss.org [microboss.org]<https://urldefense.com/v3/__https:/www.microboss.org/__;!!PtGJab4!4Po1IC4Uci...> | [facebook.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> [linkedin.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> [mobile.twitter.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> [instagram.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> [youtube.com]<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> 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,<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> 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.<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> 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.<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> _______________________________________________<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> council mailing list -- <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> council@icann.org<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> To unsubscribe send an email to <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> council-leave@icann.org<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> _______________________________________________<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> 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://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJab4!4Po1IC4Uciu-bbgeBNYeGncd1lAX_OSBDktLsJw5HBaInI6BmN8LiLweAm9YyH1VO3HmdodfcMntqNzFA5WX34Q$>https://www.icann.org/privacy/policy<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJab4!4Po1IC4Uciu-bbgeBNYeGncd1lAX_OSBDktLsJw5HBaInI6BmN8LiLweAm9YyH1VO3HmdodfcMntqNzFA5WX34Q$>) and the website Terms of Service (<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJab4!4Po1IC4Uciu-bbgeBNYeGncd1lAX_OSBDktLsJw5HBaInI6BmN8LiLweAm9YyH1VO3HmdodfcMntqNzFA5WX34Q$>https://www.icann.org/privacy/tos<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJab4!4Po1IC4Uciu-bbgeBNYeGncd1lAX_OSBDktLsJw5HBaInI6BmN8LiLweAm9YyH1VO3HmdodfcMntqNzFA5WX34Q$>). 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.<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England<https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England<https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England<https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland<https://www.google.com/maps/search/15+William+Street,+South+West+Lane,+Edinb...>; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2<https://www.google.com/maps/search/Calle+Barcas+2?entry=gmail&source=g>, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/> _______________________________________________ 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.
Lawrence, As you already know, I completely agree the ASP Qualification issue was properly handled in accordance with the SPIRT Charter. (This Category 2 issue was raised by ICANN directly to the SPIRT for guidance and resolution.) The result reflected in the Change Log on this Category 2 issue is just fine in my opinion. (It would be good to confirm that the SPIRT developed consensus on this point before it appeared in the Change Log.) Thank you very much for accepting two out of three bullet points in the SPIRT Alert process as friendly. I do hope we may also hear from the RySG and from ICANN Org regarding the RSP Qualification issue, which, as noted, is more complex both in its substance and in its procedural stance than the ASP Qualification issue. And thanks for all your hard work with the SPIRT as the Council Liaison. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com On Tue, May 12, 2026 at 3:23 PM Lawrence O. Olawale-Roberts < lawrence@microboss.org> wrote:
Dear Anne,
In fairness to the SPIRT, they haven't discussed the issue around RSP yet, as they are waiting for council to refer this task to them.
The ASP on the other hand was handled by ICANN Org and they reverted to the SPIRT for concurrence.
1, SPIRT is awaiting the Council's formalized process to be adopted and communicated to them via the liaison and 2, SPIRT is requesting that the RSP issue be referred to them for their recommendation,
I would await Council's decision and communicate same to the SPIRT in due course.
Lawrence.
Get Outlook for iOS <https://aka.ms/o0ukef> ------------------------------ *From:* Anne ICANN <anneicanngnso@gmail.com> *Sent:* Tuesday, May 12, 2026 10:01:47 PM *To:* Lawrence O. Olawale-Roberts <lawrence@microboss.org> *Cc:* farzaneh badii <farzaneh.badii@gmail.com>; GNSO council < council@icann.org> *Subject:* Re: [council] Re: GNSO Council Motion for SPIRT Alerts
Lawrence, The Charter empowers the SPIRT to deal with issues other than Policy issues directly without bringing them back to Council WHEN THE ISSUE IS RAISED BY ICANN, the BOARD, or COUNCIL. Its reason for existence is defined accordlngly in the Charter but in this case, apparently no one was comfortable saying the issue could be resolved without Council involvement.
You saw the SPIRT resolve an issue re ASP Qualification via the SPIRT change log. Obviously there is a reason for the SPIRT to exist but its' existence is defined by its Charter and the Alert process is not part of that Charter. Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com
On Tue, May 12, 2026 at 1:54 PM Lawrence O. Olawale-Roberts < lawrence@microboss.org> wrote:
Dear Farzi, the SPIRT as a body of experts have been chartered through a process approved by the GNSO Council to deliver on its mandate as spelt out in its charter. The council has a role as an arbiter between the SPIRT and ICANN Org whenever there is a diffrence in opinions between both parties - as such inserting the Council as the validator of any decision made by SPIRT makes us an interested party and may cause for the process flow of the Council task to be moved to the Board.
A coordination group or small team seating with SPIRIT cannot substitute for receiving approval from the GNSO Council neither can the body refer a Type-3 issue to the Council - hence cannot serve this process.
Dear Anne, Once the Council refers an issue to the SPIRT as per the charter, the SPIRT would have to first determine and confirm that it is a Type 2 issue and after collaboration with the GNSO Council, if appropriate, inform ICANN org of a needed change to the program. ICANN org will then determine if a change to the ongoing round is needed and if contrary to the SPIRT’s position ICANN Org determines that No change is needed the SPIRT comes back to confer with the GNSO Council and on determining that a change is needed, the Council engages with the Board, allowing the ICANN Board to ultimately decide if a change is needed, and were they do direct ICANN Org to apply the Predictability framework.
I am not aware that ICANN Org. asked that the issue identified around RSP applications be brought as a council belief, rather ICANN staff were approached to see if there was merit refering it to the SPIRT and were advised to use the SPIRT membership route to introduce it as a topic to nurge Council to have referred to SPIRT. Leadership went ahead to review and ask members if they objected to having the issue passed on to Council for referral to SPIRT. Whilst the SPIRT is expected to collaborate with Council, I am not sure they are designed to come back to council for a Solution, otherwise why have them assembled?
LOR.
-----
[image: Image]
[image: Image]
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
[image: Image]
[image: Image]
*…collaboration to enhance communication*.
[image: Image]
[image: Image] <https://www.facebook.com/microbosstech/>
[image: Image] <https://www.linkedin.com/company/microbosstech/>
[image: Image] <https://mobile.twitter.com/microbosstech>
[image: Image] <https://www.instagram.com/microbosstech/?hl=en>
[image: Image] <https://www.youtube.com/@microboss>
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:* Lawrence O. Olawale-Roberts via council <council@icann.org> *Sent:* Tuesday, May 12, 2026 7:01 PM *To:* farzaneh badii <farzaneh.badii@gmail.com>; Anne ICANN < anneicanngnso@gmail.com> *Cc:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
Frankly Farzaneh, this is not how the SPIRT is chartered to work. Your proposal would require re-drafting the SPIRT charter and basically resetting the group without even allowing them or ICANN test the current process.
The SPIRT other path through which the can mitigate issues referred to them through ICANN Org. Does not require SPIRT coming back to Council for concurrence or consultations as long as the issue is not determined to be Type 3 - hence over engineering this process of just getting to secure council's approval to look into a matter might subsequently push dependence on staff to initiate issues for the SPIRT to act on.
LOR
-----
[image: Image]
[image: Image]
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
[image: Image]
[image: Image]
*…collaboration to enhance communication*.
[image: Image]
[image: Image] <https://www.facebook.com/microbosstech/>
[image: Image] <https://www.linkedin.com/company/microbosstech/>
[image: Image] <https://mobile.twitter.com/microbosstech>
[image: Image] <https://www.instagram.com/microbosstech/?hl=en>
[image: Image] <https://www.youtube.com/@microboss>
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:* farzaneh badii via council <council@icann.org> *Sent:* Tuesday, May 12, 2026 6:41:01 PM *To:* Anne ICANN <anneicanngnso@gmail.com> *Cc:* Lawrence O. Olawale-Roberts <lawrence@microboss.org>; GNSO council < council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
Hi Anne
I said a coordination group. And they only coordinate, they provide briefing, they provide background. If all council members want to focus on it, they can. And I didn’t say don’t bring back to the council. From the beginning I have been insiting council involvement through all the process. I think this is better than having a liaison have to do it and be the messenger, this workload is going to get heavy.
Another way is, a stakeholder group provide an issue to their council member, we discuss with the whole council and having SPIRT come to the council and discuss further and come up with a solution.
Farzaneh
On Tue, May 12, 2026 at 1:06 PM Anne ICANN <anneicanngnso@gmail.com> wrote:
Hi Farzaneh. I'm a bit surprised that you suggest a "small team" of Councilors that want to work with SPIRT to develop the analysis and work on solutions? If the issue is assigned to the SPIRT due to their expertise, I would favor having them bring a proposal back to the full Council. Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com
On Tue, May 12, 2026 at 9:04 AM farzaneh badii <farzaneh.badii@gmail.com> wrote:
Well if we have a group of council members that are more active and monitor SPIRT issues and in touch with their stakeholders and they can bring the issue to the council and then the Council in collaboration with SPIRT sorts it out, I think that’s for the better. For now I can’t say yes to this motion there are too many unknowns and not much clarification and the more I look into it the more complicated it looks. And it will get more complicated. One stakeholder nor SPIRT should bring the issue to the council. This should be in a collaborative way. The more collaborative, the more efficient too!
But to address the problem Jeff has submitted on behalf of the registry stakeholder group, I think we can just discuss the issue during next week meeting and ask the council members that want to work with SPIRT to come up with a solution to do so and bring back the result to the council.
Farzaneh
On Tue, May 12, 2026 at 11:18 AM Anne ICANN via council <council@icann.org> wrote:
P.S. I should explain again that the Category 2 issue on RSP was actually raised by a SPIRT member on behalf of the RySG. To the extent that we are authorizing the SPIRT to raise an issue itself, It does not seem to me that the logic of just letting the SPIRT proceed to resolve on its own without conferring with Council still applies. (This comment is limited to Category 2 issues raised by the SPIRT itself or one of its members.)
Reminder again that the Charter actually prohibits the SPIRT from raising issues. During Charter drafting, it was assumed the SG or C would raise the issue at the Council level if it was not raised by Board, ICANN, or the Council in some other way. So this mechanism for allowing the SPIRT (or in this case an RySG member of the SPIRT) to raise an issue was not contemplated by the Charter. Again, it may be more efficient to allow the SPIRT to do this, if only because it presumably meets more often than Council, but that does not mean that the SPIRT should be authorized to resolve an issue it has raised on its own (either by consensus or by Leadership team of the SPIRT or by an individual member) without coming back to the Council with the proposed solution. The very notion that the SPIRT can raise an issue itself is a new one and we need to be especially careful with a 7 day non-objection/consent process. Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com
On Tue, May 12, 2026 at 6:29 AM Anne ICANN <anneicanngnso@gmail.com> wrote:
Thanks Lawrence. Re the third issue, the RSP issue is a Categroy 2 issue - non-minor operational with material impact on applicants - but apparently ICANN has asked that this issue be briefed to the Council. Some members of SPIRT thought they could deal with it alone without talking to us. ICANN Org did not agree - presumably because of the nature of the material impact on RSP Qualification. So how is it that Council can agree with you that a Category 2 issue brought to the Council in this manner does not need to come back to Council for the proposed solution?
Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com
On Mon, May 11, 2026 at 1:04 PM Lawrence O. Olawale-Roberts via council < council@icann.org> wrote:
Dear Susan and Anne,
Thank you for your inputs and contribution to the subject matter.
@Susan your submission is spot on and am sure it provides some further clarity. where the Council adopts a 7 day timeframe in providing its consent over referring an issue to SPIRT, on a case-by-case basis I am hopeful the Council can beat this deadline in providing its conscent where needed.
@ Anne i consider your first two proposals friendly and have gone ahead to update the motion before the Council in line with your suggestions - That the time for a consent be extended to 7 days and that Council leadership make the call for an objection.
*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 your third request, the SPIRT charter explicitly recommends they come back to council on an issue that revolves around developing new policy (Type 3 Process)- Note that the SPIRT is a team of experts that are deemed to have the required competence to work along ICANN Org. In resolving any Type 2 issue that may arise. Mandating that they revert back to council at every point a decision needs to be made nullifies the intent behind how they are currently chatered, saddles the council with the same task they are to resolve and i believe isn’t the spirt behind the Predictability framework. I would urge that the council aligns with the PF and SPIRT Charther.
Hopefully, this gets us all moving towards a consensus on the issue.
Lawrence.
-----
[image: Image]
[image: Image]
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
[image: Image]
[image: Image]
*…collaboration to enhance communication*.
[image: Image]
[image: Image] <https://www.facebook.com/microbosstech/>
[image: Image] <https://www.linkedin.com/company/microbosstech/>
[image: Image] <https://mobile.twitter.com/microbosstech>
[image: Image] <https://www.instagram.com/microbosstech/?hl=en>
[image: Image] <https://www.youtube.com/@microboss>
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:* Susan Payne via council <council@icann.org> *Sent:* Monday, May 11, 2026 5:44:15 PM *To:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
Thanks to Lawrence for bringing this to Council in his capacity as the liaison to the SPIRT, and to Anne and Farzi for their comments.
I wanted to just make a couple of comments, for the benefit of Councillors, particularly those who perhaps are not so familiar with the detail as yet.
As a reminder, the SPIRT operates under the oversight of Council. Where an issue comes to the attention of the SPIRT which may require a change to the New gTLD Program, the SPIRT cannot consider that issue of its own volition, since the SPIRT cannot refer an issue to itself. Council may refer the issue to the SPIRT, however, and ask the SPIRT to look at it. What we are doing here is trying to set out a process for how that happens, including some timing expectations since such issues may be quite time-sensitive.
Under the SPIRT Charter, the first task of the SPIRT is to determine whether the issue can be resolved in a manner that is consistent with existing policy recommendations. If SPIRT concludes that it cannot (in other words, that a policy change would be needed), then the SPIRT is already required under its Charter to confer with the Council on a path forward. But, with an issue that the SPIRT is aware of (but which has not been referred to it) it cannot even make that assessment because it is not empowered to act. By this process, Council will only be giving the SPIRT permission to evaluate the issue, we are not signing off on a proposed solution.
Nothing in this process supersedes the SPIRT Charter. It is merely a pathway that allows the SPIRT to put something on Council’s radar and get permission from Council to look at it.
I hope that we can work collaboratively to agree a timeline that allows Councillors time to confer with their groups, and allows the SPIRT to be put to work, where appropriate, as quickly as possible in time-sensitive situations. Input from others on what that timing might be – whether 72 hours, 7 days, or other – would be welcome.
Susan Payne Head of Legal Policy Com Laude *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
*Follow us on **LinkedIn* <https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0>* and* *Youtube* <https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0>
*From:* Anne ICANN via council <council@icann.org> *Sent:* 11 May 2026 15:51 *To:* Terri Agnew <terri.agnew@icann.org> *Cc:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
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.
-----
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
*…collaboration to enhance communication*.
https://www.microboss.org [microboss.org] <https://urldefense.com/v3/__https:/www.microboss.org/__;!!PtGJab4!4Po1IC4Uci...> |
[facebook.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[linkedin.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[mobile.twitter.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[instagram.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[youtube.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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, <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
_______________________________________________ <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> council mailing list -- <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> *council@icann.org* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> To unsubscribe send an email to <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> *council-leave@icann.org* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
_______________________________________________ <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> 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://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> *https://www.icann.org/privacy/policy* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>) and the website Terms of Service ( <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> *https://www.icann.org/privacy/tos* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>). 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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
------------------------------ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland <https://www.google.com/maps/search/15+William+Street,+South+West+Lane,+Edinb...>; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2 <https://www.google.com/maps/search/Calle+Barcas+2?entry=gmail&source=g>, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com/> _______________________________________________ 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.
Farzaneh On Tue, May 12, 2026 at 4:54 PM Lawrence O. Olawale-Roberts < lawrence@microboss.org> wrote:
Dear Farzi, the SPIRT as a body of experts have been chartered through a process approved by the GNSO Council to deliver on its mandate as spelt out in its charter. The council has a role as an arbiter between the SPIRT and ICANN Org whenever there is a diffrence in opinions between both parties - as such inserting the Council as the validator of any decision made by SPIRT makes us an interested party and may cause for the process flow of the Council task to be moved to the Board.
A coordination group or small team seating with SPIRIT cannot substitute for receiving approval from the GNSO Council neither can the body refer a Type-3 issue to the Council - hence cannot serve this process.
I have suggested exactly the contrary to this and correcting the record again. The coordination group is not a small team and it doesn’t make decisions. It’s a “coordination group” and it helps the liaison to provide documentation and background to the issue for the council to consider. On this issue for example we had to go through the Zoom meeting to understand what the issue is and prepare. It’s a task that I think will go beyond the ability of one liaison to do. I think we can expedite decision-making by informing the council proactively instead of giving them a tight deadline.
Dear Anne, Once the Council refers an issue to the SPIRT as per the charter, the SPIRT would have to first determine and confirm that it is a Type 2 issue and after collaboration with the GNSO Council, if appropriate, inform ICANN org of a needed change to the program. ICANN org will then determine if a change to the ongoing round is needed and if contrary to the SPIRT’s position ICANN Org determines that No change is needed the SPIRT comes back to confer with the GNSO Council and on determining that a change is needed, the Council engages with the Board, allowing the ICANN Board to ultimately decide if a change is needed, and were they do direct ICANN Org to apply the Predictability framework.
I am not aware that ICANN Org. asked that the issue identified around RSP applications be brought as a council belief, rather ICANN staff were approached to see if there was merit refering it to the SPIRT and were advised to use the SPIRT membership route to introduce it as a topic to nurge Council to have referred to SPIRT. Leadership went ahead to review and ask members if they objected to having the issue passed on to Council for referral to SPIRT. Whilst the SPIRT is expected to collaborate with Council, I am not sure they are designed to come back to council for a Solution, otherwise why have them assembled?
LOR.
-----
[image: Image]
[image: Image]
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
[image: Image]
[image: Image]
*…collaboration to enhance communication*.
[image: Image]
[image: Image] <https://www.facebook.com/microbosstech/>
[image: Image] <https://www.linkedin.com/company/microbosstech/>
[image: Image] <https://mobile.twitter.com/microbosstech>
[image: Image] <https://www.instagram.com/microbosstech/?hl=en>
[image: Image] <https://www.youtube.com/@microboss>
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:* Lawrence O. Olawale-Roberts via council <council@icann.org> *Sent:* Tuesday, May 12, 2026 7:01 PM *To:* farzaneh badii <farzaneh.badii@gmail.com>; Anne ICANN < anneicanngnso@gmail.com>
*Cc:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
Frankly Farzaneh, this is not how the SPIRT is chartered to work. Your proposal would require re-drafting the SPIRT charter and basically resetting the group without even allowing them or ICANN test the current process.
The SPIRT other path through which the can mitigate issues referred to them through ICANN Org. Does not require SPIRT coming back to Council for concurrence or consultations as long as the issue is not determined to be Type 3 - hence over engineering this process of just getting to secure council's approval to look into a matter might subsequently push dependence on staff to initiate issues for the SPIRT to act on.
LOR
-----
[image: Image]
[image: Image]
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
[image: Image]
[image: Image]
*…collaboration to enhance communication*.
[image: Image]
[image: Image] <https://www.facebook.com/microbosstech/>
[image: Image] <https://www.linkedin.com/company/microbosstech/>
[image: Image] <https://mobile.twitter.com/microbosstech>
[image: Image] <https://www.instagram.com/microbosstech/?hl=en>
[image: Image] <https://www.youtube.com/@microboss>
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:* farzaneh badii via council <council@icann.org> *Sent:* Tuesday, May 12, 2026 6:41:01 PM *To:* Anne ICANN <anneicanngnso@gmail.com> *Cc:* Lawrence O. Olawale-Roberts <lawrence@microboss.org>; GNSO council < council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
Hi Anne
I said a coordination group. And they only coordinate, they provide briefing, they provide background. If all council members want to focus on it, they can. And I didn’t say don’t bring back to the council. From the beginning I have been insiting council involvement through all the process. I think this is better than having a liaison have to do it and be the messenger, this workload is going to get heavy.
Another way is, a stakeholder group provide an issue to their council member, we discuss with the whole council and having SPIRT come to the council and discuss further and come up with a solution.
Farzaneh
On Tue, May 12, 2026 at 1:06 PM Anne ICANN <anneicanngnso@gmail.com> wrote:
Hi Farzaneh. I'm a bit surprised that you suggest a "small team" of Councilors that want to work with SPIRT to develop the analysis and work on solutions? If the issue is assigned to the SPIRT due to their expertise, I would favor having them bring a proposal back to the full Council. Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com
On Tue, May 12, 2026 at 9:04 AM farzaneh badii <farzaneh.badii@gmail.com> wrote:
Well if we have a group of council members that are more active and monitor SPIRT issues and in touch with their stakeholders and they can bring the issue to the council and then the Council in collaboration with SPIRT sorts it out, I think that’s for the better. For now I can’t say yes to this motion there are too many unknowns and not much clarification and the more I look into it the more complicated it looks. And it will get more complicated. One stakeholder nor SPIRT should bring the issue to the council. This should be in a collaborative way. The more collaborative, the more efficient too!
But to address the problem Jeff has submitted on behalf of the registry stakeholder group, I think we can just discuss the issue during next week meeting and ask the council members that want to work with SPIRT to come up with a solution to do so and bring back the result to the council.
Farzaneh
On Tue, May 12, 2026 at 11:18 AM Anne ICANN via council <council@icann.org> wrote:
P.S. I should explain again that the Category 2 issue on RSP was actually raised by a SPIRT member on behalf of the RySG. To the extent that we are authorizing the SPIRT to raise an issue itself, It does not seem to me that the logic of just letting the SPIRT proceed to resolve on its own without conferring with Council still applies. (This comment is limited to Category 2 issues raised by the SPIRT itself or one of its members.)
Reminder again that the Charter actually prohibits the SPIRT from raising issues. During Charter drafting, it was assumed the SG or C would raise the issue at the Council level if it was not raised by Board, ICANN, or the Council in some other way. So this mechanism for allowing the SPIRT (or in this case an RySG member of the SPIRT) to raise an issue was not contemplated by the Charter. Again, it may be more efficient to allow the SPIRT to do this, if only because it presumably meets more often than Council, but that does not mean that the SPIRT should be authorized to resolve an issue it has raised on its own (either by consensus or by Leadership team of the SPIRT or by an individual member) without coming back to the Council with the proposed solution. The very notion that the SPIRT can raise an issue itself is a new one and we need to be especially careful with a 7 day non-objection/consent process. Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com
On Tue, May 12, 2026 at 6:29 AM Anne ICANN <anneicanngnso@gmail.com> wrote:
Thanks Lawrence. Re the third issue, the RSP issue is a Categroy 2 issue - non-minor operational with material impact on applicants - but apparently ICANN has asked that this issue be briefed to the Council. Some members of SPIRT thought they could deal with it alone without talking to us. ICANN Org did not agree - presumably because of the nature of the material impact on RSP Qualification. So how is it that Council can agree with you that a Category 2 issue brought to the Council in this manner does not need to come back to Council for the proposed solution?
Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com
On Mon, May 11, 2026 at 1:04 PM Lawrence O. Olawale-Roberts via council < council@icann.org> wrote:
Dear Susan and Anne,
Thank you for your inputs and contribution to the subject matter.
@Susan your submission is spot on and am sure it provides some further clarity. where the Council adopts a 7 day timeframe in providing its consent over referring an issue to SPIRT, on a case-by-case basis I am hopeful the Council can beat this deadline in providing its conscent where needed.
@ Anne i consider your first two proposals friendly and have gone ahead to update the motion before the Council in line with your suggestions - That the time for a consent be extended to 7 days and that Council leadership make the call for an objection.
*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 your third request, the SPIRT charter explicitly recommends they come back to council on an issue that revolves around developing new policy (Type 3 Process)- Note that the SPIRT is a team of experts that are deemed to have the required competence to work along ICANN Org. In resolving any Type 2 issue that may arise. Mandating that they revert back to council at every point a decision needs to be made nullifies the intent behind how they are currently chatered, saddles the council with the same task they are to resolve and i believe isn’t the spirt behind the Predictability framework. I would urge that the council aligns with the PF and SPIRT Charther.
Hopefully, this gets us all moving towards a consensus on the issue.
Lawrence.
-----
[image: Image]
[image: Image]
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
[image: Image]
[image: Image]
*…collaboration to enhance communication*.
[image: Image]
[image: Image] <https://www.facebook.com/microbosstech/>
[image: Image] <https://www.linkedin.com/company/microbosstech/>
[image: Image] <https://mobile.twitter.com/microbosstech>
[image: Image] <https://www.instagram.com/microbosstech/?hl=en>
[image: Image] <https://www.youtube.com/@microboss>
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:* Susan Payne via council <council@icann.org> *Sent:* Monday, May 11, 2026 5:44:15 PM *To:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
Thanks to Lawrence for bringing this to Council in his capacity as the liaison to the SPIRT, and to Anne and Farzi for their comments.
I wanted to just make a couple of comments, for the benefit of Councillors, particularly those who perhaps are not so familiar with the detail as yet.
As a reminder, the SPIRT operates under the oversight of Council. Where an issue comes to the attention of the SPIRT which may require a change to the New gTLD Program, the SPIRT cannot consider that issue of its own volition, since the SPIRT cannot refer an issue to itself. Council may refer the issue to the SPIRT, however, and ask the SPIRT to look at it. What we are doing here is trying to set out a process for how that happens, including some timing expectations since such issues may be quite time-sensitive.
Under the SPIRT Charter, the first task of the SPIRT is to determine whether the issue can be resolved in a manner that is consistent with existing policy recommendations. If SPIRT concludes that it cannot (in other words, that a policy change would be needed), then the SPIRT is already required under its Charter to confer with the Council on a path forward. But, with an issue that the SPIRT is aware of (but which has not been referred to it) it cannot even make that assessment because it is not empowered to act. By this process, Council will only be giving the SPIRT permission to evaluate the issue, we are not signing off on a proposed solution.
Nothing in this process supersedes the SPIRT Charter. It is merely a pathway that allows the SPIRT to put something on Council’s radar and get permission from Council to look at it.
I hope that we can work collaboratively to agree a timeline that allows Councillors time to confer with their groups, and allows the SPIRT to be put to work, where appropriate, as quickly as possible in time-sensitive situations. Input from others on what that timing might be – whether 72 hours, 7 days, or other – would be welcome.
Susan Payne Head of Legal Policy Com Laude *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
*Follow us on **LinkedIn* <https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0>* and* *Youtube* <https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0>
*From:* Anne ICANN via council <council@icann.org> *Sent:* 11 May 2026 15:51 *To:* Terri Agnew <terri.agnew@icann.org> *Cc:* GNSO council <council@icann.org> *Subject:* [council] Re: GNSO Council Motion for SPIRT Alerts
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.
-----
*Lawrence* *Olawale-Roberts* Global President & Managing Director
Mobile: +234 8070892705, (0)8056 3333 97 Lawrence@microboss.org
*…collaboration to enhance communication*.
https://www.microboss.org [microboss.org] <https://urldefense.com/v3/__https:/www.microboss.org/__;!!PtGJab4!4Po1IC4Uci...> |
[facebook.com] <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[linkedin.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[mobile.twitter.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[instagram.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
*[youtube.com]* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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, <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
<https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
_______________________________________________ <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> council mailing list -- <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> *council@icann.org* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> To unsubscribe send an email to <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> *council-leave@icann.org* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
_______________________________________________ <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> 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://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> *https://www.icann.org/privacy/policy* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>) and the website Terms of Service ( <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...> *https://www.icann.org/privacy/tos* <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>). 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. <https://urldefense.com/v3/__https:/www.facebook.com/microbosstech/__;!!PtGJa...>
------------------------------ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland <https://www.google.com/maps/search/15+William+Street,+South+West+Lane,+Edinb...>; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2 <https://www.google.com/maps/search/Calle+Barcas+2?entry=gmail&source=g>, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com/> _______________________________________________ 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.
participants (6)
-
Anne ICANN -
farzaneh badii -
Gaurav Vedi -
Lawrence O. Olawale-Roberts -
Susan Payne -
Terri Agnew