May 2026 - Gnso-ssad - lists.icann.org

SSAD SRT - Implementation Guidance and MUST
by Anderson, Marc June 2, 2026

June 2, 2026

Dear SSAD SRT Members, During this week's meeting, a question was raised by Anne regarding the use of MUST within implementation guidance. The EPDP working group considered this and included the following in the EPDP Phase 2 Final Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phas…> (section 3.4 - page 16), "Where Implementation Guidance is referenced, the EPDP Team considers this supplemental context and/or clarifying information to help inform the implementation of the policy recommendations but the EPDP Team notes that implementation guidance does not have the same weight and standing as recommendation text to create policy." Generally speaking, when a Working Group or EPDP team provides Implementation Guidance, the group is recommending the stated action, and there is a presumption that it will be implemented. Because Implementation Guidance is not the same as a policy recommendation, however, ICANN org, in consultation with the IRT, has the flexibility to deviate from the implementation guidance so long as the alternative course is transparently described, has been carefully considered, and a rationale for any deviation is provided. With respect to SSAD supplemental recommendations specifically, if the SSAD SRT believes an instance of MUST should be changed to SHOULD or MAY, that is something the group can consider when modifying the SSAD recommendations. Thank you, Marc Anderson

3 3

Notes and Action Items: SSAD Supplemental Recommendations Team Meeting #3 - 27 May 2026
by Andrew Chen May 28, 2026

May 28, 2026

