January 2026 - Gnso-spirt - lists.icann.org

Post Call | Standing Predictability Implementation Review Team (SPIRT) | Thursday, 29 January 2026
by Terri Agnew Jan. 30, 2026

Jan. 30, 2026

Dear all, All recordings for the Standing Predictability Implementation Review Team (SPIRT) call held on Thursday, 29 January 2026 at 20:00 UTC can be found on the agenda wiki page <https://icann-community.atlassian.net/wiki/x/HQAEKQ> . You can also access via the GNSO Calendar 2026<https://gnso.icann.org/en/group-activities/calendar/2026>. Agenda wiki page includes: * Attendance * Audio recording * Zoom recording (including audio, visual, rough transcript, and chat.) * Agenda and Notes/Action Items For additional information, you may consult the mailing list archives<https://lists.icann.org/hyperkitty/list/gnso-spirt@icann.org/> and the main wiki page<https://icann-community.atlassian.net/wiki/x/nwB2HQ>. Thank you. Kind regards, Terri Policy Team Supporting the GNSO

2 1

Notes and Action Items | SPIRT Meeting #3 | 29 January 2026 at 13:00 UTC
by Saewon Lee Jan. 30, 2026

Jan. 30, 2026

Dear SPIRT, Please see the following outcomes, action items, and high-level notes from today’s SPIRT Meeting #3<https://icann-community.atlassian.net/wiki/x/HQAEKQ>. Kind regards, Saewon Key Outcomes, Action Items, and Notes from SPIRT Meeting #3<https://icann-community.atlassian.net/wiki/x/HQAEKQ> – Thursday, 29 January 2026, at 13:00 UTC. [KEY OUTCOMES] 1. The Members List has been updated with the “Disclosure Statement” in the wiki page<https://icann-community.atlassian.net/wiki/spaces/SPIRTS/pages/495517697/3.…>. 2. The Change Log has been created in the wiki page<https://icann-community.atlassian.net/wiki/x/LIC9Lg>. 3. A SPIRT Issue Consideration Process draft<https://docs.google.com/document/d/1zITIUCB5yvjV_Rj5Z87ljyqajA5VliMSPvPb77A…> has been created – including a google request form – for review to address those situations where a SPIRT member may have identified issues for the New gTLD Program. 4. SPIRT Meetings will take place every other week; next meeting will be on 12 February 2026 (Time to be reconfirmed). 5. No planned meetings during ICANN85 in Mumbai. [ACTION ITEMS] 1. All SPIRT members to update their SOIs in accordance with the SOP for the completion of the “Disclosure Statement” within the “Members List” by 26 February 2026 SPIRT Meeting. 2. Members that are facing any problems with accessing or updating their SOIs to contact gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> for support. 3. GDS Staff to share the current typographical changes file with the SPIRT after the call. 4. GNSO Support Staff to circulate the SPIRT procedures draft with the SPIRT Members after the call 5. SPIRT Members to review the procedures document and provide input for leadership team’s consideration and finalization. [NOTES] * Retrieve slides from here: https://icann-community.atlassian.net/wiki/x/HQAEKQ 1. Welcome and SOIs o See Members List in the wiki here: https://icann-community.atlassian.net/wiki/x/AQCJHQ o “Section 13” in the SOI should be updated to ensure it is current; “Disclosure Statement” column in the members wiki page is updated based on SOI updates in accordance with the SOP – this column must be updated by all members by the second meeting of February 2026 (26 February 2026) or they will be moved to observer status. o As for SOP and disclosure statement, the Chair re-emphasized that the use of “conflict of interest” should be avoided; rather, the members should focus on disclosing their association with applicants and/or a party that may file objections. * Outcome: Members List has been updated with the “Disclosure Statement” in the wiki page<https://icann-community.atlassian.net/wiki/x/AQCJHQ>. * Action Item: 1) All SPIRT members to update their SOIs in accordance with the SOP for the completion of the “Disclosure Statement” within the “Members List” by 26 February 2026 SPIRT Meeting; 2) Members that are facing any problems with accessing or updating their SOIs to contact gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> for support. 1. Review of Change Log Wiki o See the Change Log of the New gTLD Program in the wiki here: https://icann-community.atlassian.net/wiki/x/LIC9Lg o You may also subscribe to receive from the wiki page directly: see page 6 on slide<https://icann-community.atlassian.net/wiki/spaces/SPIRTS/pages/688128029/20…> o A separate Change Log exists for RSP. See the RSP page here: https://newgtldprogram.icann.org/en/application-rounds/round2/rsp/handbook o GDS Staff informed the SPIRT that there are typographical changes in the AGB that are currently being collected by GDS Staff; to be clear, they are not minor or non-minor changes that have any material impact to the applicants, thus will be logged under a new category – i.e., typographical changes. This file will be shared with the SPIRT after the call. o Several suggestions were made related to these changes: 1) For these changes, noting that they are a simple typographical change in the rationale would suffice; 2) adding another column to show “impact/no impact on applicants/application process” o AGB in html version: https://newgtldprogram-2026-agb.icann.org/en/2-preamble.html o A request was made for the AGB version # to be tracked thoroughly and to be placed or shown in a more prominent space. * Outcome: The Change Log has been created in the wiki page<https://icann-community.atlassian.net/wiki/x/LIC9Lg>. * Action Item: GDS Staff to share the current typographical changes file with the SPIRT after the call. 1. Issue Submission Methodology * Per the SPIRT Charter<https://gnso.icann.org/sites/default/files/policy/2025/draft/version2point0…>, issues can be forwarded to ICANN org by the ICANN Board or the GNSO Council. ICANN org may also refer an issue to itself but SPIRT cannot directly refer an issue to itself; however, for those circumstances where a SPIRT member may encounter an issue and want to bring it forward for discussion, a quick and easy form has been prepared for the members to utilize which can be found in the procedures form below. The form will be shared with the SPIRT via the mailing list separately at a later date. * Procedures for the SPIRT Issue Consideration Process is as follows: https://docs.google.com/document/d/1zITIUCB5yvjV_Rj5Z87ljyqajA5VliMSPvPb77A… * This procedures document will also be shared with the SPIRT members via the mailing list, requesting feedback on the draft. * A suggestion was made that Step #6 in the process should be "The GNSO council refers the issue to ICANN Org" and not to both "SPIRT and ICANN Org” – this item will be revisted by the LT/Staff when reviewing and considering all comments from the SPIRT members. * Outcome: A SPIRT Issue Consideration Process draft<https://docs.google.com/document/d/1zITIUCB5yvjV_Rj5Z87ljyqajA5VliMSPvPb77A…> has been created – including a google request form – for review to address those situations where a SPIRT member may have identified issues for the New gTLD Program. * Action Items: 1) GNSO Support Staff to circulate the SPIRT procedures draft with the SPIRT Members after the call; 2) SPIRT Members to review the process document and provide input for leadership team’s consideration and finalization. 4. ICANN Org Update o RSP Update on the list being published on 30 January, which will include organizations that have cleared evaluation and organizations that have cleared some, but not all, of the technical evaluations. – See Blog here: https://www.icann.org/en/blogs/details/upcoming-publication-of-2026-round-l… o This update was also sent to the SPIRT’s mailing list (gnso-spirt(a)icann.org<mailto:gnso-spirt@icann.org>) and the email archives can be found here: https://lists.icann.org/hyperkitty/list/gnso-spirt@icann.org/ 5. Upcoming Meeting * SPIRT Meetings are to take place every other week per agreement; No planned meetings during ICANN85 in Mumbai. * Ad hoc meetings can arise at any time. * Next Meeting: 12 February 2026 (Time to be reconfirmed). * Outcomes: 1) SPIRT Meetings are to take place every other week; 2) No planned meetings during ICANN85 in Mumbai; 3) Next meeting will be on 12 February 2026 (Time to be reconfirmed). 1. AOB * N/A From: Andrew Chen via Gnso-spirt <gnso-spirt(a)icann.org> Reply-To: Andrew Chen <andrew.chen(a)icann.org> Date: Wednesday, January 28, 2026 at 5:00 PM To: Jeff Neuman via Gnso-spirt <gnso-spirt(a)icann.org> Subject: [Gnso-spirt] [SPIRT] AGENDA | SPIRT Meeting #3 | 29 January 2026 at 13:00 UTC Dear SPIRT Members, Please find below the proposed agenda for the Standing Predictability Implementation Review Team (SPIRT) meeting #3 on 29 January 2026 at 13:00 UTC. Agenda: 1. Welcome and SOIs/SOPs 2. Review of Change Log Wiki 3. Issue Submission Methodology 4. ICANN org Update 5. Upcoming Meeting 6. AOB We would like to remind participants that to ensure transparency of participation in ICANN's multistakeholder model, we ask that you sign in to Zoom sessions using your full name. For example, First Name and Last Name or Surname. You may be removed from the session if you do not sign in using your full name. Please do not hesitate to contact us should you have any questions. Sincerely, Andrew -- Andrew Chen Policy Development Support Sr. Specialist, Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org/ Microsoft Teams: atchen122

