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

2025-04-28 RDRS Standing Committee - Meeting #30
by Feodora Hamza April 29, 2025

April 29, 2025

Dear RDRS SC, Please see below the notes and action items from the last meeting. The next meeting is scheduled for 12 May at 17:30 UTC. Kind regards, Feodora and Caitlin 2025-04-28 RDRS Standing Committee - Meeting #30<https://icann-community.atlassian.net/wiki/spaces/EOTSFGRD/pages/236912642/…> Action Item: ICANN Org to draft a proposed structure for Chapter 4. Include a comparative table analyzing each SSAD recommendation against RDRS implementation. 1. Welcome · SC Chair opened the meeting. The intent was to ensure the Standing Committee was aligned on its purpose and direction, particularly regarding Assignments 3 and 4. 1. Continue discussion on Chapter 4 · ICANN Org - Presentation · ICANN Org provided a presentation and recap on Assignment Scope for Assignment 3 and 4 based on Charter.<https://gnso.icann.org/sites/default/files/policy/2023/draft/draft-rdrs-sta…> · In addition, ICANN Org presented procedural scenarios based on the Assignment 4 scope. · The slides of the presentation can be found here. <https://docs.google.com/presentation/d/1BvcyoJk_N8UfUm5KWtSFHmYBeY5uZ2vS/ed…> · Discussion Summary · Some SC members noted preference for keeping RDRS voluntary; SSAD should not be built. · Against selective adoption without policy development, as choosing parts of SSAD implies policy work. · SC members toted the group would find it relatively easy to recommend which RDRS features to continue. · SC members also noted difficulties for the Standing Committee to settle what SSAD parts to change, given historical difficulty during EPDP Phase 2. · Some SC members disagreed with the immediate dismissal of SSAD without evaluating all recommendations. Suggested the committee to walk through Assignment 4 carefully. · SC members suggested it is premature to declare SSAD dead without conducting the policy evaluation work mandated in Assignment 4. · Suggested a practical approach: · Review all 18 recommendations. · Determine consensus areas: which could be endorsed, which required further work, and which should be discarded. · Allow the Council to determine next steps, including whether a new EPDP is required. · Clarified that while this is not developing new policy, it is evaluative work to inform the Council and Board. · Proposed that public comment could happen while the evaluation is ongoing. · SC members suggested a more flexible, diplomatic wording of Scenario 4. · Suggested restructuring options to make them more consensus-friendly. * SC Chair observed agreement that the group should: * Evaluate each recommendation against RDRS experience. * Provide informed, but non-binding, guidance to Council without making policy recommendations themselves. * Emphasized the deliverable should be scoping advice, not direct policy. * The group should gather as much informational context as possible. * Commented that the final output should help the Council understand the size and nature of any future policy work. 1. AOB * Next Meeting: May 12, 2025 (due to May 5 conflict with CP Summit)

1 0

Post call | RDRS Standing Committee | Monday, 28 April 2025
by Terri Agnew April 28, 2025

April 28, 2025

Dear all, The recordings for the RDRS Standing Committee call held on Monday, 28 April 2025 can be found on the agenda wiki page <https://icann-community.atlassian.net/wiki/x/AgAfDg> 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, Terri Policy Team Supporting the GNSO

1 0

Meeting Invitation | RDRS Standing Committee | Monday, 12 May 2025
by Terri Agnew April 28, 2025

April 28, 2025

**Reminder, no meeting on 05 May 2025. Make sure you have removed it from your calendars. See information below for next scheduled meeting. Dear all, The next RDRS Standing Committee call is scheduled for Monday, 12 May 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…> * 2025 Meetings Wiki agenda pages: https://icann-community.atlassian.net/wiki/x/NjTlBg * Check your time zone: https://tinyurl.com/3nh5jc5u 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, Terri Policy Team Supporting the GNSO

1 0

**Starting in 15 minutes | Meeting Invitation | RDRS Standing Committee | Monday, 28 April 2025
by Terri Agnew April 28, 2025

April 28, 2025

**Starting in 15 minutes Dear all, The next RDRS Standing Committee call is scheduled for Monday, 28 April 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/AgAfDg * Check your time zone: https://tinyurl.com/425755yr 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 RDRS SC Call agenda 28 April
by Feodora Hamza April 28, 2025

April 28, 2025

Dear RDRS SC, please see below the proposed agenda for our next call. Proposed Agenda RDRS SC Call agenda 28 April 17:30 UTC 1. Welcome 2. Continue discussion on Chapter 4 3. 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>

2 1

