Dear Subgroup members,
Following our discussion on Data Accuracy and Compliance during the F2F meeting earlier this week, the following questions have been proposed and confirmed by Susan for ICANN Compliance:
1.
Does the Compliance Team attempt to identify patterns within ARS-detected inaccuracies to enable proactive remediation
of underlying causes?
2.
If a domain registration is suspended due to a reported or detected WHOIS inaccuracy, can the domain name be un-suspended
without the inaccuracy being remediated?
3.
Does the WHOIS Quality Review (or any other program) audit how often un-suspension without accuracy remediation occurs?
If so, for how long after suspension are those follow-up accuracy checks performed?
4.
Considering ARS compliance metrics: Why are the percentage of ticketed domains that end up being suspended or cancelled
is increasing?

1.
Is it known (or can it be determined from ARS-sampled data) how often Registrant Contact data elements such as Registrant
email address, Registrant postal address, and Registrant telephone number are absent from WHOIS records for grandfathered domain names?
2.
Why are a significant number of WHOIS Inaccuracy Complaints closed without any action being taken? What does Compliance
treat as valid reasons for immediate ticket closure and are there any metrics for how often tickets are closed for each of those reasons?
3.
What additional evidence in WHOIS Inaccuracy Complaints would Compliance find useful?
4.
Does Compliance do any analysis of WHOIS Inaccuracy trends? If not, why not? For example, would a policy be necessary
to enable trend analysis?
5.
It shows that one of Compliance activities is ICANN-initiated monitoring to take proactive actions. What kind of monitoring
programs have been conducted or planned?
6.
Is there any monitoring program to check some common grounds or linkages among ARS, Audit Program, public complaints
received, e.g. from specific registrar, gTLD, region?
7.
Does compliance credit-rate registrars or just treat all of them equally?
For your information and comments, thank you!
Lili
From: SUN Lili
Sent: Thursday, 12 April, 2018 8:29 PM
To: 'Lisa Phifer' <lisa@corecom.com>; rds-whois2-dataaccuracy@icann.org
Subject: RE: [RDS-WHOIS2-DataAccuracy] Draft Accuracy slides for Lili to expand
Hi all,
Attached is the slides I’m going to present during the F2F meeting next Monday.
Best regards,
Lili
From: RDS-WHOIS2-DataAccuracy [mailto:rds-whois2-dataaccuracy-bounces@icann.org]
On Behalf Of Lisa Phifer
Sent: Tuesday, 10 April, 2018 9:07 AM
To: rds-whois2-dataaccuracy@icann.org
Subject: [RDS-WHOIS2-DataAccuracy] Draft Accuracy slides for Lili to expand
Dear Recs 5-9 (Accuracy) Subgroup -
As discussed in our plenary call, attached are draft slides for Lili to review/revise on behalf of your subgroup.
The content of these slides is based on this draft subgroup report:
https://community.icann.org/download/attachments/71604714/Proposed%20Subgroup%20Report%20Structure%20Rec%20%235-9%20Data%20Accuracy.docx
along with questions enumerated in your first pass plan:
https://community.icann.org/download/attachments/71604714/First%20Pass%20-%20WHOIS1%20Rec%20%235-9%20-%20Data%20Accuracy%20v4.0.docx
As a reminder, here is the timeline for slide completion:
• Monday 9 April COB - ICANN org support team to send draft slides to subgroup Rapporteurs
• Thursday 12 April COB - Rapporteurs to send final updates to slides to ICANN org support team
• Friday 13 April COB - ICANN org support team to circulate final slide-deck with the review team
Regards
Lisa