2 1

[SPIRT] AGENDA | SPIRT Meeting #3 | 29 January 2026 at 13:00 UTC
by Andrew Chen Jan. 29, 2026

Jan. 29, 2026

Dear SPIRT Members, Please find below the proposed agenda for the Standing Predictability Implementation Review Team (SPIRT) meeting #3 on 29 January 2026 at 13:00 UTC. Agenda: 1. Welcome and SOIs/SOPs 2. Review of Change Log Wiki 3. Issue Submission Methodology 4. ICANN org Update 5. Upcoming Meeting 6. AOB We would like to remind participants that to ensure transparency of participation in ICANN's multistakeholder model, we ask that you sign in to Zoom sessions using your full name. For example, First Name and Last Name or Surname. You may be removed from the session if you do not sign in using your full name. Please do not hesitate to contact us should you have any questions. Sincerely, Andrew -- Andrew Chen Policy Development Support Sr. Specialist, Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org/ Microsoft Teams: atchen122

2 1

Re: [Ext] Re: Update on the list of evaluated Registry Service Providers (RSPs)
by Jared Erwin Jan. 27, 2026

Jan. 27, 2026

Dear Jeff, Yes, the list will be published on 30 January as previously communicated. As noted below: “The published list of evaluated RSPs will include the status of applications for MAIN, DNS, DNSSEC, PROXY, and IDN Tables that have cleared technical screening and testing, and those that have cleared technical screening but are still in the process of clearing technical testing. Additionally, the IDN Support Level applications that have been successfully evaluated will be included in the list.” The applications (i.e., the responses to the questions in the RSP handbook) for RSP, IDN Services, and additional Registry Services are expected to be published to the list in early March 2026. I hope this helps. Thank you, Jared From: Jeff Neuman <jeff(a)jjnsolutions.com> Date: Monday, January 26, 2026 at 16:38 To: Jared Erwin <jared.erwin(a)icann.org>, "gnso-spirt(a)icann.org" <gnso-spirt(a)icann.org> Subject: [Ext] Re: Update on the list of evaluated Registry Service Providers (RSPs) Jared, I am a little confused by this update. Does this mean that you will be posting the MAIN list on January 31st as previously announced (which already represented over a month delay), but not post other lists until March. Or are you saying that no list will be published in March. If the later, I view this personally as a HUGE problem and really cuts against the whole purpose of having the pre-evaluation process. The time applicants are discussing these issues with RSPs is now. Please clarify. Sincerely, Jeff Sincerely, Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC +1.202.549.5079 Jeff(a)jjnsolutions.com ________________________________ From: Jared Erwin via Gnso-spirt <gnso-spirt(a)icann.org> Sent: Monday, January 26, 2026 7:21:29 PM To: gnso-spirt(a)icann.org <gnso-spirt(a)icann.org> Subject: [Gnso-spirt] Update on the list of evaluated Registry Service Providers (RSPs) Dear SPIRT Members, On behalf of the RSP Program Team, I’m sharing now for your information an update that was sent to RSP applicants today regarding the list of evaluated RSPs. See the communication below: As we work toward opening the 2026 Round of the New Generic Top-Level Domains (gTLD) Program, I would like to share an update about the upcoming 30 January publication of the List of Evaluated Registry Service Providers (RSPs). To complete the evaluation process, RSP applicants must go through two phases of technical evaluation – technical screening and technical testing. The published list of evaluated RSPs will include the status of applications for MAIN, DNS, DNSSEC, PROXY, and IDN Tables that have cleared technical screening and testing, and those that have cleared technical screening but are still in the process of clearing technical testing. Additionally, the IDN Support Level applications that have been successfully evaluated will be included in the list. This comprehensive list will provide the most up-to-date information on the status of RSP applicants for these services as of 28 January 2026, end of day UTC. Due to the complexity of generating reports, ICANN org requires additional time to publish the RSP, IDN Services, and Registry Services applications to the list of evaluated RSPs. These applications are expected to be published in early March 2026. The List of Evaluated RSPs will be updated on an ongoing basis as applicants progress through the evaluation process. ICANN org encourages RSP applicants to complete their technical testing in a timely manner and stands ready to support them as needed. ICANN will also communicate this update to the broader community with an ICANN blog that is planned to be published on 27 January. Thank you, Jared -- Jared Erwin Senior Director, New gTLD Program Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) jared.erwin(a)icann.org<mailto:jared.erwin@icann.org>

