Dear Olivier,
Please allow me to rephrase - I meant to say, as it stands, I do not see that we have an active role in either meetings, but still we should still pay attention to both.
As for the GAC-Board-GNSO trilateral meeting, it is an open session so although we, sadly, aren't at the table at panelist, some of us can still attend the meeting, noting that, again sadly, it clashes with the CPWG meeting.
ICANN86 - GAC Discussion on Registration Data Issues and GAC/ICANN Board/GNSO Trilateral Dialogue11:45 CEST (UTC+2), 9 June 2026
09:45 UTC, 9 June 2026
FIBES 1 - Pabellon 3C (GAC)
ID# 18273
Session Details
11:45-12:30 - GAC Discussion on Registration Data. This session aims to discuss status and consider possible next steps for the GAC in relation to the WHOIS/Registration Data policy framework, taking into account relevant Data Protection law. The GAC will discuss latest developments and related policy concerns, in connection with:
- Status and next steps regarding the ongoing development of law enforcement requestor authentication mechanisms to enable implementation of the 24-hour timeline for Contracted Parties to respond to Urgent Requests for disclosure of registration data;
- Modification of the GNSO policy recommendations for a System for Standardized Access/Disclosure (SSAD) adopted in 2021 to reflect lessons learned and Community input from operations of the Registration Data Request Service (RDRS) to date;
- Expected progress of the implementation of the Privacy/Proxy Services Accreditation Policy Recommendations (PPSA) in the coming year.
12:30-13:15 - Trilateral Dialogue with ICANN Board. The GAC Chair requested the convening of trilateral dialogue between the GAC, the ICANN Board and the GNSO to address domain registration data accuracy, and specifically to address the gap between a domain’s registration and the point at which a registrar may validate the registrant’s contact information (also referred to as the “15-day timeline for registrars to validate and verify registrants contact information” in the ICANN85 Communiqué).