**REMINDER** Meeting Invitation | RDRS Standing Committee | Monday, 28 April 2025
by Julie Bisland April 25, 2025

April 25, 2025

Dear all, The next RDRS Standing Committee call is scheduled for Monday, 28 April 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/AgAfDg * Check your time zone: https://tinyurl.com/425755yr 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

Clarification of Expectations for Assignments #3 and #4 of the RDRS Standing Committee
by Feodora Hamza April 24, 2025

April 24, 2025

Sent on behalf of Sebastien Ducos Dear RDRS SC Members, Thank you for your Email exchange. As the SC continues its work on its Final Findings Report, I would like to provide a clear summary of expectations for Assignment #3 (Lessons Learned) and Assignment #4 (Recommendations to the Council), as outlined in the Standing Committee Charter (Section II: Mission, Purpose, and Deliverables).<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Assignment #3: Specific Lessons Learned Charter Source: Section II, Scope, p. 3 The Charter tasks the Committee with: “Specific lessons learned that should be factored into the consideration of how to proceed with the SSAD recommendations.” Assignment #4: Proposed Recommendations to the Council Charter Source: Section II, Scope, p. 3–4 As outlined in the Charter, the Committee is to: “Provide suggestions to the Council for a proposed recommendation(s) to the ICANN Board in relation to the consideration of the SSAD recommendations.” The Charter notes possible outcomes that may be considered in this context: “The small team does expect that before the 2-year period ends clarity is provided on the expected next steps in relation to the EPDP Phase 2 SSAD Recommendations which could include: 1. Approval of EPDP Phase 2 SSAD recommendations (in current or modified format) which would replace the SSAD proof of concept; 2. Determination that adoption of EPDP Phase 2 SSAD recommendations is not in the best interest of the ICANN community or ICANN and termination of SSAD proof of concept; 3. Modification of EPDP Phase 2 SSAD recommendations by GNSO Council informed by SSAD proof of concept findings; 4. A variation and/or combination of the above scenarios.” Furthermore, the Charter notes “although further enhancements may be considered by ICANN org based on the actual experience with the Whois Disclosure System (now RDRS) once it is operational, it is not the intent or objective of the 6-month intervals to focus on technical enhancements for the Whois Disclosure System (now RDRS).” Ultimately, the Final Findings Report is intended to help inform subsequent decisions on how to proceed with the SSAD recommendations and to ground GNSO Council deliberations based on the data-informed RDRS pilot experience. Thank you again for your dedicated efforts and thoughtful contributions to the Final Findings Report. Kindly, Sebastien Ducos Chair – RDRS SC

1 0

2025-04-21 RDRS Standing Committee - Meeting #29
by Feodora Hamza April 23, 2025

April 23, 2025

