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

Reminder: Pending Action Items 2025-07-14 RDRS Standing Committee - Meeting #39
by Feodora Hamza July 17, 2025

July 17, 2025

Dear RDRS SC, hope all is well. This is a kind reminder on the pending Action Items from the last meeting. As shared with you yesterday on behalf of the SC Chair, please find below (quote from yesterday`s Email): * (updated) Draft Report: https://docs.google.com/document/d/11RPDqWgI0lcuMDe6OgIjLgmsrpdZZ1Eb/edit?u… * Review Document: https://docs.google.com/document/d/1cZnyjmibAysU4g7rayrHPzISsd_sIDhH/edit<https://urldefense.com/v3/__https:/docs.google.com/document/d/1cZnyjmibAysU…> Please note: To streamline the process and ensure all input is captured consistently, the current working document - the “consolidated version”- is now closed for comments. This is to avoid duplication or fragmentation of feedback. From this point forward, we ask that the SC focuses exclusively on reviewing the updated version. Commenting Procedure Moving Forward * As we approach the finish line, we are also adjusting the comment process. SC members will now have “comment-only” access to the document rather than editing rights. This helps staff better track outstanding issues and prioritise them for SC discussion. * As done in the past with other WGs, we are asking SC members to focus on three types of comments: • Text you cannot live with • Text you can live with but think needs clarification • Any grammatical or formatting errors * To support this, staff has prepared an overview/exercise document to help organise your input. Pending Comments from the previous draft are already included in the review document. That said, we understand this format may not work for everyone, so you’re welcome to either comment directly in the report (as comment) or use the review sheet. Staff will ensure all comments are collected and included. * When providing comments, please include a clear rationale and proposed alternative text. This is crucial to help staff fully understand your concern and to support us in drafting language that accurately reflects SC consensus. * For example, if you cannot live with a particular phrase, please explain why and offer a suggestion for what would be acceptable. This clarity is key for constructive progress. Kind regards, Feodora on behalf of the support team From: Feodora Hamza <feodora.hamza(a)icann.org> Date: Tuesday, 15 July 2025 at 21:15 To: "gnso-rdrs-sc(a)icann.org" <gnso-rdrs-sc(a)icann.org> Subject: 2025-07-14 RDRS Standing Committee - Meeting #39 Dear RDRS SC, Please find below the high-level meeting minutes and Action Items from the last meeting. The next meeting is scheduled for 21 July 2025 at 17:30 UTC. Kind regards, Feodora and Caitlin 2025-07-14 RDRS Standing Committee - Meeting #39<https://icann-community.atlassian.net/wiki/spaces/EOTSFGRD/pages/303562777/…> Action Items: Responsible Item Due Support Staff Final draft report in ICANN format to be shared with SC By 17 July Support Staff Share comments review sheet with SC with instructions By 17 July All members Review final draft and submit comments (color-coded) By 21 July Mark Anderson/ Gabriel Andrews Propose revised language for Rec 3.2 (display guidance) 21 July Mark Anderson Draft updated text for Rec 6 on what to do with SSAD Recs/Council Action 21 July Support Staff Standardize reporting timeframe across document (use June 2025) Before publication Gabriel Andrews Additional Language in Lessons Learned regarding experience w P/P. 21 July Gabriel Andrews Review and provide additional Language to Recommendation 4. 21 July Support Staff Lock working doc and provide comment-only version of final draft 17 July · Members are asked to provide comments to the final draft by 21 July (first deadline). · Comment types are categorized into: · “Cannot live with” (red table) · “Can live with BUT Needs clarification” (orange table) · “Editorial/grammatical correction” (blue table) · Support Staff will manage comment consolidation and track discussion items via a centralized spreadsheet. · SC to comment directly into the draft report or the exercise sheet. SC will go through the comments in the exercise sheet for easier tracking and overview. · SC to provide clear rationale on why they “cannot live with” a statement or parts of the document and provide new language they can live with. Proposed Agenda 1. Welcome · The SC Chair opened the meeting. · Emphasis was placed on ensuring that Support Staff had everything necessary to finalize the draft report. · The goal was to move through open questions efficiently. · The goal is for the final document to be made available for public comment in mid-August, pending SC progress. 1. Continue Discussion of documented concerns from Draft Chapter 4 · Rec. 3.1 (Privacy/Proxy Data) · Support Staff reviewed the proposed language regarding further policy work on privacy/proxy services within RDRS. · Discussion centered on the vagueness and potential duplicative nature of recommending “further policy work.” There was broad recognition of issues around registrar-affiliated proxy services, their impact on disclosure, and the challenges posed for requesters such as public safety officials. · SC members supported the bracketed clarification but expressed strong concern with recommending policy work already being explored elsewhere, or which might contradict other frameworks. · Other SC members supported the idea of policy work on consistent disclosure practices for affiliated proxy providers. · SC members expressed frustration of requesters when privacy/proxy data is returned in response to lawful requests. · SC members proposed revised wording: “The Subcommittee recommends further policy work be considered on the lawful release of privacy/proxy data for privacy/proxy providers affiliated with registrars.” Action Item: · General agreement emerged to remove mention of the RDRS and focus instead on privacy/proxy disclosure consistency. · The concerns raised by some SC members with P/P to be included in lessons learned. Gabe to provide updated language. · Rec. 3.2 (Inclusion of RDRS links in RDAP responses) · Support Staff referenced a comment regarding the suggestion to include RDRS links in RDAP responses. · The group discussed the appropriateness of including RDRS references in RDAP responses. Action Item: Marc and Gabe to provide new language to update the recommendation based on SC discussion. · Rec. 4 (Authentication) - updated text, which incorporates feedback from 7 July meeting and Rec. 5 (Financial Sustainability) - updated text, which incorporates feedback from 30 June and 7 July meeting · Recommendation 4: · New draft introduced to separate partial authentication from broader enhancement recommendations. · SC members sought clarity from ICANN Org on how they would interpret and implement the recommendation. · Support Staff noted ICANN is working closely with the Public Safety Working Group (PSWG) on short- and long-term authentication solutions. · Recommendation 5: · Revised language aimed at providing middle ground on financial sustainability. · SC members noted that while the initial burden fell on ICANN, the partial authentication model shifts costs to requesters, satisfying much of the original concern. · SC members noted that long-term funding should not come solely from ICANN. · Rec. 6 (Consideration regarding next steps on EPDP Phase 2/SSAD recs. · Support Staff noted that the current draft lacks clear guidance to the GNSO Council on what to do with SSAD recommendations. · One SC member noted that the group consensus appears to be: · The SSAD recommendations should not be adopted as-is. · The SSAD Recommendations should be returned to the GNSO Council for further review and potential modification. · SC members supported retaining the SSAD Recommendations Table but preferred a consolidated version rather than two tables in different chapters. Action Item: Mark to propose draft wording clarifying Council action recommendation/what to do with SSAD Recommendations. 1. Next Steps · Staff delivery of Draft Findings Report · Staff will distribute the complete draft report (in ICANN template format) by Wednesday. · Once distributed, the working document (consolidated version) will be locked (view-only) and all feedback should be directed to the new/official version. (Note: unresolved comments from the consolidated version will be carried over to the accompanying review document for transparency.) · Members are asked to provide comments by 21 July (first deadline). · Comment types are categorized into: · “Cannot live with” (red) · “Can live with BUT Needs clarification” (orange) · “Editorial/grammatical” (blue) · Support Staff will manage comment consolidation and track discussion items via a centralized spreadsheet. · SC to provide clear rationale on why they “cannot live with” with a statement or parts of the document and provide new language they can live with. Action Item: SC to comment directly into the draft report or the exercise sheet. SC will go through the comments in the exercise sheet for easier tracking and overview. 1. AOB

1 0

Post-SC system management?
by Sarah Wyld July 16, 2025

July 16, 2025

Hi team, Thinking about how change requests and suggested enhancements to the RDRS are managed between when the report is published and when whatever it is that the Board decides should be next (without anticipating what that decision will be) goes live. I understand that this Standing Committee's work is complete when the report is published. So who makes those decisions after that? This may be an important topic to speak to in our recommendations? Or it may be already known/decided and I just don't have the info. Thoughts? Thanks! -- *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>/

2 1

Draft Findings Report and Action Items
by Feodora Hamza July 16, 2025

July 16, 2025

Sent on behalf of Sebastien Ducos Dear RDRS SC, Please find below the link to the Draft of the RDRS SC Findings Report. Thank you all for your hard work and constructive feedback in this endeavour. * Draft Report: https://docs.google.com/document/d/11RPDqWgI0lcuMDe6OgIjLgmsrpdZZ1Eb/edit?u… * Review Document: https://docs.google.com/document/d/1cZnyjmibAysU4g7rayrHPzISsd_sIDhH/edit<https://urldefense.com/v3/__https:/docs.google.com/document/d/1cZnyjmibAysU…> Important updates to consider: * The report starts with Assignment 4 (the Recommendations) and goes “backwards” in chapters 4-1. * In limited instances, Support Staff has adjusted text such as introductions, conclusions etc., for consistency, flow, and removal of duplicative text and unnecessary repetitions. However, the substance has not changed. * Support Staff has also included line numbering for easier identification of comments. Tables don’t have line numbers, but can be referenced based on page number and row. * An SC member noted that the table in Chapter 4 could be clearer, particularly in the specific direction of what the SC believes should happen to the SSAD Recommendations. To that end, Support Staff and SC leadership added an extra column with Level of Effort to signal to the Council the anticipated level of policy effort involved in a proposed modification or adjustment. * Support Staff has also updated the comparison table as suggested by Sarah for comprehensiveness and to avoid duplication. * Leadership suggested to include the metrics of Chapter 1 (up to June 2025) in the Annex and has provided additional text in the Assignment 1 Section to explain what the SC did in terms of Metrics review. Please note: To streamline the process and ensure all input is captured consistently, the current working document - the “consolidated version”- will now be closed for comments. This is to avoid duplication or fragmentation of feedback. From this point forward, we ask that the SC focuses exclusively on reviewing the updated version that will be shared mid-week. Commenting Procedure Moving Forward * As we approach the finish line, we are also adjusting the comment process. SC members will now have “comment-only” access to the document rather than editing rights. This helps staff better track outstanding issues and prioritise them for SC discussion. * As done in the past with other WGs, we are asking SC members to focus on three types of comments: • Text you cannot live with • Text you can live with but think needs clarification • Any grammatical or formatting errors * To support this, staff has prepared an overview/exercise document to help organise your input. Pending Comments from the previous draft are already included in the review document. That said, we understand this format may not work for everyone, so you’re welcome to either comment directly in the report (as comment) or use the review sheet. Staff will ensure all comments are collected and included. * When providing comments, please include a clear rationale and proposed alternative text. This is crucial to help staff fully understand your concern and to support us in drafting language that accurately reflects SC consensus. * For example, if you cannot live with a particular phrase, please explain why and offer a suggestion for what would be acceptable. This clarity is key for constructive progress. Please note, the SC input is essential not just to improve the report, but also to keep the SC’s work on track. The SC is operating on a tight timeline, and it’s important that comments are clear, specific, and constructive. This will help the SC move forward efficiently and avoid revisiting the same points. We now have four more weeks to review the report. Based on the current timeline, I plan to take a consensus call the week of 11 August, one week before the public comment period begins. Advance notice will be given if adjustments to that timing are needed. Thank you all again for getting us to this important milestone. I look forward to continuing this work with you and bringing it to a close when the time is ready. Regards, Sebastien Ducos

1 0

Re: The June RDRS Usage Metrics Report is Published
by Lisa Carter July 15, 2025

July 15, 2025

Hello Standing Committee Members, ICANN has published the June RDRS Usage Metrics Report: July 2025 (Reporting period: 1 June – 30 June 2025) [PDF] [CSV] [CSV 18] [CSV 19] Best, Lisa Carter Sr. Program Manager, Strategic Initiatives ICANN

1 0

2025-07-14 RDRS Standing Committee - Meeting #39
by Feodora Hamza July 15, 2025

July 15, 2025

Dear RDRS SC, Please find below the high-level meeting minutes and Action Items from the last meeting. The next meeting is scheduled for 21 July 2025 at 17:30 UTC. Kind regards, Feodora and Caitlin 2025-07-14 RDRS Standing Committee - Meeting #39<https://icann-community.atlassian.net/wiki/spaces/EOTSFGRD/pages/303562777/…> Action Items: Responsible Item Due Support Staff Final draft report in ICANN format to be shared with SC By 17 July Support Staff Share comments review sheet with SC with instructions By 17 July All members Review final draft and submit comments (color-coded) By 21 July Mark Anderson/ Gabriel Andrews Propose revised language for Rec 3.2 (display guidance) 21 July Mark Anderson Draft updated text for Rec 6 on what to do with SSAD Recs/Council Action 21 July Support Staff Standardize reporting timeframe across document (use June 2025) Before publication Gabriel Andrews Additional Language in Lessons Learned regarding experience w P/P. 21 July Gabriel Andrews Review and provide additional Language to Recommendation 4. 21 July Support Staff Lock working doc and provide comment-only version of final draft 17 July · Members are asked to provide comments to the final draft by 21 July (first deadline). · Comment types are categorized into: · “Cannot live with” (red table) · “Can live with BUT Needs clarification” (orange table) · “Editorial/grammatical correction” (blue table) · Support Staff will manage comment consolidation and track discussion items via a centralized spreadsheet. · SC to comment directly into the draft report or the exercise sheet. SC will go through the comments in the exercise sheet for easier tracking and overview. · SC to provide clear rationale on why they “cannot live with” a statement or parts of the document and provide new language they can live with. Proposed Agenda 1. Welcome · The SC Chair opened the meeting. · Emphasis was placed on ensuring that Support Staff had everything necessary to finalize the draft report. · The goal was to move through open questions efficiently. · The goal is for the final document to be made available for public comment in mid-August, pending SC progress. 1. Continue Discussion of documented concerns from Draft Chapter 4 · Rec. 3.1 (Privacy/Proxy Data) · Support Staff reviewed the proposed language regarding further policy work on privacy/proxy services within RDRS. · Discussion centered on the vagueness and potential duplicative nature of recommending “further policy work.” There was broad recognition of issues around registrar-affiliated proxy services, their impact on disclosure, and the challenges posed for requesters such as public safety officials. · SC members supported the bracketed clarification but expressed strong concern with recommending policy work already being explored elsewhere, or which might contradict other frameworks. · Other SC members supported the idea of policy work on consistent disclosure practices for affiliated proxy providers. · SC members expressed frustration of requesters when privacy/proxy data is returned in response to lawful requests. · SC members proposed revised wording: “The Subcommittee recommends further policy work be considered on the lawful release of privacy/proxy data for privacy/proxy providers affiliated with registrars.” Action Item: · General agreement emerged to remove mention of the RDRS and focus instead on privacy/proxy disclosure consistency. · The concerns raised by some SC members with P/P to be included in lessons learned. Gabe to provide updated language. · Rec. 3.2 (Inclusion of RDRS links in RDAP responses) · Support Staff referenced a comment regarding the suggestion to include RDRS links in RDAP responses. · The group discussed the appropriateness of including RDRS references in RDAP responses. Action Item: Marc and Gabe to provide new language to update the recommendation based on SC discussion. · Rec. 4 (Authentication) - updated text, which incorporates feedback from 7 July meeting and Rec. 5 (Financial Sustainability) - updated text, which incorporates feedback from 30 June and 7 July meeting · Recommendation 4: · New draft introduced to separate partial authentication from broader enhancement recommendations. · SC members sought clarity from ICANN Org on how they would interpret and implement the recommendation. · Support Staff noted ICANN is working closely with the Public Safety Working Group (PSWG) on short- and long-term authentication solutions. · Recommendation 5: · Revised language aimed at providing middle ground on financial sustainability. · SC members noted that while the initial burden fell on ICANN, the partial authentication model shifts costs to requesters, satisfying much of the original concern. · SC members noted that long-term funding should not come solely from ICANN. · Rec. 6 (Consideration regarding next steps on EPDP Phase 2/SSAD recs. · Support Staff noted that the current draft lacks clear guidance to the GNSO Council on what to do with SSAD recommendations. · One SC member noted that the group consensus appears to be: · The SSAD recommendations should not be adopted as-is. · The SSAD Recommendations should be returned to the GNSO Council for further review and potential modification. · SC members supported retaining the SSAD Recommendations Table but preferred a consolidated version rather than two tables in different chapters. Action Item: Mark to propose draft wording clarifying Council action recommendation/what to do with SSAD Recommendations. 1. Next Steps · Staff delivery of Draft Findings Report · Staff will distribute the complete draft report (in ICANN template format) by Wednesday. · Once distributed, the working document (consolidated version) will be locked (view-only) and all feedback should be directed to the new/official version. (Note: unresolved comments from the consolidated version will be carried over to the accompanying review document for transparency.) · Members are asked to provide comments by 21 July (first deadline). · Comment types are categorized into: · “Cannot live with” (red) · “Can live with BUT Needs clarification” (orange) · “Editorial/grammatical” (blue) · Support Staff will manage comment consolidation and track discussion items via a centralized spreadsheet. · SC to provide clear rationale on why they “cannot live with” with a statement or parts of the document and provide new language they can live with. Action Item: SC to comment directly into the draft report or the exercise sheet. SC will go through the comments in the exercise sheet for easier tracking and overview. 1. AOB

1 0

Post call | RDRS Standing Committee | Monday, 14 July 2025
by Julie Bisland July 14, 2025

July 14, 2025

Dear all, The recordings for the RDRS Standing Committee call held on Monday, 14 July 2025 can be found on the agenda wiki page <https://icann-community.atlassian.net/wiki/x/GQAYEg> 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, 21 July 2025
by Julie Bisland July 14, 2025

July 14, 2025

Dear all, The next RDRS Standing Committee call is scheduled for Monday, 21 July 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/AQAZEg * Check your time zone: https://tinyurl.com/4mcjxms6 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, 14 July 2025
by Julie Bisland July 14, 2025

July 14, 2025

**15-MINUTE REMINDER** Dear all, The next RDRS Standing Committee call is scheduled for Monday, 14 July 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/GQAYEg * Check your time zone: https://tinyurl.com/yzjkv7ux 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

**REMINDER** Meeting Invitation | RDRS Standing Committee | Monday, 14 July 2025
by Julie Bisland July 11, 2025

July 11, 2025

Dear all, The next RDRS Standing Committee call is scheduled for Monday, 14 July 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/GQAYEg * Check your time zone: https://tinyurl.com/yzjkv7ux 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

Proposed agenda - RDRS SC meeting - Monday, 14 July @ 17:30 UTC
by Caitlin Tubergen July 10, 2025

July 10, 2025

Dear RDRS Standing Committee Members, Please find below the proposed agenda for our next meeting on Monday, 14 July at 17:30 UTC. RDRS SC Meeting Monday, 14 July 2025 17:30 UTC 1. Welcome 2. Continue Discussion of documented concerns from Draft Chapter 4 [<https://urldefense.com/v3/__https:/docs.google.com/document/d/1oqXdMgsGltTo…>docs.google.com<http://docs.google.com>]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1oqXdMgsGltTo…> * Rec. 3.1 (Privacy/Proxy Data) * Rec. 3.2 (Inclusion of RDRS links in RDAP responses) * Rec. 6 (Consideration regarding next steps on EPDP Phase 2/SSAD recs. * Rec. 4 (Authentication) - updated text, which incorporates feedback from 7 July meeting * Rec. 5 (Financial Sustainability) - updated text, which incorporates feedback from 30 June and 7 July meeting 1. Next Steps * Staff delivery of Draft Findings Report 1. AOB Thank you. Best regards, Caitlin

1 0

Notes and action items - RDRS SC Meeting - 7 July 2025
by Caitlin Tubergen July 8, 2025

July 8, 2025

Dear RDRS Standing Committee Members, Please find the notes and action items from the RDRS Standing Committee Meeting on Monday, 7 July 2025. Thank you. Best regards, Caitlin RDRS Standing Committee Call Monday, 7 July @ 17:30 UTC High-Level Notes and Action Items Action Items 1. Standing Committee members to continue commenting on Chapter 4<https://docs.google.com/document/d/1oqXdMgsGltToV_JxDtubedfymvrmvoAH43kssxO…> through Wednesday, 9 July. Reminder: Chapter 4 must represent recommendations and observations that can reach consensus of the Standing Committee. Accordingly, this requires SC members to respond to other members’ proposed additional text, comments, and questions and noting if you cannot support the proposed text or edits. 2. RDRS Support Staff to update Chapter 4 based on today’s discussion. 3. Following Wednesday, 9 July, RDRS Support Staff to compile the full draft Findings Report, including removing duplicative text, moving the recommendations to the beginning of the report, etc., for presentation and provision to the Standing Committee during its meeting on Monday, 14 July. – Notes 1. Welcome 2. Discussion of Draft Chapter 4<https://docs.google.com/document/d/1oqXdMgsGltToV_JxDtubedfymvrmvoAH43kssxO…> · Intro text re: cost of SSAD · Per our discussion last week, ICANN org is planning to provide a cost estimate for maintaining the system as is while the Board and GNSO Council discussions regarding the next steps for the SSAD recommendations are ongoing. · ICANN org will provide an updated number for the overall budget in Chapter 3 next week - this will go through June 2025. ICANN org will also provide a cost estimate for maintaining the RDRS as is while the GNSO Council and Board discuss the SSAD recs. · Important to make clear that a large share of this cost is ICANN org personnel. While the SC may be familiar with these numbers, readers may not appreciate this nuance, and it’s important to make this clear. · ICANN org staff time dedicated to RDRS is included in the chart in Chapter 3. All staff time, including the staff supporting the RDRS SC, is included in that number. · Support Staff to add text clarifying the number in Point 1, noting the large share of the cost is ICANN org personnel hours. · Sarah added text for the SC to consider, noting that financial sustainability is very central to what this SC is working on. Ultimately, if the RDRS is to continue, Rec. 14 should be implemented - in other words, the RDRS should be paid for by requestors and not the community (registrants). · Could we consider having ICANN partially fund the RDRS and having an arbitrary fee for requestors? · Would need to further consider this. May consider the going forward costs needs to be borne by requestors. · The previous text may conflate two concepts - the cost/value and who is paying for it. The main point is that the RDRS should not be permitted to continue in its current funding model. · The requestor pays concept was very important to NCSG. The requestor should not get the service for free, but until we can achieve something that is reasonable for requestors to pay, perhaps ICANN could cover some of this. · Rec. 14 should be considered for the SSAD, but this is the RDRS - not the SSAD. All we are saying is we think RDRS should continue. · Not supportive of the text as it stands - GAC is discussing making RDRS a more permanent system. These points should be bifurcated. · If we are recommending RDRS should be kept as a long-term solution, then it’s appropriate for us to say if we think it should be free of charge or not. What we seem to be hearing is that the RDRS is going to be maintained indefinitely and will be paid for entirely by ICANN, which is not appropriate. · The concern here is if the requestor community is unable to fully fund it - is there a compromise solution here? · There is confusion here on if the RDRS will become permanent and if that is what this group is suggesting. We should be clear on this. · It is our job to figure out what comes next and provide a clear recommendation of this. So far, we have not done this. · This group should be specifying exactly what capabilities a new system should have and then it’s up to someone else to decide how to implement that. · This group is not constituted to take on the task of what a future system should look like because these discussions have largely been excluded; we have discussed the RDRS vis-a-vis the SSAD recs. It’s important to have a fresh discussion on what a future system could look like. · We are being asked to provide lessons learned based on what we learned from what was incorporated in RDRS. What we are suggesting is how the SSAD recs can be interpreted in light of what we learned from RDRS. · One thing we can recommend is new policy work. We could say - based on the learnings from RDRS, this particular recommendation needs to be revisited. We could even provide a recommendation of what the new recommendation could look like based on our experience with RDRS. · Rec 1 - continue RDRS beyond pilot period · No additional comments. · Recommendation 2.2 · Marc noted a concern with the way this is worded. · Support work on the authentication challenge, but not sure the current wording explains what the Council is expected to do with this. This needs to detail what should be done, what are the next steps, etc. · The key point is the system can exist without authentication, but we recommend partial authentication instead of originally-recommended full authentication, and that is a change that will make the system more viable. · Hope to have ICANN take a proactive role in creating the technical and administrative standards for authentication - hoping to collaborate with ICANN on this. Technical - here is how to receive authentication token; admin - sign some sort of MOU. · There is no single entity in the world that will be trusted by everyone else. There could be multiple entities that make attestations for their individual members. · Authentication is an important component going forward. Is this something we want to say about a future system or bolt onto RDRS. The idea that one entity cannot be trusted to authenticate everyone is an important lesson learned. 3. Next Steps · The support team is currently working on incorporating all chapters into the official report template. The Standing Committee will have ample time to review and comment on the complete draft in its final format. · Please note the structure of the chapters might change slightly (reducing duplication, relocating recommendations to the beginning, etc.), but the substance will remain the same. 4. AOB

1 0

Meeting Invitation | RDRS Standing Committee | Monday, 14 July 2025
by Julie Bisland July 7, 2025

July 7, 2025

Dear all, The next RDRS Standing Committee call is scheduled for Monday, 14 July 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/GQAYEg * Check your time zone: https://tinyurl.com/yzjkv7ux 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

Post call | RDRS Standing Committee | Monday, 07 July 2025
by Julie Bisland July 7, 2025

July 7, 2025

Dear all, The recordings for the RDRS Standing Committee call held on Monday, 07 July 2025 can be found on the agenda wiki page <https://icann-community.atlassian.net/wiki/x/AYAYEg> 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

**1-MINUTE REMINDER** Meeting Invitation | RDRS Standing Committee | Monday, 07 July 2025
by Julie Bisland July 7, 2025

July 7, 2025

ON in 1 Minute! Dear all, The next RDRS Standing Committee call is scheduled for Monday, 07 July 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/AYAYEg * Check your time zone: https://tinyurl.com/3fjv3pp4 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

RDRS SC Report - Financial Sustainability
by Sarah Wyld July 7, 2025

July 7, 2025

Hello Standing Committee, I have drafted some suggested text to add to Chapter 4 of our report which discusses the EPDP Phase 2 recommendation on Financial Sustainability and the RDRS's costs and value. I will drop the text into the document but since I think some of us prefer email I wanted to share it here as well. I hope this is helpful and look forward to discussing all our comments as we finalize the report. Thank you. Considerations regarding financial sustainability As the purpose of the RDRS pilot project is to gather data to further inform the Operational Design Assessment’s consideration of costs of building and operating the SSAD, the RDRS SC discussed Recommendation #14 and the RDRS costs (see Chapter 3 Lessons Learned). These costs should be considered in relation to (a) the value provided to requestors, (b) the value provided to (and costs incurred by) participating registrars, and (c) any costs incurred by registrants. Value to requestors can be measured in terms of volume of requests and in feedback from requestors about their experiences with the service. Request volume has dropped over the term of the pilot project. Requestors have indicated generally low opinion of the RDRS (see Chapter 1 “Outcomes and Satisfaction” and “Likelihood of Continued Use”). Value to registrars can be measured in terms of the volume of participating registrars and in feedback from registrars about their experiences with the service. Registrar participation has dropped over the course of the pilot project. Registrars have also indicated a generally low opinion (see Chapter 1 “System Usability and Experience”, “Outcomes and Satisfaction”, and “Likelihood of Continued Use”.) The current operational funding of RDRS is provided by ICANN, so the true source of funding is domain owners themselves—the registration fees paid to registrars that fund ICANN are being used to fund the disclosure of registrants’ private data. As such, all RDRS costs are ultimately borne by domain owner data subjects themselves, directly contradicting the goal stated in Recommendation #14: 14.2. The objective is that the SSAD is financially self-sufficient without causing any additional fees for registrants. Data subjects MUST NOT bear the costs for having data disclosed to third parties; Requestors of the SSAD data should primarily bear the costs of maintaining this system. Furthermore, Data Subjects MUST NOT bear the costs of processing of data disclosure requests, which have been denied by Contracted Parties following evaluation of the requests submitted by SSAD users. ICANN MAY contribute to the (partial) covering of costs for maintaining the Central Gateway. For clarity, the EPDP Team understands that registrants are ultimately the source of much of ICANN’s revenue. The Standing Committee acknowledges the value of a lightweight system to standardize the disclosure request process and distribute requests to registrars, as well as the potential value of the possible enhancements discussed for the RDRS. Considering the general satisfaction levels indicated by RDRS users (both requestors and registrars) and the significant ongoing operational costs (not to mention the initial costs of building the system), the Standing Committee does not believe that the value presented is of such benefit that ICANN should continue funding this service. If the RDRS is to continue or any successor system is to be created, it must adhere to the consensus reached in Recommendation #14 relating to Financial Sustainability. -- *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>/

2 1

**15-MINUTE REMINDER** Meeting Invitation | RDRS Standing Committee | Monday, 07 July 2025
by Julie Bisland July 7, 2025

July 7, 2025

**15-MINUTE REMINDER** Dear all, The next RDRS Standing Committee call is scheduled for Monday, 07 July 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/AYAYEg * Check your time zone: https://tinyurl.com/3fjv3pp4 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

REMINDER | Meeting Invitation | RDRS Standing Committee | Monday, 07 July 2025
by Terri Agnew July 3, 2025

July 3, 2025

Dear all, The next RDRS Standing Committee call is scheduled for Monday, 07 July 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/AYAYEg * Check your time zone: https://tinyurl.com/3fjv3pp4 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

Proposed agenda - RDRS SC meeting - Monday, 7 July @ 17:30 UTC
by Caitlin Tubergen July 2, 2025

July 2, 2025

Dear RDRS SC, Please find below the proposed agenda for our next meeting on Monday, 7 July at 17:30 UTC. RDRS SC Meeting Monday, 7 July 17:30 UTC 1. Welcome 2. Continue Discussion of Draft Chapter 4 [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1oqXdMgsGltTo…> 3. Next Steps 4. AOB Thank you. Best regards, Caitlin

1 0

Notes and action items - RDRS Standing Committee Meeting - 30 June 2025
by Caitlin Tubergen July 2, 2025

July 2, 2025

Dear RDRS Standing Committee Members, Please find the notes and action items from the RDRS Standing Committee Meeting on Monday, 30 June 2025. Thank you. Best regards, Caitlin -- RDRS Standing Committee Call Monday, 30 June @ 17:30 UTC Action Items 1. Standing Committee members to continue commenting on Chapter 4<https://docs.google.com/document/d/1oqXdMgsGltToV_JxDtubedfymvrmvoAH43kssxO…> in before Monday, 7 July (our next meeting). Reminder: Chapter 4 must represent recommendations and observations that can reach consensus of the Standing Committee. Accordingly, this requires SC members to respond to other members’ proposed additional text, comments, and questions and noting if you cannot support the proposed text or edits. 2. RDRS Support Staff to update Chapter 4 based on today’s discussion, including providing requested financial estimates, where possible. 3. Following Wednesday, 9 July, RDRS Support Staff to compile the full draft Findings Report, including removing duplicative text, moving the recommendations to the beginning of the report, etc., for presentation and provision to the Standing Committee during its meeting on Monday, 14 July. – Notes 1. Welcome 2. Discussion of Draft Chapter 4<https://docs.google.com/document/d/1oqXdMgsGltToV_JxDtubedfymvrmvoAH43kssxO…> · Intro text re: cost of SSAD · The intro text to Chapter 4 includes proposed text from Gabe and Sarah for discussion. · There was an email discussion between Sebastien, ICANN org, and other members of the SC. Based on the email exchange, it seems the cost of the pilot was approximately 50% staff. Seb specifically requested more granularity with respect to the staff costs. · Gabe noted he added text with the goal of trying to make clear that this is talking about the development work and servicer operation - this text attempts to differentiate between one time costs and recurring costs on a monthly basis. · Consider adding future development costs from additional recommendations. It’s important to call out that the incremental cost per request is essentially 0 - in other words, if we receive 5 requests next month or 5,000 requests next month, the cost of operating the system will still be the same. It is important to clarify these three categories and make fact-based statements. · In response to Sarah’s proposed text - do not favor this text, and not sure this is something the group can get consensus on. · For the cost per request to be 0, that assumes that we are not adding any humans in the process. · Fair to flag that - ICANN’s process is currently automated; if that were to change, then the assumption that each request costs 0 would also change. · Chapter 3 provides a breakdown of costs for the RDRS pilot. The numbers go through December of 2024, where the one-time development cost was totaling $1,646,835. It also includes operational costs from December 2023 - December 2024 at $856,471 with a project-to-date cost overall of $2,502,306. · The one-time cost in development occurred before the pilot launched the recommended enhancements from this group. The costs after the pilot are assumed at $856,000. · ICANN org is working to get an updated chart for Chapter 3 that includes more recent calculations (through June 2025, for example) · In Chapter 3, we broke everything down to a per request cost, including development and without development. · We note that in item 2, Gabe has requested a per month cost of maintaining the system indefinitely. ICANN staff can provide a general figure for operational maintenance post-pilot (which will still be inclusive of some support for the ongoing policy discussions, promoting the service, etc.) · It is important to distinguish (i) an estimated cost to keep the system running while the Board and GNSO Council discuss the findings of the RDRS report and how to proceed with the SSAD recommendations vs. (ii) an estimated cost to keep the system running and concurrently introducing the proposed enhancements. Because the enhancements are still under discussion and will continue to be discussed at the Council and Board level, that is not something ICANN org could provide at this time since no final decision has been made on what enhancements or changes are accepted. · The personnel cost of $856,471 is calculated based on ICANN staff overall efforts for RDRS operations, including time dedicated to the SC (as it is part of overall RDRS pilot operations). Time dedicated to the SC isn’t tracked separately, as staff support for RDRS operations is recorded based on the percentage of time contributed to the project overall for each staff member. · Request best cost estimate of staff supporting the RDRS as that appears to be the lion’s share of the cost. · Without the staff cost estimate, the SC is working blind. One of the problems with the original asset costing is, it was very difficult to separate out those costs and understand what part of the 100 million estimate and what part was actually operating the system. · Number 3 should be “marginal cost per request” · The numbers that are going to be meaningful are the ones that are going to come from the people who have to run the service and bear the costs. In other words, ask the people who will bear the cost to provide the numbers and avoid parsing the numbers too carefully ourselves. · Suggest that whatever period we use be consistent throughout the entire document · Believe this information is already laid out in Chapter 3 so find it confusing to repeat here. What Sarah tried to add with the proposed text is to include a discussion around the cost and value of the service. Hope to achieve consensus on affirming recommendation 14. · Request to have numbers through June 2025 (an even number). · Need to make clear the sunk costs, the ongoing operational costs, and the marginal per request costs to avoid misinterpretation. There has been a push for some members to refer to the per request cost in the hundreds of dollars, which is not the best statement of fact. If a reader sees that a request costs $500, they may make a false assumption and this group needs to avoid that risk. · Staff should supply these numbers to the Board to inform its decision. We can inform the board about the past, but we recommend that the board get a proposal from staff. Full stop. · Would like to see lessons learned from staff incorporated into this report. · ICANN org would have a difficult time providing an estimate of how much the system would cost before this Board/Council discussion since the final enhancements or changes have not been decided, but Org could work on a cost estimate for RDRS following the delivery of the SC report to the Council/during the Council/Board discussion. · There’s probably a way to do this, through some sort of finite budget, without knowing all of the final enhancements · Recommendation 1 · Comment to separate the concepts of continue the RDRS after the pilot phase and improve the RDRS after the pilot phase, as the improvements are discussed in Recommendation 2. · The recommendations should be in four categories: · 1. Continue the RDRS after the pilot concludes; · 2. Recommended system enhancements; · 3. Recommended areas for further policy work; · 4. Considerations for what to do with the SSAD recommendations · Recommend avoiding duplicate text - for example, the enhancements are already included in Chapter 2 - why don’t we just refer to that? · Comment on SSAD recommendation 5 in the table - this group should think about how to make the recommendations of fundamental rights balancing more universal and not just GDPR-oriented. Fundamental rights balancing should be global. · The suggestions in response to Rec. 5 seem more appropriately place in response to Rec. 8. · The idea behind these comments to Rec. 5 is to align RDRS more with the SSAD recs. · If that is the goal, suggest getting more specific about how these suggestions could practically be implemented into RDRS. 3. Next Steps · The support team is currently working on incorporating all chapters into the official report template. The Standing Committee will have ample time to review and comment on the complete draft in its final format. · Please note the structure of the chapters might change slightly (reducing duplication, relocating recommendations to the beginning, etc.), but the substance will remain the same. 4. AOB

1 0