With apologies, it was brought to my attention that the consensus call needs to be published on the ALAC-announce list, rather than individual ALAC members’ emails. Correction and update: This is a consensus call only for the ALAC Statement on the Initial Report on the Second CSC Effectiveness Review. The ALAC statement on the Registration Data Public Comment proceeding was circulated by Jonathan Zuck and closes on Monday, 5 December. Further details are below, including the new language. Please use reply all for discussion. So far, Bill Jouris and Eduardo Diaz have replied in support of the changes. Thank you, Chantelle From: chantelle doerksen <chantelle.doerksen@icann.org> Date: Wednesday, November 30, 2022 at 9:32 PM Cc: ICANN At-Large Staff <staff@atlarge.icann.org> Subject: URGENT: 24-hour Consensus call on ALAC Statements (two): Initial Report on the Second CSC Effectiveness Review & Registration Data Consensus Policy for gTLDs Dear all, This is a 24-hour consensus call on two additional comments added to the two recently ratified ALAC statements. For convenience, changes have been flagged in the Google docs and are listed below. New language is in blue. Statement 1 Workspace: Initial Report on the Second CSC Effectiveness Review | Statement 5.6 Need to appoint Alternates for Members and/or Liaisons of the CSC? Recommendation: That the SO/ACs appoint an alternate for their member/liaison. ■ UPDATED Response: The ALAC supports the appointment of an alternate by each SO/AC for their member/liaison of the CSC. The alternate should be regularly updated on CSC meetings. Further, the ALAC believes alternates should be added to the group mailing list (and thus receive all posts). Alternates should be able to attend as observers. If they are unable to attend meetings as observers, we request that alternates have access to the recordings and meeting materials. Statement 2 Workspace: Registration Data Consensus Policy for gTLDs | Statement (as approved by CPWG on 30 November call) | Submission (including approved updates) Thick Whois Transition Policy for .COM, .NET, and. JOBS Please review the Redlined Thick Whois Transition Policy. Based on the requirements outlined in the Registration Data Consensus Policy, are the proposed redlined changes identified in the Thick Whois Transition Policy correct? ( _ ) Yes ( x ) No If no, please explain why the suggested changes are incorrect and provide any suggested changes. UPDATED ALAC RESPONSE: EPDP recommendation on the transfer of data from registrars to registries makes the implementation of the Thick Whois policy difficult, but it does not make it impossible. This is particularly true for registrations that contain no personal information. Moreover, the recently approved EU NIS2 requires that registries and registrars publish publicly available data, and make available redacted data to legitimate users; AND that registrars and registries cooperate so that data does not need to be collected twice. That implies that if registrars are the prime collector of the data (as they are with gTLDs) that registrars must cooperate and provide registries with the data. NIS 2 notes that this obligation is sufficient legal reason for processing the registration data under GDPR Article 6.1(c). Thank you, Chantelle From: ICANN At-Large Staff <staff@atlarge.icann.org> Date: Monday, November 21, 2022 at 7:30 PM Subject: VOTE ANNOUNCEMENT: ALAC Statements (two):Initial Report on the Second CSC Effectiveness Review & Registration Data Consensus Policy for gTLDs Dear all, This is to let you know that two statements are now final: Initial Report on the Second CSC Effectiveness Review Registration Data Consensus Policy for gTLDs Jonathan Zuck, ALAC Chair, has asked the 15 ALAC members to consider ratification of these statement. Please note the ALAC ratification vote will end on Monday, 28 November at 23:59 UTC. Thank you. Kind Regards, ICANN Policy Staff in support of the At-Large Community