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

2nd REMINDER | Action needed | Doodle | RDRS meeting cadence
by Terri Agnew April 10, 2025

April 10, 2025

**2nd REMINDER: complete doodle, thank you to the five who have at this time. Hello all, As discussed on today’s meeting, the meeting cadence may need to be changed up from bi-weekly, 1-hour meetings to either weekly 1-hour meetings or bi-weekly 1.5-hour meetings. Please complete the doodle to help determine the path forward. * If weekly 1-hour meetings, select 14 April, 21 April, and 28 April all at 17:30 UTC for 1-hour * If bi-weekly 1.5-hour meeting, select 21 April either 17:00 or 17:30 UTC for 1.5 hour Reminder, this is not only for April meetings but to adjust the meeting cadence going forward. Doodle: https://doodle.com/meeting/participate/id/aO6g4RLe Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

REMINDER | Action needed | Doodle | RDRS meeting cadence
by Terri Agnew April 9, 2025

April 9, 2025

**REMINDER: complete doodle Hello all, As discussed on today’s meeting, the meeting cadence may need to be changed up from bi-weekly, 1-hour meetings to either weekly 1-hour meetings or bi-weekly 1.5-hour meetings. Please complete the doodle to help determine the path forward. * If weekly 1-hour meetings, select 14 April, 21 April, and 28 April all at 17:30 UTC for 1-hour * If bi-weekly 1.5-hour meeting, select 21 April either 17:00 or 17:30 UTC for 1.5 hour Reminder, this is not only for April meetings but to adjust the meeting cadence going forward. Doodle: https://doodle.com/meeting/participate/id/aO6g4RLe Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

2025-04-07 RDRS Standing Committee - Meeting #28
by Feodora Hamza April 8, 2025

April 8, 2025

Dear RDRS SC, Please see below the notes and action items from the last meeting. The next meeting is currently scheduled for 21 April at 17:30 UTC. Action Items: 1. SC is kindly asked to review the prioritization in Chapter 2.<https://docs.google.com/document/d/1oqXdMgsGltToV_JxDtubedfymvrmvoAH43kssxO…> If no further comments are received, report will move with the proposed ranking. 2. ICANN Org to update Chapter 3<https://docs.google.com/document/d/1c2Nm5s1Q-4jrAqWvsurH-k6BhpyanGIW/edit> with discussed comments and amendments (based on SC discussion). 3. SC to review Chapter 3<https://docs.google.com/document/d/1c2Nm5s1Q-4jrAqWvsurH-k6BhpyanGIW/edit> and provide any comments for further discussion by 16 April. 4. SC to reply to ICANN Org Email (sent on 7 April and see below) regarding Meeting Cadence by 16 April. As discussed, the meeting cadence may need to be changed up from bi-weekly, 1-hour meetings to either weekly 1-hour meetings or bi-weekly 1.5-hour meetings. Please complete the doodle to help determine the path forward. Doodle: https://doodle.com/meeting/participate/id/aO6g4RLe [doodle.com]<https://urldefense.com/v3/__https:/doodle.com/meeting/participate/id/aO6g4R…> * If weekly 1-hour meetings, select 14 April, 21 April, and 28 April all at 17:30 UTC for 1-hour * If bi-weekly 1.5-hour meeting, select 21 April either 17:00 or 17:30 UTC for 1.5 hour Reminder, this is not only for April meetings but to adjust the meeting cadence going forward. Kind regards, Feodora 2025-04-07 RDRS Standing Committee - Meeting #28<https://icann-community.atlassian.net/wiki/spaces/EOTSFGRD/pages/115684757/…> Documents: * Draft Chapter 3: https://docs.google.com/document/d/1c2Nm5s1Q-4jrAqWvsurH-k6BhpyanGIW/edit * Slides for RDRS Call 7 April: https://docs.google.com/presentation/d/1yNQN87iELueDffYDhIdq5rDJlsbXlI8P/ed… * Draft Chapter 2: https://docs.google.com/document/d/1oqXdMgsGltToV_JxDtubedfymvrmvoAH43kssxO… Agenda: 1. Welcome · SC Chair welcomed attendees and introduced the agenda. · SC Chair noted that Chapter 2 item prioritization remains pending; Chair added tentative priorities in the interim (1–10 for high relevance; >10 for lower urgency; 20 for least priority, e.g., request to redevelop tool outside of Salesforce). Action Item: SC is kindly asked to review the prioritization in Chapter 2. If no further comments are received, we will move with the proposed ranking. 1. Review Chapter 3 (flagged issues) · ICANN Org presented the outline of Chapter 3. · Steve DelBianco raised a concern about conflating SSAD (staff implementation concept with $100M estimate) with EPDP Phase 2 recommendations. · Sarah Wyld confirmed “SSAD” is referenced in the Phase 2 report (definitions, page 18), but agreed discussion should focus on actual recommendations. · ICANN Org clarified the comparison and reference in Chapter and report is with EPDP Phase 2 policy recommendations. · Flagged items for discussion: · Staff presented the flagged items in Slides. HERE<https://docs.google.com/presentation/d/1yNQN87iELueDffYDhIdq5rDJlsbXlI8P/ed…> · General Comments · Sarah Wyld retracted the first comment, acknowledging the language was acceptable. · Registrar Participation & Data Limitation: Sarah Wyld and Alan Greenberg noted that direct disclosure paths to registrars would be similar in SSAD, so describing this as a limitation in RDRS is incorrect. Conclusion: Paragraph should be revised or removed. · Specific Recommendation Discussions · Rec 5 (Response Recommendations): Sarah proposed clarifying the text by explicitly referencing Rec. 5. Conclusion: Changes accepted. · Rec 7 (Requester Purpose): Sarah Wyld noted a mismatch between purposes listed in RDRS vs. the Phase 2 policy. Conclusion: Differences should be documented for potential future policy review. · Lessons Learned · Developing RDRS- PGP Encrypted Email: 30% of RDRS resources were spent developing functionality not used by registrars. Seen as a cautionary example of overinvesting in features without confirming utility. Conclusion: This experience should be factored into future development planning. · Lack of Response Interaction / Ticketing: SC Chair asked whether a back-and-forth feature is necessary within RDRS. Sarah Wyld located confirmation in the implementation guidance of Recommendation 5 that should support back-and-forth communication between requesters and registrars. · Cost Analysis Discussion: Sarah Wyld calculated ~$1,000/request (including development costs), but the report used ~$354/request (operational cost only). Conclusion: Resolved that both figures are useful, but clarity is needed in how costs are represented. Action Items: a) ICANN Org to update Chapter 3 with discussed comments and amendments. b) SC to review Chapter 3 and provide any comments for further discussion. 1. Discuss Meeting Cadence * Two proposals: * Maintain bi-weekly meetings but extend to 90 minutes * Move to weekly 60-minute meetings * Decision deferred to mailing list discussion for consensus. Action Item: SC to reply to ICANN Org Email regarding Meeting Cadence. 1. Update to GNSO Council * SC Chair to present to the Council on: * Progress on the report * Request for guidance: Should the report go out for public comment? * SC Chair will present the options to Council, clarifying the scope and nature of this team`s work and discuss public comment. 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>

