Thanks so much! *Sarah Wyld, CIPP/E* Pronouns: she/they Head, Policy & Privacy Tucows #MakingTheInternetBetter swyld@tucows.com /Responses to this email are processed according to the Tucows Privacy Policy <https://www.tucows.com/privacy>/ On 2025-06-25 1:46 p.m., Caitlin Tubergen wrote:
Hi Sarah,
Thank you for your message. In response to your request, we have put together a consolidated table, which now includes the columns from both Chapter 3 (lessons learned), Chapter 4 (proposed treatment, rationale), and the text of the recommendations. As the recommendation text is extensive, the table is now quite long (99 pages). Footnotes from the recommendations are not included in the table due to formatting, but there are hyperlinks to all of the recommendations. Additionally, we endeavored to respond to this request quickly due to the short turnaround for the review of Chapter 4, so please excuse copy/paste errors.
Please find a link to the table here: https://docs.google.com/document/d/1OddR7A1fnHj3woTqmS_oaIBeJFJGAsCZZSefZYND...
We hope this is helpful to you and others in your review of Chapter 4. Please let us know if we can be of further assistance.
Best regards,
Feodora and Caitlin
*From: *Sarah Wyld via Gnso-rdrs-sc <gnso-rdrs-sc@icann.org> *Organization: *Tucows *Reply-To: *Sarah Wyld <swyld@tucows.com> *Date: *Wednesday, June 25, 2025 at 7:03 AM *To: *"gnso-rdrs-sc@icann.org" <gnso-rdrs-sc@icann.org> *Subject: *[Gnso-rdrs-sc] Re: 2025-06-23 RDRS Standing Committee - Meeting #36
Thank you Feodora for providing the consolidated version with all chapters as tabs. This should make our review easier.
Chapter 3 contains a table comparing RDRS operational attributes with the EPDP Phase 2 recommendations. Chapter 4 has the table with the Phase 2 recs and keep/modify with rationale. I wonder if these can be combined into one table with all the info, including the text of the rec itself, how it compared, and the keep/modify and rationale.
One difficulty I've had with the report is that we don't address all aspects of all the recommendations, and it's hard to know when we're leaving something out, so if we can see it all together in one place I think we could catch and resolve those gaps.
Thanks,
*Sarah Wyld, CIPP/E* Pronouns: she/they
Head, Policy & Privacy Tucows #MakingTheInternetBetter
swyld@tucows.com
/Responses to this email are processed according to the Tucows Privacy Policy [tucows.com] <https://urldefense.com/v3/__https:/www.tucows.com/privacy__;!!PtGJab4!5K_Ar0q7yQhqmHFoJ6fIXb8R2jt1nOTZBzeqvQFauYUPknxfZ-VwmPMNrM9a2EHbFb5G66DwJluL5mQpmiijipR8P_9xDDEdYA$>/
On 2025-06-23 4:55 p.m., Feodora Hamza via Gnso-rdrs-sc wrote:
Dear RDRS SC,
Please find below the high-level notes and Action Items today`s meeting. Please also find below the consolidated google document with all draft chapters (4 different tabs) in one document.
*Documents: *
1. *RDRS SC Report- _Consolidated Version all draft chapters: _*https://docs.google.com/document/d/1oqXdMgsGltToV_JxDtubedfymvrmvoAH43kssxOT... [docs.google.com] <https://urldefense.com/v3/__https:/docs.google.com/document/d/1oqXdMgsGltToV...>
*Action Items:*
1. *SC members to review and comment on Chapter 4 by 30 June. Please note: *Consensus required for Chapter 4 content (recommendation and rationale). Non-consensus items/suggestions to be deferred to earlier chapters e.g. Chapter 3 lessons learned or Chapter 2 Proposed System Enhancements. 2. *Support Staff to provide a consolidated google document with all draft chapters. *
The next meeting is scheduled for 30 June at 17:30 UTC.
Kind regards,
Feodora
2025-06-23 RDRS Standing Committee - Meeting #36 [icann-community.atlassian.net] <https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/spaces...>
*Documents: *
2. *RDRS SC Report- Consolidated Version all Chapters: *https://docs.google.com/document/d/1oqXdMgsGltToV_JxDtubedfymvrmvoAH43kssxOT... [docs.google.com] <https://urldefense.com/v3/__https:/docs.google.com/document/d/1oqXdMgsGltToV...>
3. *Slides 23 June: *https://docs.google.com/presentation/d/1QQlJf20vUc0BNYcrjneCatlAql7lkizR/edi... [docs.google.com] <https://urldefense.com/v3/__https:/docs.google.com/presentation/d/1QQlJf20vU...>
4. *Slides Timeline: *https://docs.google.com/presentation/d/1pF8dmdnMSX-1zQwQLajgK7tRGBBkZkCb/edi... [docs.google.com] <https://urldefense.com/v3/__https:/docs.google.com/presentation/d/1pF8dmdnMS...>
*Action Items:*
3. *SC members to review and comment on Chapter 4 by 30 June. Please note: *Consensus required for Chapter 4 content (recommendation and rationale). Non-consensus items/suggestions to be deferred to earlier chapters e.g. Chapter 3 lessons learned or Chapter 2 Proposed System Enhancements. 4. *Support Staff to provide a consolidated google document with all draft chapters. *
*Proposed Agenda:*
1. *Welcome* 2. *Presentation of draft Chapter 4*
1.Support staff began drafting the final chapter of the GNSO Council report based on prior chapters and ICANN 83 discussions.
2.The chapter begins with scope and reminders that this is advice to the GNSO Council, not binding policy.
3.*Three Main Recommendations:*
1.*Continuation of RDRS Beyond Pilot*– Recommended to continue RDRS while future policy work proceeds on EPDP Phase 2.
2.*System Enhancements*– Top four system improvements include API development, authentication mechanisms (especially for law enforcement), privacy/proxy handling, and RDAP response enhancements.
3.*Reassessment of EPDP Phase 2 Recommendations*– Review each of the 18 recommendations individually for suitability or modification.
•A table summarizing these assessments includes:
•Recommendation number.
•Function/title.
•Proposed treatment (“Keep,” “Modify,” etc.).
•Rationale (requires consensus).
•Draft conclusions.
1.*Next Steps:*
1.SC members to provide comments and suggestions by *30 June*.
2.Document compilation planned for early July, final report for review by early August.
1. *Discussion on draft Chapter 4*
1. *Main Discussion Points:*
1. SC members noted that since RDRS is not policy and not mandatory, the ICANN Board can implement it without new policy.
1. SC members noted RDRS could become a more cost-effective version of SSAD. Suggested reinterpretation of original EPDP recommendations to fit RDRS.
1. SC members voiced recurring concern about centralized architecture (ICANN as intermediary). Offered to provide more background proposing a more distributed approach and share them via mailing list.
1. SC members requested changes to EPDP Phase 2 Recommendation 5 rationale.
1. SC members queried the suggestion (RDRS SC Rec 2.3) for more policy work. Argued that affiliated proxies are already handled by registrars.
1. SC members agreed clarification needed and suggested language should encourage voluntary action and avoid implying policy change.
1. SC members noted that a dedicated recommendation to Council should be made regarding financial sustainability of the system.
1. Consensus required for Chapter 4 content. Non-consensus items to be deferred to earlier chapters.
1. Final reminder to provide detailed, constructive feedback within the document that can reach consensus.
1. SC members requested that all chapters be merged into a single, navigable document to facilitate comprehensive review.
1. AOB
1. *SC Chair shared ideal timeline and milestones*
1. *30 June:*Deadline for Chapter 4 comments.
1. *Early July:*Staff compiles full report.
1. *Mid July to August:*SC reviews full draft and conducts consensus call.
1. *Mid-September:*Review of public comment received.
1. *October:*Submit report to GNSO Council.
_______________________________________________
Gnso-rdrs-sc mailing list --gnso-rdrs-sc@icann.org
To unsubscribe send an email tognso-rdrs-sc-leave@icann.org
_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.