October 2024 - Gnso-rdrs-sc

Upcoming RDRS Standing Committee calls
by Devan Reed Nov. 13, 2024

Nov. 13, 2024

**We are sending in advance to get dates on everyone’s calendar. Dear all, The .ics is attached for next 8 calls for the RDRS Standing Committee; dates are listed below. The calls take place at 17:30 UTC for 60 minutes. * Monday, 11 March 2024 (invite has been sent) * Monday, 25 March 2024 * Monday, 08 April 2024 * Monday, 22 April 2024 * Monday, 06 May 2024 * Monday, 20 May 2024 * Monday, 03 June 2024 * Monday, 17 June 2024 You should have received an email invite for the next meeting, 11 March; future invites will be sent out closer to the date of the calls. Thank you. With kind regards, Devan

2 1

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

Proposed Agenda RDRS Standing Committee Meeting on Monday, 4 November 2024 at 17:30 UTC
by Feodora Hamza Oct. 31, 2024

Oct. 31, 2024

Dear members of the RDRS Standing Committee, Please find below the proposed agenda for the next meeting. RDRS Standing Committee Meeting on Monday, 4 November 2024 at 17:30 UTC Proposed Agenda 1. Welcome 2. Europol Session Update (Gabe) 3. ICANN81 Session planning: * How to maximize the face to face at ICANN? * What trends have been identified so far? * What has one year of RDRS taught us? * Walkthrough of registrar feedback 4. Metrics * September Usage Metrics * Metric 19 Preview (Is this the last metrics change/update)? 5. Enhancements update 6. AOB 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>

2 1

ICANN81 GNSO Policy Briefing & ICANN81 Policy Outlook Report
by Julie Bisland Oct. 29, 2024

Oct. 29, 2024

Dear All, On behalf of the GNSO Team, I am happy to report that the GNSO Policy Briefing for ICANN81 is now available for download: http://go.icann.org/gnsobriefing. In addition, the ICANN81 Policy Outlook Report is available: https://go.icann.org/outlook81 Happy reading! Best Regards, Julie -- Julie Bisland Policy Operations Sr. Coordinator (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: 79613b691cb8a6c1 Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

1 0

2024-10-21 RDRS Standing Committee Meeting Notes
by Caitlin Tubergen Oct. 25, 2024

Oct. 25, 2024

