Link (content reproduced below):
...
- Registration Data Accuracy Requirements and the General Data Protection Regulation (GDPR)(ICANN org briefing doc)
- Enforcement of Registration Data Accuracy Obligations Before and After GDPR (Blog post by Jamie Hedlund, ICANN org)
- ICANN Organization Enforcement of Registration Data Accuracy Obligations Before and After GDPR
- ICANN org responses to RDS-WHOIS2 RT questions related to accuracy (see also compilation)
As the team continues its deliberations, further questions may arise, but we hope that with the list below we have identified the most pertinent ones.
...
The Council instructions to the scoping team (https://icann-community.icannatlassian.orgnet/wiki/displayspaces/AST/pages/103580947/2.+Council+Instructions+to+Scoping+Team) include the following charge:
...
As noted in real-time during the discussion, metrics from Compliance are based on complaints received. Prior to the transition to the Naming Services portal (NSp) on 29 August 2020, ICANN did not track complaints received by reporter type, as the level of granularity in reporting was limited within the legacy system. ICANN Contractual Compliance’s monthly dashboard contains historical data about complaints received/closed that are related to accuracy which is available here. Additional information specifically addressing complaints received before and after GDPR went into effect is available here.
3. What is the status of the DPA negotiation between ICANN org and contracted parties?
...