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

Notes and actions from ICANN82 session
by Caitlin Tubergen March 20, 2025

March 20, 2025

Dear Standing Committee Members, Thank you for all for your active participation during the ICANN82 session. As you have likely seen, there be no meeting on Monday, 24 March. HOMEWORK: Please use the additional time to finish your review of Chapter 2<https://docs.google.com/document/d/1oqXdMgsGltToV_JxDtubedfymvrmvoAH43kssxO…>. As a reminder, SC Members are kindly requested to: 1. evaluate the effectiveness of the implemented enhancements in the final column of table 1. (Did the enhancement have the intended effect?); 2. provide justification (goal/rationale) and identify risks/dependencies for each proposed enhancement in table 3 of Chapter 2; and 3. provide a priority ranking from 1 to 10 for each proposal. (1 being high priority and 10 being lowest priority.) MEETING CADENCE: Leadership met with Staff Support, and we discussed increasing the meeting length or cadence as we continue making progress on our report to the Council. We have the option of meeting every Monday for 60 minutes, or every other Monday for 90 minutes. We will discuss the options during our upcoming meeting, but if you are welcome to share thoughts on the list. ICANN82 SESSION NOTES: Please find the notes from our ICANN82 meeting below. Support Staff has made some updates to Chapter 1<https://docs.google.com/document/d/1CBAHz7G2AmjOt7C68Rn_hFl5c9F83lz9/edit?u…> based on the discussions during the session. Thank you. Best regards, Feodora and Caitlin -- 2025-03-12 RDRS Standing Committee Work Session - ICANN82<https://icann-community.atlassian.net/wiki/spaces/EOTSFGRD/pages/115684608/…> Agenda: 1. Welcome (2min) * SC Chair took the floor, welcoming attendees and providing a brief introduction into the pilot. * Link to RDRS Annual Report: here<https://www.icann.org/en/system/files/files/rdrs-annual-report-24feb25-en.p…> 2. Update on the progress of the final findings report (5min) * During ICANN81 in Istanbul, the RDRS SC concluded that enough data has been received and decided to start drafting their final findings report. * SC Chair provided an update on the RDRS Council report. · Standing Committee discussions and observations, including areas of disagreement, will be noted in the report, where relevant. · There will not be a formal consensus call and the report will not include policy recommendations as described in the ICANN Bylaws, but the RDRS SC will make recommendations to inform the GNSO Council as it prepares its dialogue with the ICANN Board on how to proceed with SSAD recommendations/RDRS. · The recommendations from chapter 1 will be moved to Chapter 3 or 4 for clarity and can be reviewed again when we discuss those chapters. The conclusions can be reviewed again during the chapter 3 and 4 discussions. 3. Working Session (45 min) * The SC discussed the flagged items from draft chapter 1. Flagged items for further discussion (Chapter1) · Volume of Requests: Some concerns were raised that the RDRS’s request volume is too low compared to historical WHOIS query levels. While the volume is not comparable to WHOIS, the pilot still provides valuable data. Proposal: Neutral presentation of statistics is recommended in reporting. · Mandatory Participation: Some SC members consider mandatory participation in RDRS as a means to enhance system usage. Other SC members noted that this is not supported by all SGs due to various factors. SC members also noted the recommendations from the EPDP phase 2 for the SSAD envisioned a mandatory centralized system. · Clarity and Accessibility of Requests: There were concerns about whether RDRS forms and processes are clear to users. Proposal: Establish a stakeholder review group (including requesters, registrars, and registrants) to refine the request language for clarity. · Timelines for Request Processing: RDRS does not currently enforce response timeframes. SLA (Service Level Agreements) were included in EPDP Phase 2 recommendations but not implemented in RDRS. Some requests may take longer due to delays from either registrars or requesters. Proposal: Response timeframes should not be strictly defined within RDRS until a final system is decided upon. · Technical & Operational Considerations: Some registrars found the system difficult to integrate into their workflows. The requirement to log into ICANN’s secure portal to access requests was seen as a barrier. Proposal: Develop better automation and integration with registrars’ ticketing systems. Further review needed, particularly in reference to EPDP Phase 2 recommendations. · Expanding RDRS to Include ccTLDs: Some discussion on whether country-code TLDs (ccTLDs) should be included in the system. Many ccTLDs do not use RDAP, making integration difficult. Operational aspects – Would requests go to ccTLD registrars or registries? 4. Next Steps (5min) * SC members to review Chapter Two<https://urldefense.com/v3/__https:/docs.google.com/document/d/1oqXdMgsGltTo…>. SC Members are kindly requested to evaluate the effectiveness of the implemented enhancements in the final column of table 1. (Did the enhancement have the intended effect?) SC members are kindly requests to provide justification (goal/rationale) and identify risks/dependencies for each proposed enhancement in table 3 of the document. SC Members kindly asked to provide a priority ranking from 1 to 10 for each proposal. 1 being high priority and 10 being lowest priority. 5. AOB (3min) * Next meeting is scheduled for: 7 April 2025 17:30 UTC

1 0

