December 2024 - Gnso-rdrs-sc

GAC inputs to RDRS SC workbook
by Fletcher, Owen Dec. 17, 2024

Dec. 17, 2024

Dear members of the RDRS SC, On behalf of the GAC, I have entered GAC inputs under the "Feedback for Findings Report" tab in the SC workbook. This feedback summarizes GAC comments from past communiqués. Please note further GAC discussion may result in additional comments on the assignment topics. Best regards, Owen Fletcher U.S. Alternate Representative to the ICANN Governmental Advisory Committee (GAC) National Telecommunications and Information Administration (NTIA) U.S. Department of Commerce

1 0

2024-12-16 RDRS Standing Committee - Meeting #22
by Feodora Hamza Dec. 17, 2024

Dec. 17, 2024

Dear RDRS SC member, Please see below the notes and action items from the last meeting. The next meeting is schedule for 13 January 2025 at 17:30 UTC. Wishing you all a joyful holiday season and a well-deserved break! Kind regards, Feodora and Caitlin 2024-12-16 RDRS Standing Committee - Meeting #22<https://community.icann.org/pages/viewpage.action?pageId=390332707> Action Item: SC Members are kindly requested to continue adding feedback and reviewing other members' observations in the workbook <https://docs.google.com/spreadsheets/d/1XFK-RCT5Nv-KcNgX4eQunkUKgSI35Yc_nUZ…> for the final report. 1. Welcome (2min) · Next meeting: 13 January 2024 – coincides with the eve of the GNSO Council Strategic Priorities Session. · Sebastien noted he will be traveling and unable to chair the meeting. · John has confirmed he can lead in Sebastien’s absence. 1. Pending AIs from Workbook [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1XFK-RCT5…> (3min) · Open Action Item: Input to the RDRS Standing Committee workbook. SC Members are kindly requested to continue adding feedback and reviewing other members' observations. * Key Points: * Feedback should include clear rationale and conclusions based on observed trends. * Two additional tabs have been added: “Rationale/Background” and “Comments Provided by Others.” * Next Steps: * Support staff will start populating the final report template. * Assignment 1 chapter will be shared ahead of the 13 January 2024 meeting for review. · SC Chair inquired about the timeline for pivoting the workbook (spreadsheet format) into a Word document. · ICANN Org confirmed that assignment-based chapters will be created and shared as Word documents. Raw data will remain in the workbook for reference. 1. Review SC final report feedback (30min) * Discussion on final report observations from Workbook * Suggest SC members use test domain, rdrs.test to help inform feedback for final report * “How to” video: How to use the system [youtu.be]<https://urldefense.com/v3/__https:/youtu.be/iTCaug10dRE__;!!PtGJab4!7h1xVE5…> * “How to” video: How to use the template [youtu.be]<https://urldefense.com/v3/__https:/youtu.be/HlDsW_xpRr4__;!!PtGJab4!7h1xVE5…> · Mark Anderson suggested asking ICANN Org for lessons learned in developing the current RDRS system (what worked, challenges, etc.). · Steve Crocker highlighted the need to consider the long-term roadmap: Is the current system permanent or temporary? Should a new system be designed from scratch? Proposed analyzing current gaps and future decision processes. · SC Chair added that SC does not assume that this system, as is right now plugged into salesforce, is the one to keep for the future. Someone should study the possibility of starting a new development session, possibly externalized. If the SC is under the above assumption, the next steps would be to keep the current RDRS as is and not develop it further but maintain it until a better system is in place? · The SC Chair asked to further consider how long would it take to get to a next version to see some of the improvements the SC has been looking for. For example, the API. · The SC Chair also asked the SC to consider if the SC assumes/recommends that there will be policy work needed after the RDRS pilot. For instance, to bring back the SSAD recommendations and consider what to propose on those? · Gabriel Andrews proposed a compare-and-contrast document between RDRS and the original SSAD policy recommendations. ICANN Org provided the WHOIS disclosure system design paper<https://www.icann.org/en/system/files/files/whois-disclosure-system-design-…> that includes a table comparing SSAD and RDRS. (Annex4) · Steve Crocker asked if the follow up system should focus only on contracted parties? · SC members pointed out that ccTLDs should be encouraged to participate and included in RDRS. · SC Chair noted the need to clarify whether future work would involve scaling back SSAD to fit RDRS or creating a new approach entirely? Creating test requests using rdrs.test ICANN Org encouraged SC members to: · Use the test domain to experience the RDRS system firsthand. · Review the training videos on using the system and templates. · Purpose: Provide further recommendations for system improvements. 1. Discuss presentation of metrics reports data for year 2 of RDRS pilot (20min) · ICANN Org informed the SC that for the second year of the pilot, ICANN will continue to show each month’s metrics in charts and graphs by changing the orientation of the page to landscape to accommodate additional months. Also, any updates to the data that are a result of registrars indicating decision dates for months past will be reflected in reports. Currently all reports only reflect the data that was originally gathered on the report generation date for any given month. · Feedback: * Steve Crocker questioned the utility of current data for measuring demand. Suggested it does not reflect “true demand” since existing processes and limitations may constrain usage. * Alan Greenberg stressed that the data cannot reliably measure demand and proposed focusing efforts on actionable insights. * ICANN org indicated that the current metrics were requested by the GSNO Small Team. 1. AOB (5min) * RDRS Surveys for year 2 of the pilot * ICANN Org informed about the low response rates for automated surveys. ICANN Org asked the SC if they see value in continuing the survey or if the one-on-one user experience interviews are sufficient. Both requestor and registrar UIs have a way for users to request interviews with ICANN. Gabriel Andrews supported keeping automated surveys to capture feedback from non-ICANN insiders who may not opt for interviews. 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