Dear SSAD Supplemental Recommendations Team Members, Below, please find action items and high-level notes from yesterday’s meeting. Best regards, Andrew on behalf of the GNSO Support Team Action Items: * All members are to closely review the reading materials highlighted in the Straw Document - including the original recommendation, the modified recommendation, the Standing Committee’s Report, the Board’s resolution, etc. * Groups to coordinate ahead of ICANN86 so that we can hear reactions from groups rather than individuals. Reading Materials for Day 0 and ICANN86 meetings: * Reading materials have been linked below. For ease of reference, the pages associated with the recommendation have been added. Please note that this is not an exhaustive list, please see the Assignment Form<https://gnso.icann.org/sites/default/files/policy/2026/agenda/gnso-council-…> for additional documents. * Recommendation 1 (Authentication) * RDRS Standing Committee Report<https://gnso.icann.org/sites/default/files/policy/2025/draft/rdrs-sc-findin…> - pages 13 and 35 * Registration Data Request Service Policy Alignment Analysis<https://itp.cdn.icann.org/en/files/registration-data-request-service-rdrs/r…> - page 12 * SSAD ODA<https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf> - pages 23-30 and 56-59 * Recommendation 2 (Accreditation of Governmental Entities) * RDRS Standing Committee Report<https://gnso.icann.org/sites/default/files/policy/2025/draft/rdrs-sc-findin…> - pages 14 and 35 * Registration Data Request Service Policy Alignment Analysis<https://itp.cdn.icann.org/en/files/registration-data-request-service-rdrs/r…> - page 12 * SSAD ODA<https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf> - pages 23-30 and 56-59 * Recommendation 6 (Priority Levels) * RDRS Standing Committee Report<https://gnso.icann.org/sites/default/files/policy/2025/draft/rdrs-sc-findin…> - pages 18, 37, 62, and 67-68 * Registration Data Request Service Policy Alignment Analysis<https://itp.cdn.icann.org/en/files/registration-data-request-service-rdrs/r…> - page 13 * SSAD ODA<https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf> - pages 65-66 * Recommendation 8 (Contracted Party Authorization) * RDRS Standing Committee Report<https://gnso.icann.org/sites/default/files/policy/2025/draft/rdrs-sc-findin…> - pages 20, 37-38 * SSAD ODA<https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf> - pages 65, 83, 86, 88-89, 95, 102-103 * Recommendation 10 (Determining Variable SLAs for Response Times for SSAD) * RDRS Standing Committee Report<https://gnso.icann.org/sites/default/files/policy/2025/draft/rdrs-sc-findin…> - pages 22 and 38 * Registration Data Request Service Policy Alignment Analysis<https://itp.cdn.icann.org/en/files/registration-data-request-service-rdrs/r…> - page 13 * SSAD ODA<https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf> - pages 21, 46-47, and 65-66 * Reading materials and the pages that members must read in preparation for the Day 0 meeting are also highlighted in the RDRS SC Feedback row of the strawperson document. Upcoming Meetings: * Day 0 in Seville - Sunday, 7 June 2026 10:00 - 18:00 CEST (08:00 - 16:00 UTC) * ICANN86 - Monday, 8 June 2026 10:00 - 11:15 CEST (08:00 - 09:15 UTC) * ICANN86 - Wednesday, 10 June 2026 11:45am - 1:15pm CEST (09:45 - 11:15 UTC) * ICANN86 - Thursday, 11 June 2026 2:45pm - 4:00pm CEST (12:45 - 14:00 UTC) Important Links: * Team Wiki<https://icann-community.atlassian.net/wiki/x/AYB2P> * Strawperson Document<https://docs.google.com/document/d/17N6Y3yYUmbfbAFO6QwR8S1u0uZY0HxKYc8HaadB…> * Assignment Form<https://gnso.icann.org/sites/default/files/policy/2026/agenda/gnso-council-…> High-Level Notes: 1. Welcome * Support Staff noted that SRT Members may participate on the call while Alternates are asked not to participate unless they are temporarily filling in for a Member. * This will be the last meeting before the Day 0 meeting in Seville and ICANN86. 1. Recap of Recommendation 11 Discussion and Working Methodology * Additional page references noting key required reading for recommendations have been added to the grey RDRS SC Feedback section of the strawperson document. * An “SSAD SRT High-Level Flags and Noted Dependencies” row has been added to recommendation 11. This row is for items and dependencies that have been mentioned but may not necessarily belong in recommendation 11. * Two recurring themes were identified and shared with members. * The first noted theme was regarding the handling of SSAD Terms and Conditions violations. The SRT Lead noted Recommendation 11 may not be the appropriate recommendation to address this theme. The SRT Lead assured the group that this theme will continue to be tracked and addressed in future SRT discussions. * The second noted theme was the 18 SSAD recommendations are interconnected and will be revisited when needed. Changes to other recommendations could impact Recommendation 11. * Members noted further discussions may be needed to explore the usage of “MUST” and revisions to Implementation Guidance. 1. Plan for ICANN86 Day 0 Meeting * David Plumb of the Consensus Building Institute introduced himself and noted he will be joining the Day 0 meeting. * David Plumb noted the benefits of in-person interaction and plans for the SRT to participate in breakout sessions during the Day 0 meeting. * David Plumb’s goal is to help members express their key priorities and assist the SRT in finding agreement on a way forward for high level of effort (LOE) recommendations. * The focus of the Day 0 meeting will be Recommendation 1 (Authentication), Recommendation 2 (Accreditation of Governmental Entities), and Recommendation 10 (Service-Level Agreement). * The Lead emphasized the importance of Members preparing for the ICANN86 sessions by completing all of the required reading (see above in the Reading Materials section). In order to make important progress during our time together, everyone must come prepared. * Members are encouraged to ask questions and discuss recommendations on the SRT mailing list. * Members were reminded that the SRT is tasked with modifying recommendations. 1. Overview of Recommendations denoted by Standing Committee as HIGH level of effort to modify * High LOE recommendations were identified by the RDRS Standing Committee. The RDRS Standing Committee noted that these recommendations would require either a considerable amount of edits or would be substantially impacted by revisions. * Recommendation 1 – Accreditation * Support Staff noted that Recommendation 1 was the longest recommendation in the EPDP and would have been costly to implement according to SSAD ODA estimates * Support Staff explained that initial changes to Recommendation 1 were drafted to address potential high cost, confusion over the difference between accreditation, authentication, and authorization, and the necessity of authenticating law enforcement entities as a starting point. * The overarching principles considered when modifying recommendation 1 include: * High estimated cost of accrediting all users may result in a system that is not adoptable or Board ready; * Authentication does not equate to authorization. Registrars must review request to determine if it can authorize the disclosure of the requested data; * Authentication of law enforcement entities is important, particularly to facilitate responses to urgent requests; * Exploration of authentication should begin with law enforcement, but did not mean to restrict other interested requestor constituencies; * What is the minimum viable product and what can achieve consensus. * Support Staff provided a high-level overview of the changes made to Recommendation 1 in the Strawperson document. * Recommendation 2 - Accreditation of Government Entities * Support Staff mentioned that Recommendation 2 originally envisioned a separate accreditation process for government entities seeking access to nonpublic registration data but would have been costly to implement according to the SSAD ODA . * Support Staff noted that accreditation of all government entities as envisioned by Recommendation 2 was likely no longer considered for implementation due to cost and complexity. * Support Staff noted that the RDRS Standing Committee Report advised focusing first on the authentication of law enforcement agents. * Support Staff provided a high-level overview of the changes made to Recommendation 2 in the Strawperson document. * The overarching principles considered when modifying recommendation 2 include: * Authentication of law enforcement entities is important, particularly to facilitate responses to urgent requests; * Exploration of authentication should begin with law enforcement, but did not mean to restrict other interested requestor constituencies. * Recommendation 6 - Priority Levels * Support Staff noted that Recommendation 6 envisioned a system that allowed Requestors to select from three priority levels. * The RDRS pilot did not implement the three priority levels but did allow for Requestors to flag their request as “expedited”. * Support Staff noted that the RDRS Standing Committee supported keeping priority levels and noted that authentication of law enforcement agents is needed to address urgent requests. * Support Staff provided a high-level overview of the changes made to Recommendation 6 in the Strawperson document. * The overarching principles considered when modifying recommendation 6 include: * Criteria to define an urgent request is provided in the recommendation and matches the current definition used in the updated Registration Data Policy; * This recommendation provides the definitional threshold requirements for when access to registration data is needed urgently in response to an imminent threat to life, serious bodily injury, critical infrastructure (online and offline) or child exploitation * Registrars must be able to re-categorize requests due to the short timeline for response, and there needs to be a consequence for repeated abuse of priority levels flag * Recommendation 8 - Contracted Party Authorization * Support Staff noted that Recommendation 8 goes over the requirement for the registrar to review and respond to SSAD requests. * Registrars retain the ultimate authority to approve or deny the request due to the liability associated with disclosure. * Support Staff noted that adjustments to the recommendation may be needed to address confusion around GDPR-specific language * Support Staff provided a high-level overview of the changes made to Recommendation 8 in the Strawperson document. * The overarching principles considered when modifying recommendation 8 include: * Registrar must evaluate disclosure requests in accordance with their local laws. SSAD recommendations cannot impede this * RDRS was a voluntary pilot. The SSAD, including any updates as a result of modified recommendations will be mandatory due to consensus policy recommendations * The recommendation was prescriptive to GDPR * Requestors noted that the inclusion of GDPR-specific language was confusing, particularly because not all requests fall under GDPR. * Recommendation 10 - Service Level Agreements * Support Staff noted that Recommendation 10 covers SLA requirements for Registrars to respond to SSAD requests. * Support Staff noted that binding SLAs were not implemented in the RDRS. The Board has mentioned that the successor system needs enforceable SLAs. * Support Staff provided a high-level overview of the changes made to Recommendation 10 in the Strawperson document. * The overarching principles considered when modifying recommendation 10 include: * Timely responses to disclosure requests are important and provide predictability to registrars and requestors. * SLAs need to balance registrars’ need to carefully consider the request to avoid improper disclosure with requestors’ need for predictability in terms of response time. * The urgent request timeline requires authentication in order to be enforced. * Members were reminded that these initial changes represent a starting point for discussion and are not finalized Supplemental Recommendations. 1. Discussion of Recommendation 17 * Members did not discuss Recommendation 17 during this meeting. * Some members noted that it would be helpful to have a cost analysis for revised recommendation that may be compared to the estimate provided in the SSAD ODA. The SRT should work with org and Board liaisons to understand cost implications and ensure the future system is cost effective. * Some members noted they would like to ensure that authentication is thoroughly and holistically discussed. 1. Recap of Action Items and Agreements * Members to closely review reading materials and the straw document * Groups to coordinate ahead of ICANN86 so we may hear reaction from the group’s perspective rather than individual perspectives 1. AOB * Members asked whether it would be helpful to provide suggested edits, comments, and non-general written input ahead of the Day 0 meeting and ICANN Meeting. It would be appropriate to raise topics on the mailing list. Suggested edits and comments to the straw person document are welcomed ahead of the Day 0 meeting. * When members suggest an edit or comment, they should consider the motivation behind the edit and be prepared to speak to the suggested edit or comment. 1. Next Meeting * Our next meeting will be on Sunday, 7 June 2026 10:00 - 18:00 CEST (08:00 - 16:00 UTC). * The next meeting will be the Day 0 meeting in Seville, Spain.