Dear RDRS SC, Please see below the notes and action items from the last meeting. The next meeting is currently scheduled for 28 April at 17:30 UTC. Kind regards, Feodora and Caitlin 2025-04-21 RDRS Standing Committee - Meeting #29<https://icann-community.atlassian.net/wiki/spaces/EOTSFGRD/pages/115684781/…> Action Items: 1. Support Staff to provide a draft of Chapter 4 (Standing Committee’s Recommendations to the GNSO Council). 2. RDRS SC will now be focusing on Chapter 4, but RDRS SC asked to please ensure you have reviewed the text of Chapter 2<https://docs.google.com/document/d/1oqXdMgsGltToV_JxDtubedfymvrmvoAH43kssxO…> and 3<https://docs.google.com/document/d/1c2Nm5s1Q-4jrAqWvsurH-k6BhpyanGIW/edit#h…> and provided comments. Documents: * Chapter 1-3: * 1https://docs.google.com/document/d/1CBAHz7G2AmjOt7C68Rn_hFl5c9F83lz9/edit * 2https://docs.google.com/document/d/1oqXdMgsGltToV_JxDtubedfymvrmvoAH43kssx… * 3https://docs.google.com/document/d/1c2Nm5s1Q-4jrAqWvsurH-k6BhpyanGIW/edit Agenda 1. Welcome * Update on Chapter 2 and 3 · There have been no further comments received on Chapter 2<https://docs.google.com/document/d/1oqXdMgsGltToV_JxDtubedfymvrmvoAH43kssxO…> and Chapter 3<https://docs.google.com/document/d/1c2Nm5s1Q-4jrAqWvsurH-k6BhpyanGIW/edit#h…> · Support Staff has updated the text based on earlier comments received Action Item: RDRS SC will now be focusing on Chapter 4, but RDRS SC asked to please ensure you have reviewed the text of Chapter 2<https://docs.google.com/document/d/1oqXdMgsGltToV_JxDtubedfymvrmvoAH43kssxO…> and 3<https://docs.google.com/document/d/1c2Nm5s1Q-4jrAqWvsurH-k6BhpyanGIW/edit#h…> and provided comments. 1. Update from RDRS doodle poll · Based on poll results, we will be moving to weekly 60-minute meetings · Meetings will continue to be on Monday 17:30 UTC. · Based on feedback, we will not be meeting the week of 5 May due to member conflicts from the CP Summit. 1. Discussion on Chapter 4 · Chapter 4 is the crux of the Standing Committee’s assignment as this section provides the recommendations the Standing Committee will be making the GNSO Council. · ICANN Org presented rough overview of potential recommendations to GNSO Council based on review and feedback from Chapter 1 -3. · Disclaimers: · Support Staff worked with RDRS Leadership to provide rough drafts of recommendations that we thought we heard during the group’s work · This text/slides presented were for discussion purposes and can be edited later. · It’s important to remember that the recommendations the group makes should represent what the group largely agrees to or can achieve consensus on. · The aims was to show the potential recommendation ideas to get initial feedback from RDRS, and once the group provides initial input, Support Staff will take this input and incorporate it into draft text that the Committee can review. · There are not capital “r” Recommendations, but rather, lowercase “r” recommendations to the Council, as these are not policy recommendations. · Potential Recommendations and Group’s reactions · Maintain RDRS while additional policy and implementation work is outstanding · Suggest changing this to maintain RDRS until a successor system is in place · Consider treating SSAD recs with flexibility rather than strictly adhering to the recommendations as one package · Discomfort with the text as currently worded, as could result in cherry picking which recommendations to keep or modify and which not to keep or modify, which amounts to policy work. · Instead of saying “treat with flexibility,” the SC may identify which recommendations were implemented in RDRS and which were not and make some further observations on that the GNSO could potentially send to a working group to work on. · It may not have to be a new PDP. · Consider additional policy work on key system enhancements · Privacy/Proxy disclosure · RDRS links to RDAP · Making RDRS mandatory · The recommendation should clearly state the GNSO Council should consider additional policy work · P/P should be included in the discussion of the successor system (in whatever form that takes), but important to note that there is currently an IRT working on P/P accreditation. · Regarding making RDRS mandatory, what does this mean? Does it mean registrars must participate in this as a stopgap measure prior to the successor system, or do we mean the successor system should be mandatory? · Consider additional implementation work on key system enhancements · API · Authentication Mechanism · Optional ccTLD participation · The API should be RDAP-based · Update from PSWG on authentication – there are currently discussions ongoing regarding a short-term and long-term solution. The short-term idea is to provide unique domain names for known law enforcement agencies to ICANN to include in RDRS so that if someone were to make an RDRS request and the email address they're using that a response would be sent to matches with a known law enforcement agency's domain, that data point could also be shared with the registrar, so they can use that in their balancing test and their disclosure decisions. · NCSG to consider this point · No other objections · Question whether it makes sense to add these bullets (like API) to the existing RDRS or if we want to apply these recommendations to a successor system · Not the Committee’s place to tell Org how to implement, but it would be helpful to know what they intend to do, i.e., start from scratch or add on to RDRS so that we can word the recommendations appropriately. · Implementation in this context means technical work on RDRS, not the work of a traditional IRT · A significant part of the SCs work is proposing a path – it seems what the Committee is coalescing on is that there is a need for a system, and there is a need for further policy work in this area. The SSAD recs, as written, however, are not fit for purpose, and new policy work is needed. This should be made clear in Chapter 4 what the SC thinks the GNSO Council should consider doing. 1. AOB 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>

5 7

Meeting Invitation | RDRS Standing Committee | Monday, 28 April 2025
by Julie Bisland April 21, 2025

April 21, 2025

Dear all, The next RDRS Standing Committee call is scheduled for Monday, 28 April 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/AgAfDg * Check your time zone: https://tinyurl.com/425755yr 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

Canceled: RDRS Standing Committee
by ICANN Policy Calendar April 21, 2025

April 21, 2025

Meeting: RDRS Standing Committee Pattern: Weekly on Mondays at 17:30 UTC for 60 minutes (28 April - 02 June 2025) (cancelled 05 May) 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 pages starting with 28 April: https://icann-community.atlassian.net/wiki/x/AgAfDg * Check your time zone (28 April 2025): https://tinyurl.com/425755yr 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.

1 0