Attachment protected by Amazon: [GNSO_Council_Assignments_Proposal on Accuracy.docx] https://us-east-1.secure-attach.amazon.com/a1a8bd9c-167a-47d9-885f-625701c91... Amazon has replaced attachment with download link. Downloads will be available until October 12, 2024, 13:47 (UTC+00:00). [Tell us what you think] https://amazonexteu.qualtrics.com/jfe/form/SV_ehuz6zGo8YnsRKK [For more information click here] https://docs.secure-attach.amazon.com/guide Dear Councilors, During our August meeting we discussed next steps on accuracy. While Councilors generally agreed that restarting the scoping team seemed premature given the limitations on collecting data, we did not agree on next steps. We discussed the possibility of forming a Council small team to solicit feedback from the Community and try reach a common understanding of the underlying issues. However, others suggested that this work should not be undertaken until we have more clarity around the implementation of accuracy requirements in the Network and Information Security (NIS 2) Directive being implemented in the EU. Taking all this under consideration, Council Leadership proposes the following path forward (this approach is outlined in the attached document): First, seek input from ICANN's legal team on the state of current and near future legislation that may affect requirements related to the accuracy of registrant information. Second, when this is complete, pose a set of threshold framing questions to each Stakeholder Group/Constituency (SG/C) that will guide our conversation (including the analysis on whether to form a small team). These questions will be informed by the feedback from ICANN on potential regulation that may impact our work. Please review the attached document and discuss with your respective SGs. The specific questions contained in this document are merely a starting point and so please proceed under the assumption they can be modified. We will discuss in our September meeting. Thanks, Greg