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:
Action Items:
-
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.
-
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
Documents:
Action Items:
-
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.
-
Support Staff to provide a consolidated google document with all draft chapters.
Proposed Agenda:
-
Welcome
-
Presentation of draft Chapter 4
·
Support staff began drafting the final chapter of the GNSO Council report based on prior chapters and ICANN 83 discussions.
·
The chapter begins with scope and reminders that this is advice to the GNSO Council, not binding policy.
·
Three Main Recommendations:
·
Continuation of RDRS Beyond Pilot – Recommended to continue RDRS while future policy work proceeds on EPDP Phase 2.
·
System Enhancements – Top four system improvements include API development, authentication mechanisms (especially for law enforcement),
privacy/proxy handling, and RDAP response enhancements.
·
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.
·
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.
-
Discussion on draft Chapter 4
-
SC members noted that since RDRS is not policy and not mandatory, the ICANN Board can implement it without new policy.
-
SC members noted RDRS could become a more cost-effective version of SSAD. Suggested reinterpretation of original EPDP recommendations to fit RDRS.
-
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.
-
SC members requested changes to EPDP Phase 2 Recommendation 5 rationale.
-
SC members queried the suggestion (RDRS SC Rec 2.3) for more policy work. Argued that affiliated proxies are already handled by registrars.
-
SC members agreed clarification needed and suggested language should encourage voluntary action and avoid implying policy change.
-
SC members noted that a dedicated recommendation to Council should be made regarding financial sustainability of the system.
-
Consensus required for Chapter 4 content. Non-consensus items to be deferred to earlier chapters.
-
Final reminder to provide detailed, constructive feedback within the document that can reach consensus.
-
SC members requested that all chapters be merged into a single, navigable document to facilitate comprehensive review.
-
AOB
-
SC Chair shared ideal timeline and milestones
-
30 June: Deadline for Chapter 4 comments.
-
Early July: Staff compiles full report.
-
Mid July to August: SC reviews full draft and conducts consensus call.
-
Mid-September: Review of public comment received.
-
October: Submit report to GNSO Council.