2 1

Update on the list of evaluated Registry Service Providers (RSPs)
by Jared Erwin Jan. 27, 2026

Jan. 27, 2026

Dear SPIRT Members, On behalf of the RSP Program Team, I’m sharing now for your information an update that was sent to RSP applicants today regarding the list of evaluated RSPs. See the communication below: As we work toward opening the 2026 Round of the New Generic Top-Level Domains (gTLD) Program, I would like to share an update about the upcoming 30 January publication of the List of Evaluated Registry Service Providers (RSPs). To complete the evaluation process, RSP applicants must go through two phases of technical evaluation – technical screening and technical testing. The published list of evaluated RSPs will include the status of applications for MAIN, DNS, DNSSEC, PROXY, and IDN Tables that have cleared technical screening and testing, and those that have cleared technical screening but are still in the process of clearing technical testing. Additionally, the IDN Support Level applications that have been successfully evaluated will be included in the list. This comprehensive list will provide the most up-to-date information on the status of RSP applicants for these services as of 28 January 2026, end of day UTC. Due to the complexity of generating reports, ICANN org requires additional time to publish the RSP, IDN Services, and Registry Services applications to the list of evaluated RSPs. These applications are expected to be published in early March 2026. The List of Evaluated RSPs will be updated on an ongoing basis as applicants progress through the evaluation process. ICANN org encourages RSP applicants to complete their technical testing in a timely manner and stands ready to support them as needed. ICANN will also communicate this update to the broader community with an ICANN blog that is planned to be published on 27 January. Thank you, Jared -- Jared Erwin Senior Director, New gTLD Program Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) jared.erwin(a)icann.org<mailto:jared.erwin@icann.org>

