Accuracy: Difference between revisions

Line 10:

On 21 October 2020, the [[GNSO Council]] adopted a proposal that recommended that a Scoping Team address the effects of [[GDPR]] on Registration Data accuracy requirements and the [[Whois]] Accuracy Reporting System (ARS).

On 22 July 2021, the GNSO Council confirmed the formation of the Accuracy Scoping Team tasked to consider accuracy-related factors such as the current enforcement, reporting, measurement, and overall effectiveness of accuracy-related efforts. These considerations will inform the deliberations and development of recommendations to the GNSO Council to improve accuracy levels.<ref>[https://community.icann.org/display/gnsocouncilmeetings/Project+List?preview=/150178773/210469897/GNSO_Council_Project-List_20220825.pdf GNSO Council Project List, August 2022, Community, ICANN]</ref><br/>

In October 2021, the scoping team began its deliberations, focusing on defining, enforcement and reporting, and measuring accuracy. As of [[ICANN 75]], the team is focused on proposals that do not require access to gTLD registration data, such as a registrar survey or registrar audit, but is concerned about low participation.<ref>[https://meetings.icann.org/en/remote75/icann75-policy-outlook-report-05sep22-en, EPDP-IDNs Background, GNSO Sessions, ICANN 75 Policy Outlook]</ref>

The [[ICANN Board]] directed [[ICANN Organization]] to develop scenarios for obtaining access to gTLD registration data to confirm accuracy that could be tested with the European Data Protection Board (EDPB). As of September 2022, the EDPB has not responded.

''Scoping Team Members:''<ref>[https://community.icann.org/pages/viewpage.action?pageId=170787487 Accuracy Scoping Team Members, Community, ICANN]</ref>

* [[Volker Greimann]]

@@ Line 10: / Line 10: @@
 On 21 October 2020, the [[GNSO Council]] adopted a proposal that recommended that a Scoping Team address the effects of [[GDPR]] on Registration Data accuracy requirements and the [[Whois]] Accuracy Reporting System (ARS).
 On 22 July 2021, the GNSO Council confirmed the formation of the Accuracy Scoping Team tasked to consider accuracy-related factors such as the current enforcement, reporting, measurement, and overall effectiveness of accuracy-related efforts. These considerations will inform the deliberations and development of recommendations to the GNSO Council to improve accuracy levels.<ref>[https://community.icann.org/display/gnsocouncilmeetings/Project+List?preview=/150178773/210469897/GNSO_Council_Project-List_20220825.pdf GNSO Council Project List, August 2022, Community, ICANN]</ref><br/>
 In October 2021, the scoping team began its deliberations, focusing on defining, enforcement and reporting, and measuring accuracy. As of [[ICANN 75]], the team is focused on proposals that do not require access to gTLD registration data, such as a registrar survey or registrar audit, but is concerned about low participation.<ref>[https://meetings.icann.org/en/remote75/icann75-policy-outlook-report-05sep22-en, EPDP-IDNs Background, GNSO Sessions, ICANN 75 Policy Outlook]</ref>
+The [[ICANN Board]] directed [[ICANN Organization]] to develop scenarios for obtaining access to gTLD registration data to confirm accuracy that could be tested with the European Data Protection Board (EDPB). As of September 2022, the EDPB has not responded.
 ''Scoping Team Members:''<ref>[https://community.icann.org/pages/viewpage.action?pageId=170787487 Accuracy Scoping Team Members, Community, ICANN]</ref>
 * [[Volker Greimann]]