- Gnso-rdrs-sc - lists.icann.org

Pending Action Item: Review Draft Chapter 4 of the RDRS SC Report
by Sebastien＠registry.godaddy June 26, 2025

June 26, 2025

Dear RDRS SC Members, Following our recent call on Monday, we are writing to kindly request your review of the draft Chapter 4<https://urldefense.com/v3/__https:/docs.google.com/document/d/1oqXdMgsGltTo…> of the RDRS Standing Committee report. As discussed, this chapter has been developed based on the Standing Committee’s extensive discussions to date, particularly those held during ICANN83, as well as the input you provided in the Assignment Four review document. We understand there have been requests to view the report in a more consolidated format, and we’re pleased to share that staff has now delivered a unified version of all chapters<https://urldefense.com/v3/__https:/docs.google.com/document/d/1oqXdMgsGltTo…> following our last meeting. Tab 1 to 4 reflect the respective draft chapters, Tab 6 in the document includes all relevant links and review documents to date for easier navigation. Additionally, the comparison table from Chapters 3 and 4 has been merged (Tab 5) for easier review and to help provide a more complete view of the recommendations in context. We hope this version supports a more streamlined and effective review process. Going forward, Standing Committee members are kindly asked to make all comments and suggestions directly in the consolidated version of the document. This will ensure that feedback is captured in a single place and that all members can easily track and respond to each other’s input. * Consolidated Document: https://docs.google.com/document/d/1oqXdMgsGltToV_JxDtubedfymvrmvoAH43kssxO…<https://urldefense.com/v3/__https://docs.google.com/document/d/1oqXdMgsGltT…> For now, we kindly ask that you focus your attention on Chapter 4 and consider the following: • Does the draft accurately reflect the discussions and agreements the SC has had to date? • Can we, as a SC, support and recommend the content of this chapter to the GNSO Council? In parallel, the support team is currently working on incorporating all chapters into the official report template, in accordance with the timeline we discussed. Please rest assured that the Standing Committee will have ample time to review and comment on the complete draft in its final format. We fully acknowledge that the current deadline of 30 June may feel tight. However, the content should not be new to the SC, as it stems directly from our prior discussions and deliberations. We aim to see how far we can progress in our next call and will allow additional time for further review following that discussion. Thank you once again for your continued commitment to this effort. We look forward to your feedback on Draft Chapter 4 and to our continued work together in the weeks ahead. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [cid:image001.png@01D81E10.09821660] +49 172 690 8418 Germany sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy>

1 0

2025-06-23 RDRS Standing Committee - Meeting #36
by Feodora Hamza June 26, 2025

June 26, 2025