2 1

[SPIRT] AGENDA | SPIRT Meeting #2 | 15 January 2026 at 20:00 UTC
by Andrew Chen Jan. 18, 2026

Jan. 18, 2026

Dear SPIRT Members, Please find below the proposed agenda for the Standing Predictability Implementation Review Team (SPIRT) meeting #2 on 15 January 2026 at 20:00 UTC. Agenda: 1. Welcome and SOIs 2. Statement of Interest (SOI) and Statement of Participation (SOP) Discussion 3. Issue Submission Methodology 4. Upcoming Meeting 5. AOB Please note that the Next Round Team understands there is an interest in the Registry Service Provider (RSP) Evaluation Program and Registry System Testing (RST). While the Next Round Team needs additional time to prepare an update on the RSP Program and RST, the latest statistics can be found here: https://newgtldprogram.icann.org/en/application-rounds/round2/rsp/program-s…. The Next Round Team expects to be able to provide an update in the coming weeks. We would like to remind participants that to ensure transparency of participation in ICANN's multistakeholder model, we ask that you sign in to Zoom sessions using your full name. For example, First Name and Last Name or Surname. You may be removed from the session if you do not sign in using your full name. Please do not hesitate to contact us should you have any questions. Sincerely, Andrew -- Andrew Chen Policy Development Support Sr. Specialist, Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org/ Microsoft Teams: atchen122

