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

Meeting Invitation | RDRS Standing Committee | Monday, 02 June 2025
by Devan Reed May 19, 2025

May 19, 2025

**The Monday, 26 May call has been cancelled. Please remove it from your calendars. Dear all, The next RDRS Standing Committee call is scheduled for Monday, 02 June 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: https://icann-community.atlassian.net/wiki/x/zjXlBg * Check your time zone: https://tinyurl.com/y47s3v99 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

Canceled: RDRS Standing Committee
by ICANN Policy Calendar May 19, 2025

May 19, 2025

Meeting: RDRS Standing Committee Pattern: Weekly on Mondays at 17:30 UTC for 60 minutes (28 April - 02 June 2025) (cancelled 05 May) 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 pages starting with 28 April: https://icann-community.atlassian.net/wiki/x/AgAfDg * Check your time zone (28 April 2025): https://tinyurl.com/425755yr 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

15 MINUTES REMINDER | Meeting Invitation | RDRS Standing Committee | Monday, 19 May 2025
by Devan Reed May 19, 2025

May 19, 2025

Dear all, The next RDRS Standing Committee call is scheduled for Monday, 19 May 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: https://icann-community.atlassian.net/wiki/x/wzXlBg * Check your time zone: https://tinyurl.com/uchsmy7m 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

REMINDER | Meeting Invitation | RDRS Standing Committee | Monday, 19 May 2025
by Devan Reed May 16, 2025

May 16, 2025

Dear all, The next RDRS Standing Committee call is scheduled for Monday, 19 May 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: https://icann-community.atlassian.net/wiki/x/wzXlBg * Check your time zone: https://tinyurl.com/uchsmy7m 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

Proposed Agenda RDRS SC Call agenda 19 May
by Feodora Hamza May 16, 2025

May 16, 2025

Dear RDRS SC, please see below the proposed agenda for our next call. Proposed Agenda RDRS SC Call agenda 19 May 17:30 UTC 1. Welcome 2. Continue discussion on Chapter 4 3. AOB Also, a kind reminder on the pending Action Item: * Review Document for Assignment 4<https://docs.google.com/document/d/1NOhKGqMMSypLpEF5rucEb-_Z3-iPb5_q/edit?u…> by Deadline 19 May 2025. * Review and comment on the document provided by ICANN Org for assignment 4. (Review EPDP Phase 2 Recs – 1, 2, 8, 10, 14, 16) based on instructions in the document. 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 0

NCSG Feedback/Law enforcement domains
by farzaneh badii May 15, 2025

May 15, 2025

Hello SC and Gabe, Thank you for raising the proposal regarding the submission of verified law enforcement domain names to ICANN for potential integration into the Registration Data Request System (RDRS). I’ve shared this with the NCSG and there is general support for the idea as a *supplementary data point* to help improve the credibility of law enforcement requests. Here is a summary of the key feedback and considerations: 1. *Supplementary Signal Only* There is consensus that verified law enforcement domains can be a useful *additional* signal but should not be treated as a definitive authentication mechanism. Disclosure decisions must continue to rely on rights-balancing considerations. 2. *Spoofing Awareness* The group noted the ease with which email addresses can be spoofed and emphasized the need to ensure ICANN and registrars understand this risk. Domain verification alone is not sufficient to establish authenticity. 3. *Renewal and Maintenance* Any verified domain list should include a mechanism for *periodic review and renewal* to avoid stale or misused entries—especially where multiple domains may exist within the same agency or department. 4. *Toward a More Robust Solution* While the domain-based check may be a useful *palliative*, it should be clearly framed as a *temporary* measure while a more robust authentication method is developed. 5. *Review Timeline and Evaluation* As a next step, the group recommends setting a *review period of six months* to evaluate progress toward a longer-term solution. This review could also look at how registrars are engaging with the verified domain signal—not necessarily by measuring an increase in granted requests, but rather by assessing *registrar confidence and acceptance* of this signal in their decision-making process. Overall, we welcome continued exploration of this approach, provided it is implemented with *clear accountability safeguards*, transparent review cycles, and an understanding that it is not a final solution. Best regards, Farzaneh

3 2

Action Required: Assignment 4 Review – RDRS Standing Committee
by Feodora Hamza May 15, 2025

May 15, 2025

