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

Meeting Invitation | RDRS Standing Committee | Monday, 13 October 2025
by Terri Agnew Oct. 1, 2025

Oct. 1, 2025

Dear all, The next RDRS Standing Committee call is scheduled for Monday, 13 October 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…> * Wiki agenda page 2025: https://icann-community.atlassian.net/wiki/x/NjTlBg 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

RDRS Standing Committee call
by ICANN Policy Calendar Oct. 1, 2025

Oct. 1, 2025

Meeting: RDRS Standing Committee call Date/time: Monday, 13 October 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…> * Wiki agenda page 2025: https://icann-community.atlassian.net/wiki/x/NjTlBg 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.

1 0

ICANN84 GNSO Sessions - How to Get Organized / Remote Participation Details
by Julie Bisland Sept. 29, 2025

Sept. 29, 2025

Dear all, With ICANN84<https://meetings.icann.org/en/meetings/icann84/> just around the corner, please take a moment to read the information below for a seamless and successful meeting. ICANN84 key dates: * Prep Week will take place virtually 13 - 15 October 2025. * Deadline for IN-PERSON registration is 24 October 2025. * ICANN84 will take place in Dublin 25 - 30 October 2025. On-site registration will not be available. Registration for ICANN84 does not automatically create a user account on sched.com. Instructions and guides to register as well as personalize your schedule can be found on these pages: * Visit this page to REGISTER: https://meetings.icann.org/en/meetings/icann84/ * General information about Dublin, hotels, transportation and rates, and links to food options can also be found here * The ICANN84 Schedule: https://icann84.sched.com/ * Instructions for personalizing your schedule can also be found here There will be no calendar invitations sent, as the meeting schedule allows you to download all sessions of interest to your individual calendars A reminder to review the Participation Tools page and update Zoom * All sessions that use Zoom rooms, access details will be 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 in the blue box on the right side of the page for more information on how to get the most out of the virtual meeting tools. * If participating on-site, please read the Frequently Asked Questions here<https://meetings.icann.org/en/meetings/icann84/#faq>. Links to Bookmark ICANN84 Meeting Schedule<https://icann84.sched.com/> ICANN84 GNSO Remote Participation Wiki Page<https://icann-community.atlassian.net/wiki/x/FYBUGQ> GNSO Session agendas<https://icann-community.atlassian.net/wiki/x/AYCMFQ> For all GNSO meeting-related queries, 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 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 August RDRS Usage Metrics Report is Published
by Lisa Carter Sept. 16, 2025

Sept. 16, 2025

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

1 0

Re: Links to Public Comment - RDRS SC Findings Report
by Lisa Carter Aug. 20, 2025

Aug. 20, 2025

SC members, I second the congratulations to all on this major milestone! Thanks for all of your hard work. Best, Lisa Carter Sr. Program Manager, Strategic Initiatives ICANN From: Feodora Hamza via Gnso-rdrs-sc <gnso-rdrs-sc(a)icann.org> Reply-To: Feodora Hamza <feodora.hamza(a)icann.org> Date: Wednesday, August 20, 2025 at 12:53 PM To: "gnso-rdrs-sc(a)icann.org" <gnso-rdrs-sc(a)icann.org> Subject: [Gnso-rdrs-sc] Links to Public Comment - RDRS SC Findings Report Dear RDRS SC members, Congratulations on finalizing the RDRS SC Findings report. Please find below for your convenience: Link to Proceeding: https://www.icann.org/en/public-comment/proceeding/registration-data-reques… Link to Announcement: https://www.icann.org/en/announcements/details/icann-generic-names-supporti… Kind regards, Feodora

1 0

Links to Public Comment - RDRS SC Findings Report
by Feodora Hamza Aug. 20, 2025

Aug. 20, 2025

Dear RDRS SC members, Congratulations on finalizing the RDRS SC Findings report. Please find below for your convenience: * Link to Proceeding: https://www.icann.org/en/public-comment/proceeding/registration-data-reques… * Link to Announcement: https://www.icann.org/en/announcements/details/icann-generic-names-supporti… Kind regards, Feodora

1 0

Consensus Call RDRS SC
by Sebastien＠registry.godaddy Aug. 18, 2025

Aug. 18, 2025

