[RDS-WHOIS2-DataAccuracy] ICANN compliance input on your questions

Tue May 1 08:05:24 UTC 2018

Dear Data Accuracy Subgroup,
Attached to this email you will ICANN Compliance’s answers to your list of questions below.
Thanks so much,
Kind regards
Alice

From: SUN Lili <L.SUN at interpol.int>
Date: Saturday 21 April 2018 at 08:53
To: "rds-whois2-dataaccuracy at icann.org" <rds-whois2-dataaccuracy at icann.org>
Cc: Alice Jansen <alice.jansen at icann.org>
Subject: [Ext] Follow up questions for ICANN Compliance

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:

  *   Data-Accuracy Subgroup Follow-up Questions 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?
[cid:image002.jpg at 01D3D7DE.F0100690]

  *   Compliance Subgroup Follow-up Questions for ICANN Compliance
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 at corecom.com>; rds-whois2-dataaccuracy at 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 at icann.org] On Behalf Of Lisa Phifer
Sent: Tuesday, 10 April, 2018 9:07 AM
To: rds-whois2-dataaccuracy at icann.org<mailto:rds-whois2-dataaccuracy at 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[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_71604714_Proposed-2520Subgroup-2520Report-2520Structure-2520Rec-2520-25235-2D9-2520Data-2520Accuracy.docx&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=hgoi2V8bykqXjZC9kZZRTDSEJ4lQIyKh6k8Q-TUv6Ks&m=HK46xWqd5l7_-lrwNi7xi_iZV4U52cSNP06wI30J3O0&s=7jN4PsK9D0uNzXyXKD4xg5w7RtuSKjCrxbq04zX5_fY&e=>
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[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_71604714_First-2520Pass-2520-2D-2520WHOIS1-2520Rec-2520-25235-2D9-2520-2D-2520Data-2520Accuracy-2520v4.0.docx&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=hgoi2V8bykqXjZC9kZZRTDSEJ4lQIyKh6k8Q-TUv6Ks&m=HK46xWqd5l7_-lrwNi7xi_iZV4U52cSNP06wI30J3O0&s=fIjdmJNXWn7LebysR3cx4EOaDD5kiNKmBt-Xe3IQC7Q&e=>

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
***************************************************************************************************
This message, and any attachment contained, are confidential and subject of legal privilege. It may be used solely for the designated police/justice purpose and by the individual or entity to whom it is addressed. The information is not to be disseminated to another agency or third party without the author’s consent, and must not be retained longer than is necessary for the fulfilment of the purpose for which the information is to be used. All practicable steps shall be taken by the recipients to ensure that information is protected against unauthorised access or processing. INTERPOL reserves the right to enquire about the use of the information provided.
If you are not the intended recipient, be advised that you have received this message in error. In such a case, you should not print it, copy it, make any use of it or disclose it, but please notify us immediately and delete the message from any computer.
*************************************************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/rds-whois2-dataaccuracy/attachments/20180501/31a44a99/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 24917 bytes
Desc: image001.jpg
URL: <http://mm.icann.org/pipermail/rds-whois2-dataaccuracy/attachments/20180501/31a44a99/image001-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Data Accuracy questions - April 2018.pdf
Type: application/pdf
Size: 667454 bytes
Desc: Data Accuracy questions - April 2018.pdf
URL: <http://mm.icann.org/pipermail/rds-whois2-dataaccuracy/attachments/20180501/31a44a99/DataAccuracyquestions-April2018-0001.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Compliance questions - April 2018.pdf
Type: application/pdf
Size: 876370 bytes
Desc: Compliance questions - April 2018.pdf
URL: <http://mm.icann.org/pipermail/rds-whois2-dataaccuracy/attachments/20180501/31a44a99/Compliancequestions-April2018-0001.pdf>