Registration Data Accuracy Scoping Team: Difference between revisions

Line 22:

* consider whether a new or updated accuracy measurement programme (including ARS or a successor) could be effectively implemented.<ref name="rda-formation"></ref>

The first meeting of the Registration Data Accuracy Scoping Team took place on 5 ~~October~~ 2021, and the team met on a weekly basis thereafter.<ref name="rda-gac-briefing-icann82">[https://gac.icann.org/briefing-materials/public/icann82-gac-briefing-session-13-whois-and-registration-data-issues-v2.pdf ICANN GAC: WHOIS and Registration Data Issues]</ref>

The first meeting of the Registration Data Accuracy Scoping Team took place on October 5, 2021, and the team met on a weekly basis thereafter.<ref name="rda-gac-briefing-icann82">[https://gac.icann.org/briefing-materials/public/icann82-gac-briefing-session-13-whois-and-registration-data-issues-v2.pdf ICANN GAC: WHOIS and Registration Data Issues]</ref>

== Mandate and Scope ==

The Formation and Instructions document organised the work into four main assignments:

* Enforcement and reporting: assess how existing registration data accuracy requirements are currently implemented and enforced, including ICANN Contractual Compliance activities, complaint-handling mechanisms, and any evidence of systemic issues in accuracy.

* Measurement of accuracy: examine how accuracy has been and could be measured, including a review of past efforts such as WHOIS ARS, and recommend how levels of accuracy might be determined and measured under current legal and technical constraints.

* Effectiveness of accuracy requirements: consider the effectiveness of existing accuracy requirements in ICANN contracts and consensus policies, including whether these are fit for purpose in light of GDPR and other data protection laws.

* Possible changes or further work: determine whether changes to existing requirements, new accuracy-related programmes, or initiation of a GNSO policy development process (or other mechanism) should be recommended.<ref name="rda-formation"></ref>

As an initial question, the Scoping Team was also asked to determine whether there was an agreed definition of “registration data accuracy”. Failing agreement, it was asked to consider working definitions to use in its deliberations.<ref name="rda-formation"></ref> In practice the team did not reach consensus on a single definition and instead referred to the description of validation and verification obligations in the 2013 Registrar Accreditation Agreement (RAA) Registration Data Directory Services (RDDS) Accuracy Programme Specification, using “operability” of contact data as a minimum baseline.<ref name="rda-assessment">[https://gnso.icann.org/sites/default/files/policy/2023/correspondence/yokoyama-to-gnso-council-et-al-19oct23-en.pdf ICANN GNSO: Assessment of Registration Data Accuracy Scenarios]</ref>

== Work and Deliberations ==

The Scoping Team’s work was heavily informed by materials developed by ICANN org, including:

* the February 2021 briefing “Registration Data Accuracy Requirements and the European GDPR”,<ref name="rda-briefing"></ref>

* a January 2022 memorandum on the WHOIS Accuracy Reporting System (ARS), and

* responses to follow-up questions from the Scoping Team, including information on Contractual Compliance practices and historical accuracy studies.

The team also reviewed findings from the WHOIS ARS reports, relevant sections of the RDS-WHOIS2 and SSR2 review reports, and existing ICANN Contractual Compliance statistics related to accuracy.<ref name="rda-writeup"></ref>

== References ==

@@ Line 22: / Line 22: @@
 * consider whether a new or updated accuracy measurement programme (including ARS or a successor) could be effectively implemented.<ref name="rda-formation"></ref>
-The first meeting of the Registration Data Accuracy Scoping Team took place on 5 October 2021, and the team met on a weekly basis thereafter.<ref name="rda-gac-briefing-icann82">[https://gac.icann.org/briefing-materials/public/icann82-gac-briefing-session-13-whois-and-registration-data-issues-v2.pdf ICANN GAC: WHOIS and Registration Data Issues]</ref>
+The first meeting of the Registration Data Accuracy Scoping Team took place on October 5, 2021, and the team met on a weekly basis thereafter.<ref name="rda-gac-briefing-icann82">[https://gac.icann.org/briefing-materials/public/icann82-gac-briefing-session-13-whois-and-registration-data-issues-v2.pdf ICANN GAC: WHOIS and Registration Data Issues]</ref>
+== Mandate and Scope ==
+The Formation and Instructions document organised the work into four main assignments:
+* Enforcement and reporting: assess how existing registration data accuracy requirements are currently implemented and enforced, including ICANN Contractual Compliance activities, complaint-handling mechanisms, and any evidence of systemic issues in accuracy.
+* Measurement of accuracy: examine how accuracy has been and could be measured, including a review of past efforts such as WHOIS ARS, and recommend how levels of accuracy might be determined and measured under current legal and technical constraints.
+* Effectiveness of accuracy requirements: consider the effectiveness of existing accuracy requirements in ICANN contracts and consensus policies, including whether these are fit for purpose in light of GDPR and other data protection laws.
+* Possible changes or further work: determine whether changes to existing requirements, new accuracy-related programmes, or initiation of a GNSO policy development process (or other mechanism) should be recommended.<ref name="rda-formation"></ref>
+As an initial question, the Scoping Team was also asked to determine whether there was an agreed definition of “registration data accuracy”. Failing agreement, it was asked to consider working definitions to use in its deliberations.<ref name="rda-formation"></ref> In practice the team did not reach consensus on a single definition and instead referred to the description of validation and verification obligations in the 2013 Registrar Accreditation Agreement (RAA) Registration Data Directory Services (RDDS) Accuracy Programme Specification, using “operability” of contact data as a minimum baseline.<ref name="rda-assessment">[https://gnso.icann.org/sites/default/files/policy/2023/correspondence/yokoyama-to-gnso-council-et-al-19oct23-en.pdf ICANN GNSO: Assessment of Registration Data Accuracy Scenarios]</ref>
+== Work and Deliberations ==
+The Scoping Team’s work was heavily informed by materials developed by ICANN org, including:
+* the February 2021 briefing “Registration Data Accuracy Requirements and the European GDPR”,<ref name="rda-briefing"></ref>
+* a January 2022 memorandum on the WHOIS Accuracy Reporting System (ARS), and
+* responses to follow-up questions from the Scoping Team, including information on Contractual Compliance practices and historical accuracy studies.
+The team also reviewed findings from the WHOIS ARS reports, relevant sections of the RDS-WHOIS2 and SSR2 review reports, and existing ICANN Contractual Compliance statistics related to accuracy.<ref name="rda-writeup"></ref>
 == References ==