1 0

Meeting Info | SSAD Supplemental Recommendations Team | ICANN86
by Julie Bisland May 28, 2026

May 28, 2026

Dear all, The next SSAD Supplemental Recommendations Team meeting will take place during ICANN86. See the dates and times below: DAY 0: Sunday, 07 June 2026, 10:00 – 18:00 CEST This meeting is not on the ICANN86 schedule. You will receive an email with the join information 24 hours before the session. #1 of 3<https://icann86.sched.com/event/2NQMo/gnso-ssad-supplemental-recommendation…>-Monday, 08 June 2026, 10:00 – 11:15 CEST #2 of 3<https://icann86.sched.com/event/2NQNH/gnso-ssad-supplemental-recommendation…>-Wednesday, 10 June 2026, 11:45 – 13:15 CEST #3 of 3<https://icann86.sched.com/event/2NQRM/gnso-ssad-supplemental-recommendation…>-Thursday, 11 June 2026, 14:45 – 16:00 CEST The team wiki page, Meeting Recordings tab, also has this information: https://icann-community.atlassian.net/wiki/x/AYB2P ALL: Before joining the call: * Please send apologies and dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> , the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…> and the ICANN Community Participant Code of Conduct<https://www.icann.org/en/system/files/files/adopted-icann-community-partici…>. Thank you. Kind regards, Julie Policy Team Supporting the GNSO

