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

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