October 2025 - Gnso-rdrs-sc

Re: RDRS Policy Alignment Analysis has been published for Public Comment
by Lisa Carter Oct. 30, 2025

Oct. 30, 2025

Dear Standing Committee Members, The ICANN Board has just adopted the resolution to continue RDRS, and it will be published soon. Concurrently, the RDRS Policy Alignment Analysis has been published for public comment. Safe travels home to all in Dublin! Many thanks. Lisa Carter Sr. Program Manager, Strategic Initiatives ICANN

1 0

Kind reminder: For review: Updated draft RDRS SC report
by Feodora Hamza Oct. 30, 2025

Oct. 30, 2025

Dear RDRS SC, hope you are enjoying Dublin. This is a kind reminder to review the updated RDRS report based on the RDRS discussions at ICANN84. Please review the document and suggest if anything has not been reflected properly or if we should amend any language by 29 October 16:00 IST. If there are any concerns raised by the deadline, we will keep the RDRS SC session on Wednesday to discuss those concerns. If there are no further substantial comments, we would cancel that session. The SC agreed to include (highlighted in green) * A brief intro how PC has been considered in the report * A summary of the PC under each recommendation/rationale * The additional rec item 3.4 * Additional rationale based on PC in the rec 5 table * Updates to the rec 5 table on SSAD rec 10 and 17 in terms of how the rec should be treated Draft Report: https://docs.google.com/document/d/1K3SbhEInIGpY5idi_LWpzFR5tLova63A/edit?u… [docs.google.com]<https://docs.google.com/document/d/1K3SbhEInIGpY5idi_LWpzFR5tLova63A/edit?u…>. Kind regards, Feodora From: Feodora Hamza <feodora.hamza(a)icann.org> Date: Saturday, 25 October 2025 at 20:10 To: "gnso-rdrs-sc(a)icann.org" <gnso-rdrs-sc(a)icann.org> Subject: For review: Updated draft RDRS SC report Dear RDRS SC, Thank you for today`s sessions. As discussed, please find below the link the the updated RDRS SC report. The SC agreed to include (highlighted in green) * A brief intro how PC has been considered in the report * A summary of the PC under each recommendation/rationale * The additional rec item 3.4 * Additional rationale based on PC in the rec 5 table * Updates to the rec 5 table on SSAD rec 10 and 17 in terms of how the rec should be treated https://docs.google.com/document/d/1K3SbhEInIGpY5idi_LWpzFR5tLova63A/edit?u… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1K3SbhEInIGpY…>. The sections have been updated based on today’s discussion. Please review the document and suggest if anything has not been reflected properly or if we should amend any language by 29 October 16:00 IST Thank you and enjoy ICANN84. Kind regards, Feodora and Caitlin

3 5

Cancelled: RDRS SC Session Wednesday 29 October
by Feodora Hamza Oct. 29, 2025

Oct. 29, 2025

Dear RDRS SC, we have been informed that some SC members will share some editorial feedback to the updated report. Since no further concerns were raised on the updated SC report, we will cancel today`s RDRS session. We will reach out shortly with the next steps. Thank you, Feodora From: Feodora Hamza <feodora.hamza(a)icann.org> Date: Wednesday, 29 October 2025 at 08:50 To: "gnso-rdrs-sc(a)icann.org" <gnso-rdrs-sc(a)icann.org> Subject: Re: Kind reminder: For review: Updated draft RDRS SC report Dear RDRS SC, a kind reminder for the below. Draft Report: https://docs.google.com/document/d/1K3SbhEInIGpY5idi_LWpzFR5tLova63A/edit?u… [docs.google.com]<https://docs.google.com/document/d/1K3SbhEInIGpY5idi_LWpzFR5tLova63A/edit?u…>. Kind regards, Feodora From: Feodora Hamza <feodora.hamza(a)icann.org> Date: Monday, 27 October 2025 at 13:30 To: "gnso-rdrs-sc(a)icann.org" <gnso-rdrs-sc(a)icann.org> Subject: Kind reminder: For review: Updated draft RDRS SC report Dear RDRS SC, hope you are enjoying Dublin. This is a kind reminder to review the updated RDRS report based on the RDRS discussions at ICANN84. Please review the document and suggest if anything has not been reflected properly or if we should amend any language by 29 October 16:00 IST. If there are any concerns raised by the deadline, we will keep the RDRS SC session on Wednesday to discuss those concerns. If there are no further substantial comments, we would cancel that session. The SC agreed to include (highlighted in green) * A brief intro how PC has been considered in the report * A summary of the PC under each recommendation/rationale * The additional rec item 3.4 * Additional rationale based on PC in the rec 5 table * Updates to the rec 5 table on SSAD rec 10 and 17 in terms of how the rec should be treated Draft Report: https://docs.google.com/document/d/1K3SbhEInIGpY5idi_LWpzFR5tLova63A/edit?u… [docs.google.com]<https://docs.google.com/document/d/1K3SbhEInIGpY5idi_LWpzFR5tLova63A/edit?u…>. Kind regards, Feodora From: Feodora Hamza <feodora.hamza(a)icann.org> Date: Saturday, 25 October 2025 at 20:10 To: "gnso-rdrs-sc(a)icann.org" <gnso-rdrs-sc(a)icann.org> Subject: For review: Updated draft RDRS SC report Dear RDRS SC, Thank you for today`s sessions. As discussed, please find below the link the the updated RDRS SC report. The SC agreed to include (highlighted in green) * A brief intro how PC has been considered in the report * A summary of the PC under each recommendation/rationale * The additional rec item 3.4 * Additional rationale based on PC in the rec 5 table * Updates to the rec 5 table on SSAD rec 10 and 17 in terms of how the rec should be treated https://docs.google.com/document/d/1K3SbhEInIGpY5idi_LWpzFR5tLova63A/edit?u… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1K3SbhEInIGpY…>. The sections have been updated based on today’s discussion. Please review the document and suggest if anything has not been reflected properly or if we should amend any language by 29 October 16:00 IST Thank you and enjoy ICANN84. Kind regards, Feodora and Caitlin