3 5

Post Call | SSAD Supplemental Recommendations Team | Wednesday, 27 May 2026
by Julie Bisland May 28, 2026

May 28, 2026

Dear all, All recordings for the SSAD Supplemental Recommendations Team call held on Wednesday, 27 May 2026 at 21:00 UTC can be found on the small team wiki page <https://icann-community.atlassian.net/wiki/x/AYB2P> . Agenda wiki page includes: * Agenda * Audio recording * Zoom recording (including audio, visual, rough transcript, and chat.) * Attendance For additional information, you may consult the mailing list archives<https://lists.icann.org/hyperkitty/list/gnso-ssad@icann.org/> and the wiki page<https://icann-community.atlassian.net/wiki/x/AYB2P>. Thank you. Kind regards, Julie Policy Team Supporting the GNSO

1 0

Scope of SSAD Team work
by Anne ICANN May 27, 2026

May 27, 2026

Hi Marc, Thank you for confirming that you and staff will work on how Implementation Guidance in the SSAD Recommendations which contain the word, MUST, will be treated as a general rule in our work. I know we don't want to get too far into the details on all the Implementation Guidance so I think we have to discuss a universal replacement for the word "MUST" in Implementation Guidance. A couple of points made in the chat in today's meeting raise questions for me as to process for the Day 0 meeting and the rest of our meetings in Seville. So I raise these for your consideration as to what is in scope. 1. There was a chat suggestion for redefining Urgent Requests, but I note the following from a staff report on the work of the IRT: "However, the IRT did reach agreement on the circumstances to be defined as “Urgent”: Urgent Requests for Lawful Disclosure are limited to circumstances that pose an imminent threat to life, of serious bodily injury, to critical infrastructure, or of child exploitation in cases where disclosure of the data is necessary in combatting or addressing this threat*. *Critical infrastructure refers to the physical and cyber systems that are vital in that their incapacity or destruction would have a debilitating impact on economic security or public safety." 2. I also heard a comment during the meeting that the Team's approach to Authentication should be re-examined and possibly be the subject of a new PDP. I am not at all certain that this is consistent with the Assignment Form but defer to you and staff for further analysis. As I understand our Council process under the Bylaws, our task is to develop Supplemental Policy Recommendations based on the prior SSAD policy work. ( I do understand that questions were raised at the Council level with regard to the Board's expectations regarding matters not specifically covered in the SSAD Recommendations.) My own concern is that the work of this Team ultimately be recognized as an example of improved Organizational Effectiveness in the ICANN realm. Your efforts to regulate scope and anticipate Board readiness issues are very much appreciated. Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso(a)gmail.com

1 0

Proposed Agenda | SSAD Supplemental Recommendations Team | 27 May 2026
by Andrew Chen May 27, 2026

May 27, 2026

Dear SSAD Supplemental Recommendations Team Members, Please find below the proposed agenda for our next meeting on Wednesday, 27 May 2026. Proposed Agenda 1. Welcome and Overview of Agenda 2. Recap of Recommendation 11 discussion and working methodology 3. Plan for ICANN 86 Face-to-Face * Introduction of David Plumb, Consensus Building Institute * Goal of Day 0 Meeting * Recommendations covered 4. Overview of Recommendations denoted by Standing Committee as HIGH level of effort to modify * Recommendation 1 – Accreditation * Recommendation 2 - Accreditation of Gov’t Entities * Recommendation 6 - Priority Levels * Recommendation 8 - Contracted Party Authorization * Recommendation 10 - Service Level Agreements 5. Discussion of Recommendation 17 (Reporting Requirements) 6. Recap of Action Items and Agreements 7. AOB Sincerely, Andrew on behalf of the GNSO Support Team -- Andrew Chen Policy Development Support Sr. Specialist, Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org/