Dear RDRS SC Members, This message is to notify you of the closing of the Consensus Call process on the RDRS SC Findings Report. * Please find attached the updated Consensus Designation based on the comments received by SC members during the Consensus Call. We have received three objections to RDRS SC recommendation #5 and leadership has updated the Consensus Designation for that recommendation only. The comments received have been uploaded to the Wiki<https://urldefense.com/v3/__https://gnso.icann.org/sites/default/files/poli…> and are linked in the RDRS Findings Report accordingly with the Consensus Designations for all recommendations. * Leadership has also accepted the minor wording change for the recommendation #1 rationale, which doesn’t impact the substance of the recommendations. Please find the Final Report attached. This is a huge milestone that involved many months of volunteer work, dozens of calls, and a lot of creative thinking and compromising for all involved. Congratulations to all of you on achieving a major milestone and thank you again for all your hard work! Kindly, Sebastien Ducos RDRS SC Chair Sebastien Ducos +49 172 690 8418 Germany sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy>

2 1

Consensus Call RDRS Standing Committee
by Sebastien＠registry.godaddy Aug. 16, 2025

Aug. 16, 2025

Dear RDRS Standing Committee, As discussed during our meeting today this message is to notify you of the opening of the Consensus Call process on the RDRS SC Assignment 4 recommendations to GNSO Council. The RDRS SC leadership team has proposed a consensus designation for every recommendation that the SC has finalized. These consensus designations are contained in the attached document entitled, “RDRS SC Consensus Call - Leadership Proposed Consensus Designations.” This Consensus Call process opens today, 11 August and closes on 15 August at 23:59 UTC. In accordance with the GNSO Working Group Guidelines [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…>, SC members are required to indicate via reply to this message whether they accept, or do not accept, the leadership team’s proposed consensus designations. If no objection is raised by any member, the consensus designation is considered accepted by that SC member. If you do not respond before 15 August at 23:59 UTC, the leadership team will take this as acceptance of the consensus designations. If any objection is raised for any specific recommendation, the leadership team is expected to reevaluate the consensus designation of such recommendation and publish an updated designation to be reviewed by the working group. In the event there is no disagreement by the SC with the proposed consensus designations, Support Staff will incorporate the designations into the RDRS SC Report to GNSO Council. As set out in the RDRS SC Charter, only Members appointed by their representative groups are expected to participate in the Consensus Call process. Participants and observers will not be able to participate. For reference, please also see the attached document entitled “RDRS SC Recommendations to GNSO Council” that contains the 6 recommendations included in the Report. For more information about the Consensus Call, you may review the GNSO Working Group Guidelines [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> or the RDRS SC Charter (Section VI: Decision Making Methodologies). Kindly, Sebastien Ducos RDRS SC Chair Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [cid:image001.png@01D81E10.09821660] +49 172 690 8418 Germany sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy>

4 4

Re: The July RDRS Usage Metrics Report is Published
by Lisa Carter Aug. 14, 2025

Aug. 14, 2025

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

1 0

Notes and action items - RDRS Standing Committee meeting - 11 August 2025
by Caitlin Tubergen Aug. 11, 2025

Aug. 11, 2025

Dear RDRS Standing Committee members, Please find below the notes and action items from today’s meeting. Congratulations to all on the hard work it took to get to this point. Best regards, Caitlin on behalf of the RDRS SC Support Team -- RDRS Standing Committee Meeting 11 August 2025 Action Items 1. SC Leadership to open consensus call on six recommendations today, 11 August 2025. [COMPLETE] 2. SC to review the consensus call and note objections (if any) by the deadline of Friday, 15 August 2025 by 23:59 UTC. 3. Support staff to update the draft report based on today’s discussion. 4. SC members may still make non-substantive edits to the Draft Report until Friday, 15 August 2025. 5. Support Staff to open public comment proceeding on Tuesday, 19 August. Agenda 1. Welcome (5 min) · This will be the last call prior to publication of our draft report for public comment 1. Review pending comments and action items (105 min) o Draft Report [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/11RPDqWgI0lcu…> · As an outcome from the last meeting, Support Staff made some updates to the recommendations. · The main pending discussion item relates to Rec. 14 (financial considerations) - specifically the table. · Gabe proposes to change the action from “keep” to “modify” · 14.5.1 should be modified: · 14.5. In relation to the accreditation framework: · 14.5.1. Accreditation applicants MUST be charged a to-be-determined non-refundable fee proportional to the cost of validating an application, except under certain circumstances these fees may be waived or zero for certain types or categories of applicants which SHOULD be further defined during the implementation phase. · Want to avoid a situation where Interpol, FBI, or other public safety agencies are required to charge fees if they accredit their constituent groups when they may not want to. · Open to accreditation-related fees being modified. · If that is what we are proposing, would like to see that made very clear in the report. · Proposed text: The Standing Committee notes that the considerations in Recommendation 14.5 relating to the accreditation framework may need to be adjusted depending on specifics determined by the accreditation provider. · Could add “for example, public safety agencies acting for their constituent members.” · “Specifically, the Standing Committee notes that the considerations in Recommendation 14.5 relating to the accreditation framework may need to be adjusted depending on specifics determined by the accreditation provider. For example, public safety agencies may choose to waive fees for their constituent members.” · This discussion about fee waiver is re: 14.5 only. · This group has discussed Rec. 14 at length. The group discussed they would leave it alone, with the exception of 14.5. The articulated disagreements to parts of Rec. 14 are included in the Lessons Learned section of the report. · On previous calls, we discussed a possible enhancement for a link in RDRS with non-participating Rrs with their own request system. It would be a good enhancement to add this. Even if there isn’t agreement to include that in recommendations, recommend adding this to lessons learned. · Support staff can include this in assignment 2 for a future enhancement. Would the SC like to add this to a recommendation? If so, the enhancements may need to be reranked? · Recommend putting this as an enhancement and not adding as a recommendation this late in the day. · Thought that in RDRS if the Rr for the desired domain name is not participating, the RDRS would say - sorry, can’t use RDRS, but here is the info that they passed along for your reference - phone number, email, link to form, as applicable. · Right now, if there is a non-participating registrar, that is as far as you can go. Without a significant amount of effort, we can do better. Registrars are required to provide information and mechanisms for requesting access to non-public data. · The text highlighted on the left re: prima facie review, this text may be too prescriptive in terms of telling registrars exactly what they have to do and how they have to do it. Some of these steps may be unnecessary. That said, all of this may be pointless if this text was suggested for removal anyway. · The text in this paragraph is not a lesson learned or suggested enhancement. There could be something better done with communication about decisions, but the copy/paste of the recommendation makes it unclear. The Standing Committee cannot change the requirements. · One lesson learned is that we don’t know how registrars come to their decision to make the disclosure or not. NCSG believes that fundamental rights balancing should happen. If the Rr does not want to do fundamental rights balancing, it should be documented why. · This text is part of Assignment 3, part of lessons learned, so SC is free to note disagreement here. · Re: the table - comments on p. 19 re: clarification on new text. · Disclosure must occur if a lawful basis exists, provided the human rights must be taken into account. The words “if applicable” don’t make sense here - when is human rights not applicable? · Human rights may not be impacted if it doesn’t lead to unfair arrest or chilling right of expression. · Suggest rephrasing “potential violation of human rights must be taken into account.” Do not want to imply that there are people who do not have human rights. · Follow-on question - there are entities that have tried to obtain Rr status before but espouse views in which they highly value privacy above all other rights. Does this suggest that as long as a Rr can suggest that, they could always deny every request for disclosure? · This paragraph is just meant to make it transparent why a request is denied, and it should be documented. If a registrar feels they are given carte blanche to deny every request, it is possible that a registrar could reject based on its fundamental rights balancing. If a registrar does this repeatedly, we will know. · Fear that if there is a MUST for a registrar to call out that the human rights assessment, you may be putting registrars in a risky situation with authoritarian regimes. Allowing registrars the option to do this and have flexibility to not be targets to authoritarian regimes. · We are not prescribing how the documentation should take place. · Either the requestor and Rr both subscribe to the human rights convention, or they do not. Consensus Call · While the consensus call will be opened today on the recommendations, other text and clarifications if non-substantial can be considered throughout the week. · Do not object to text submitted by Farzaneh, but would like to confirm the text matches what it is in the ODA. · Following this call, Sebastien will send the consensus call via email – 11 August. The consensus call applies to the recommendations only. Per Marc’s request last week, the recommendations have been reordered. · Leadership has designated all recs as full consensus. · The consensus call will close at 23:59 UTC on Friday, 15 August. · If you agree with what is on screen/later in email, no action is needed. If you disagree, please indicate your disagreement by the deadline (Friday, 15 August). · Only members of the SC are to participate in this consensus call. · Support Staff will provide a PDF of just the recommendation text so that it is clear what the group is being asked to review. · Understand that this is the consensus of this team, not the constituent groups. o Review Document<https://urldefense.com/v3/__https:/docs.google.com/document/d/1cZnyjmibAysU…> 1. AOB (10 min)

1 0