Difference between revisions of "Accuracy"

From ICANNWiki
Jump to navigation Jump to search
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 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/>
 
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>
+
In October 2021, the scoping team began its deliberations, focusing on defining, enforcing, reporting, and measuring accuracy. As of [[ICANN 75]], the team 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.  
+
Specifically, the Scoping Team recommended to the GNSO Council:<ref>[https://75.schedule.icann.org/meetings/mLgjoa3GEzrYfnKba Accuracy Scoping Team Sessions, ICANN 75]</ref>
 +
# requests that ICANN org carry out a Registrar Survey
 +
# explore the option of conducting a Registrar Audit
 +
Or
 +
# pause the work involving proposals requiring access to registration data until it's a viable path
 +
# request that ICANN org proceed with their outreach to EDPB with urgency as well as DPIA in connection with the scenarios
 +
# encourage the finalizing the DPA between ICANN org and Contracted Parties
 +
 
 +
The [[ICANN Board]] has also 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>
 
''Scoping Team Members:''<ref>[https://community.icann.org/pages/viewpage.action?pageId=170787487 Accuracy Scoping Team Members, Community, ICANN]</ref>

Revision as of 15:58, 6 October 2022

Data Accuracy is the state of error-free records that can be used as a reliable source of information. Types of data accuracy discussed by the GNSO's Registration Data Accuracy Scoping Team include: syntactical, operational, and validated.[1]

Related Debates

Where people fall in terms of the following debates may affect their perspectives on the value of achieving complete data accuracy.

What's more important? Data Privacy or Cybersecurity

  • The Data Privacy camp,[2] such as proponents of GDPR, argues natural persons have a right to their privacy and encourages limiting broad access to accurate personal or identifying data.
  • Cybersecurity workers and enthusiasts insist that data accuracy is important to mitigating DNS Abuse as law enforcement agencies and regulatory bodies need it for notifying victims, acting as a dissuading factor for bad actors, and ultimately catching perpetrators.[3]

Will Ensuring Data Accuracy actually stop bad actors

  • Data registration regulation flowing down the ICANN hierarchy may not reach malicious activity because hackers do not provide accurate email addresses, money trails, or registration data.[4]

Post-GDPR

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.[5]
In October 2021, the scoping team began its deliberations, focusing on defining, enforcing, reporting, and measuring accuracy. As of ICANN 75, the team 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.[6] Specifically, the Scoping Team recommended to the GNSO Council:[7]

  1. requests that ICANN org carry out a Registrar Survey
  2. explore the option of conducting a Registrar Audit

Or

  1. pause the work involving proposals requiring access to registration data until it's a viable path
  2. request that ICANN org proceed with their outreach to EDPB with urgency as well as DPIA in connection with the scenarios
  3. encourage the finalizing the DPA between ICANN org and Contracted Parties

The ICANN Board has also 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:[8]

References

  1. ↑ Registration Data Accuracy Scoping Team Meeting, GNSO, ICANN 72
  2. ↑ Data Privacy Associations, Privacy Bee
  3. ↑ Gabriel Andrews, of the FBI, representing the Public Safety Working Group, on the GAC Discussions: IGO Protection Matters and DNS Abuse Mitigation Panel, ICANN 72
  4. ↑ Theo Geurts, presenting on a DNS Abuse Dashboard at the GNSO: NCSG Membership Meeting, ICANN 72]
  5. ↑ GNSO Council Project List, August 2022, Community, ICANN
  6. ↑ EPDP-IDNs Background, GNSO Sessions, ICANN 75 Policy Outlook
  7. ↑ Accuracy Scoping Team Sessions, ICANN 75
  8. ↑ Accuracy Scoping Team Members, Community, ICANN
Retrieved from "https://icannwiki.org/index.php?title=Accuracy&oldid=1345034"