3 5

**15-MINUTE REMINDER** Meeting Invite | SSAD Supplemental Recommendations Team | Wednesday, 27 May 2026
by Julie Bisland May 27, 2026

May 27, 2026

**15-MINUTE REMINDER** Dear all, The next SSAD Supplemental Recommendations Team meeting is scheduled for Wednesday, 27 May 2026 at 21:00 UTC for 90 minutes. (recurring weekly on Tuesdays 12 May – 02 June 2026, one exception 27 May at 21:00 UTC). Join Zoom Room (webinar room has been changed to a regular zoom room): https://icann.zoom.us/j/94379024946?pwd=gb0blhnNZ50pJORTKSVnWTnkILIBCR.1 Passcode:7!&u3WB3PU Meeting ID: 943 7902 4946 Passcode: 8477018167 International numbers available: https://icann.zoom.us/u/abaeiDlpR9 ALL: Before joining the call: * Please send apologies and dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> , the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…> and the ICANN Community Participant Code of Conduct<https://www.icann.org/en/system/files/files/adopted-icann-community-partici…>. * Visit the 2026 Wiki Agenda meeting pages: https://icann-community.atlassian.net/wiki/x/AYB2P Thank you. Kind regards, Julie Policy Team Supporting the GNSO

2 1

REMINDER | Meeting Invite | SSAD Supplemental Recommendations Team | Wednesday, 27 May 2026
by Terri Agnew May 26, 2026

May 26, 2026

Dear all, The next SSAD Supplemental Recommendations Team meeting is scheduled for Wednesday, 27 May 2026 at 21:00 UTC for 90 minutes. (recurring weekly on Tuesdays 12 May – 02 June 2026, one exception 27 May at 21:00 UTC). Join Zoom Room (webinar room has been changed to a regular zoom room): https://icann.zoom.us/j/94379024946?pwd=gb0blhnNZ50pJORTKSVnWTnkILIBCR.1 Passcode:7!&u3WB3PU Meeting ID: 943 7902 4946 Passcode: 8477018167 International numbers available: https://icann.zoom.us/u/abaeiDlpR9 ALL: Before joining the call: * Please send apologies and dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> , the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…> and the ICANN Community Participant Code of Conduct<https://www.icann.org/en/system/files/files/adopted-icann-community-partici…>. * Visit the 2026 Wiki Agenda meeting pages: https://icann-community.atlassian.net/wiki/x/AYB2P Thank you. Kind regards, Julie Policy Team Supporting the GNSO

2 1

Notes and Action Items: SSAD Supplemental Recommendations Team Meeting #2 - 19 May 2026
by Andrew Chen May 19, 2026

May 19, 2026

