Dear members of the RDRS SC, Please find below the main discussion points and action items from this week`s meeting. The next meeting is scheduled for Wednesday, 13 November 2024 at 16:30 local time (Istanbul). Kind regards, Feodora and Caitlin 2024-11-04 RDRS Standing Committee - Meeting #20<https://community.icann.org/pages/viewpage.action?pageId=347373600> AI: SC members are kindly requested to include similar feedback and observations on RDRS (as the Rrs did) to the Workbook prior to ICANN81. AI: SC encouraged to review the workbook for any additional requestor or registrar enhancement (that currently have an owner) that the SC should consider adding to the queue for ICANN. 1. Welcome SC chair welcomed all attendees and initiated the meeting. ICANN Org reviewed pending action items, noting: * AI: ICANN Org following up to confirm they can provide the list of LEA's that were contacted for RDRS. - Completed - ICANN Org shared the list last week via Email. * AI: Chair Letter to GNSO Council. Still pending * AI: SC Members to populate initial Feedback for SC discussion for the RDRS SC Findings Report (assignment per its Charter) within the tab of this Workbook, titled Feedback Findings Report. - In process - Registrard details added. * AI: SC Members to log any events, meetings, or webinars they participate in related to RDRS, especially those focused on engaging stakeholders outside the immediate ICANN community (e.g., registrars, registrants, law enforcement) in the RDRS SC Outreach Tab of this Workbook. Still pending * AI: SC Chair suggested to inquire the GNSO Council about the follow up policy process after the RDRS pilot phase ends. Still pending 2. Europol Session Update Gabriel recapped his recent presentation at a Europol session in The Hague. Key points included: * The session focused on introducing the RDRS tool to law enforcement practitioners. * A live demo of a data request through the RDRS test domain, which was provided for training purposes. * Limited prior awareness among law enforcement about the RDRS, with only one participant familiar with it. * Challenges reported by users, such as confusion when requested information was already publicly available, often due to privacy proxy services. * Gabriel highlighted that the lack of understanding about proxy service responses remains a pain point, necessitating ongoing user education. 3. ICANN81 Session Planning The SC discussed objectives for the upcoming ICANN81 public session. Objective of the ICANN81 Session: * The SC discussed the structure and focus of the upcoming ICANN81 public session, aiming to make it a working group session that emphasizes tangible outcomes rather than a general community update. * Since a comprehensive RDRS overview was already provided during the ICANN prep week, the general consensus was to limit updates and instead concentrate on engaging directly with actionable discussions. Outline for ICANN81 Session: 1. Brief Overview/Recap for Public Attendees: * The session will begin with a very brief summary of the RDRS project and its objectives, to orient any public attendees unfamiliar with recent updates. * This section will include a slide with a link to the prep week session recording, allowing attendees to review the in-depth background information at their convenience. * If possible, the prep week recording will also be linked in the session’s public agenda to help manage expectations for those new to the topic. 1. Focus on Drafting Recommendations for the Final RDRS Pilot Report: * The main agenda item will be a working discussion on the preliminary recommendations for the final RDRS report, with a particular focus on: * User experiences and issues encountered (both registrars and requesters). * Feedback themes, including the need for more education and better user support materials, especially regarding responses from proxy services. * Key challenges identified in law enforcement’s use of RDRS, such as low initial awareness of the system and a lack of clarity on certain response categories. 1. Assessment of Pilot’s Current Status and Defining Next Steps: * The committee will review the current state of RDRS pilot metrics, enhancements, and any additional pending items to ensure that all critical feedback and observations are addressed in the final report. * The discussion will cover: * The effectiveness of implemented enhancements and the impact on user experience. * Any remaining enhancement requests that have not been prioritized, with a focus on deciding if they should be included in the final report as recommendations for future improvements. * Gabriel Andrews raised that it might be essential to highlight the impact of resource limitations on the pace of feature rollouts, which should be documented for transparency in the final report. AI: SC members are kindly requested to include similar feedback and observations on RDRS (as the Rrs did) to the Workbook prior to ICANN81. 4. Metrics ICANN Org reviewed recent RDRS metrics, specifically: * Metric 19 Preview: This will display disclosure requests by jurisdiction and request category, expected in the November 15 report. The metric format was displayed, with minor feedback about ensuring consistency in country code usage. * Discussion on whether this would be the final metrics update. The group agreed that future metric adjustments may be postponed unless significant feedback warrants it. 5. Enhancements Update ICANN Org provided an update on ongoing enhancements: * Test domain rdrs.test has been created to help Gabe and team with their front end solution work for RDRS and law enforcement. * Registrar Item 18 in the impressions document has been completed. * Requestor Item 7: Gabe and team have received the RDRS schema and test domain requested from ICANN. * The RDRS UI “Submission Completion” page has been updated to include language to invite requestors to share their user experiences with ICANN directly. * Work on Item 2 for registrars (ability to change RDRS request category) will be started after ICANN81, but will take 3 sprints to complete which means the feature won’t be available until January 2025. AI: SC encouraged to review the workbook for any additional requestor or registrar enhancement (that currently have an owner) that the SC should consider adding to the queue for ICANN. 6. AOB * ICANN Org encouraged members to help promote ICANN81 user experience interviews during ICANN81 for further user insights. * Paul McGrady suggested expanding outreach to organizations like INTA for broader feedback, particularly from non-technical stakeholders. * Upcoming Event: Sara mentioned a meeting with the Royal Canadian Mounted Police taking place on 5 November w/ ICANN. She will discuss registration data and Lisa will demo RDRS. Feodora Hamza Policy Development Support Manager (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +32 496 30 24 15 Email: feodora.hamza@icann.org<mailto:feodora.hamza@icann.org> Website: www.icann.org<http://www.icann.org>