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

Circle ID Article: eco Provides Recommendations for the Effective Use of ICANN’s Registration Data Request Services (RDRS)
by Lisa Carter Aug. 2, 2024

Aug. 2, 2024

Hi All, Thought I’d share for those who may not have seen it yet. Circle ID just published this article about eco’s recommendations for effective use of RDRS along with the downloadable guide. Thanks Lisa Carter Sr. Program Manager, Strategic Initiatives ICANN From: Lisa Carter via Gnso-rdrs-sc <gnso-rdrs-sc(a)icann.org> Reply-To: Lisa Carter <lisa.carter(a)icann.org> Date: Monday, July 15, 2024 at 6:45 AM To: "gnso-rdrs-sc(a)icann.org" <gnso-rdrs-sc(a)icann.org> Subject: [Gnso-rdrs-sc] Re: The June RDRS Usage Metrics report is published. Hi All, The RDRS Usage Metrics Report covering 1-30 June has been published to the RDRS page. https://www.icann.org/en/system/files/files/rdrs-usage-metrics-15jul24-en.p… Thanks. Lisa Carter Sr. Program Manager, Strategic Initiatives ICANN

1 0

2024-07-29 RDRS Standing Committee - Meeting #13
by Feodora Hamza July 30, 2024

July 30, 2024