Dear SSAD Supplemental Recommendations Team Members, Below, please find action items and high-level notes from today’s meeting. Best regards, Andrew on behalf of the GNSO Support Team Action Items: * Members to review recommendations 11 and 17 in the strawperson document<https://docs.google.com/document/d/17N6Y3yYUmbfbAFO6QwR8S1u0uZY0HxKYc8HaadB…> and propose modification and comments in the document by Tuesday, 26 May at 16:00 UTC. * Please reach out to GNSO-Secs (gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>) if you have a different preferred google friendly email that you would like added to the SSAD SRT Google Drive Next Meeting: * The next meeting will not be at the team’s usual time. Our next meeting will be on WEDNESDAY, 27 May at 21:00 UTC. * The meeting time has been changed due to the US Holiday schedule and conflicting meetings that SRT members are a part of. Important Links * SSAD Supplemental Recommendations Team Wiki<https://icann-community.atlassian.net/wiki/x/AYB2P> * Strawperson Document<https://docs.google.com/document/d/17N6Y3yYUmbfbAFO6QwR8S1u0uZY0HxKYc8HaadB…> * Assignment Form<https://gnso.icann.org/sites/default/files/policy/2026/agenda/gnso-council-…> High-Level Notes 1. Welcome * We will be using a standard Zoom room during next week's meeting. Staff ask that those on the call respect the format of the team. * As a reminder, members may speak and chat while alternates and observers are asked to refrain from discussions. Staff may revert back to a webinar format if alternates and observers do not refrain from discussions. 1. Reminder of Assignment * The SRT is tasked with providing supplemental recommendations as outlined in the Assignment Form<https://gnso.icann.org/sites/default/files/policy/2026/agenda/gnso-council-…>. * Members are to consider the RDRS Standing Committee’s analysis, the Board’s feedback, and additional documents mentioned in the Assignment Form when reviewing supplemental recommendations. * Members are to consider if the supplemental recommendations are implementable, acceptable to the GNSO Council, and Board-ready. 1. Presentation of Strawman * The strawperson will be a starting point for discussions and comments. * What has been presented today is not the final version of the recommendation. There will be more opportunities to refine and finalize the supplemental recommendations * Staff noted that in the strawperson document the current SSAD recommendations are in the left-hand column labeled “Current Recommendation” while draft text is in the right-hand column labeled “Revised Recommendation”. The RDRS Standing Committee’s feedback has been added to the top of each recommendation section. Changes to the recommendations will be highlighted in blue in the right-hand column. 1. Presentation of Recommendation 11 Updates and Discussion * Staff noted that the recommendations should not be too vague or too prescriptive. Rather, the recommendations should allow for flexibility and a minimum viable product. * Members discussed their role in updating implementation guidance provided within a recommendation. Members concluded that is within the SRTs remit to update the implementation guidance, though some members highlighted the importance of focusing on the policy recommendation text as a priority. * Members sought clarification on when the Global Public Interest and Human Rights Impact Assessment would be conducted for Supplemental SSAD recommendations. Staff noted that these assessments will be conducted once text is in a stable state. * Members inquired about how implementation related suggestions would be handled. The Lead noted that the group should focus on the development of policy recommendations and should refrain, as much as possible, from raising implementation questions. * Implementation Guidance should be provided if and when it assists in updating implementable policy recommendations, but main focus should be on finding alignment on policy recommendations. * GDS Staff provided an overview of terms and conditions that were implemented during RDRS. Those include: * Terms of Use for Registrars in the Naming Services portal * Terms of Use for Requestors * Terms and Conditions between the Requestor and the Registrar * Members noted that requestors did not experience issues with the Terms and Conditions during the RDRS pilot. * Members noted that requestors have selected the wrong user group or misused the RDRS without corrective action, which may need further discussion when addressing separate, existing SSAD recommendations. Members noted that mentioned issues could be addressed in Recommendation 13. * Members noted that it would be helpful for Staff to add discussion notes to the end of each recommendation. 1. Presentation of Recommendation 17 Updates and Discussion * N/A - Members did not discuss Recommendation 17 during this meeting. 1. Review of Action Items and Agreements * Members to review recommendations 11 and 17 in the strawperson document and propose modification and comments in the document by Tuesday, 26 May at 16:00 UTC. * Members are encouraged to provide their feedback and input on the mailing list and Google document in order to allow for more substantive discussions during the 90-minute meetings. 1. AOB * Members are encouraged to thoroughly review the RDRS Standing Committee report. Staff to consider how to incorporate additional RDRS Standing Committee report information into the strawperson document. * Members noted that they would find an updated financial analysis, similar to the analysis conducted during the SSAD ODA, during the course of the SRT’s work to be helpful to the team’s discussions. 1. Next Meeting * The next meeting will not be at the team’s usual time. Our next meeting will be on WEDNESDAY, 27 May at 21:00 UTC. * The meeting time has been changed due to the US Holiday schedule and conflicting meetings that SRT members are a part of.

1 0

Post Call | SSAD Supplemental Recommendations Team | Tuesday, 19 May 2026
by Julie Bisland May 19, 2026

May 19, 2026

Dear all, All recordings for the SSAD Supplemental Recommendations Team call held on Tuesday, 19 May 2026 at 12:00 UTC can be found on the small team wiki page <https://icann-community.atlassian.net/wiki/x/AYB2P> . Agenda wiki page includes: * Agenda * Audio recording * Zoom recording (including audio, visual, rough transcript, and chat.) * Attendance For additional information, you may consult the mailing list archives<https://lists.icann.org/hyperkitty/list/gnso-ssad@icann.org/> and the wiki page<https://icann-community.atlassian.net/wiki/x/AYB2P>. Thank you. Kind regards, Julie Policy Team Supporting the GNSO

1 0