Re: The November RDRS Usage Metrics Report is Published.
by Lisa Carter Dec. 17, 2024

Dec. 17, 2024

Hello Standing Committee Members, ICANN has just published the November RDRS Metrics Usage Report: December 2024 (reporting period: 1 November – 30 November 2024) [PDF] [CSV] [CSV 18] [CSV 19] Enjoy the break and see you in 2025! Best, Lisa Carter Sr. Program Manager, Strategic Initiatives ICANN

1 0

Post call | RDRS Standing Committee | Monday, 16 December 2024
by Devan Reed Dec. 16, 2024

Dec. 16, 2024

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

1 0

Meeting Invitation | RDRS Standing Committee | Monday, 13 January 2025
by Devan Reed Dec. 16, 2024

Dec. 16, 2024

Dear all, The next RDRS Standing Committee call is scheduled for Monday, 13 January 2025 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…> and the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…> * 2025 Wiki agenda pages: https://community.icann.org/x/JwFEFw * Check your time zone: https://tinyurl.com/2v4t72w2 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

15 MINUTE REMINDER | Meeting Invitation | RDRS Standing Committee | Monday, 16 December 2024
by Devan Reed Dec. 16, 2024

Dec. 16, 2024

Dear all, The next RDRS Standing Committee call is scheduled for Monday, 16 December 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…> and the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…> * 2024 Wiki agenda pages: https://community.icann.org/x/_YAYEQ * Check your time zone: https://tinyurl.com/52cbsdhk 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, Terri Policy Team Supporting the GNSO

1 0

Proposed Agenda topics for 16 December RDRS SC Meeting 17:30 UTC
by Feodora Hamza Dec. 16, 2024

Dec. 16, 2024

Dear RDRS SC, Please see below the proposed agenda for our next meeting. Proposed Agenda topics for 16 December RDRS SC Meeting 17:30 UTC * Welcome (2min) * Pending AIs from Workbook<https://docs.google.com/spreadsheets/d/1XFK-RCT5Nv-KcNgX4eQunkUKgSI35Yc_nUZ…> (3min) * Review SC final report feedback (30min) i. Discussion on final report observations from Workbook ii. Suggest SC members use test domain, rdrs.test to help inform feedback for final report * “How to” video: How to use the system<https://youtu.be/iTCaug10dRE> * “How to” video: How to use the system<https://youtu.be/iTCaug10dRE> * Discuss presentation of metrics reports data for year 2 of RDRS pilot (20min) * AOB (5min) Kind regards, 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 1

REMINDER | Meeting Invitation | RDRS Standing Committee | Monday, 16 December 2024
by Terri Agnew Dec. 13, 2024

Dec. 13, 2024

Dear all, The next RDRS Standing Committee call is scheduled for Monday, 16 December 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…> and the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…> * 2024 Wiki agenda pages: https://community.icann.org/x/_YAYEQ * Check your time zone: https://tinyurl.com/52cbsdhk 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, Terri Policy Team Supporting the GNSO

1 0

Request to review of RDRS final report observations - Workbook - 16 December
by Feodora Hamza Dec. 10, 2024

Dec. 10, 2024

Sent on behalf of Sebastien Ducos Dear RDRS Steering Committee Members, Thank you for your valuable time and effort in providing extensive feedback in the "feedback for findings report" tab within the RDRS Workbook.<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1XFK-RCT5…> Your contributions are greatly appreciated. At your earliest convenience, I kindly request you to revisit the document to: 1. Provide the rationale for the observations you have made. 2. Add your comments or feedback on the observations submitted by your fellow RDRS members. It would be highly appreciated if you could complete your review by 16 December. This timeline will allow the support staff sufficient time to start populating the report template with all feedback incorporated. As discussed during our last RDRS meeting, support staff has updated the table in the "Feedback for Findings Report" tab. In this updated version, we have incorporated a space for the rationale behind each observation and the corresponding feedback from other SC members. For those who have already completed this task, thank you for your promptness and diligence. Thank you in advance for your continued support. Kind regards, Sebastien Ducos Chair of the RDRS SC

