Key Outcomes and Action Items from SPIRT Session during ICANN86
Dear SPIRT, Please see the following key outcome and action items from today’s SPIRT Meeting during ICANN86<https://icann86.sched.com/event/2NQRY/gnso-next-round-spirt>. [KEY OUTCOME] * SPIRT Members to review the Registry Service Provider (RSP) issue that has been referred by the GNSO Council and respond within 5 calendar days if any objections. * [ACTION ITEMS] 1. Ongoing: All SPIRT Members to update their SOIs in accordance with the SOP. 2. SPIRT Members to review the RSP issue and voice objections or concerns via the SPIRT mailing list by Tuesday, 16 June 2026, at 23:59 UTC (5 calendar days) if they determine that a change to the ongoing round is not required. 3. GNSO Support Staff to reorganize the next set of SPIRT Meetings for June-July and send calendar invites, as necessary. Safe travels back home! Kind regards, Saewon Get Outlook for Mac<https://aka.ms/GetOutlookForMac>
Hi Anil, It is correct that the next meeting is scheduled for 18 June. However as noted in action item 3, any updates concerning meeting cancellations or invitations for June/July will be shared by mid-next week once arrangements have been finalized. Thank you for your patience. Kind regards, Saewon Sent from my iPhone On Jun 12, 2026, at 9:28 AM, anil Jain <asdj1990@gmail.com> wrote: Saewon, Thanks a lot for trailing email of SPIRT meeting during ICANN86. No email for such meeting received by me. Infact as per information received, next meeting is on 18th June at 1300 hrs. I request you to kindly reverify email process. Anil Sent from my iPhone On 11 Jun 2026, at 21:28, Saewon Lee via Gnso-spirt <gnso-spirt@icann.org> wrote: Dear SPIRT, Please see the following key outcome and action items from today’s SPIRT Meeting during ICANN86 [icann86.sched.com]<https://urldefense.com/v3/__https://icann86.sched.com/event/2NQRY/gnso-next-...>. [KEY OUTCOME] * SPIRT Members to review the Registry Service Provider (RSP) issue that has been referred by the GNSO Council and respond within 5 calendar days if any objections. * [ACTION ITEMS] 1. Ongoing: All SPIRT Members to update their SOIs in accordance with the SOP. 2. SPIRT Members to review the RSP issue and voice objections or concerns via the SPIRT mailing list by Tuesday, 16 June 2026, at 23:59 UTC (5 calendar days) if they determine that a change to the ongoing round is not required. 3. GNSO Support Staff to reorganize the next set of SPIRT Meetings for June-July and send calendar invites, as necessary. Safe travels back home! Kind regards, Saewon Get Outlook for Mac [aka.ms]<https://urldefense.com/v3/__https://aka.ms/GetOutlookForMac__;!!PtGJab4!4bk6...> _______________________________________________ Gnso-spirt mailing list -- gnso-spirt@icann.org To unsubscribe send an email to gnso-spirt-leave@icann.org
Dear SPIRT, Thank you for yesterday's meeting. It was incredibly productive and within the room it seemed as if there was consensus that the new gTLD Program requires a change regarding the EPP Issue referred to us by the GNSO Counsel. As a reminder I have attached their original submission that described the nature of the issue to our group. I encourage everyone to re-watch (or watch for the first time) Elaine's presentation on the issue. She did a fantastic job describing what could be highly technical into an easily digestible format that those who do not run registries can understand. FYI, Here is the motion that was passed by the Council on Wednesday. Motion - Referral of RSP Issue to the SPIRT Submitted by: Samantha Demetriou Seconded by: Osvaldo Novoa Whereas, 1. On 21 May 2026 <https://icann-community.atlassian.net/wiki/x/MoA_J>, the RySG through Samantha Demetriou shared a Registry Service Provider (RSP) issue with the GNSO Council for potential referral to the SPIRT; 2. A draft version of the Base Registry Agreement (Base RA) for 2026 Next Round applicants required that all registry operators only use extensible provisioning protocol (EPP) extensions that are registered with the Internet Assigned Numbers Authority (IANA); 3. gTLD registries have historically used EPP extensions that are not included in that database; 4. ICANN org agreed to remove this requirement, and the ICANN Board adopted the Base RA that does not include the prohibition of the use of non-IANA registered EPP extension; 5. The RSP evaluation questions require RSP applicants to attest that they will only use the EPP extensions that are registered in the IANA registry, which is also tested during Registry System Testing; 6. This creates a misalignment between what is tested for and what is required to be attested to during Registry System Testing, and what is required under the Base Registry Agreement; 7. The RSP Evaluation Program has already evaluated numerous RSPs and is currently accepting applications from prospective RSPs and will be conducting Registry System Testing on those applicants, further underscoring the need to address the aforementioned misalignment; 8. The Council has now considered the RySG’s request to refer this issue to the SPIRT to consider how to address this misalignment. Resolved, 1. The GNSO Council confirms the referral of the RSP issue brought forth by the RySG to the SPIRT for discussion and alignment with ICANN org. 2. The GNSO Council requests that its liaison to the SPIRT provide this information to the SPIRT for discussion and alignment with ICANN org. 3. The GNSO Council requests that the liaison to the SPIRT advise the Council of the proposed solution when finalized by ICANN Org in cooperation with the SPIRT. Please let us know by 2*3:59 on Tuesday *whether you support or object to the determination that a change is required to the new gTLD program to resolve the issues as described in the GNSO Council's motion and further set forth in the attached submission form. Also remember that this is the only question pending before the group. Any solutions described in the Submission Form will be discussed but only AFTER we determine that a change is required AND ICANN also states that it believes that a change is required as well. On Thu, Jun 11, 2026 at 10:28 PM Saewon Lee via Gnso-spirt < gnso-spirt@icann.org> wrote:
Dear SPIRT,
Please see the following key outcome and action items from today’s SPIRT Meeting during ICANN86 <https://icann86.sched.com/event/2NQRY/gnso-next-round-spirt>.
*[KEY OUTCOME]*
-
SPIRT Members to review the Registry Service Provider (RSP) issue that has been referred by the GNSO Council and respond within 5 calendar days if any objections.
-
*[ACTION ITEMS]*
1. Ongoing: All SPIRT Members to update their SOIs in accordance with the SOP. 2. SPIRT Members to review the RSP issue and voice objections or concerns via the SPIRT mailing list by Tuesday, 16 June 2026, at 23:59 UTC (5 calendar days) if they determine that a change to the ongoing round is not required. 3. GNSO Support Staff to reorganize the next set of SPIRT Meetings for June-July and send calendar invites, as necessary.
Safe travels back home!
Kind regards, Saewon
Get Outlook for Mac <https://aka.ms/GetOutlookForMac> _______________________________________________ Gnso-spirt mailing list -- gnso-spirt@icann.org To unsubscribe send an email to gnso-spirt-leave@icann.org
-- ***Please Note that JJN Solutions, LLC is now JJN Solutions Law, PLLC*** Jeffrey J. Neuman Founder & CEO JJN Solutions Law, PLLC +1.202.549.5079 Jeff@jjnsolutions.com https://www.jjnsolutions.com *This email and any attachments are intended only for the person or entity to which they are addressed and may contain confidential and/or privileged information. If you are not the intended recipient, you may not review, use, disclose, or distribute this message. If you received this email in error, please notify the sender immediately and delete it from your system.* *Nothing in this email is intended to create, and receipt does not establish, an attorney-client relationship unless expressly agreed in writing by JJN Solutions Law, PLLC. Any legal advice contained in this communication is provided solely for the client identified and may not be relied upon by any other person.*
Thanks Jeff, Thanks Elaine, I support that a change is required. Mark Sent from Outlook for Android<https://aka.ms/AAb9ysg> ________________________________ From: Jeff Neuman via Gnso-spirt <gnso-spirt@icann.org> Sent: Friday, June 12, 2026 10:11:27 AM To: Saewon Lee <saewon.lee@icann.org> Cc: gnso-spirt@icann.org <gnso-spirt@icann.org> Subject: [Gnso-spirt] Re: Key Outcomes and Action Items from SPIRT Session during ICANN86 Dear SPIRT, Thank you for yesterday's meeting. It was incredibly productive and within the room it seemed as if there was consensus that the new gTLD Program requires a change regarding the EPP Issue referred to us by the GNSO Counsel. As a reminder I have attached their original submission that described the nature of the issue to our group. I encourage everyone to re-watch (or watch for the first time) Elaine's presentation on the issue. She did a fantastic job describing what could be highly technical into an easily digestible format that those who do not run registries can understand. FYI, Here is the motion that was passed by the Council on Wednesday. Motion - Referral of RSP Issue to the SPIRT Submitted by: Samantha Demetriou Seconded by: Osvaldo Novoa Whereas, 1. On 21 May 2026<https://icann-community.atlassian.net/wiki/x/MoA_J>, the RySG through Samantha Demetriou shared a Registry Service Provider (RSP) issue with the GNSO Council for potential referral to the SPIRT; 2. A draft version of the Base Registry Agreement (Base RA) for 2026 Next Round applicants required that all registry operators only use extensible provisioning protocol (EPP) extensions that are registered with the Internet Assigned Numbers Authority (IANA); 3. gTLD registries have historically used EPP extensions that are not included in that database; 4. ICANN org agreed to remove this requirement, and the ICANN Board adopted the Base RA that does not include the prohibition of the use of non-IANA registered EPP extension; 5. The RSP evaluation questions require RSP applicants to attest that they will only use the EPP extensions that are registered in the IANA registry, which is also tested during Registry System Testing; 6. This creates a misalignment between what is tested for and what is required to be attested to during Registry System Testing, and what is required under the Base Registry Agreement; 7. The RSP Evaluation Program has already evaluated numerous RSPs and is currently accepting applications from prospective RSPs and will be conducting Registry System Testing on those applicants, further underscoring the need to address the aforementioned misalignment; 8. The Council has now considered the RySG’s request to refer this issue to the SPIRT to consider how to address this misalignment. Resolved, 1. The GNSO Council confirms the referral of the RSP issue brought forth by the RySG to the SPIRT for discussion and alignment with ICANN org. 2. The GNSO Council requests that its liaison to the SPIRT provide this information to the SPIRT for discussion and alignment with ICANN org. 3. The GNSO Council requests that the liaison to the SPIRT advise the Council of the proposed solution when finalized by ICANN Org in cooperation with the SPIRT. Please let us know by 23:59 on Tuesday whether you support or object to the determination that a change is required to the new gTLD program to resolve the issues as described in the GNSO Council's motion and further set forth in the attached submission form. Also remember that this is the only question pending before the group. Any solutions described in the Submission Form will be discussed but only AFTER we determine that a change is required AND ICANN also states that it believes that a change is required as well. On Thu, Jun 11, 2026 at 10:28 PM Saewon Lee via Gnso-spirt <gnso-spirt@icann.org<mailto:gnso-spirt@icann.org>> wrote: Dear SPIRT, Please see the following key outcome and action items from today’s SPIRT Meeting during ICANN86<https://icann86.sched.com/event/2NQRY/gnso-next-round-spirt>. [KEY OUTCOME] * SPIRT Members to review the Registry Service Provider (RSP) issue that has been referred by the GNSO Council and respond within 5 calendar days if any objections. * [ACTION ITEMS] 1. Ongoing: All SPIRT Members to update their SOIs in accordance with the SOP. 2. SPIRT Members to review the RSP issue and voice objections or concerns via the SPIRT mailing list by Tuesday, 16 June 2026, at 23:59 UTC (5 calendar days) if they determine that a change to the ongoing round is not required. 3. GNSO Support Staff to reorganize the next set of SPIRT Meetings for June-July and send calendar invites, as necessary. Safe travels back home! Kind regards, Saewon Get Outlook for Mac<https://aka.ms/GetOutlookForMac> _______________________________________________ Gnso-spirt mailing list -- gnso-spirt@icann.org<mailto:gnso-spirt@icann.org> To unsubscribe send an email to gnso-spirt-leave@icann.org<mailto:gnso-spirt-leave@icann.org> -- **Please Note that JJN Solutions, LLC is now JJN Solutions Law, PLLC** [cid:ii_19ebad6f7bc01] Jeffrey J. Neuman Founder & CEO JJN Solutions Law, PLLC +1.202.549.5079 Jeff@jjnsolutions.com<mailto:Jeff@jjnsolutions.com> https://www.jjnsolutions.com This email and any attachments are intended only for the person or entity to which they are addressed and may contain confidential and/or privileged information. If you are not the intended recipient, you may not review, use, disclose, or distribute this message. If you received this email in error, please notify the sender immediately and delete it from your system. Nothing in this email is intended to create, and receipt does not establish, an attorney-client relationship unless expressly agreed in writing by JJN Solutions Law, PLLC. Any legal advice contained in this communication is provided solely for the client identified and may not be relied upon by any other person. Domunis Ltd. is a limited company registered in England and Wales. Registered number: 16425022 Registered office: 2a New Street, Charfield, Wotton Under Edge GL12 8ES, UK VAT registration number: 493 4753 54 Confidentiality, Contract, and Liability: This message is confidential and is intended solely for the use of the addressee. Its contents do not constitute a binding commitment by Domunis Ltd. Any advice or information contained herein should not be relied upon as formal professional advice unless confirmed in a separate, written contract. Unauthorised disclosure or use is prohibited. If you are not the intended recipient, please notify the sender and delete this message immediately. Domunis Ltd. accepts no liability for any reliance placed on this message. Copyright © 2026 All rights reserved.
Support. Alan On Fri, Jun 12, 2026, 10:12 a.m. Jeff Neuman via Gnso-spirt < gnso-spirt@icann.org> wrote:
Dear SPIRT,
Thank you for yesterday's meeting. It was incredibly productive and within the room it seemed as if there was consensus that the new gTLD Program requires a change regarding the EPP Issue referred to us by the GNSO Counsel. As a reminder I have attached their original submission that described the nature of the issue to our group.
I encourage everyone to re-watch (or watch for the first time) Elaine's presentation on the issue. She did a fantastic job describing what could be highly technical into an easily digestible format that those who do not run registries can understand.
FYI, Here is the motion that was passed by the Council on Wednesday.
Motion - Referral of RSP Issue to the SPIRT
Submitted by: Samantha Demetriou
Seconded by: Osvaldo Novoa
Whereas,
1. On 21 May 2026 <https://icann-community.atlassian.net/wiki/x/MoA_J>, the RySG through Samantha Demetriou shared a Registry Service Provider (RSP) issue with the GNSO Council for potential referral to the SPIRT; 2. A draft version of the Base Registry Agreement (Base RA) for 2026 Next Round applicants required that all registry operators only use extensible provisioning protocol (EPP) extensions that are registered with the Internet Assigned Numbers Authority (IANA); 3. gTLD registries have historically used EPP extensions that are not included in that database; 4. ICANN org agreed to remove this requirement, and the ICANN Board adopted the Base RA that does not include the prohibition of the use of non-IANA registered EPP extension; 5. The RSP evaluation questions require RSP applicants to attest that they will only use the EPP extensions that are registered in the IANA registry, which is also tested during Registry System Testing; 6. This creates a misalignment between what is tested for and what is required to be attested to during Registry System Testing, and what is required under the Base Registry Agreement; 7. The RSP Evaluation Program has already evaluated numerous RSPs and is currently accepting applications from prospective RSPs and will be conducting Registry System Testing on those applicants, further underscoring the need to address the aforementioned misalignment; 8. The Council has now considered the RySG’s request to refer this issue to the SPIRT to consider how to address this misalignment.
Resolved,
1. The GNSO Council confirms the referral of the RSP issue brought forth by the RySG to the SPIRT for discussion and alignment with ICANN org. 2. The GNSO Council requests that its liaison to the SPIRT provide this information to the SPIRT for discussion and alignment with ICANN org. 3. The GNSO Council requests that the liaison to the SPIRT advise the Council of the proposed solution when finalized by ICANN Org in cooperation with the SPIRT.
Please let us know by 2*3:59 on Tuesday *whether you support or object to the determination that a change is required to the new gTLD program to resolve the issues as described in the GNSO Council's motion and further set forth in the attached submission form. Also remember that this is the only question pending before the group. Any solutions described in the Submission Form will be discussed but only AFTER we determine that a change is required AND ICANN also states that it believes that a change is required as well.
On Thu, Jun 11, 2026 at 10:28 PM Saewon Lee via Gnso-spirt < gnso-spirt@icann.org> wrote:
Dear SPIRT,
Please see the following key outcome and action items from today’s SPIRT Meeting during ICANN86 <https://icann86.sched.com/event/2NQRY/gnso-next-round-spirt>.
*[KEY OUTCOME]*
-
SPIRT Members to review the Registry Service Provider (RSP) issue that has been referred by the GNSO Council and respond within 5 calendar days if any objections.
-
*[ACTION ITEMS]*
1. Ongoing: All SPIRT Members to update their SOIs in accordance with the SOP. 2. SPIRT Members to review the RSP issue and voice objections or concerns via the SPIRT mailing list by Tuesday, 16 June 2026, at 23:59 UTC (5 calendar days) if they determine that a change to the ongoing round is not required. 3. GNSO Support Staff to reorganize the next set of SPIRT Meetings for June-July and send calendar invites, as necessary.
Safe travels back home!
Kind regards, Saewon
Get Outlook for Mac <https://aka.ms/GetOutlookForMac> _______________________________________________ Gnso-spirt mailing list -- gnso-spirt@icann.org To unsubscribe send an email to gnso-spirt-leave@icann.org
-- ***Please Note that JJN Solutions, LLC is now JJN Solutions Law, PLLC***
Jeffrey J. Neuman
Founder & CEO
JJN Solutions Law, PLLC
+1.202.549.5079
Jeff@jjnsolutions.com
*This email and any attachments are intended only for the person or entity to which they are addressed and may contain confidential and/or privileged information. If you are not the intended recipient, you may not review, use, disclose, or distribute this message. If you received this email in error, please notify the sender immediately and delete it from your system.*
*Nothing in this email is intended to create, and receipt does not establish, an attorney-client relationship unless expressly agreed in writing by JJN Solutions Law, PLLC. Any legal advice contained in this communication is provided solely for the client identified and may not be relied upon by any other person.* _______________________________________________ Gnso-spirt mailing list -- gnso-spirt@icann.org To unsubscribe send an email to gnso-spirt-leave@icann.org
Hi Jeff and SPIRT colleagues, Regarding this RSP matter, I support that a change is needed to the new gTLD program to address it. Best regards, Heather Diaz Vice President, Compliance and Policy fTLD Registry - .Bank | .Insurance Office: +1 408 316 7202 www.fTLD.com Schedule a meeting with me <https://meetings.hubspot.com/heather-diaz> On Fri, Jun 12, 2026 at 4:12 AM Jeff Neuman via Gnso-spirt < gnso-spirt@icann.org> wrote:
Dear SPIRT,
Thank you for yesterday's meeting. It was incredibly productive and within the room it seemed as if there was consensus that the new gTLD Program requires a change regarding the EPP Issue referred to us by the GNSO Counsel. As a reminder I have attached their original submission that described the nature of the issue to our group.
I encourage everyone to re-watch (or watch for the first time) Elaine's presentation on the issue. She did a fantastic job describing what could be highly technical into an easily digestible format that those who do not run registries can understand.
FYI, Here is the motion that was passed by the Council on Wednesday.
Motion - Referral of RSP Issue to the SPIRT
Submitted by: Samantha Demetriou
Seconded by: Osvaldo Novoa
Whereas,
1. On 21 May 2026 <https://icann-community.atlassian.net/wiki/x/MoA_J>, the RySG through Samantha Demetriou shared a Registry Service Provider (RSP) issue with the GNSO Council for potential referral to the SPIRT; 2. A draft version of the Base Registry Agreement (Base RA) for 2026 Next Round applicants required that all registry operators only use extensible provisioning protocol (EPP) extensions that are registered with the Internet Assigned Numbers Authority (IANA); 3. gTLD registries have historically used EPP extensions that are not included in that database; 4. ICANN org agreed to remove this requirement, and the ICANN Board adopted the Base RA that does not include the prohibition of the use of non-IANA registered EPP extension; 5. The RSP evaluation questions require RSP applicants to attest that they will only use the EPP extensions that are registered in the IANA registry, which is also tested during Registry System Testing; 6. This creates a misalignment between what is tested for and what is required to be attested to during Registry System Testing, and what is required under the Base Registry Agreement; 7. The RSP Evaluation Program has already evaluated numerous RSPs and is currently accepting applications from prospective RSPs and will be conducting Registry System Testing on those applicants, further underscoring the need to address the aforementioned misalignment; 8. The Council has now considered the RySG’s request to refer this issue to the SPIRT to consider how to address this misalignment.
Resolved,
1. The GNSO Council confirms the referral of the RSP issue brought forth by the RySG to the SPIRT for discussion and alignment with ICANN org. 2. The GNSO Council requests that its liaison to the SPIRT provide this information to the SPIRT for discussion and alignment with ICANN org. 3. The GNSO Council requests that the liaison to the SPIRT advise the Council of the proposed solution when finalized by ICANN Org in cooperation with the SPIRT.
Please let us know by 2*3:59 on Tuesday *whether you support or object to the determination that a change is required to the new gTLD program to resolve the issues as described in the GNSO Council's motion and further set forth in the attached submission form. Also remember that this is the only question pending before the group. Any solutions described in the Submission Form will be discussed but only AFTER we determine that a change is required AND ICANN also states that it believes that a change is required as well.
On Thu, Jun 11, 2026 at 10:28 PM Saewon Lee via Gnso-spirt < gnso-spirt@icann.org> wrote:
Dear SPIRT,
Please see the following key outcome and action items from today’s SPIRT Meeting during ICANN86 <https://icann86.sched.com/event/2NQRY/gnso-next-round-spirt>.
*[KEY OUTCOME]*
-
SPIRT Members to review the Registry Service Provider (RSP) issue that has been referred by the GNSO Council and respond within 5 calendar days if any objections.
-
*[ACTION ITEMS]*
1. Ongoing: All SPIRT Members to update their SOIs in accordance with the SOP. 2. SPIRT Members to review the RSP issue and voice objections or concerns via the SPIRT mailing list by Tuesday, 16 June 2026, at 23:59 UTC (5 calendar days) if they determine that a change to the ongoing round is not required. 3. GNSO Support Staff to reorganize the next set of SPIRT Meetings for June-July and send calendar invites, as necessary.
Safe travels back home!
Kind regards, Saewon
Get Outlook for Mac <https://aka.ms/GetOutlookForMac> _______________________________________________ Gnso-spirt mailing list -- gnso-spirt@icann.org To unsubscribe send an email to gnso-spirt-leave@icann.org
-- ***Please Note that JJN Solutions, LLC is now JJN Solutions Law, PLLC***
Jeffrey J. Neuman
Founder & CEO
JJN Solutions Law, PLLC
+1.202.549.5079
Jeff@jjnsolutions.com
*This email and any attachments are intended only for the person or entity to which they are addressed and may contain confidential and/or privileged information. If you are not the intended recipient, you may not review, use, disclose, or distribute this message. If you received this email in error, please notify the sender immediately and delete it from your system.*
*Nothing in this email is intended to create, and receipt does not establish, an attorney-client relationship unless expressly agreed in writing by JJN Solutions Law, PLLC. Any legal advice contained in this communication is provided solely for the client identified and may not be relied upon by any other person.* _______________________________________________ Gnso-spirt mailing list -- gnso-spirt@icann.org To unsubscribe send an email to gnso-spirt-leave@icann.org
---- Secured by Paubox - HITRUST certified https://www.paubox.com ----
Thanks Jeff and Saewon, I support the determination that a change is required to the new gTLD program to resolve the issues. Elaine From: Jeff Neuman via Gnso-spirt <gnso-spirt@icann.org> Reply-To: Jeff Neuman <jeff@jjnsolutions.com> Date: Friday, June 12, 2026 at 10:12 AM To: Saewon Lee <saewon.lee@icann.org> Cc: "gnso-spirt@icann.org" <gnso-spirt@icann.org> Subject: [EXTERNAL] [Gnso-spirt] Re: Key Outcomes and Action Items from SPIRT Session during ICANN86 Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Dear SPIRT, Thank you for yesterday's meeting. It was incredibly productive and within the room it seemed as if there was consensus that the new gTLD Program requires a change regarding the EPP Issue referred to us by the GNSO Counsel. As a reminder I have attached their original submission that described the nature of the issue to our group. I encourage everyone to re-watch (or watch for the first time) Elaine's presentation on the issue. She did a fantastic job describing what could be highly technical into an easily digestible format that those who do not run registries can understand. FYI, Here is the motion that was passed by the Council on Wednesday. Motion - Referral of RSP Issue to the SPIRT Submitted by: Samantha Demetriou Seconded by: Osvaldo Novoa Whereas, 1. On 21 May 2026<https://secure-web.cisco.com/1q7eR1y7HENhbiFkKUxvx9BYG3fR2hmIK8FzKz11aI5r812...>, the RySG through Samantha Demetriou shared a Registry Service Provider (RSP) issue with the GNSO Council for potential referral to the SPIRT; 2. A draft version of the Base Registry Agreement (Base RA) for 2026 Next Round applicants required that all registry operators only use extensible provisioning protocol (EPP) extensions that are registered with the Internet Assigned Numbers Authority (IANA); 3. gTLD registries have historically used EPP extensions that are not included in that database; 4. ICANN org agreed to remove this requirement, and the ICANN Board adopted the Base RA that does not include the prohibition of the use of non-IANA registered EPP extension; 5. The RSP evaluation questions require RSP applicants to attest that they will only use the EPP extensions that are registered in the IANA registry, which is also tested during Registry System Testing; 6. This creates a misalignment between what is tested for and what is required to be attested to during Registry System Testing, and what is required under the Base Registry Agreement; 7. The RSP Evaluation Program has already evaluated numerous RSPs and is currently accepting applications from prospective RSPs and will be conducting Registry System Testing on those applicants, further underscoring the need to address the aforementioned misalignment; 8. The Council has now considered the RySG’s request to refer this issue to the SPIRT to consider how to address this misalignment. Resolved, 1. The GNSO Council confirms the referral of the RSP issue brought forth by the RySG to the SPIRT for discussion and alignment with ICANN org. 2. The GNSO Council requests that its liaison to the SPIRT provide this information to the SPIRT for discussion and alignment with ICANN org. 3. The GNSO Council requests that the liaison to the SPIRT advise the Council of the proposed solution when finalized by ICANN Org in cooperation with the SPIRT. Please let us know by 23:59 on Tuesday whether you support or object to the determination that a change is required to the new gTLD program to resolve the issues as described in the GNSO Council's motion and further set forth in the attached submission form. Also remember that this is the only question pending before the group. Any solutions described in the Submission Form will be discussed but only AFTER we determine that a change is required AND ICANN also states that it believes that a change is required as well. On Thu, Jun 11, 2026 at 10:28 PM Saewon Lee via Gnso-spirt <gnso-spirt@icann.org<mailto:gnso-spirt@icann.org>> wrote: Dear SPIRT, Please see the following key outcome and action items from today’s SPIRT Meeting during ICANN86<https://secure-web.cisco.com/1761Fl1kkQEMDah0-UabfPOTM8CVQom9CoenLnxjBxg4YvM...>. [KEY OUTCOME] · SPIRT Members to review the Registry Service Provider (RSP) issue that has been referred by the GNSO Council and respond within 5 calendar days if any objections. · [ACTION ITEMS] 1. Ongoing: All SPIRT Members to update their SOIs in accordance with the SOP. 1. SPIRT Members to review the RSP issue and voice objections or concerns via the SPIRT mailing list by Tuesday, 16 June 2026, at 23:59 UTC (5 calendar days) if they determine that a change to the ongoing round is not required. 1. GNSO Support Staff to reorganize the next set of SPIRT Meetings for June-July and send calendar invites, as necessary. Safe travels back home! Kind regards, Saewon Get Outlook for Mac<https://aka.ms/GetOutlookForMac> _______________________________________________ Gnso-spirt mailing list -- gnso-spirt@icann.org<mailto:gnso-spirt@icann.org> To unsubscribe send an email to gnso-spirt-leave@icann.org<mailto:gnso-spirt-leave@icann.org> -- **Please Note that JJN Solutions, LLC is now JJN Solutions Law, PLLC** [cid:image001.png@01DCFA6F.A08E0C90] Jeffrey J. Neuman Founder & CEO JJN Solutions Law, PLLC +1.202.549.5079 Jeff@jjnsolutions.com<mailto:Jeff@jjnsolutions.com> https://www.jjnsolutions.com<https://secure-web.cisco.com/1hJs3HUgMM5nvnZzdJdgCyNV9EKfjsWCE3Tg0cDPJHX_fJrCZSDAT-S_MVmeBqQa3Vs_cXvg8FSWXaCGXV2FDCEkDtmspH6MpwcfeoUopiiu21ToRyTOxJofTa7gE_68ccqrtaIopRuIqvjtIFT3tbawNElGpBeeOUFJqgjKtlVfXrcjqJGp7OHOmazkoGHIVY1Dethg1JDhU3pZLPIMHHHoxOP2cPL_0y3cGPKEzXnCdyePrqyqnKi3SaRCeWvVC-lX61yvi_ohJazbAjuh7CRNBP476WzwAl24IwkAvjkk/https%3A%2F%2Fwww.jjnsolutions.com> This email and any attachments are intended only for the person or entity to which they are addressed and may contain confidential and/or privileged information. If you are not the intended recipient, you may not review, use, disclose, or distribute this message. If you received this email in error, please notify the sender immediately and delete it from your system. Nothing in this email is intended to create, and receipt does not establish, an attorney-client relationship unless expressly agreed in writing by JJN Solutions Law, PLLC. Any legal advice contained in this communication is provided solely for the client identified and may not be relied upon by any other person.
Dear all, My support for change suggested For new gTLD programme. Anil Kumar Jain On Fri, 12 Jun 2026 at 12:30, Pruis, Elaine via Gnso-spirt < gnso-spirt@icann.org> wrote:
Thanks Jeff and Saewon,
I support the determination that a change is required to the new gTLD program to resolve the issues.
Elaine
*From: *Jeff Neuman via Gnso-spirt <gnso-spirt@icann.org> *Reply-To: *Jeff Neuman <jeff@jjnsolutions.com> *Date: *Friday, June 12, 2026 at 10:12 AM *To: *Saewon Lee <saewon.lee@icann.org> *Cc: *"gnso-spirt@icann.org" <gnso-spirt@icann.org> *Subject: *[EXTERNAL] [Gnso-spirt] Re: Key Outcomes and Action Items from SPIRT Session during ICANN86
*Caution:* This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Dear SPIRT,
Thank you for yesterday's meeting. It was incredibly productive and within the room it seemed as if there was consensus that the new gTLD Program requires a change regarding the EPP Issue referred to us by the GNSO Counsel. As a reminder I have attached their original submission that described the nature of the issue to our group.
I encourage everyone to re-watch (or watch for the first time) Elaine's presentation on the issue. She did a fantastic job describing what could be highly technical into an easily digestible format that those who do not run registries can understand.
FYI, Here is the motion that was passed by the Council on Wednesday.
*Motion - Referral of RSP Issue to the SPIRT*
*Submitted by: Samantha Demetriou*
*Seconded by: Osvaldo Novoa*
Whereas,
1. On 21 May 2026 <https://secure-web.cisco.com/1q7eR1y7HENhbiFkKUxvx9BYG3fR2hmIK8FzKz11aI5r812...>, the RySG through Samantha Demetriou shared a Registry Service Provider (RSP) issue with the GNSO Council for potential referral to the SPIRT;
2. A draft version of the Base Registry Agreement (Base RA) for 2026 Next Round applicants required that all registry operators only use extensible provisioning protocol (EPP) extensions that are registered with the Internet Assigned Numbers Authority (IANA);
3. gTLD registries have historically used EPP extensions that are not included in that database;
4. ICANN org agreed to remove this requirement, and the ICANN Board adopted the Base RA that does not include the prohibition of the use of non-IANA registered EPP extension;
5. The RSP evaluation questions require RSP applicants to attest that they will only use the EPP extensions that are registered in the IANA registry, which is also tested during Registry System Testing;
6. This creates a misalignment between what is tested for and what is required to be attested to during Registry System Testing, and what is required under the Base Registry Agreement;
7. The RSP Evaluation Program has already evaluated numerous RSPs and is currently accepting applications from prospective RSPs and will be conducting Registry System Testing on those applicants, further underscoring the need to address the aforementioned misalignment;
8. The Council has now considered the RySG’s request to refer this issue to the SPIRT to consider how to address this misalignment.
Resolved,
1. The GNSO Council confirms the referral of the RSP issue brought forth by the RySG to the SPIRT for discussion and alignment with ICANN org.
2. The GNSO Council requests that its liaison to the SPIRT provide this information to the SPIRT for discussion and alignment with ICANN org.
3. The GNSO Council requests that the liaison to the SPIRT advise the Council of the proposed solution when finalized by ICANN Org in cooperation with the SPIRT.
Please let us know by 2*3:59 on Tuesday *whether you support or object to the determination that a change is required to the new gTLD program to resolve the issues as described in the GNSO Council's motion and further set forth in the attached submission form. Also remember that this is the only question pending before the group. Any solutions described in the Submission Form will be discussed but only AFTER we determine that a change is required AND ICANN also states that it believes that a change is required as well.
On Thu, Jun 11, 2026 at 10:28 PM Saewon Lee via Gnso-spirt < gnso-spirt@icann.org> wrote:
Dear SPIRT,
Please see the following key outcome and action items from today’s SPIRT Meeting during ICANN86 <https://secure-web.cisco.com/1761Fl1kkQEMDah0-UabfPOTM8CVQom9CoenLnxjBxg4YvM...> .
*[**KEY OUTCOME]*
· SPIRT Members to review the Registry Service Provider (RSP) issue that has been referred by the GNSO Council and respond within 5 calendar days if any objections.
·
*[**ACTION ITEMS]*
1. Ongoing: All SPIRT Members to update their SOIs in accordance with the SOP.
2. SPIRT Members to review the RSP issue and voice objections or concerns via the SPIRT mailing list by Tuesday, 16 June 2026, at 23:59 UTC (5 calendar days) if they determine that a change to the ongoing round is not required.
3. GNSO Support Staff to reorganize the next set of SPIRT Meetings for June-July and send calendar invites, as necessary.
Safe travels back home!
Kind regards,
Saewon
Get Outlook for Mac <https://aka.ms/GetOutlookForMac>
_______________________________________________ Gnso-spirt mailing list -- gnso-spirt@icann.org To unsubscribe send an email to gnso-spirt-leave@icann.org
--
***Please Note that JJN Solutions, LLC is now JJN Solutions Law, PLLC***
* Jeffrey J. Neuman*
Founder & CEO
*JJN Solutions Law, PLLC*
+1.202.549.5079
*Jeff@jjnsolutions.com <Jeff@jjnsolutions.com>*
*https://www.jjnsolutions.com <https://secure-web.cisco.com/1hJs3HUgMM5nvnZzdJdgCyNV9EKfjsWCE3Tg0cDPJHX_fJrCZSDAT-S_MVmeBqQa3Vs_cXvg8FSWXaCGXV2FDCEkDtmspH6MpwcfeoUopiiu21ToRyTOxJofTa7gE_68ccqrtaIopRuIqvjtIFT3tbawNElGpBeeOUFJqgjKtlVfXrcjqJGp7OHOmazkoGHIVY1Dethg1JDhU3pZLPIMHHHoxOP2cPL_0y3cGPKEzXnCdyePrqyqnKi3SaRCeWvVC-lX61yvi_ohJazbAjuh7CRNBP476WzwAl24IwkAvjkk/https%3A%2F%2Fwww.jjnsolutions.com>*
*This email and any attachments are intended only for the person or entity to which they are addressed and may contain confidential and/or privileged information. If you are not the intended recipient, you may not review, use, disclose, or distribute this message. If you received this email in error, please notify the sender immediately and delete it from your system.*
*Nothing in this email is intended to create, and receipt does not establish, an attorney-client relationship unless expressly agreed in writing by JJN Solutions Law, PLLC. Any legal advice contained in this communication is provided solely for the client identified and may not be relied upon by any other person.* _______________________________________________ Gnso-spirt mailing list -- gnso-spirt@icann.org To unsubscribe send an email to gnso-spirt-leave@icann.org
Hello Jeff, Hello Elaine, Thanks Jeff, for a very productive SPIRT meeting in Sevilla. Thanks Elaine, for your very clear presentation regarding the RSP EPP issue referred to the SPIRT by the GNSO Council. I fully support the change required to the next Round Base Registry Agreement. Regards Phil Phil Buckingham Unfortunately, I will not be able to attend to the next SPIRT meeting on Thursday 18 June at 13.00 UTC . I wish to raise a material issue/ problem(s) regarding the ASP Program . What are my next steps ? From: Jeff Neuman via Gnso-spirt <gnso-spirt@icann.org> Sent: 12 June 2026 09:11 To: Saewon Lee <saewon.lee@icann.org> Cc: gnso-spirt@icann.org Subject: [Gnso-spirt] Re: Key Outcomes and Action Items from SPIRT Session during ICANN86 Dear SPIRT, Thank you for yesterday's meeting. It was incredibly productive and within the room it seemed as if there was consensus that the new gTLD Program requires a change regarding the EPP Issue referred to us by the GNSO Counsel. As a reminder I have attached their original submission that described the nature of the issue to our group. I encourage everyone to re-watch (or watch for the first time) Elaine's presentation on the issue. She did a fantastic job describing what could be highly technical into an easily digestible format that those who do not run registries can understand. FYI, Here is the motion that was passed by the Council on Wednesday. Motion - Referral of RSP Issue to the SPIRT Submitted by: Samantha Demetriou Seconded by: Osvaldo Novoa Whereas, 1. On <https://icann-community.atlassian.net/wiki/x/MoA_J> 21 May 2026, the RySG through Samantha Demetriou shared a Registry Service Provider (RSP) issue with the GNSO Council for potential referral to the SPIRT; 2. A draft version of the Base Registry Agreement (Base RA) for 2026 Next Round applicants required that all registry operators only use extensible provisioning protocol (EPP) extensions that are registered with the Internet Assigned Numbers Authority (IANA); 3. gTLD registries have historically used EPP extensions that are not included in that database; 4. ICANN org agreed to remove this requirement, and the ICANN Board adopted the Base RA that does not include the prohibition of the use of non-IANA registered EPP extension; 5. The RSP evaluation questions require RSP applicants to attest that they will only use the EPP extensions that are registered in the IANA registry, which is also tested during Registry System Testing; 6. This creates a misalignment between what is tested for and what is required to be attested to during Registry System Testing, and what is required under the Base Registry Agreement; 7. The RSP Evaluation Program has already evaluated numerous RSPs and is currently accepting applications from prospective RSPs and will be conducting Registry System Testing on those applicants, further underscoring the need to address the aforementioned misalignment; 8. The Council has now considered the RySG’s request to refer this issue to the SPIRT to consider how to address this misalignment. Resolved, 1. The GNSO Council confirms the referral of the RSP issue brought forth by the RySG to the SPIRT for discussion and alignment with ICANN org. 2. The GNSO Council requests that its liaison to the SPIRT provide this information to the SPIRT for discussion and alignment with ICANN org. 3. The GNSO Council requests that the liaison to the SPIRT advise the Council of the proposed solution when finalized by ICANN Org in cooperation with the SPIRT. Please let us know by 23:59 on Tuesday whether you support or object to the determination that a change is required to the new gTLD program to resolve the issues as described in the GNSO Council's motion and further set forth in the attached submission form. Also remember that this is the only question pending before the group. Any solutions described in the Submission Form will be discussed but only AFTER we determine that a change is required AND ICANN also states that it believes that a change is required as well. On Thu, Jun 11, 2026 at 10:28 PM Saewon Lee via Gnso-spirt <gnso-spirt@icann.org <mailto:gnso-spirt@icann.org> > wrote: Dear SPIRT, Please see the following key outcome and action items from today’s SPIRT Meeting during ICANN86 <https://icann86.sched.com/event/2NQRY/gnso-next-round-spirt> . [KEY OUTCOME] * SPIRT Members to review the Registry Service Provider (RSP) issue that has been referred by the GNSO Council and respond within 5 calendar days if any objections. * [ACTION ITEMS] 1. Ongoing: All SPIRT Members to update their SOIs in accordance with the SOP. 2. SPIRT Members to review the RSP issue and voice objections or concerns via the SPIRT mailing list by Tuesday, 16 June 2026, at 23:59 UTC (5 calendar days) if they determine that a change to the ongoing round is not required. 3. GNSO Support Staff to reorganize the next set of SPIRT Meetings for June-July and send calendar invites, as necessary. Safe travels back home! Kind regards, Saewon Get Outlook for Mac <https://aka.ms/GetOutlookForMac> _______________________________________________ Gnso-spirt mailing list -- gnso-spirt@icann.org <mailto:gnso-spirt@icann.org> To unsubscribe send an email to gnso-spirt-leave@icann.org <mailto:gnso-spirt-leave@icann.org> -- **Please Note that JJN Solutions, LLC is now JJN Solutions Law, PLLC** Jeffrey J. Neuman Founder & CEO JJN Solutions Law, PLLC +1.202.549.5079 <mailto:Jeff@jjnsolutions.com> Jeff@jjnsolutions.com <https://www.jjnsolutions.com> https://www.jjnsolutions.com This email and any attachments are intended only for the person or entity to which they are addressed and may contain confidential and/or privileged information. If you are not the intended recipient, you may not review, use, disclose, or distribute this message. If you received this email in error, please notify the sender immediately and delete it from your system. Nothing in this email is intended to create, and receipt does not establish, an attorney-client relationship unless expressly agreed in writing by JJN Solutions Law, PLLC. Any legal advice contained in this communication is provided solely for the client identified and may not be relied upon by any other person.
Dear SPIRT, It has been brought to my attention that the notes below may not align with the information communicated in Jeff's Call for Support message and may therefore have caused some confusion. Please see the updated language below (yellow highlights) and we look forward to hearing more from the members by Tuesday, 16 June 2026. Kind regards, Saewon Get Outlook for Mac<https://aka.ms/GetOutlookForMac> From: Saewon Lee <saewon.lee@icann.org> Date: Thursday, June 11, 2026 at 4:28 PM To: gnso-spirt@icann.org <gnso-spirt@icann.org> Subject: Key Outcomes and Action Items from SPIRT Session during ICANN86 Dear SPIRT, Please see the following key outcome and action items from today’s SPIRT Meeting during ICANN86<https://icann86.sched.com/event/2NQRY/gnso-next-round-spirt>. [KEY OUTCOME] * SPIRT Members to review the Registry Service Provider (RSP) issue that has been referred by the GNSO Council and respond within 5 calendar days if any objections.whether you support or object to the determination that a change is required to the New gTLD Program. * [ACTION ITEMS] 1. Ongoing: All SPIRT Members to update their SOIs in accordance with the SOP. 2. SPIRT Members to review the RSP issue and voice your support or objectionsobjections or concerns via the SPIRT mailing list by Tuesday, 16 June 2026, at 23:59 UTC (5 calendar days) ifwhether they determine that a change to the ongoing round is not required. 3. GNSO Support Staff to reorganize the next set of SPIRT Meetings for June-July and send calendar invites, as necessary. Safe travels back home! Kind regards, Saewon Get Outlook for Mac<https://aka.ms/GetOutlookForMac>
Please note my *Support* for a timely change to the new gTLD Program regarding the RSP issue discussed at our meeting during ICANN86. Cheryl Langdon-Orr <https://about.me/cheryl.LangdonOrr?promo=email_sig&utm_source=product&utm_me...> Cheryl Langdon-Orr about.me/cheryl.LangdonOrr <https://about.me/cheryl.LangdonOrr?promo=email_sig&utm_source=product&utm_me...> On Mon, 15 Jun 2026 at 13:00, Saewon Lee via Gnso-spirt < gnso-spirt@icann.org> wrote:
Dear SPIRT,
It has been brought to my attention that the notes below may not align with the information communicated in Jeff's Call for Support message and may therefore have caused some confusion.
Please see the updated language below (yellow highlights) and we look forward to hearing more from the members by Tuesday, 16 June 2026.
Kind regards, Saewon
Get Outlook for Mac <https://aka.ms/GetOutlookForMac> *From: *Saewon Lee <saewon.lee@icann.org> *Date: *Thursday, June 11, 2026 at 4:28 PM *To: *gnso-spirt@icann.org <gnso-spirt@icann.org> *Subject: *Key Outcomes and Action Items from SPIRT Session during ICANN86
Dear SPIRT,
Please see the following key outcome and action items from today’s SPIRT Meeting during ICANN86 <https://icann86.sched.com/event/2NQRY/gnso-next-round-spirt>.
*[KEY OUTCOME]*
-
SPIRT Members to review the Registry Service Provider (RSP) issue that has been referred by the GNSO Council and respond within 5 calendar days if any objections.whether you support or object to the determination that a change is required to the New gTLD Program. -
*[ACTION ITEMS]*
1. Ongoing: All SPIRT Members to update their SOIs in accordance with the SOP. 2. SPIRT Members to review the RSP issue and voice your support or objectionsobjections or concerns via the SPIRT mailing list by Tuesday, 16 June 2026, at 23:59 UTC (5 calendar days) ifwhether they determine that a change to the ongoing round is not required. 3. GNSO Support Staff to reorganize the next set of SPIRT Meetings for June-July and send calendar invites, as necessary.
Safe travels back home!
Kind regards, Saewon
Get Outlook for Mac <https://aka.ms/GetOutlookForMac> _______________________________________________ Gnso-spirt mailing list -- gnso-spirt@icann.org To unsubscribe send an email to gnso-spirt-leave@icann.org
+1 ( I do support the
a timely change to the new gTLD Program regarding the RSP issue discussed at our meeting during ICANN86
Sincerely Yours, Maxim Alzoba Special projects manager, International Relations Department, FAITID
On 15 Jun 2026, at 06:05, Cheryl Langdon-Orr via Gnso-spirt <gnso-spirt@icann.org> wrote:
Please note my *Support* for a timely change to the new gTLD Program regarding the RSP issue discussed at our meeting during ICANN86.
Cheryl Langdon-Orr
<https://about.me/cheryl.LangdonOrr?promo=email_sig&utm_source=product&utm_me...> Cheryl Langdon-Orr about.me/cheryl.LangdonOrr <https://about.me/cheryl.LangdonOrr?promo=email_sig&utm_source=product&utm_me...>
On Mon, 15 Jun 2026 at 13:00, Saewon Lee via Gnso-spirt <gnso-spirt@icann.org <mailto:gnso-spirt@icann.org>> wrote:
Dear SPIRT,
It has been brought to my attention that the notes below may not align with the information communicated in Jeff's Call for Support message and may therefore have caused some confusion.
Please see the updated language below (yellow highlights) and we look forward to hearing more from the members by Tuesday, 16 June 2026.
Kind regards, Saewon
Get Outlook for Mac <https://aka.ms/GetOutlookForMac> From: Saewon Lee <saewon.lee@icann.org <mailto:saewon.lee@icann.org>> Date: Thursday, June 11, 2026 at 4:28 PM To: gnso-spirt@icann.org <mailto:gnso-spirt@icann.org> <gnso-spirt@icann.org <mailto:gnso-spirt@icann.org>> Subject: Key Outcomes and Action Items from SPIRT Session during ICANN86
Dear SPIRT,
Please see the following key outcome and action items from today’s SPIRT Meeting during ICANN86 <https://icann86.sched.com/event/2NQRY/gnso-next-round-spirt>.
[KEY OUTCOME] SPIRT Members to review the Registry Service Provider (RSP) issue that has been referred by the GNSO Council and respond within 5 calendar days if any objections.whether you support or object to the determination that a change is required to the New gTLD Program.
[ACTION ITEMS] Ongoing: All SPIRT Members to update their SOIs in accordance with the SOP. SPIRT Members to review the RSP issue and voice your support or objectionsobjections or concerns via the SPIRT mailing list by Tuesday, 16 June 2026, at 23:59 UTC (5 calendar days) ifwhether they determine that a change to the ongoing round is not required. GNSO Support Staff to reorganize the next set of SPIRT Meetings for June-July and send calendar invites, as necessary.
Safe travels back home!
Kind regards, Saewon
Get Outlook for Mac <https://aka.ms/GetOutlookForMac>_______________________________________________ Gnso-spirt mailing list -- gnso-spirt@icann.org <mailto:gnso-spirt@icann.org> To unsubscribe send an email to gnso-spirt-leave@icann.org <mailto:gnso-spirt-leave@icann.org>
Gnso-spirt mailing list -- gnso-spirt@icann.org To unsubscribe send an email to gnso-spirt-leave@icann.org
Dear Team, I am writing to support the determination that a change to the new gTLD program is needed based on the RSP issue. Warm Regards, Christabel ________________________________ From: Saewon Lee via Gnso-spirt <gnso-spirt@icann.org> Sent: 15 June 2026 04:00 To: gnso-spirt@icann.org <gnso-spirt@icann.org> Subject: [Gnso-spirt] Re: Key Outcomes and Action Items from SPIRT Session during ICANN86 Dear SPIRT, It has been brought to my attention that the notes below may not align with the information communicated in Jeff's Call for Support message and may therefore have caused some confusion. Please see the updated language below (yellow highlights) and we look forward to hearing more from the members by Tuesday, 16 June 2026. Kind regards, Saewon Get Outlook for Mac<https://aka.ms/GetOutlookForMac> From: Saewon Lee <saewon.lee@icann.org> Date: Thursday, June 11, 2026 at 4:28 PM To: gnso-spirt@icann.org <gnso-spirt@icann.org> Subject: Key Outcomes and Action Items from SPIRT Session during ICANN86 Dear SPIRT, Please see the following key outcome and action items from today’s SPIRT Meeting during ICANN86<https://icann86.sched.com/event/2NQRY/gnso-next-round-spirt>. [KEY OUTCOME] * SPIRT Members to review the Registry Service Provider (RSP) issue that has been referred by the GNSO Council and respond within 5 calendar days if any objections.whether you support or object to the determination that a change is required to the New gTLD Program. * [ACTION ITEMS] 1. Ongoing: All SPIRT Members to update their SOIs in accordance with the SOP. 2. SPIRT Members to review the RSP issue and voice your support or objectionsobjections or concerns via the SPIRT mailing list by Tuesday, 16 June 2026, at 23:59 UTC (5 calendar days) ifwhether they determine that a change to the ongoing round is not required. 3. GNSO Support Staff to reorganize the next set of SPIRT Meetings for June-July and send calendar invites, as necessary. Safe travels back home! Kind regards, Saewon Get Outlook for Mac<https://aka.ms/GetOutlookForMac>
participants (12)
-
Alan Greenberg -
anil Jain -
Cheryl Langdon-Orr -
Chris Disspain -
Christabel Mebaghandu -
Heather Diaz -
Jeff Neuman -
Mark Wilson -
Maxim Alzoba -
Phil Buckingham -
Pruis, Elaine -
Saewon Lee