4 3

Post Call | Standing Predictability Implementation Review Team (SPIRT) | Thursday, 15 January 2026
by Julie Bisland Jan. 15, 2026

Jan. 15, 2026

Dear all, All recordings for the Standing Predictability Implementation Review Team (SPIRT) call held on Thursday, 15 January 2026 at 20:00 UTC can be found on the agenda wiki page <https://icann-community.atlassian.net/wiki/x/AQAEKQ> . You can also access via the GNSO Calendar 2026<https://gnso.icann.org/en/group-activities/calendar/2026>. Agenda wiki page includes: * Attendance * Audio recording * Zoom recording (including audio, visual, rough transcript, and chat.) * Agenda and Notes/Action Items For additional information, you may consult the mailing list archives<https://lists.icann.org/hyperkitty/list/gnso-spirt@icann.org/> and the main wiki page<https://icann-community.atlassian.net/wiki/x/nwB2HQ>. Thank you. Kind regards, Julie Policy Team Supporting the GNSO

1 0

Notes and Action Items | SPIRT Meeting #2 | 15 January 2026 at 20:00 UTC
by Saewon Lee Jan. 15, 2026

Jan. 15, 2026

Dear SPIRT, A belated Happy New Year to you ALL! Please see the following outcomes, action items, and high-level notes from today’s SPIRT Meeting #2<https://icann-community.atlassian.net/wiki/x/AQAEKQ>. Kind regards, Saewon Key Outcomes, Action Items, and Notes from SPIRT Meeting #2 – Thursday, 15 January 2026 at 20:00 UTC<https://icann-community.atlassian.net/wiki/x/AQAEKQ>. [KEY OUTCOMES] 1. A quick and easy form will be shared with the SPIRT members to fill out if and when an issue needs attention and discussion. The leadership team will consider the issue and share on the mailing list by Friday before or the Monday of the Meeting week. 2. A written internal procedural document will be made and shared with SPIRT. 3. SPIRT Meetings will take place every other week; next meeting will be on 29 January 2026 at 13:00 UTC. [ACTION ITEMS] 1. SPIRT members to update their SOIs, especially focusing on “Section 13. Additional Information,” to disclose association with applicants in the Next Round and/or a party(ies) that may file objections. 2. SPIRT members to fill out a form/checklist when an issue needs attention and consideration by the SPIRT leadership team. 3. LT/Staff to prepare a written internal procedural document and share with SPIRT. [NOTES] * Retrieve slides from here: https://icann-community.atlassian.net/wiki/x/AQAEKQ 1. Welcome and SOIs * Welcome and introduction 1. Statement of Interest (SOI) and Statement of Participation (SOP) Discussion * Per the SPIRT Charter<https://gnso.icann.org/sites/default/files/policy/2025/draft/version2point0…>, all members shall disclose whether they are in any way associated with an application for a new gTLD string in the current round – This includes being an employee, consultant, outside advisor (including legal), or any other association with the applicant, a back-end operator and/or any other service provider in the new gTLD Program. Prior to applications being revealed, the member must only disclose that it is working with one or more applications; provided, however, that after all applications are revealed to the public, the member must specify which applications it is associated with. * Within the SOI, SPIRT members can include this information in “Section 13 (Additional Information)”: The members need to disclose their roles associated to the applicants/New gTLD Program. After reveal day, the details on the association to which application need to be disclosed. * The Statement of Participation (SOP): SPIRT members agree to disclose, on a regular and ongoing basis, whether I am or will be employed by, under contract with, have a financial interest in, or will provide consulting, financial, legal or other services to any new gTLD applicant, objector, or commenter. * The list of members and attached SOIs, the members’ disclosure statement can be found here: https://icann-community.atlassian.net/wiki/x/AQCJHQ * Action Item: SPIRT members to update their SOIs, especially focusing on “Section 13. Additional Information,” to disclose association with applicants in the Next Round and/or a party that may file objections. * Regarding a question on applicants and when they would be recognized as one, the Chair noted that applicant is only an applicant when applied; however, if the intention is to file an application and/or likely to, the disclosure of association is required. * Per the Charter, disclosures shall take place at the beginning of every SPIRT meeting and will be captured on the recording of the meeting. This will be done regularly. Therefore, though it will be tedious, the SPIRT Chair requested all members on the call to disclose such information – There is no need to do this on every call unless there are new members and/or new updates/changes to the SOI/SOP. * As for SOP and disclosure statement, the Chair re-emphasized that the use of “conflict of interest” should be avoided; rather, the members should focus on disclosing their association with applicants and/or a party that may file objections. * Disclosure of SOI/SOP: Check SOIs and updated “Disclosure Statement” column from today’s meeting through the members page here: https://icann-community.atlassian.net/wiki/x/AQCJHQ * Moving forward, only the new members and/or updates/changes will be shared at the beginning of each call. 1. Issue Submission Methodology * Per the SPIRT Charter, issues can be forwarded to ICANN org by the ICANN Bard or the GNSO Council. ICANN org may also refer an issue to itself but SPIRT cannot directly refer an issue to itself; it may have an issue referred to it by the GNSO Council, confer with the GNSO Council if it wishes to request change and determine the change mechanism. In essence, the issue is only dealt with by SPIRT, if the GNSO Council or ICANN org forward the issue to SPIRT. * Therefore, a quick and easy form will be shared with and requested by the SPIRT members at a later date, informing the SPIRT leadership team on the issue for consideration; the SPIRT leadership team will discuss whether it is something ICANN org should bring forward or discuss through the GNSO Council. This form will act as a checklist to ensure any submissions are in scope. If the issue is to be discussed within SPIRT, this form will be translated into and shared on the mailing list by Friday before or Monday of the Meeting week. * It is important to note that all issues forwarded to ICANN org be subject to thoughtful analysis and have an impact beyond a single applicant. * Outcome: A quick and easy form will be shared with the SPIRT members to fill out if and when an issue needs attention and discussion. The leadership team will consider the issue and share on the mailing list by Friday before or the Monday of the Meeting week. * Action Item: SPIRT members to fill out the form when an issue needs attention and consideration by the SPIRT leadership team. * A question was raised on whether there is a time limit to by when the members should respond to the list. The Chair noted that guidelines are stipulated in the SPIRT Charter. For example, per the Charter, it stipulates that “When ICANN org notifies the SPIRT of the type of change considered by ICANN org, the SPIRT shall endeavor to provide guidance, if any, within seven (7) calendar days or as otherwise required to maintain the operation of the Program if it disagreed with the decision. For changes designated as minor operational changes (Type 1), the SPIRT shall review the decision through the Change Log and take no more than three (3) calendar days to provide guidance if it disagrees with the decision.” * Per the Predictability Framework the Change Log will proceed as follows: “ICANN org will document all changes to the Program in a publicly available change log and will set up a publicly archived mailing list for all parties that wish to be notified of Program changes. For non-minor operational changes, ICANN org will inform all applicants directly. Should a change relate to sensitive or security-related issues, information will be redacted as necessary. ICANN org will add any minor operational changes to the Change Log within five business days after implementing it.” * Regarding how any issues from the Council will be brought to SPIRT, especially in urgent cases, the SPIRT Chair asked the Council liaison to the SPIRT (Lawrence Olawale-Roberts) to discuss with the Council on how to proceed in such cases; i.e., resolution, correspondence, etc.? * A written internal procedural doc. will be made for the SPIRT and will be brought bring back to group. * Outcome: A written internal procedural document will be made and shared with SPIRT. * Action Item: LT/Staff to prepare a written internal procedural document and share with SPIRT. 1. Upcoming Meeting * SPIRT Meetings are to take place every other week. * Next Meeting: 29 January 2026 at 13:00 UTC. * Outcomes: 1) SPIRT Meetings are to take place every other week; 2) Next meeting will be on 29 January 2026 at 13:00 UTC. 1. AOB * GDS update on RST: GDS Staff noted that the discussion on list has been acknowledged but there is currently no thorough updates; a written update will be available soon. From: Andrew Chen via Gnso-spirt <gnso-spirt(a)icann.org> Reply-To: Andrew Chen <andrew.chen(a)icann.org> Date: Wednesday, January 14, 2026 at 7:00 PM To: Denise de alcantara-hochbaum via Gnso-spirt <gnso-spirt(a)icann.org> Subject: [Gnso-spirt] [SPIRT] AGENDA | SPIRT Meeting #2 | 15 January 2026 at 20:00 UTC Dear SPIRT Members, Please find below the proposed agenda for the Standing Predictability Implementation Review Team (SPIRT) meeting #2 on 15 January 2026 at 20:00 UTC. Agenda: 1. Welcome and SOIs 2. Statement of Interest (SOI) and Statement of Participation (SOP) Discussion 3. Issue Submission Methodology 4. Upcoming Meeting 5. AOB Please note that the Next Round Team understands there is an interest in the Registry Service Provider (RSP) Evaluation Program and Registry System Testing (RST). While the Next Round Team needs additional time to prepare an update on the RSP Program and RST, the latest statistics can be found here: https://newgtldprogram.icann.org/en/application-rounds/round2/rsp/program-s… [newgtldprogram.icann.org]<https://urldefense.com/v3/__https:/newgtldprogram.icann.org/en/application-…>. The Next Round Team expects to be able to provide an update in the coming weeks. We would like to remind participants that to ensure transparency of participation in ICANN's multistakeholder model, we ask that you sign in to Zoom sessions using your full name. For example, First Name and Last Name or Surname. You may be removed from the session if you do not sign in using your full name. Please do not hesitate to contact us should you have any questions. Sincerely, Andrew -- Andrew Chen Policy Development Support Sr. Specialist, Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org/ Microsoft Teams: atchen122

