[RDS-WHOIS2-REC4-Compliance] Answers to your 19 July questions to ICANN Compliance

[Alice Jansen]

Hi WHOIS1 Rec #4 subgroup!
Please find attached ICANN compliance’s input in response to your questions:
How many reports they have received concerning timeouts on the WHOIS lookup tool on ICANN.org?
How many WHOIS inaccuracy reports relate to proxy privacy registrations?
We will share GDD’s answer to your question below as soon as we receive it.
Kind regards
Alice
From: Susan Kawaguchi <susankpolicy at gmail.com>
Date: Thursday 19 July 2018 at 16:03
To: Jean-Baptiste Deroulez <jean-baptiste.deroulez at icann.org>, Alice Jansen <alice.jansen at icann.org>
Cc: RDS WHOIS2-RT List <rds-whois2-rt at icann.org>
Subject: [Ext] Additional questions

Hello Jean-Baptiste and Alice,

I have several additional questions.  Is it possible to send the following questions to the appropriate parties?

For GDD

If we assume the sample of ARS domain names of 40% grandfathered domain names then we can extrapolate this to 40% of all domain names registered before 2013 MAY not have this registrant data collected, displayed, verified or validated. Can GDD tell us how many domain names total fall into the Grandfathered category?

For ICAAN compliance

How many reports they have received concerning timeouts on the WHOIS lookup tool on ICANN.org?

How many WHOIS inaccuracy reports relate to proxy privacy registrations?


 Thanks,

Susan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/rds-whois2-rec4-compliance/attachments/20180726/7f4f13c6/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: RDS-WHOIS2 Compliance Questions July 2018 FINAL[1].docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 27993 bytes
Desc: RDS-WHOIS2 Compliance Questions July 2018 FINAL[1].docx
URL: <http://mm.icann.org/pipermail/rds-whois2-rec4-compliance/attachments/20180726/7f4f13c6/RDS-WHOIS2ComplianceQuestionsJuly2018FINAL1-0001.docx>