Meeting Invitation | RDRS Standing Committee | Monday, 07 April 2025
by Terri Agnew March 19, 2025

March 19, 2025

**The 24 March meeting has been cancelled, please remove it from your calendars. See information below for next scheduled meeting. Dear all, The next RDRS Standing Committee call is scheduled for Monday, 07 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…> * 2025 Wiki agenda pages: https://icann-community.atlassian.net/wiki/x/NjTlBg * Check your time zone: https://tinyurl.com/356m43ef 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

Canceled: RDRS Standing Committee
by ICANN Policy Calendar March 19, 2025

March 19, 2025

Meeting: RDRS Standing Committee Pattern: Biweekly on Mondays at 17:30 UTC for 60 minutes (24 March – 02 June 2025) 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 Wiki agenda pages: https://community.icann.org/x/JwFEFw * Check your time zone (24 March 2025): https://tinyurl.com/mfhdznx9 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

Re: The February RDRS Usage Metrics Report is Published
by Lisa Carter March 18, 2025

March 18, 2025

Hello Standing Committee Members, I hope everyone had a successful ICANN82 experience and safe travels home. ICANN has published the February RDRS Metrics Usage Report: March 2025 (Reporting period: 1 February – 28 February 2025) [PDF] [CSV] [CSV 18] [CSV 19] Best, Lisa Carter Sr. Program Manager, Strategic Initiatives ICANN

1 0

REMINDER | Meeting Invitation | RDRS Standing Committee | Monday, 27 January 2025
by Devan Reed March 13, 2025

March 13, 2025

Dear all, The next RDRS Standing Committee call is scheduled for Monday, 27 January 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 Wiki agenda pages: https://community.icann.org/x/JwFEFw * Check your time zone: https://tinyurl.com/rp2v6y5s 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, Devan Policy Team Supporting the GNSO

3 4

ICANN82: Proposed Agenda and Action Items for RDRS Working Session
by Feodora Hamza March 4, 2025

March 4, 2025

Sent on behalf of Sebastien Ducos Dear RDRS SC members, As we continue to progress with our work on the final findings report and in preparation for ICANN82, I want to kindly remind everyone of the pending action items that need your attention before our next meeting. 1. SC Members to review Chapter One <https://urldefense.com/v3/__https:/docs.google.com/document/d/1CBAHz7G2AmjO…> and the flagged recommendations/conclusions (marked in Red in the document) that needed further discussion by Tuesday 11 March. Flagged items will be added to the upcoming meeting agenda and the comment owner will be invited to present their point. 1. SC members to review Chapter Two<https://urldefense.com/v3/__https:/docs.google.com/document/d/1oqXdMgsGltTo…> that focuses on proposed system enhancements by Tuesday 11 March. SC Members are kindly requested to evaluate the effectiveness of the implemented enhancements in the final column of table 1. (Did the enhancement have the intended effect?) SC members are kindly requests to provide justification (goal/rationale) and identify risks/dependencies for each proposed enhancement in table 3 of the document. SC Members kindly asked to provide a priority ranking from 1 to 10 for each proposal. 1 being high priority and 10 being lowest priority. As discussed during our last call, Standing Committee discussions and observations, including areas of disagreement, will be noted in the report, where relevant. There will not be a formal consensus call and the report will not include policy recommendations as described in the ICANN Bylaws, but the RDRS SC will make recommendations to inform the GNSO Council as it prepares its dialogue with the ICANN Board on how to proceed with SSAD recommendations/RDRS. The recommendations from chapter 1 will be moved to Chapter 3 or 4 for clarity and can be reviewed again when we discuss those chapters. In addition, please see below the proposed agenda for our ICANN82 working session. Proposed Agenda for ICANN82 - Wednesday March 12, 2025, 16:30 - 17:30 PDT - 23:30 UTC * Welcome (2min) * Update on progress – (5min) * Working Session/Discussion (45min) * Next Steps (5min) * AOB (3min) Please let me know if you have any questions or require any clarifications. Thank you for your time and effort. Looking forward to your valuable input. Safe travels, Sebastien Ducos Chair - RDRS SC

1 0

2025-02-24 RDRS Standing Committee - Meeting #26
by Feodora Hamza Feb. 26, 2025

Feb. 26, 2025