1 0

Initial Issue for discussion
by Jeff Neuman Jan. 5, 2026

Jan. 5, 2026

All, I wanted to raise a topic for the SPIRT Team’s awareness and discussion regarding the current status of the RSP Evaluation Program, particularly the registry system testing component. As you know, the RSP Handbook (https://newgtldprogram.icann.org/sites/default/files/documents/rsp-handbook…) sets out the published timelines for the program, and implementation has been progressing in line with those materials. The Handbook indicated that the results of the RSP Evaluation program would be posted on December 9, 2025. Recently, ICANN indicated that some challenges had arisen with the system testing environment, which in turn affected the timing for posting the list of successful RSPs. At the Public Forum, in response to a question I raised, ICANN’s CEO suggested that any delay would likely be limited to approximately two weeks. ICANN has since posted an updated date of January 30, 2026 for publication of the results. Although this update was not included in the weekly digest, it appears to reflect an adjustment from the previously published schedule. ICANN has noted that this change should not affect its overall readiness for the planned April 2026 application window. However, from a SPIRT perspective, even relatively small timeline shifts may have implications for applicant readiness and predictability—areas that fall directly within our remit. ICANN has also made available information about ongoing updates to the Registry System Testing Platform (https://www.icann.org/en/contracted-parties/registry-operators/registry-sys…) including a list of “known issues” that are being addressed. It may be helpful for SPIRT to better understand the nature of these issues, the anticipated timeframe for resolution, and whether further downstream impacts to applicants or service providers are expected. Given SPIRT’s role in identifying and elevating potential issues that could affect predictability in the program, this seems like an appropriate matter for us to discuss and monitor. A clearer understanding of the situation would help ensure that both the community and prospective applicants have a realistic sense of what to expect as we approach the next application window. Sincerely, Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC +1.202.549.5079 Jeff(a)jjnsolutions.com

5 7