2 1

For review: Updated draft RDRS SC report
by Feodora Hamza Oct. 26, 2025

Oct. 26, 2025

Dear RDRS SC, Thank you for today`s sessions. As discussed, please find below the link the the updated RDRS SC report. The SC agreed to include (highlighted in green) * A brief intro how PC has been considered in the report * A summary of the PC under each recommendation/rationale * The additional rec item 3.4 * Additional rationale based on PC in the rec 5 table * Updates to the rec 5 table on SSAD rec 10 and 17 in terms of how the rec should be treated https://docs.google.com/document/d/1K3SbhEInIGpY5idi_LWpzFR5tLova63A/edit?u… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1K3SbhEInIGpY…>. The sections have been updated based on today’s discussion. Please review the document and suggest if anything has not been reflected properly or if we should amend any language by 29 October 16:00 IST Thank you and enjoy ICANN84. Kind regards, Feodora and Caitlin

1 1

Link to draft updated report
by Caitlin Tubergen Oct. 25, 2025

Oct. 25, 2025

RDRS Standing Committee Members: Here is the updated draft report the RDRS Standing Committee is currently discussing during its working sessions at ICANN84: https://docs.google.com/document/d/1K3SbhEInIGpY5idi_LWpzFR5tLova63A/edit?u…. Please note that updated text is highlighted and bracketed for transparency. Best regards, Caitlin

1 0

Meeting during ICANN84
by Alan Greenberg Oct. 23, 2025

Oct. 23, 2025

Meetings 1-3 overlap with NomCom meetings and I will likely not be able to attend. Alan

1 0

Action Item and notes from 2025-10-13 RDRS Standing Committee - Meeting #42
by Feodora Hamza Oct. 21, 2025

Oct. 21, 2025

Dear RDRS SC, please find below the high-level notes and action items from yesterday’s meeting. We look forward to seeing you in Dublin. Safe travels, Feodora on behalf of the Support Team 2025-10-13 RDRS Standing Committee - Meeting #42<https://icann-community.atlassian.net/wiki/spaces/EOTSFGRD/pages/508526629/…> Action Items: Next steps for SC members: · Review all 11 comments in full. · Flag any mischaracterizations in the overview/review tool.<https://docs.google.com/spreadsheets/d/17iQS2v3Wbb35ApO3CVrnPey4BekwODqpfSu…> · If suggested edits are minor and editorial in nature, focus on whether you can live with them. · If suggested edits are substantive, focus on what new information or insights that have been provided by the commenter. · If concerns, information, or perspectives have already been considered in the development of the recommendations, consider how the report can strengthen the rationale by showing how these have been addressed and why the SC took the approach it did. Review Tool: https://docs.google.com/spreadsheets/d/17iQS2v3Wbb35ApO3CVrnPey4BekwODqpfSu… ICANN84 Sessions: · Prep-Week Session: 14 October 19:30 UTC · Working Session 1: 25 October 14:00 UTC · Working Session 2: 25 October 15:30 UTC · Working Session 3: 26 October 16:30 UTC · Working Session 4: 29 October 16:30 UTC 1. Welcome 2. Update ICANN Board * Board signalled intent to adopt a resolution at ICANN84 to continue RDRS beyond the pilot period and to publish a policy gap analysis for public comment focused on the gaps the Board previously indicated, including mandatory registrar participation, privacy/proxy access via RDRS, addition of APIs, and authentication for law enforcement. * Consultation with the GNSO Council on SSAD recommendations will be deferred until after the gap-analysis comment period closes. * Tentative timeline: Intention to publish gap analysis on 30 Oct with the comment period open through year-end (exact close date to be confirmed and shared with SC when available). High level discussion points: · SC members asked whether the gap analysis could include transparency of registrar decision criteria and cross-registrar consistency. · Board’s request focuses on the items mentioned above, but commenters are encouraged to raise additional gaps. · Concern about premature push for mandatory opt-in, privacy/proxy inclusion, and APIs without explicit rights-balancing and accountability safeguards. · Human rights and data protection have been considered across prior work. · Some members noted RDRS is a request system, not a mandated disclosure system; registrars decide disclosures under applicable law. · Board open to transparency improvements, while noting ICANN’s limited mission and existing RAA obligation to provide accurate, up-to-date data in accordance with law. · Some SC members raised concerns that if use is too expensive, some stakeholders might not use it. · The original self-funding concept raises questions. ICANN Board seeking clarity on realistic models and ICANN’s potential cost-sharing. · ICANN Board is open to voluntary ccTLD participation but acknowledges complexities. · Primary focus is on registrar-affiliated privacy/proxy providersSome members noted requests for privacy/proxy data may require additional requester information compared to standard cases. · ICANN Board believes registrar participation should be mandatory; the gap analysis will inform what policy is needed to achieve that. 1. Update on Public Comment<https://www.icann.org/en/public-comment/proceeding/registration-data-reques…> * 11 public comments received on the Standing Committee’s Findings Report. * Review Tool structure: · A master tab linking to all submissions. · One tab per recommendation, each split into three groupings: Support as written, Support intent, Concerns / Not supported. · Recommendation 5 has two tabs (the recommendation itself + a comparison table from the report). · An “Other comments” tab captures feedback not tied to a specific recommendation. · Working document to aid deliberations; does not replace members’ obligation to read all input. · Next steps for SC members: · Review all 11 comments in full. · Flag any mischaracterizations in the overview/review tool.<https://docs.google.com/spreadsheets/d/17iQS2v3Wbb35ApO3CVrnPey4BekwODqpfSu…> · If suggested edits are minor and editorial in nature, focus on whether you can live with them. · If suggested edits are substantive, focus on what new information or insights that have been provided by the commenter. · If concerns, information, or perspectives have already been considered in the development of the recommendations, consider how the report can strengthen the rationale by showing how these have been addressed and why the SC took the approach it did. · Planned sessions: · Prep-Week Session: 14 October 19:30 UTC · Working Session 1: 25 October 14:00 UTC · Working Session 2: 25 October 15:30 UTC · Working Session 3: 26 October 16:30 UTC · Working Session 4: 29 October 16:30 UTC · Rationale: in-person time has proven most effective for complex discussion; however, sessions can be cancelled if work is completed earlier. · Concerns raised: Avoid overcrowding the schedule; note a conflict with the NCSG Accuracy session on the last slot: suggestion to aim for three sessions if feasible. 1. AOB

1 1

Invitation to HRIA and RDRS
by farzaneh badii Oct. 20, 2025

Oct. 20, 2025

Hi all I’d like to invite you to join our NCSG session– DNS Security Without Sacrificing Rights: HRIA on RDRs”. Here is the link: https://icann84.sched.com/event/29QGf/gnso-dns-security-without-sacrificing… This session will explore how disclosure frameworks and triage systems—particularly in the context of Registration Data Requests (RDRs)—can be implemented in a way that upholds human rights, with a focus on Human Rights Impact Assessments (HRIAs). Best regards Farzaneh

1 0

ICANN84 GNSO Policy Briefing and ICANN84 Policy Outlook Report
by Julie Bisland Oct. 17, 2025

Oct. 17, 2025

Dear All, On behalf of the GNSO Team, we are happy to share the ICANN84 reports below are available for download. * GNSO Policy Briefing: http://go.icann.org/gnsobriefing * Policy Outlook Report: https://go.icann.org/outlook84 Happy reading! With kind regards, Julie -- Julie Bisland Policy Operations Analyst (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) 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

Re: The September RDRS Usage Metrics Report is Published
by Lisa Carter Oct. 16, 2025

Oct. 16, 2025

Hello Standing Committee Members, ICANN has published the September RDRS Usage Metrics Report: October 2025 (Reporting period: 1 September – 30 September 2025) [PDF] [CSV] [CSV 18] [CSV 19] Best, Lisa Carter Sr. Program Manager, Strategic Initiatives ICANN

1 0