Dear RDRS SC, Please find below the high-level notes and Action Items today`s meeting. Please also find below the consolidated google document with all draft chapters (4 different tabs) in one document. Documents: * RDRS SC Report- Consolidated Version all draft chapters: https://docs.google.com/document/d/1oqXdMgsGltToV_JxDtubedfymvrmvoAH43kssxO… Action Items: * SC members to review and comment on Chapter 4 by 30 June. Please note: Consensus required for Chapter 4 content (recommendation and rationale). Non-consensus items/suggestions to be deferred to earlier chapters e.g. Chapter 3 lessons learned or Chapter 2 Proposed System Enhancements. * Support Staff to provide a consolidated google document with all draft chapters. The next meeting is scheduled for 30 June at 17:30 UTC. Kind regards, Feodora 2025-06-23 RDRS Standing Committee - Meeting #36<https://icann-community.atlassian.net/wiki/spaces/EOTSFGRD/pages/303562753/…> Documents: * RDRS SC Report- Consolidated Version all Chapters: https://docs.google.com/document/d/1oqXdMgsGltToV_JxDtubedfymvrmvoAH43kssxO… * Slides 23 June: https://docs.google.com/presentation/d/1QQlJf20vUc0BNYcrjneCatlAql7lkizR/ed… * Slides Timeline: https://docs.google.com/presentation/d/1pF8dmdnMSX-1zQwQLajgK7tRGBBkZkCb/ed… Action Items: * SC members to review and comment on Chapter 4 by 30 June. Please note: Consensus required for Chapter 4 content (recommendation and rationale). Non-consensus items/suggestions to be deferred to earlier chapters e.g. Chapter 3 lessons learned or Chapter 2 Proposed System Enhancements. * Support Staff to provide a consolidated google document with all draft chapters. Proposed Agenda: 1. Welcome 2. Presentation of draft Chapter 4 · Support staff began drafting the final chapter of the GNSO Council report based on prior chapters and ICANN 83 discussions. · The chapter begins with scope and reminders that this is advice to the GNSO Council, not binding policy. · Three Main Recommendations: · Continuation of RDRS Beyond Pilot – Recommended to continue RDRS while future policy work proceeds on EPDP Phase 2. · System Enhancements – Top four system improvements include API development, authentication mechanisms (especially for law enforcement), privacy/proxy handling, and RDAP response enhancements. · Reassessment of EPDP Phase 2 Recommendations – Review each of the 18 recommendations individually for suitability or modification. • A table summarizing these assessments includes: • Recommendation number. • Function/title. • Proposed treatment (“Keep,” “Modify,” etc.). • Rationale (requires consensus). • Draft conclusions. · Next Steps: 1. SC members to provide comments and suggestions by 30 June. 2. Document compilation planned for early July, final report for review by early August. 1. Discussion on draft Chapter 4 * Main Discussion Points: * SC members noted that since RDRS is not policy and not mandatory, the ICANN Board can implement it without new policy. * SC members noted RDRS could become a more cost-effective version of SSAD. Suggested reinterpretation of original EPDP recommendations to fit RDRS. * SC members voiced recurring concern about centralized architecture (ICANN as intermediary). Offered to provide more background proposing a more distributed approach and share them via mailing list. * SC members requested changes to EPDP Phase 2 Recommendation 5 rationale. * SC members queried the suggestion (RDRS SC Rec 2.3) for more policy work. Argued that affiliated proxies are already handled by registrars. * SC members agreed clarification needed and suggested language should encourage voluntary action and avoid implying policy change. * SC members noted that a dedicated recommendation to Council should be made regarding financial sustainability of the system. * Consensus required for Chapter 4 content. Non-consensus items to be deferred to earlier chapters. * Final reminder to provide detailed, constructive feedback within the document that can reach consensus. * SC members requested that all chapters be merged into a single, navigable document to facilitate comprehensive review. 1. AOB * SC Chair shared ideal timeline and milestones * 30 June: Deadline for Chapter 4 comments. * Early July: Staff compiles full report. * Mid July to August: SC reviews full draft and conducts consensus call. * Mid-September: Review of public comment received. * October: Submit report to GNSO Council.

3 3

Post call | RDRS Standing Committee | Monday, 23 June 2025
by Julie Bisland June 23, 2025

June 23, 2025

Dear all, The recordings for the RDRS Standing Committee call held on Monday, 23 June 2025 can be found on the agenda wiki page <https://icann-community.atlassian.net/wiki/x/AQAYEg> and the GNSO Master Calendar<https://gnso.icann.org/en/group-activities/calendar/2025>. These include: * Attendance (please let us know if your name has been left off the attendance list) * Audio recording * Zoom recording (including audio, visual, rough transcript, chat archive) * Presentation displayed during the meeting (if applicable) * Agenda and Notes/Action Items (if applicable) For additional information, you may consult the mailing list archives<https://urldefense.com/v3/__https:/lists.icann.org/hyperkitty/list/gnso-rdr…> and the main wiki page<https://community.icann.org/x/HgH8E>. Thank you! Kind regards, Julie Policy Team Supporting the GNSO

1 0

Meeting Invitation | RDRS Standing Committee | Monday, 30 June 2025
by Julie Bisland June 23, 2025

June 23, 2025

Dear all, The next RDRS Standing Committee call is scheduled for Monday, 30 June 2025 at 17:30 UTC for 60 minutes. To join - Zoom Information: Main Zoom Webinar link: https://icann.zoom.us/j/92181477886?pwd=TlJHTU5EY1d3bUxLV2s3UStPS2MxZz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/92181477886?pwd=TlJHTU5E…> Passcode: Z@S07?t=v5 Audio only option: Webinar ID: 921 8147 7886 Passcode: 3121016458 International numbers available: https://icann.zoom.us/u/acS1yc2A1 <https://urldefense.com/v3/__https:/icann.zoom.us/u/acS1yc2A1__;!!PtGJab4!9A…> Members, alternates, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send apologies 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…> and the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…> * Wiki agenda page: https://icann-community.atlassian.net/wiki/x/DQAYEg * Check your time zone: https://tinyurl.com/2zc4meky ONLY for Members & Alternates * Please join via the above Zoom Webinar link and staff will promote you to panelist. * Please select “ Everyone” when posting to the chat for everyone to see your chat and so it’s captured in the recording. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Julie Policy Team Supporting the GNSO

1 0

Report chapter consolidation
by Sarah Wyld June 23, 2025

June 23, 2025

Hello team, I am writing to further track my request that the consolidated report with all chapters be provided ASAP. I note also that there are many open questions in the earlier chapters which need to be completed before we can complete chapter 4. Thank you, -- *Sarah Wyld, CIPP/E* Pronouns: she/they Head, Policy & Privacy Tucows #MakingTheInternetBetter swyld(a)tucows.com /Responses to this email are processed according to the Tucows Privacy Policy <https://www.tucows.com/privacy>/

1 0

**1-MINUTE REMINDER** Meeting Invitation | RDRS Standing Committee | Monday, 23 June 2025
by Julie Bisland June 23, 2025

June 23, 2025

Dear all, The next RDRS Standing Committee call is scheduled for Monday, 23 June 2025 at 17:30 UTC for 60 minutes. To join - Zoom Information: Main Zoom Webinar link: https://icann.zoom.us/j/92181477886?pwd=TlJHTU5EY1d3bUxLV2s3UStPS2MxZz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/92181477886?pwd=TlJHTU5E…> Passcode: Z@S07?t=v5 Audio only option: Webinar ID: 921 8147 7886 Passcode: 3121016458 International numbers available: https://icann.zoom.us/u/acS1yc2A1 <https://urldefense.com/v3/__https:/icann.zoom.us/u/acS1yc2A1__;!!PtGJab4!9A…> Members, alternates, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send apologies 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…> and the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…> * Wiki agenda page: https://icann-community.atlassian.net/wiki/x/AQAYEg * Check your time zone: https://tinyurl.com/29yfk57t ONLY for Members & Alternates * Please join via the above Zoom Webinar link and staff will promote you to panelist. * Please select “ Everyone” when posting to the chat for everyone to see your chat and so it’s captured in the recording. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Julie Policy Team Supporting the GNSO

1 0

**15-MINUTE REMINDER** Meeting Invitation | RDRS Standing Committee | Monday, 23 June 2025
by Julie Bisland June 23, 2025

June 23, 2025

**15-MINUTE REMINDER** Dear all, The next RDRS Standing Committee call is scheduled for Monday, 23 June 2025 at 17:30 UTC for 60 minutes. To join - Zoom Information: Main Zoom Webinar link: https://icann.zoom.us/j/92181477886?pwd=TlJHTU5EY1d3bUxLV2s3UStPS2MxZz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/92181477886?pwd=TlJHTU5E…> Passcode: Z@S07?t=v5 Audio only option: Webinar ID: 921 8147 7886 Passcode: 3121016458 International numbers available: https://icann.zoom.us/u/acS1yc2A1 <https://urldefense.com/v3/__https:/icann.zoom.us/u/acS1yc2A1__;!!PtGJab4!9A…> Members, alternates, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send apologies 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…> and the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…> * Wiki agenda page: https://icann-community.atlassian.net/wiki/x/AQAYEg * Check your time zone: https://tinyurl.com/29yfk57t ONLY for Members & Alternates * Please join via the above Zoom Webinar link and staff will promote you to panelist. * Please select “ Everyone” when posting to the chat for everyone to see your chat and so it’s captured in the recording. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Julie Policy Team Supporting the GNSO

1 0

Meeting Invitation | RDRS Standing Committee | Monday, 23 June 2025
by Julie Bisland June 20, 2025

June 20, 2025

Please note: The next meetings of the RDRS Standing Committee will take place during ICANN83. The agenda pages can be found here: Session 1, 9 June: https://icann-community.atlassian.net/wiki/x/DABoD Session 2, 10 June: https://icann-community.atlassian.net/wiki/x/AYBoD Below (and attached) is the join information for the next (23 June) meeting of the RDRS SC after ICANN83. ********************** Dear all, The next RDRS Standing Committee call is scheduled for Monday, 23 June 2025 at 17:30 UTC for 60 minutes. To join - Zoom Information: Main Zoom Webinar link: https://icann.zoom.us/j/92181477886?pwd=TlJHTU5EY1d3bUxLV2s3UStPS2MxZz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/92181477886?pwd=TlJHTU5E…> Passcode: Z@S07?t=v5 Audio only option: Webinar ID: 921 8147 7886 Passcode: 3121016458 International numbers available: https://icann.zoom.us/u/acS1yc2A1 <https://urldefense.com/v3/__https:/icann.zoom.us/u/acS1yc2A1__;!!PtGJab4!9A…> Members, alternates, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send apologies 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…> and the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…> * Wiki agenda page: https://icann-community.atlassian.net/wiki/x/AQAYEg * Check your time zone: https://tinyurl.com/29yfk57t ONLY for Members & Alternates * Please join via the above Zoom Webinar link and staff will promote you to panelist. * Please select “ Everyone” when posting to the chat for everyone to see your chat and so it’s captured in the recording. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Julie Policy Team Supporting the GNSO

2 1

Proposed Agenda for RDRS SC Call 23 June
by Feodora Hamza June 18, 2025

June 18, 2025

Dear RDRS SC, Please find below the proposed agenda for our next call taking place on 23 June at 17:30 UTC. RDRS SC Agenda 23 June 1. Welcome 2. Presentation of draft Chapter 4 3. Discussion on draft Chapter 4 4. AOB Kind regards, Feodora Hamza Policy Development Support Manager (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +32 496 30 24 15 Email: feodora.hamza(a)icann.org<mailto:feodora.hamza@icann.org> Website: www.icann.org<http://www.icann.org>

1 0

Notes and Action Items RDRS SC Working Sessions ICANN83
by Feodora Hamza June 17, 2025

June 17, 2025

Dear RDRS SC, Please find below the high-level notes and Action Items from the two RDRS sessions at ICANN83. The next meeting is scheduled for 23 June at 17:30 UTC. Kind regards, Feodora RDRS SC ICANN83 Sessions June 9 and 10 June Action Items: * Support staff to update draft conclusions<https://docs.google.com/document/d/1NOhKGqMMSypLpEF5rucEb-_Z3-iPb5_q/edit> based on ICANN83 discussion. * SC members to review working documents<https://docs.google.com/document/d/1NOhKGqMMSypLpEF5rucEb-_Z3-iPb5_q/edit> and provide additional comments by June 23. 1. Welcome * SC Chair opened the meeting and gave a brief introduction on the work and background of the RDRS SC. The slides can be found here.<https://icann-community.atlassian.net/wiki/spaces/EOTSFGRD/pages/208142348/…> 1. Working Session on Assignment 4 Discussion Summary: * EPDP Phase 2 - Recommendation 3: Criteria and Content of Requests · Proposal: To Recommend reviewing forms by a “focus group” with requesters/responders; perhaps form a Requester Group. · Some SC members noted to maintain standardized form but improve interface and documentation. * EPDP Phase 2 - Recommendation 4: Acknowledgement of Receipt and Relay · Acknowledged functionality works, but: · Not a full ticketing system. · Limited history tracking of request status changes (e.g., expedited to standard). · Suggestion to improve visibility/history of status changes. · Draft Conclusion: Functionality adequate but could benefit from enhancements. * EPDP Phase 2 -Recommendation 5: Response Requirements · Central Gateway Manager not incorporated into RDRS. · Limited explanation options (dropdown menu) may be insufficient. · Law enforcement noted some issues about being redirected away from RDRS. · Remove “auto-reject” from draft conclusion. · Explicitly note that some SSAD concepts (gateway manager) were not piloted. · Suggestion for requester-responder communication feature in RDRS. * EPDP Phase 2 - Recommendation 6: Priority Levels · Current Priority levels don’t “make sense” anymore. · Suggestion to list technical and policy prerequisites for urgent processing. · SC members noted for this recommendation to enumerate the features that would be needed to potentially handle urgent request. · SC member noted for authentication for groups other than law enforcement, LEA authentication should be prioritized, but there should be a lightweight authentication for other requestors. * EPDP Phase 2 - Recommendation 9: Automation · RDRS does not offer automation features. * EPDP Phase 2 - Recommendation 12: Disclosure Requirements · Concerns around registrars disclosing data beyond request scope. · Need for clarity in final recommendation language. · SC members noted need to look at the recommendation as a whole. * EPDP Phase 2 - Recommendation 17: Reporting Requirements · SC members noted the current RDRS are very helpful. · Some SC members noted for further metric improvements, especially around requester accountability. * EPDP Phase 2 - Recommendation 7 – Request Purpose Requirement · Request form requires requesters to identify the issue and purpose using a mandatory field and dropdown. · Some noted the GDPR-centric language. · Discussion acknowledged need for training and better user guidance. * EPDP Phase 2 - Recommendation 11 – Terms and Conditions · No further comment. * EPDP Phase 2 - Recommendation 13 – Query Policy · Concerns about assumptions equating high request volume with abuse. · Review the original Recommendation text as a whole. * EPDP Phase 2 - Recommendation 15 – Logging Requirements · RDRS logs certain data · No user-level logs currently · Differentiation of logging purposes (accountability, statistics, debugging, transparency) * EPDP Phase 2 - Recommendation 18 - Standing Committee · The current RDRS Standing Committee functions well but differs from the SSAD’s envisioned permanent review mechanism. · Partial alignment; recommendation should be retained with understanding it applies to future governance. * Other Discussion Points: · Participants see potential in RDRS but hesitant to invest further unless it's confirmed as permanent. · API development highlighted as critical to system usefulness and integration. · Standardized forms, improved interface, and better user feedback were named as other important system enhancements. · Discussion on whether RDRS will evolve into a final system or be replaced. * Timeline and Next Steps · Notes and updated draft conclusions from both sessions to be compiled. · July goal: Final review of full report by Standing Committee. · Strong emphasis placed on completing the report by July to maintain alignment with the 2-year pilot timeframe. 3. AOB

1 0