Dear members of the Standing Committee, Please find below the high-level notes from this week’s meeting. The next meeting is scheduled for Monday, 4 November at 17:30 UTC. Kind regards, Feodora and Caitlin -- RDRS Standing Committee Meeting 21 October 2024 1. Welcome 2. ICANN Standards of Behavior * This is a necessary reminder that all Standing Committee members are governed by ICANN’s Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en#:~:t…'s%20assets%20and,a%20responsible%20and%20principled%20way.> * During our last meeting, there was a comment made to an ICANN org staff member where inappropriate language was used – please remember to be respectful of all participants, including ICANN org staff. 1. Pending Action Items * Please remember to document any outreach events you participate in using the RDRS Outreach Tab<https://docs.google.com/spreadsheets/d/1XFK-RCT5Nv-KcNgX4eQunkUKgSI35Yc_nUZ…> of the RDRS Standing Committee Workbook. * The action item related to providing a rationale for reporting of countries associated with law enforcement requests will be discussed later in this meeting under Item 8. 1. GSE Presentation on RDRS Outreach and Engagement * The Global Stakeholder Engagement (GSE) Team is dividing its engagement into two buckets: (i) working with registrars in the region to increase participation, and (ii) working with potential requestors to direct them to the system to submit requests. * GSE has primarily focused on the second bucket – working on requestor awareness across the five ICANN regions * We have distributed translated written materials, conducted webinars in various time zones and multiple styles to account for different audience needs, and reached out to key stakeholders in the various regions – for example, law enforcement has been very helpful in disseminating information * We have worked closely with our Communications Team who helped create a tool kit for us to use as we meet more potential requestors * As we look to the future, we will continue participating in technical engagement events, civil society events, and governmental events to discuss the RDRS. * SC question: With respect to cyber security professionals and researchers, there are two groups: (i) security practitioners who are aligned with law enforcement, and (ii) researchers who do research on a longitudinal basis, which is broader. These groups should not be lumped together because they are distinct. * Will endeavor to take this under consideration, but this may be difficult to report on. * SC question: When you reach out to law enforcement, are you usually making groups aware for the first time or are they already familiar with the RDRS? * Speaking particularly from Latin American and the Caribbean, there have been some shifts. One year ago, all groups were hearing about this for the first time; now, there are more agencies (for example in Argentina) that are familiar, and we believe this will continue. * SC: believe we are making good progress, and appreciate all of these efforts. To that end, there is one system that everyone already knows about (Whois) where we should consider putting a message that says “for redacted data, go here” to reach as many users as possible. * SC: how are outreach efforts considering registrants? Also, it would be helpful to know, for the sake of transparency, which law enforcement agencies you work with. * We have worked with the RALOs for particular awareness for registrants. GSE could prepare additional information to drill down on the law enforcement agencies we have contacted. 1. Discussion on Vice Chair Selection for RDRS SC * To help manage the work of the SC and assist from a leadership perspective, Sebastien reached out to John McElwaine to see if he would be willing to serve as vice chair, provided the SC does not object. * John has graciously agreed to serve in this role – are there any objections to this? * No objections: John M. will serve as vice chair or the RDRS SC. 1. ICANN81 Session preparation * We will discuss this at the next meeting due to limited time today * Would like to get the ball rolling with the report to Council. Registrars have been working on this, but would appreciate input from other groups * Encourage all members to come prepared to discuss what we have learned so far in reviewing the metrics * SC: registrars plan to submit some thoughts next week, so that it will be well in advance of ICANN81 * SC: note that the BC believes the considering the pilot as a predictor of demand is incorrect and would be a terrible assessment of demand * Suggest discussing this more during ICANN81 due to time constraints today 1. Update on RDRS to GNSO Council * Update will continue at ICANN81 due to time constraints during the October Council meeting; however, wanted to note that Sebastien will send a draft letter to the Council (making sure that RDRS SC is sticking to its scope). Plan to share this letter with the RDRS SC next week. * ACTION: Sebastien to share draft letter to GNSO Council with RDRS SC by 1 November 2024. 1. Europol RDRS Webinar Feedback * Deferred to next meeting 1. Discussion on Metric 18 and 19 * ICANN org: Thank you for the feedback during the last meeting. * There is a lot of data in the monthly metrics reports, and it’s important that ICANN org understood precisely what the Standing Committee was asking for. * ICANN is committed to working with the SC to ensure you have the data that you need to fulfill your scope of work. * ICANN looked at the ask closely and has two mock-ups to share with the group. Metric 18 breaks down the requests by law enforcement type, and the country where the law enforcement requestor is coming from. * Similarly, Metric 19 breaks down the data, but this breaks it down by the jurisdiction where the data is being processed. * With this, there are two important caveats: * (1) RDRS does not have an authentication mechanism – this means, in practice, that we do not actually know if the requestor is from law enforcement. It is a self-selected field by the requestor. * (2) Within the RDRS, ICANN is not the recipient of the requests. Accordingly, ICANN is not evaluating or making determinations on requests. * While we propose to include this data in the next monthly report, it may require the production of a separate CSV. * SC: as a registrar receiving the request, we would have the same issue because we do not know if a request marked as law enforcement is actually coming from law enforcement. Also, can we get the data of all countries? * ICANN: Yes, the breakdown will be by country. * SC: the concern is that this is self-reported, unverified data, so perhaps the inclusion of a disclaimer could be helpful here. A CSV will be fine. * ICANN: The next report will include the data requested – a breakdown of self-reported law enforcement requestors by country. Also, would like to highlight that because ICANN is not the recipient of the requests, the example of a transparency report from a company like Google is not analogous to ICANN’s reporting. There was some confusion about the claim of lack of transparency. With the understanding that the data being provided is not from authenticated law enforcement agencies, ICANN can provide the data to the RDRS SC. The RDRS SC will see this data for the October report, which will be published shortly after ICANN81. * The exact format of the data (CSV, PDF, etc.) is still being worked out. 1. AOB * None.