Sent on behalf of Sebastien Ducos Dear RDRS SC Members, As we advance our work on Assignment 4 (Charter) <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> I would like to reiterate the importance of your timely and thorough participation in this critical phase of the RDRS Standing Committee’s assignment. Assignment 4 asks us to assess each of the EPDP Phase 2 recommendations considering our experience with the RDRS pilot. Specifically, your task is to evaluate whether each recommendation: • Could remain as originally drafted, • Should be considered for potential modification based on RDRS experience, or • Could be considered as no longer necessary based on RDRS experience. We have begun discussions on six of the EPDP Phase 2 recommendations. These are now available for your input in the Assignment 4 Review Document<https://urldefense.com/v3/__https:/docs.google.com/document/d/1NOhKGqMMSypL…>.<https://urldefense.com/v3/__https:/docs.google.com/document/d/1NOhKGqMMSypL…> Your feedback is critical to help us determine whether consensus can be reached on the RDRS SC recommendations to GNSO Council that will be derived from that review. Your response in the document should clearly indicate your assessment of each Recommendations status (could be retained/could be modified/potentially not needed anymore) and be based on the objective analysis of the RDRS experience and lessons learned. Please note: • A thorough and thoughtful review is essential to producing a credible and useful output for the GNSO Council and ultimately the ICANN community. • If there are uncertainties or points of confusion, Leadership and the support team are available to assist—please do not hesitate to reach out. • To ensure an informed and productive review, all members should to re-read draft Chapter 3<https://urldefense.com/v3/__https:/docs.google.com/document/d/1c2Nm5s1Q-4jr…>,<https://urldefense.com/v3/__https:/docs.google.com/document/d/1c2Nm5s1Q-4jr…> which consolidates the RDRS lessons learned and implementation alignment. • Section 3.6 of the GNSO Working Group<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/filef…> guidelines defines how consensus levels are determined. This is a collective effort, and the quality of our final report depends on the engagement and contributions of all members. Let’s ensure we meet our objectives with the diligence and professionalism this work demands. Thank you for your attention and collaboration. Kindly, Sebastien Ducos RDRS SC Chair

1 0

IP authentication?
by Sarah Wyld May 14, 2025

May 14, 2025

Hello all, I was able to listen in to this week's meeting and have a question about something I may have heard wrong. Fairly late in the call I understood Alan to say that a big cost in the SSAD ODA was the confirmation of intellectual property rights (i.e. does the requestor actually hold the copyright they claim to have). This was unfamiliar to me and I couldn't find anything related in the SSAD ODA itself, though of course it does refer to IP holders as a user category. Alan, did you perhaps instead say that requestor authentication is the big cost in the SSAD? Or what was I missing? Thanks, -- *Sarah Wyld, CIPP/E* Pronouns: she/they Head, Policy & Privacy Tucows #MakingTheInternetBetter swyld(a)tucows.com /Responses to this email are processed according to the Tucows Privacy Policy <https://www.tucows.com/privacy>/

1 0

Metric request - Priority changes
by Sarah Wyld May 14, 2025

May 14, 2025

Hello, In RDRS the registrar can now change the priority level of a request from Expedited to Standard (and presumably vice versa). Is ICANN tracking the rate of priority level changes? If so, can that please be included in our metrics reporting? And if not, maybe we can start, and also publish it? Thank you, -- *Sarah Wyld, CIPP/E* Pronouns: she/they Head, Policy & Privacy Tucows #MakingTheInternetBetter swyld(a)tucows.com /Responses to this email are processed according to the Tucows Privacy Policy <https://www.tucows.com/privacy>/

2 5

2025-05-12 RDRS Standing Committee - Meeting #32
by Feodora Hamza May 13, 2025

May 13, 2025

