November 2024 - Gnso-rdrs-sc

Proposed Agenda RDRS ICANN81 Session - Wednesday, 13 November 2024 at 16:30 local time (Istanbul)
by Feodora Hamza Nov. 7, 2024

Nov. 7, 2024

Dear members of the RDRS SC, Please see below the proposed agenda for the RDRS ICANN81 session taking place on Wednesday, 13 November 2024 at 16:30 local time (Istanbul). Proposed Agenda 1. Welcome 2. Brief Overview of 1-year RDRS 3. Discussion on Pilot’s Current Status and Defining Next Steps * What trends have been identified so far? * What has one year of RDRS taught us? 4. Recommendations for the Final RDRS Pilot Report * Walkthrough of SG feedback from RDRS Workbook 5. AOB Please also note one pending Action Item in preparation for ICANN81: SC members are kindly requested to include similar feedback and observations on 1-year RDRS (as the Rrs did) to the Workbook<https://docs.google.com/spreadsheets/d/1XFK-RCT5Nv-KcNgX4eQunkUKgSI35Yc_nUZ…> (Feedback for Findings Report Tab) prior to ICANN81. Objectives of the ICANN81 session as discussed on 4 November: * Discussion on the preliminary recommendations for the final RDRS report, including: * 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. * 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, including: * 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. Looking forward to seeing you all in Istanbul. Safe travels. Kind regards, Feodora and Caitlin 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

2024-11-04 RDRS Standing Committee - Meeting #20
by Feodora Hamza Nov. 6, 2024

Nov. 6, 2024

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(a)icann.org<mailto:feodora.hamza@icann.org> Website: www.icann.org<http://www.icann.org>

1 0

Post call | RDRS Standing Committee | Monday, 04 November 2024
by Julie Bisland Nov. 4, 2024

Nov. 4, 2024

Dear all, The recordings for the RDRS Standing Committee call held on Monday, 04 November 2024 can be found on the agenda wiki page <https://community.icann.org/x/IIC0F> (attendance included) and the GNSO Master Calendar<https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…>. These include: * Attendance (please let me 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, Julie Policy Team Supporting the GNSO

1 0

ICANN81 Session | RDRS Standing Committee work session | Wednesday, 13 November 2024
by Julie Bisland Nov. 4, 2024

Nov. 4, 2024

Dear all, The next RDRS Standing Committee call takes place during ICANN81 on Wednesday, 13 November 2024 at 16:30 local time. Remember, you must be registered for ICANN81. The session page on the ICANN81 Sched page is here: https://icann81.sched.com/event/1p2L6/gnso-rdrs-standing-committee-work-ses… ... Zoom participation links will be published here 24 hours before the session starts. 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…> * ICANN81 Wiki agenda page: https://community.icann.org/x/1QEiFg Thank you. Kind regards, Julie Policy Team Supporting the GNSO

1 0

**10-MINUTE REMINDER** Meeting Invitation | RDRS Standing Committee | Monday, 04 November 2024
by Julie Bisland Nov. 4, 2024

Nov. 4, 2024

**10-MINUTE REMINDER** Dear all, The next RDRS Standing Committee call is scheduled for Monday, 04 November 2024 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…> * Wiki agenda page: https://community.icann.org/x/IIC0F * Check your time zone: https://tinyurl.com/5ymc4su2 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

Re: Questions about timing and outputs
by Gabriel Andrews Nov. 1, 2024

Nov. 1, 2024

These are good questions to have answers to now, so we can be sure we're paying attention to the right things over this next year. Heck, here's another one: * Who is responsible for answering the below Qs? (ICANN Org? GNSO? RDRS SC itself?) From: Paul McGrady via Gnso-rdrs-sc <gnso-rdrs-sc(a)icann.org> Sent: Friday, October 25, 2024 9:14 AM To: gnso-rdrs-sc(a)icann.org Subject: [EXTERNAL EMAIL] - [Gnso-rdrs-sc] Questions about timing and outputs I recall that the RDRS is meant to be a 2 year experiment. If I recall correctly, we are done with one year. Here are my questions: * What is going to be the work product we give to Council at the end of the second year? * When are we going to start drafting a preliminary report we out for comment? * Will Staff do the first draft of the initial report, or do we need a subset of this team to start drafting? * When is our final report due? * If that is after the end of year two, does the RDRS keep running until the final report is completed and submitted to Council or is two years the finish line? Best, Paul [cid:image001.jpg@01DB26C9.734C64F0] Paul McGrady Partner Elster & McGrady 1030 16th Ave. S Floor 2 Nashville,TN 37212 3847 N. Lincoln Avenue Second Floor Chicago, IL 60613 Office Direct: +1 (312) 515-4422 paul(a)elstermcgrady.com<mailto:paul@elstermcgrady.com> www.elstermcgrady.com<http://www.elstermcgrady.com/>

4 3

Follow-up Items from Standing Committee Call on 21 October 2024: GSE Outreach List and Mockups for Metrics 18 & 19
by Lisa Carter Nov. 1, 2024

Nov. 1, 2024

Hello Standing Committee Members, As a follow up to several items discussed on the Standing Committee call on 21 October, I’d like to share the following information: The list of organizations that the ICANN Global Stakeholder Engagement (GSE) team engaged with for RDRS (see attached excel file). A mock up for Metric 18 (see attached PDF for chart), which displays the disclosure requests by country code and request category, (including the law enforcement request category). Tracking for this metric began in June 2024, and a CSV will be provided for this metric when the October RDRS Usage Metrics Report is published in November. A mock up for Metric 19 (see attached PDF for chart) which displays the disclosure requests by processing jurisdiction and request category (including the law enforcement request category). Tracking for this metric began in October 2024, and a CSV will be provided for this metric when the October RDRS Usage Metrics Report is published November. We can discuss any questions or feedback you have on these items on our call on Monday, 4 November. Have a great weekend. Kind regards, Lisa Carter Sr. Program Manager, Strategic Initiatives Internet Corporation for Assigned Names and Numbers (ICANN) Telephone: +1 310 578 8953 Email: lisa.carter(a)icann.org Skype: lisa.carter.icann www.icann.org

1 0

REMINDER | Meeting Invitation | RDRS Standing Committee | Monday, 04 November 2024
by Devan Reed Nov. 1, 2024

Nov. 1, 2024

Dear all, The next RDRS Standing Committee call is scheduled for Monday, 04 November 2024 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…> * Wiki agenda page: https://community.icann.org/x/IIC0F * Check your time zone: https://tinyurl.com/5ymc4su2 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