1 0

Questions about timing and outputs
by Paul McGrady Oct. 25, 2024

Oct. 25, 2024

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@01DB26CE.ECFE5150] 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/>

1 0

ICANN81 GNSO Sessions - How to Get Organized / Remote Participation Details
by Julie Bisland Oct. 21, 2024

Oct. 21, 2024

Dear all, With ICANN81<https://meetings.icann.org/en/meetings/icann81/> just around the corner, please take a moment to read the information below for a seamless and successful meeting. REGISTER NOW! DEADLINE FOR IN-PERSON REGISTRATION IS 08 November 2024! * Sign into Your ICANN Account or create an account here<https://account.icann.org/login>. * Register by selecting the Meeting Registration tile. * Click on the Registration link. NOTE: On-site registration will not be available so you must register in advance. In-person, advance registration will close on 08 November 2024. After that point in time, only virtual participation will be open for continued registration. Before creating your schedule, please read this page carefully: https://meetings.icann.org/en/remote-participation. If participating on-site, please read the Frequently Asked Questions here<https://meetings.icann.org/en/meetings/icann81/#faq>. CREATE YOUR MEETING SCHEDULE * Access the schedule here<https://icann81.sched.com/>. The schedule shows up with blank circular radial buttons to the left of each session. Hover over the radial button and click “ADD TO MY SCHEDULE” or just click to add the checkmark. * Once you’ve selected all sessions, click the My Schedule link in the lower left corner or hover over your profile and select My Schedule. * Click the Phone icon, “Mobile App + iCal” (located on the right side of the page) * In the bottom section, “Export Calendar”, click the link next to “My Schedule”. When the .ics is exported, add it to the appropriate calendar. OR, after exporting, drag and drop the .ics file into your calendar. * Please remember, for security purposes, participation links will be posted 24-hours prior to the session start times. There will be no calendar invitations sent, as the meeting schedule allows you to download all sessions of interest to your individual calendars Review the Participation Tools and update Zoom * All sessions will use Zoom rooms. Access details are available 24hrs prior. * Visit the Participation Tools page<https://meetings.icann.org/en/remote-participation> for links to download the latest version of Zoom for access to the ICANN Meeting sessions. * Please see the ICANN Meeting VIRTUAL AND IN-PERSON PARTICIPATION GUIDES for more information on how to get the most out of the virtual meeting tools. Links to Bookmark ICANN81 Meeting Schedule<https://icann81.sched.com/> ICANN81 GNSO Remote Participation Wiki Page<https://community.icann.org/x/gwAiFg> GNSO Session agendas<https://community.icann.org/x/gYDKF> REMINDER: Walk-up and registrations after 08 November will not be accepted. All walk-up and late registered attendees will only have access to virtual participation. To make the most of Zoom’s features, update to the latest version of Zoom<https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0060716>. For all GNSO meeting-related queries (RP or others), please email us at: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team -- Julie Bisland Policy Operations Sr. Coordinator (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: 79613b691cb8a6c1 Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

1 0

Post call | RDRS Standing Committee | Monday, 21 October 2024
by Julie Bisland Oct. 21, 2024

Oct. 21, 2024

Dear all, The recordings for the RDRS Standing Committee call held on Monday, 21 October 2024 can be found on the agenda wiki page <https://community.icann.org/x/HoC0F> (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

Meeting Invitation | RDRS Standing Committee | Monday, 04 November 2024
by Julie Bisland Oct. 21, 2024

Oct. 21, 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

**STARTING IN 2 MINUTES** Meeting Invitation | RDRS Standing Committee | Monday, 21 October 2024
by Julie Bisland Oct. 21, 2024

Oct. 21, 2024

**STARTING IN 2 MINUTES** Dear all, The next RDRS Standing Committee call is scheduled for Monday, 21 October 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/HoC0F * Check your time zone: https://tinyurl.com/mvzj8vj6 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