Seb, The IPC is going to need a bit more time. I have a call starting in a few minutes and hope to have our response to you after that call. John [http://www.nelsonmullins.com/img/ecard-logo.png] JOHN C. MCELWAINE PARTNER john.mcelwaine@nelsonmullins.com<mailto:john.mcelwaine@nelsonmullins.com> LIBERTY CENTER | SUITE 600 151 MEETING STREET | CHARLESTON, SC 29401 T 843.534.4302 F 843.722.8700 101 CONSTITUTION AVENUE, NW | SUITE 900 WASHINGTON, D.C., 20001 T 202.689.2939 F 202.689.2860 NELSONMULLINS.COM<http://www.nelsonmullins.com> VCARD<http://www.nelsonmullins.com/people/john-mcelwaine/vcard> VIEW BIO<http://www.nelsonmullins.com/people/john-mcelwaine> From: Sebastien--- via Gnso-rdrs-sc <gnso-rdrs-sc@icann.org> Sent: Wednesday, November 12, 2025 10:41 AM To: Steve DelBianco <sdelbianco@netchoice.org>; gnso-rdrs-sc@icann.org Subject: [Gnso-rdrs-sc] Re: Consensus Call RDRS Thank you, Steve and the BC, for this. All, in my enthusiasm on Monday, I forgot that yesterday was a holiday for some. Please consider this Consensus Call open for a few more hours until 23: 59 UTC today. Kindly, Sebastien Ducos GoDaddy Registry Thank you, Steve and the BC, for this. All, in my enthusiasm on Monday, I forgot that yesterday was a holiday for some. Please consider this Consensus Call open for a few more hours until 23:59 UTC today. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [cid:image001.png@01DC53C3.4AE768C0] +49 172 690 8418 Germany sebastien@registry.godaddy<mailto:sebastien@registry.godaddy> From: Steve DelBianco <sdelbianco@netchoice.org<mailto:sdelbianco@netchoice.org>> Date: Wednesday, 12 November 2025 at 3:10 pm To: Sebastien Ducos <Sebastien@registry.godaddy<mailto:Sebastien@registry.godaddy>>, gnso-rdrs-sc@icann.org<mailto:gnso-rdrs-sc@icann.org> <gnso-rdrs-sc@icann.org<mailto:gnso-rdrs-sc@icann.org>> Subject: Re: Consensus Call RDRS This Message Is From an Untrusted Sender You have not previously corresponded with this sender. Sebastien, For purposes of your consensus call, the Business Constituency (BC) supports the 6 recommendations in Assignment #4: Suggestions to the Council for a proposed recommendation to the Board in relation to SSAD recommendations. The relevant recommendations are: Recommendation 1: Continue the RDRS beyond the pilot period Recommendation 2: Allow for authentication of interested requestor groups, beginning with law enforcement Recommendation 3: Implement Key System Enhancements to sustain and evolve RDRSpost-pilot while more policy work is underway. (API, UX Redesign, optional ccTLD participation. Recommendation 4: Consider further policy work in the following areas: Privacy/Proxy Data, Inclusion of RDRS links in the RDAP responses. Recommendation 5: Consideration regarding next steps on EPDP Phase 2/SSAD Policy Recommendations Recommendation 6: Maintain the current Standing Committee with narrowed Scope. Steve DelBianco BC Rep on RDRS SC From: Sebastien--- via Gnso-rdrs-sc <gnso-rdrs-sc@icann.org<mailto:gnso-rdrs-sc@icann.org>> Date: Monday, November 10, 2025 at 6:36 AM To: gnso-rdrs-sc@icann.org<mailto:gnso-rdrs-sc@icann.org> <gnso-rdrs-sc@icann.org<mailto:gnso-rdrs-sc@icann.org>> Subject: [Gnso-rdrs-sc] Consensus Call RDRS Dear RDRS SC, As discussed during our last meeting in Dublin this message is to notify you of the opening of the Consensus Call process on the RDRS SC Assignment 4 recommendations. 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, 10 November at 14:00 UTC and closing on 12 November at 14:00 UTC. In accordance with the GNSO Working Group Guidelines [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/f...>, 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 12 November at 14:00 UTC, the leadership team will take this as acceptance of the consensus designations. If any objection is raised for any specific final 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 to be 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/f...> or the RDRS SC Charter (Section VI: Decision Making Methodologies). Regards, Sebastien Ducos RDRS SC Chair Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [cid:image001.png@01DC53C3.4AE768C0] +49 172 690 8418 Germany sebastien@registry.godaddy<mailto:sebastien@registry.godaddy> Confidentiality Notice This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged, confidential or otherwise legally exempt from disclosure. If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately either by phone (800-237-2000) or reply to this e-mail and delete all copies of this message.
