[NCSG-PC] Fwd: [council] Request for Input: Public Comment on RDRS Standing Committee Report

[farzaneh badii]

Thanks Tomslin

I raised this with the PC. I suggest we agree to public comment but ask the
announcement to be very precise about rdrs what it does and it doesn’t do.

Farzaneh


On Thu, May 8, 2025 at 8:40 AM Tomslin Samme-Nlar <mesumbeslin at gmail.com>
wrote:

> FYI
>
> Remain blessed,
> Tomslin
>
>
> ---------- Forwarded message ---------
> From: DiBiase, Gregory via council <council at icann.org>
> Date: Tue, 22 Apr 2025 at 02:45
> Subject: [council] Request for Input: Public Comment on RDRS Standing
> Committee Report
> To: Council at icann.org <council at icann.org>
>
>
> Dear Councilors,
>
>
>
> Following the recent update
> <https://icann.zoom.us/rec/play/i39NWFbE8i-ZP49d_oWAL2MoCyDGmPto7z5fs6WbJWphlsYtBbNp5jsupBJtRQrTVr5If5oUEFXp2ftK.YBeQ1j9evHUUqOe-?accessLevel=meeting&canPlayFromShare=true&from=share_recording_detail&startTime=1744318875000&componentName=rec-play&originRequestUrl=https%3A%2F%2Ficann.zoom.us%2Frec%2Fshare%2F1BdJrVMYICLOfeH4W7CEh-q9Udop0TZrUmaQ47ekzkZxRkwQ1GOzSHEEEIEUHhU.YVb3zS-ocr9VoJ41%3FstartTime%3D1744318875000>on
> the work of the Standing Committee (SC) on the Registration Data Request
> Service (RDRS), a procedural question was brought before Council: whether
> there should be a public comment on the RDRS SC Report.
>
>
>
> *Background:*
>
>
>
> The SC is nearing completion of its final findings report, which is
> structured around its assignment
> <https://gnso.icann.org/sites/default/files/policy/2023/draft/draft-rdrs-standing-committee-08sep23-en.pdf>
> from the GNSO Council, which includes information on the usage trends,
> system enhancements, lessons learned (particularly in light of SSAD
> recommendations), and suggestions to Council as it approaches its dialogue
> with the ICANN Board.
>
>
>
> As described in its Charter
> <https://gnso.icann.org/sites/default/files/policy/2023/draft/draft-rdrs-standing-committee-08sep23-en.pdf>,
> the SC should consult with the GNSO Council on whether this report, which
> is intended as a factual account of their work, not a policy document,
> should be published for public comment prior to the submission of the
> report to the Council?
>
>
>
> When considering this question, please note that all GNSO SGs are
> represented
> <https://icann-community.atlassian.net/wiki/spaces/EOTSFGRD/pages/115682448/RDRS+Standing+Committee+Team+Members+Mailing+Lists>in
> the Standing Committee. In addition, the RDRS Sc benefits from active
> participation by representatives from GAC, SSAC and ALAC, and it has
> already received community input during ICANN public sessions.
>
>
>
> While the Council always retains the option to initiate its public comment
> period prior to engaging with the ICANN Board, the SC would appreciate
> clarity whether it should initiate a public comment at this stage - prior
> to submitting their report to Council.
>
>
>
> Please consult with your stakeholder groups and be prepared to provide
> feedback at the upcoming Council meeting in May. Your input will help
> inform how the Standing Committee proceeds as it finalizes its work.
>
>
>
>
>
> Thanks,
>
> Greg
>
>
> _______________________________________________
> council mailing list -- council at icann.org
> To unsubscribe send an email to council-leave at 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.
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20250508/227476ab/attachment-0001.htm>