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 Monday, 23 September at 17:30 UTC. Kind regards, Feodora and Caitlin 2024-09-09 RDRS Standing Committee - Meeting #16<https://community.icann.org/pages/viewpage.action?pageId=347373592> 1. Welcome 2. impressions document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1XFK-RCT5N...> New Tabs * Feedback for final report (Tab 4) * ICANN Org introduced Tab 4, designed to collect feedback from the Standing Committee for the final report. * The top of the tab lists the four assignments relevant to the Standing Committee’s mandate. Below this, there is space for committee members to contribute observations, comments, and suggestions they believe should be included in the final report. * Members are encouraged to begin populating this tab with their insights as the pilot progresses. The idea is to gradually build the report while still in the middle of the pilot rather than waiting until the end. * Engagement/Outreach Tracker (Tab 5) * ICANN Org presented the Engagement/Outreach Tracker (Tab 5), developed to log events related to RDRS. * Members are 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). * ICANN Org emphasized the need for tracking external engagement to gauge the effectiveness of outreach efforts. * The tracker includes a link to ICANN's generic deck, flyers, FAQs, and other resources, which can be used during events. * Unowned requests (Tab 10) * SC Chair discussed unowned enhancement requests and called for SC owners to take ownership of these items. * Some enhancements remain without owners. Members were encouraged to review and claim where relevant. * SC Chair stressed the importance of having a designated champion for each request to ensure that the suggestions are thoroughly understood and prioritized correctly. Items that do not gain an owner may need to be dropped or deprioritized. 1. Update on latest enhancements requested * ICANN Org explained the estimated time needed based on LoE. * Low LoE: 1 -3 months * Medium LoE: 4 to 6 months * High LoE: 7 to 12 months AI: ICANN Org to add the explanation in the Impressions Document. * Registrar Item 2 & 18 * ICANN Org provided updates: * Item 18 (Return to the list of pending requests after completion): Expected completion by the end of October 2024. * Item 2 (Allow registrars to change the request category): Work to begin in November, with an initial time estimate of four to six months, but this timing may be sooner and ICANN org will provide an update on completion once the work has started. * Requestor Item 1 * Requestor Country and Jurisdiction Metrics: A low level of effort enhancement slated for completion around November 2024. Data will aggregate countries with a small number of requestors into a collective "Other" category to maintain privacy. * Data for these two metrics will not go back to launch * Requestor country metric will go back to end of June 2024 * Jurisdiction metric will be calculated from the date of metric creation going forward. 1. Events: Standing Committee Participation * 17 September RDRS Webinar * Volunteers were sought for the 17 September RDRS webinar. * One volunteer for requestor, but no volunteers for registrar * Prep Week Session: 30 October 2024 * SC Chair asked for volunteers to lead or participate in the session. 2. AOB * Reporting Cadence Discussion * Discussion on transitioning to a monthly CSV and quarterly formal reports. * Registrars were not opposed to the monthly CSV reports but emphasized the importance of making all reports, including the CSVs, public for transparency. * ICANN Org clarified that technical work is handled separately, so any change in report frequency would not affect development timelines. * ICANN 81 * Steve DB noted that during ICANN80 there were three meetings related to RDRS. (SC meeting, CSG, Roundtable discussion). He suggested that the group considers repeating these types of sessions for ICANN81 as they were fruitful in Kigali. He emphasized the need for a potential CSG-led RDRS session as it took place in Kigali. * It was proposed that Sarah could lead a roundtable with a different focus than Kigali. Sarah offered to share her template with others who may want to organize the roundtable, as she will attend ICANN81 remotely. * Broader RDRS Tool Efficacy * Steve Crocker expressed concerns about the tool’s overall effectiveness and encouraged members to think critically about its long-term utility. 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>