1 0

2024-12-02 RDRS Standing Committee - Meeting #21
by Feodora Hamza Dec. 3, 2024

Dec. 3, 2024

Dear members of the RDRS SC, Please find below the summary and action items of yesterday`s meeting. The next meeting is scheduled for 16 December at 17:30 UTC for 60 minutes. Kind regards, Feodora and Caitlin 2024-12-02 RDRS Standing Committee - Meeting #21<https://community.icann.org/pages/viewpage.action?pageId=390332705> Action Item: RDRS standing committee members to provide final report feedback to the workbook<https://docs.google.com/spreadsheets/d/1XFK-RCT5Nv-KcNgX4eQunkUKgSI35Yc_nUZ…> by Friday, December 6. Feedback to be provided in the Workbook Tab named “Feedback for Findings Report”. In cases where the workbook doesn’t work, SC members can send feedback via Email/distribution list. Action Item: ICANN Org to update Workbook<https://docs.google.com/spreadsheets/d/1XFK-RCT5Nv-KcNgX4eQunkUKgSI35Yc_nUZ…> with new columns in Final Report Tab: * Rationale of identified Observation/Feedback – SC Owner * Do you agree with Observation – Yes/No – Why – Comments – Other SC members 1. Welcome (2min) 2. Pending AIs (5min) · Deadline for standing committee members to provide final report feedback to the workbook: Friday, December 6. · Feedback to be provided in the Workbook Tab named “Feedback for Findings Report”. In cases where the workbook doesn’t work, SC members can send feedback via Email/distribution list. · SC members to include events in the outreach tracker, where relevant. · Gabriel Andrews highlighted ongoing efforts to include GAC statements in summaries for the final report/workbook. 1. Debrief/Discussion on SC session at ICANN81 (20min) · Concerns raised against framing disclosure as the only successful outcome, noting that such a narrative is legally inaccurate. Stressed the need to align stakeholder expectations with the system’s actual purpose and legal framework. (Thomas Rickert) · Suggested discussions during ICANN81 conflated two distinct topics: a) Lessons learned from RDRS operations (Assignment 3) and b) Recommendations for next steps (Assignment 4). Suggestion focusing on qualitative feedback rather than overly emphasizing quantitative metrics, which may not reflect the system’s nuances. (Marc Anderson) · Pointed out that there seems to be the assumption that RDRS metrics should directly inform a decision to proceed with SSAD. Highlighted the importance of distinguishing between RDRS as a pilot and the broader question of whether SSAD is the appropriate next step. (Steve Crocker) · Discussions around outreach and public awareness challenges regarding RDRS. Reiterated the need for stronger outreach, including embedding links to RDRS in RDAP output. Noted that RDRS’s limited “visibility” might undermine its utility as a pilot. (Gabriel Andrews) · SC members raised the question, if metrics and system enhancements will continue even if the final report is finished before the 2year pilot ends. ICANN staff confirmed metrics will continue to be published for the full pilot period and SC agreed to discuss the system enhancements matter further. 1. Final Report- Potential timeline (15 min) * ICANN Org presented the tentative timeline for the final report. · Divide the work based on assignments 1, 2, 3, 4. · Start collecting comments and feedback from RDRS SC on Assignment 1 observations – Workbook – 6 December. · RDRS SC to review the input made by their colleagues and provide feedback – 16 December * ICANN Org to update Workbook with new columns in Final Report Tab: * Rationale of identified Observation/Feedback – SC Owner * Do you agree with Observation – Yes/No – Why – Comments – Other SC members * ICANN Org to review the input from workbook and populate the Final Report template with input for further RDRS SC feedback: * 13 January – Assignment 1 * 27 January – Assignment 2 * 10 February – Assignment 3 * 24 February – Assignment 4 * Final Review and Editing – ICANN82 and beyond 1. Debrief on RDRS User Experience Interviews ICANN81 (10min) * ICANN Org conducted 8 interviews; one additional interview this week * Feedback Highlights: * Positives: User-friendly layout, good system performance, template is useful. * Challenges: Bulk feature inefficiency, lack of explanation in denials, often no communication from registrars outside the RDRS platform. * Suggestions for Improvements: API integration, registrar participation for affiliated privacy/proxy services, better explanations in request form, promotion of RDRS in RDAP output, explanation for each request category * Written summary report planned for integration into the final findings. 1. AOB (8min) · Debrief of RCMP Presentation (Sarah Wyld) * Provided an overview of the RDRS system to 45 RCMP participants. * Positive feedback noted; discussion on templates was limited due to time constraints. · Metrics and Proxy Disclosure Discussion (Gabriel Andrews) * Highlighted a potential data shift in metrics due to changes in registrar practices for privacy/proxy service disclosures. 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