Dear members of the Standing Committee, Please find below the main discussion points and action items from this week`s meeting. The next meeting is scheduled for Monday, 12 August at 17:30 UTC. Kind regards, Feodora and Caitlin 2024-07-29 RDRS Standing Committee - Meeting #13<https://community.icann.org/pages/viewpage.action?pageId=347373586> 1. Welcome * The SC chair provided an update on a pending letter to Greg, noting delays due to a demanding project but reassured attendees it remains a priority. The current project deadline is tomorrow, which is anticipated to free up time for additional tasks. AI: SC Chair to finalize and send the letter to GNSO Council. 2. RDRS Usage Metrics Report * Standing Committee feedback/questions on recent Metrics Usage Report<https://www.icann.org/en/system/files/files/rdrs-usage-metrics-15jul24-en.p…> * ICANN Org provided an overview of the metrics, highlighting new additions and clarifying data representations in particular metric 10. * BC suggested incorporating percentages alongside numerical data in metric 10 to enhance clarity and trend analysis. The feasibility of such an addition was discussed, considering potential volume and expanding requirements. * SC members raised concerns about data presentation consistency across different metrics. * SC members queried the high percentage of "not supported" domains compared to the low percentage of ccTLDs. * ICANN Org explained that unsupported domains include ccTLDs, incorrect formats, or non-existent domains. A significant portion may be due to incorrect domain formats or random strings. * SC Chair suggested scheduling a detailed discussion with Simon or relevant experts for further clarification on metrics data. AI: ICANN Org to invite Simon or another expert to discuss metrics in the next call. 3. Impressions Document <https://docs.google.com/spreadsheets/d/1XFK-RCT5Nv-KcNgX4eQunkUKgSI35Yc_nUZ…> Management 4. Impressions Document<https://docs.google.com/spreadsheets/d/1XFK-RCT5Nv-KcNgX4eQunkUKgSI35Yc_nUZ…> Review & Prioritization * Farzaneh Badii discussed implementing law enforcement location reporting and distinguishing between "per country" and "per economy" in reports. The goal is accurate jurisdiction reporting for territories like Taiwan. * ICANN Org confirmed that the dropdown list includes economies and that the technical team has considered this in the system. * Discussion followed on whether to include all request types or limit to law enforcement, with consensus leaning towards including all types for comprehensive data reporting. * ICANN Org has removed the change requests without an SC Owner from the main tables and added them to a separate tab. AI: SC members to provide additional information on the specific metric information to be displayed as requested by ICANN Org in the impressions document for item #1 on the requestor tab. 5. AOB * SC members raised the need to compile responses to the Council regarding assignment questions and suggested evaluating the stability of request data to determine if the project should continue for the full timeline. * SC Chair proposed improving post-request surveys to gather more comprehensive feedback. * ICANN Org noted updates to survey communications and ongoing discussions about refining questions and increasing response rates. 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

Post call | RDRS Standing Committee | Monday, 29 July 2024
by Julie Bisland July 29, 2024

July 29, 2024

Dear all, The recordings for the RDRS Standing Committee call held on Monday, 29 July 2024 can be found on the agenda wiki page <https://community.icann.org/x/EoC0F> (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 [lists.icann.org]<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, 12 August 2024
by Julie Bisland July 29, 2024

July 29, 2024

Dear all, The next RDRS Standing Committee call is scheduled for Monday, 12 August 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/FIC0F * Check your time zone: https://tinyurl.com/4uy5p3px 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

**10-MINUTE REMINDER** Meeting Invitation | RDRS Standing Committee | Monday, 29 July 2024
by Julie Bisland July 29, 2024

July 29, 2024

**10-MINUTE REMINDER** Dear all, The next RDRS Standing Committee call is scheduled for Monday, 29 July 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/EoC0F * Check your time zone: https://tinyurl.com/3xhcxcbw 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, Devan Policy Team Supporting the GNSO

1 0

REMINDER | Meeting Invitation | RDRS Standing Committee | Monday, 29 July 2024
by Devan Reed July 26, 2024

July 26, 2024

Dear all, The next RDRS Standing Committee call is scheduled for Monday, 29 July 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/EoC0F * Check your time zone: https://tinyurl.com/3xhcxcbw 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, Devan Policy Team Supporting the GNSO

1 0

Proposed agenda - RDRS Standing Committee Meeting - Monday, 29 July @ 17:30 UTC
by Caitlin Tubergen July 25, 2024

July 25, 2024

Dear RDRS Standing Committee Members, Please find below the agenda for the upcoming meeting of the RDRS Standing Committee on Monday, 29 July 2024 at 17:30 UTC. Best regards, Feodora and Caitlin -- RDRS Standing Committee Meeting Monday, 29 July 2024 at 17:30 UTC Proposed Agenda 1.Welcome 2. RDRS Usage Metrics Report * Standing Committee feedback/questions on recent Metrics Usage Report<https://www.icann.org/en/system/files/files/rdrs-usage-metrics-15jul24-en.p…> 3. Impressions Document Management 4. Impressions Document Review & Prioritization 5. AOB

1 0

UPDATED RDRS Impressions Doc responsibilities
by Caitlin Tubergen July 24, 2024

July 24, 2024

Dear Members of the Standing Committee, We hope this message finds you well. As we continue our efforts to streamline our processes and achieve our strategic goals, we would like to provide you with clear instructions on how to effectively use the newly-formatted Impressions Document<https://docs.google.com/spreadsheets/d/1XFK-RCT5Nv-KcNgX4eQunkUKgSI35Yc_nUZ…>. Your proactive engagement with this document is crucial to our collective success. To make our meetings more productive and aligned with our strategic goals, it is imperative that each member thoroughly reviews and updates their change request(s) in the Impressions Document before the meetings. This preparation will allow us to move discussions forward efficiently and focus on decision-making rather than catching up on updates. Going forward, we will only discuss change requests that have SC owners during meetings. For items that do have owners but lack an SC agreement to proceed and an SC-designated priority level, we will use the meeting time to agree on these two items specifically. In order to move forward in this way, we request the following from the Standing Committee: * Each SC member is asked to go into the impressions document and review the items that are not currently owned by a SC member to see if they believe the item is important and would like to own it, noting that the SC will only discuss OWNED items during the meeting. Support staff will delete change requests without a dedicated SC owner after the next SC meeting (29 July). An SC Owner is responsible for the overall accuracy and relevance of the change request. SC members can include change requests outside the SC but need to agree to be the SC owner for them. This includes the following responsibilities: * For the items that are owned, SC owner is asked to review LoE notes from ICANN and Comments in advance of the meeting to see if ICANN org has added additional questions or comments. * SC owner should either be prepared to provide additional info during the meeting or additional information in Comments if unable to attend meeting. ICANN org will be unable to provide an LoE until outstanding questions are answered. * If there are follow-up questions from ICANN org regarding an agreed to item, the SC owner will also be ICANN staff's point person for the questions. The owner may update the full SC regarding follow-up discussions, where needed. * As the group moves through outstanding (and owned) suggestions during the meetings, Support Staff will take an action to update the sheet during the meeting, where possible or shortly thereafter. For example, if the SC agrees to a Priority 1, Support Staff will update the SC Agreed Priority ranking in the sheet. The SC Owner will be responsible for reviewing Support Staff's updates and confirm accuracy by COB Fridays following SC meetings. * When entering new change requests and when discussing to move ahead with change requests, please bear in mind the success criteria as confirmed by the ICANN Board to GNSO Council (Nov 2023). In other words, how will this specific change request meet the strategic goals of the RDRS SC? Your cooperation and commitment to this process are greatly appreciated. If you have any questions or need further clarification on how to use the document, please do not hesitate to reach out. Thank you for your continued dedication to our collective success. Best regards, Feodora and Caitlin

1 0

2024-07-15 RDRS Standing Committee - Meeting #12
by Feodora Hamza July 17, 2024

July 17, 2024

Dear members of the Standing Committee, Please find below the main discussion points and action items from this week`s meeting. The next meeting is scheduled for Monday, 29 July at 17:30 UTC. Kind regards, Feodora and Caitlin 2024-07-15 RDRS Standing Committee - Meeting #12<https://community.icann.org/pages/viewpage.action?pageId=347373584> AI: SC members to review and provide necessary information (SC ownership, further details for tech team, etc.) in impressions document for subsequent meetings. 1. Welcome * The SC Chair welcomed all participants and acknowledged recent challenges in updating the letter to the GNSO council. 2. Impressions Document Review & Prioritization * SC Chair emphasized the focus on reviewing the new Impressions Document, transitioning from a Google Doc to a Google spreadsheet format. * SC Chair noted previous discussions in Kigali and the need to revisit and update the document's progress and pending tasks. * SC Chair Highlighted specific locked columns (LoE, Notes on LoE, SC agreed Priority Ranking, SC consensus, Status ) for controlled updates, ensuring collaborative changes only when in full agreement with SC. * LoE, Notes on LoE and Status columns will be determined and managed by the ICANN support staff. * The other mentioned columns will be edited by ICANN support staff but agreed on during the SC meetings, where the group has the chance to discuss and agree on the way forward on each change request. * ICANN Org confirmed column access details, clarifying permissions for different sections of the document. * SC members directed attention to the reporting of jurisdiction and location data, particularly for law enforcement requests. * ICANN Org raised the technical team's need for specifics on data parsing and reporting requirements. * Steve queried registrars' handling of jurisdiction data in requests; Sarah provided insights on registrar practices. * SC Chair refined the question regarding jurisdictional information queried by registrars, highlighting complexity with multiple jurisdictions. * ICANN Org clarified the registrar form's request for information about countries/territories where data will be processed. * SC members asked about multiple answers to country selection for jurisdiction; ICANN Org confirmed requestors can select multiple countries where the data may be processed. * ICANN Org suggested to prioritize this request against the other requests already prioritized in the document. * Discussion on ccTLD inclusion in data access processes highlighted logistical challenges. * SC Members proposed evaluating the effort required to include ccTLDs in the data access process. * SC members suggested the discussion about ccTLD is not in the remit of SC. * ICANN Org indicated the Standing Committee should reference Lisa’s mailing list response to Gabe on 21 June for ICANN’s specific feedback on what it would take to include ccTLD in RDRS. * SC members recalled discussions on individual vs. entity accounts from the SSAD recommendations, noting the RDAP pilot streamlined to individual requester accounts. * SC members proposed a streamlined process for handling multiple requests, suggesting the feasibility of a bulk upload feature or API integration. * SC members asked for more information on what LoE is based on. * ICANN Org to provide a formal evaluation on the effort required for potential ccTLD inclusion in data access processes. AI: SC members to review and provide necessary information in impressions document for subsequent meetings. · SC members raised concerns regarding data visibility and sorting challenges in the registrar tab, requesting assistance in sorting by priority. 1. Preview of updated Metric 10 & Metric 8 were not previewed as time ran out, but ICANN org indicated that Metric 10 had been updated in the RDRS Metric Usage Report published on 15 July. 2. 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, 15 July 2024
by Devan Reed July 15, 2024

July 15, 2024

Dear all, The recordings for the RDRS Standing Committee call held on Monday, 15 July 2024 can be found on the agenda wiki page <https://community.icann.org/x/EIC0F> (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 [lists.icann.org]<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, Devan Policy Team Supporting the GNSO

1 0