Dear RDRS SC, Please see below the notes and action items from the last meeting. The next meeting is scheduled for 19 May at 17:30 UTC. Kind regards, Feodora and Caitlin 2025-05-12 RDRS Standing Committee - Meeting #32<https://icann-community.atlassian.net/wiki/spaces/EOTSFGRD/pages/236912661/…> Action Items: * ICANN Org to circulate Google Doc with EPDP Phase 2 recs and link each to corresponding sections for context. Deadline 13 May * SC Members to: · Re-read Chapter 3. · Review and comment on the document provided by ICANN Org for assignment 4. (Review EPDP Phase 2 Recs – 1, 2, 8, 10, 14, 16) · To indicate if they agree with the categorization of the EPDP Phase 2 Rec and if view is divergent, provide rationale. · Review Document for Assignment 4<https://docs.google.com/document/d/1NOhKGqMMSypLpEF5rucEb-_Z3-iPb5_q/edit?u…> by Deadline 19 May 2025. Documents: * Review Document for Assignment 4<https://docs.google.com/document/d/1NOhKGqMMSypLpEF5rucEb-_Z3-iPb5_q/edit?u…> * Slides from 12 May meeting.<https://icann-community.atlassian.net/wiki/download/attachments/236912661/s…> * RDRS SC Charter<https://gnso.icann.org/sites/default/files/policy/2023/draft/draft-rdrs-sta…> * Chapter 1-3: * Chapter 1<https://docs.google.com/document/d/1CBAHz7G2AmjOt7C68Rn_hFl5c9F83lz9/edit> * Chapter 2<https://docs.google.com/document/d/1oqXdMgsGltToV_JxDtubedfymvrmvoAH43kssxO…> * Chapter 3<https://docs.google.com/document/d/1c2Nm5s1Q-4jrAqWvsurH-k6BhpyanGIW/edit> * EPDP Phase 2 Temporary Specification for gTLD Registration Data Phase 2<about:blank> Proposed Agenda: 1. Welcome · Purpose of meeting: Continue discussion on Chapter 4 of the RDRS SC Final Findings Report. 1. Continue discussion on Chapter 4 . Recap and Context for Chapter 4 (Presented by ICANN Org) Assignment 4: To provide the GNSO Council with recommendations based on the review of the EPDP Phase 2 recommendations (Recs 1–18) and their incorporation (entire, partial, or none) in the RDRS. · The group may (based on Charter): i.Recommend full adoption of all EPDP recommendations, ii.Recommend rejection, iii.Recommend modifications, iv.Or suggest a combination thereof. · Emphasized the standing committee’s role as advisory—not policy-making. They may comment and make observations, but changes to policy must follow established GNSO processes. The Council did, however, charge the Standing Committee to perform a close review of the recommendations and provide observations and guidance on how to proceed with the eventual Board/Council dialogue. · Explained potential modification paths: i.ICANN Bylaws Annex A Section 9: Path of supplemental recommendations. ii.GNSO Procedures Section 16: Council may modify recommendations before Board consideration. b. Chapter 4 Structure Proposal (Presented by ICANN Org) · Chapter 4 to consolidate findings (from Chapter 1 to 3) and provide recommendations to GNSO Council. · Proposed elements: Part 1: Overarching recommendations. Part 2: Updated table from Chapter 3, showing alignment of EPDP Phase 2 Recs with RDRS implementation. Preliminary classification of recommendations: i.1 fully aligned: Rec 8 (registrars reviewing requests individually). ii.12 partially aligned. iii.5 not included: Recs 1–2 (Accreditation), 10 (Response timing), 14 (Financial sustainability), 16 (Audits). c. Summary of SC Discussion (Lead by SC Chair) · SC members asked whether broader environmental changes could justify reconsidering recommendations. · SC Chair responded: Such work is not within the group’s charter but acknowledged consensus-flagging of outdated items is acceptable. · Emphasis on focusing on what was learned from the RDRS rather than conducting full policy re-evaluation. · SC members stressed the importance of documenting disagreements or differing views within the report. · SC Chair clarified that while Assignments 1–3 permit noting disagreement (which has been documented in the different chapters), Assignment 4 requires consensus per charter. · Divergent views may be documented in annexes or supporting material. · Some SC members emphasized the need to flag the lack of guidance and consistency in request handling, indicating that Rec#8 might not be considered as fully implemented in RDRS. · SC members objected to implying consensus on “abandoning” accreditation without proper discussion. · SC members suggested noting authentication’s value for requester accountability. (Rec #1 and #2) · SC members noted they need time to review the EPDP Phase 2 Recommendations and review chapters 1-3 again to be able to contribute meaningfully to assignment 4. 1. AOB · SC members revisited a pending enhancement request to include law enforcement authentication by checking domain ownership. · No registrar feedback yet. · Clarification requested by SC members on which platform (e.g., RDRS or another portal) will be used to process such law enforcement requests.

1 0