1 0

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

April 7, 2025

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

Action needed | Doodle | RDRS meeting cadence
by Terri Agnew April 7, 2025

April 7, 2025

Hello all, As discussed on today’s meeting, the meeting cadence may need to be changed up from bi-weekly, 1-hour meetings to either weekly 1-hour meetings or bi-weekly 1.5-hour meetings. Please complete the doodle to help determine the path forward. * If weekly 1-hour meetings, select 14 April, 21 April, and 28 April all at 17:30 UTC for 1-hour * If bi-weekly 1.5-hour meeting, select 21 April either 17:00 or 17:30 UTC for 1.5 hour Reminder, this is not only for April meetings but to adjust the meeting cadence going forward. Doodle: https://doodle.com/meeting/participate/id/aO6g4RLe Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

Meeting Invitation | RDRS Standing Committee | Monday, 21 April 2025
by Terri Agnew April 7, 2025

April 7, 2025

Dear all, The next RDRS Standing Committee call is scheduled for Monday, 21 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/2n2e47sh 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, 07 April 2025
by Terri Agnew April 7, 2025

April 7, 2025

**Starting in 15 minutes 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

REMINDER | Meeting Invitation | RDRS Standing Committee | Monday, 07 April 2025
by Devan Reed April 4, 2025

April 4, 2025

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

Draft Chapter 3 and Proposed agenda
by Feodora Hamza April 2, 2025

April 2, 2025

Dear RDRS SC members, Please find below the proposed agenda for our next meeting. Proposed Agenda for RDRS SC Call 7 April 17:30 UTC 1. Welcome 2. Review Chapter 3 (flagged issues) 3. Discuss Meeting Cadence 4. Update to GNSO Council 5. AOB In addition, please see below the draft chapter 3 for your review. Chapter 3 focuses on Assignment #3 – “Specific lessons learned that should be factored into the consideration of how to proceed with the SSAD recommendations”. * Draft Chapter 3 - https://docs.google.com/document/d/1c2Nm5s1Q-4jrAqWvsurH-k6BhpyanGIW/edit#h… The SC is kindly asked to review the draft chapter and flag any items that need further discussion. The flagged items will be discussed during the RDRS Call on 7 April. Kind regards, Feodora and Caitlin

1 0

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