Dear RDRS SC, Please see below the notes and action items from the last meeting. The next meeting will take place during ICANN82 and is scheduled for Wednesday 12 March 2025, 16:30 - 17:30 PDT - 23:30 UTC Kind regards, Feodora 2025-02-24 RDRS Standing Committee - Meeting #26<https://community.icann.org/pages/viewpage.action?pageId=390332719> Action Items Task Owner Deadline 1. Add missing pending enhancements to Chapter 2 ICANN Org 11 March 1. Incorporate Steve Crocker’s comments and responses to his comment into Chapter 3 or 4 ICANN Org when ready 1. Review Chapter Two<https://urldefense.com/v3/__https:/docs.google.com/document/d/1oqXdMgsGltTo…> that focuses on proposed system enhancements and flag areas of concerns or provide any other relevant feedback. SC members 11 March 1. Evaluate the effectiveness of the implemented enhancements in the final column of table 1 Chapter 2. (Did the enhancement have the intended effect?) SC members 11 March 1. Provide justification (goal/rationale) and identify risks/dependencies for each proposed enhancement in table 3 of Chapter 2. SC members 11 March 1. Provide a priority ranking from 1 to 10 for each proposal in Chapter 2. 1 being high priority and 10 being lowest priority. SC members 11 March Documents: 1. Draft Chapter 1: https://docs.google.com/document/d/1CBAHz7G2AmjOt7C68Rn_hFl5c9F83lz9/edit#h… 2. Draft Chapter 2: https://docs.google.com/document/d/1oqXdMgsGltToV_JxDtubedfymvrmvoAH43kssxO… 3. Report Outline: https://docs.google.com/document/d/157GemS7-sX_Vr6n9n9iXLdiEoyQ4q9ug/edit Agenda 1. Welcome (10min) * Discussion on comment made by Steve Crocker reg. final findings report * Integration of Steve’s January 27th email into the report. * Discussion on the location of these comments in Chapter 3 or 4. * Consideration of February 5th responses and further discussions. * Chapter 3 and 4 will be focusing on recommendations/conclusions, including a section to challenge assumptions. * The report will specifically note if certain conclusions are not widely supported. 1. Update on Chapter 1 (20min) * ICANN Org presented the flagged recommendations/conclusions. SC Chair noted that these recommendations/conclusions will be discussed during ICANN82 if needed. * Areas flagged: * Clarification needed regarding ticketing systems and response times. * Conclusion on RDRS forms might be too subjective. * Conclusion regarding «required timeframe for requestor responses» is not supported by all SC members. * SC members need further clarification on the conclusions regarding denial responses. * ICANN Org will address the concerns in draft chapter 1 and will provide additional language for consideration. * Discussion on whether anecdotal reporting should be included. * SC members raised concerns that some registrars deny requests outright if the "confidential request" checkbox is selected. * SC members countered that RDRS does not support legal due process for such requests. * It was suggested that rather than reporting anecdotal data, the issue could be flagged as an area for future research and improvement in the final findings report. 1. Discussion on Chapter 2 (20min) * Sarah Wyld asked for clarification on the scope of APIs (whether it’s one API or multiple APIs). * Gabriel Andrews clarified that the API is intended to integrate with existing law enforcement tools and enable authentication. * Sarah Wyld flagged missing pending enhancements from the report: * Pending input status for tracking requests. * Ability to change request outcomes or create linked follow-ups. * Missing enhancements will be added to the document. * Discussion on whether the platform should continue to be based on Salesforce or if an external solution should be considered. SC members noted the suggestion to consider an external solution should remain in chapter 2. * SC members noted that standardization of APIs, rather than a single central platform, is key to ensuring interoperability. 1. ICANN82 session update (7min) Proposed Agenda for ICANN82 - Wednesday March 12, 2025 16:30 - 17:30 PDT - 23:30 UTC * Welcome (2min) * Update on progress – (PPT with main trends from chapter one and status of chapter 2) (10min) * Working Session/Discussion Chapter 2 (40min) * Next Steps (5min) * AOB (3min) 1. AOB (3min) * SC members suggested that the RDRS report, which includes statistics, should also consider how many requests registrars handle outside of RDRS. Others pointed out that this data might be difficult to retrieve. * ICANN Org noted that some data is available from user interview reports. Feodora Hamza Policy Development Support Manager (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +32 496 30 24 15 Email: feodora.hamza(a)icann.org<mailto:feodora.hamza@icann.org> Website: www.icann.org<http://www.icann.org>

1 0

Post call | RDRS Standing Committee | Monday, 24 February 2025
by Devan Reed Feb. 24, 2025

Feb. 24, 2025

Dear all, The recordings for the RDRS Standing Committee call held on Monday, 24 February 2025 can be found on the agenda wiki page <https://community.icann.org/x/LwFEFw> and the GNSO Master Calendar<https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…>. 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, Devan Policy Team Supporting the GNSO

1 0

Meeting Invitation | RDRS Standing Committee | Monday, 24 March 2025
by Devan Reed Feb. 24, 2025

Feb. 24, 2025

The next RDRS Standing Committee Session takes place at ICANN82: https://community.icann.org/x/GYAzGg Please find below join details for the next meeting after ICANN82. Dear all, The next RDRS Standing Committee call is scheduled for Monday, 24 March 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 Wiki agenda pages: https://community.icann.org/x/JwFEFw * Check your time zone: https://tinyurl.com/mfhdznx9 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, Devan Policy Team Supporting the GNSO

1 0

15 MINUTES REMINDER | Meeting Invitation | RDRS Standing Committee | Monday, 24 February 2025
by Devan Reed Feb. 24, 2025

Feb. 24, 2025

Dear all, The next RDRS Standing Committee call is scheduled for Monday, 24 February 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 Wiki agenda pages: https://community.icann.org/x/JwFEFw * Check your time zone: https://tinyurl.com/48badwc6 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, Devan Policy Team Supporting the GNSO

1 0