<https://isoc.live/19819> [image: ISOC LIVE] <https://isoc.live/19819>*YOUTUBE <https://youtu.be/hhNyjGi45TA>* | *PATREON <https://www.patreon.com/posts/142555603/>* | *TRANSCRIPT <https://archive.org/download/icann84-RDRS/icann84-RDRS.EN.TRANSCRIPT.pdf> * | *ARCHIVE <https://archive.org/details/icann84-RDRS>* | *PERMALINK <https://isoc.live/19819>* On *October 25, 2025*, the *Non-Commercial Stakeholder Group <https://icann-community.atlassian.net/wiki/spaces/gnsononcomstake/overview>* (NCSG) in the *Generic Name Supporting Organization <https://gnso.icann.org/en>* (GNSO) hosted a session at the *Internet Corporation for Assigned Names and Numbers (ICANN) Annual General Meeting <https://meetings.icann.org/en/meetings/icann84/>*, in Dublin, Eire – ‘*DNS Security Without Sacrificing Rights: HRIA on RDRS <https://icann84.sched.com/event/29QGf/gnso-dns-security-without-sacrificing-rights-hria-on-rdrs>* ‘ The *Registrant Data Request Service <https://www.icann.org/rdrs-en>* (RDRS) is a pilot project — ICANN’s first effort, since *WHOIS <https://en.wikipedia.org/wiki/WHOIS> *was disrupted by the *GDPR <https://en.wikipedia.org/wiki/General_Data_Protection_Regulation>* — to centralize and standardize the triage of requests for non-public registration data. It does this by providing a unified form and routing system that directs such requests to participating (opt-in) registrars. In* August 2025,* the GNSO Standing Committee delivered *its report on the RDRS <https://itp.cdn.icann.org/en/files/generic-names-supporting-organization-council-gnso-council/rdrs-sc-council-report-19-08-2025-en.pdf>*, which was then *open for public comment <https://itp.cdn.icann.org/en/files/generic-names-supporting-organization-council-gnso-council/summary-report-rdrs-standing-cmte-report-gnso-council-review-20-10-2025-en.pdf>*, until just days prior to this meeting (October 20). By creating a common pathway for registrars to receive requests, RDRS raises fundamental questions about how disclosure decisions are made: when does a requester’s “legitimate interest” outweigh the registrant’s right to privacy, and how should the fundamental rights balancing test be applied across jurisdictions? This session provided an initial human rights impact assessment of the system, asking what aspects of disclosure triage can be standardized in a rights-respecting way beyond the form itself. This session aimed to go beyond the report and situate the conversation on broader challenges, such as cases where abuse is real but not obvious outside certain linguistic or cultural contexts (e.g. phishing against banks that are household names in one market but obscure elsewhere); the uneven practices of registries and registrars regarding disclosure. Subsequent to this meeting (*October 30*), ICANN issued an *RDRS Policy Alignment Analysis <https://itp.cdn.icann.org/en/files/registration-data-request-service-rdrs/registration-data-request-service-policy-alignment-analysis-30-10-2025-en.pdf>*, which is *open for public comment <https://www.icann.org/en/public-comment/proceeding/registration-data-request-service-rdrs-policy-alignment-analysis-30-10-2025>* until *December 9*. *SPEAKERS* *Rafik Dannak* – NCSG *Reg Levy* – Tucows / RrSG *Alan Woods* – Clean DNS *Sarah Wyld* – Tucows / RrSG *Thomas Rickert* – eco Association *Michele Neylon* – Blacknight / RrSG *Michaela Shapiro* – NCSG *Naoum Mengoudis* – Hellenic Police *Manju Hatolkar* – GNSO *Beth Marty* – name.com / RrSG *Sebastien Ducos* – GNSO RDRS Standing Committee #ICANN84 #RDRS #HumanRights -- -------------------------------------- Joly MacFie +12185659365 -------------------------------------- -