July 2018 - RDS-WHOIS2-REC4-Compliance

Answers to F2F Mtg #3 questions
by Alice Jansen July 31, 2018

July 31, 2018

Dear WHOIS1 Rec#4 Subgroup, Dear WHOIS1 Recs #5-9 Subgroup, Please find below answers to questions you asked during the face-to-face meeting on 26-27 July. --- For domains rechecked after suspension, what % are found to be unsuspended in total and the % that are still non-compliant? ICANN Contractual Compliance conducts a review of domain names subject to WHOIS Inaccuracy complaints that are closed based on the suspension of the domain names. For those domain names which are later found to be unsuspended and have the same WHOIS information, ICANN Contractual Compliance will follow up with the registrar to assess whether the registrar conducted the required verification and validation under the WHOIS Accuracy Program Specification prior to unsuspending the domain name. Of the suspended domain names reviewed for 2017, 4% were unsuspended and had the same WHOIS information. Upon following up with the registrar regarding these domain names, all registrars were able to demonstrate compliance by either providing the requested evidence required by the WHOIS Accuracy Program Specification or suspending the domain name again (where 0.4% of the unsuspended domain names were resuspended by the registrar). Is there a routine feedback process in place for Compliance to advise the ARS project of ARS-detected inaccuracies that were not ultimately found by Compliance to be inaccuracies (e.g., tickets generated because the state was missing in a country where states are not applicable)? Yes - there is a routine feedback process in place for ICANN Contractual Compliance to advise the ARS project of its findings. See https://whois.icann.org/en/whoisars-contractual-compliance-metrics. --- The answer to Does ARS have access to non-public data under the Temporary Specification? Is the WHOIS data that is sampled by ARS obtained from the Registrar or Registry (for thick TLDs, since under GDPR much contact data may be redacted?) will be provided this week. Kind regards Alice

1 0

Rec4 Subgroup - Draft for updates
by Lisa Phifer July 30, 2018

July 30, 2018

Dear Susan, Attached please find an updated draft of the Rec4 Compliance subgroup's section, including all F2F#3 agreements. Please use the attached to carry out your assigned action items this week, remembering to leave 'track changes' on to redline your edits. In addition, please consider which subsections should be moved to the new top-level section for Objective 6 - we will make those moves when compiling the next full draft. Alice will be distributing the meeting report with a list of action items and due dates separately. Best Regards Lisa

1 0

GDD Answers to your 19 July question
by Alice Jansen July 26, 2018

July 26, 2018

Hello again WHOIS1 Rec#4 subgroup, GDD’s response to your question - 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? - can be found in the attached. Kind regards Alice From: Susan Kawaguchi <susankpolicy(a)gmail.com> Date: Thursday 19 July 2018 at 16:03 To: Jean-Baptiste Deroulez <jean-baptiste.deroulez(a)icann.org>, Alice Jansen <alice.jansen(a)icann.org> Cc: RDS WHOIS2-RT List <rds-whois2-rt(a)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

1 0

Answers to your 19 July questions to ICANN Compliance
by Alice Jansen July 26, 2018

July 26, 2018

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(a)gmail.com> Date: Thursday 19 July 2018 at 16:03 To: Jean-Baptiste Deroulez <jean-baptiste.deroulez(a)icann.org>, Alice Jansen <alice.jansen(a)icann.org> Cc: RDS WHOIS2-RT List <rds-whois2-rt(a)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

1 0

NOTES - Meeting #8
by Alice Jansen July 20, 2018

July 20, 2018

Dear WHOIS1 Rec 4 – Compliance subgroup, Thank you for attending the call #8 – your meeting archives will be posted at: https://community.icann.org/display/WHO/Meeting+%238+-+Rec+4%3A+Compliance+… Decisions reached and action items are pasted below. Decisions Reached: * Rec#1 - revise to read "enforced as required" to address Stephanie's comment on F2F#2 * Rec#4 - incorporate into Outreach report existing recommendation 3.2 as a specific example of desired outreach, and refer to the Outreach recommendation from Section 3.2.1.2 in Compliance report * Rec #5 - expand recommendation text to focus on compliance processes to encourage use of Bulk tool, * Rec #8 - refer to Bulk WHOIS tool when discussing possible sources of input to identify systemic abuse * Rec#7 - discuss clarified text for this Recommendation in plenary * To address Accuracy issue where accuracy of P/P registration data is not monitored and cannot be enforced, draft a new recommendation that P/P registration data providers must adhere to the current RAA requirements for verification and validation. * Raise as comments on Rec #11 subgroup report (Common Interface) for discussion in plenary call: (1) As a result of GDPR implementation, RR and Ry interpretations may result in different registration data returned by WHOIS for the same domain name (e.g., the Ry may redact data that the RR displays) (2) Bulk data access has become less reliable (e.g., timeouts more frequent) Action Items: * Alan to update Outreach report recommendation 3.2 to incorporate compliance Rec #4 by Monday deadline * Susan to update Compliance report to incorporate all decisions above by Monday deadline Thanks, Kind regards Alice

1 0

Draft Compliance subgroup report
by Susan Kawaguchi July 19, 2018

July 19, 2018

Hello All, Please see the latest draft of the compliance subgroup report. Looking forward to the subgroup call tomorrow. Susan

1 0

ACTION REQUESTED: Doodle for WHOIS1 Rec #4-Compliance
by MSSI Secretariat July 16, 2018

July 16, 2018

Hello RDS-WHOIS2 Subgroup – WHOIS1 Rec #4-Compliance, Please select your availability from the Doodle poll link below for a subgroup call later this week. The timeline is short for this doodle and your speedy reply is greatly appreciated. https://doodle.com/poll/xpssrbhdkmq9a5rh Many thanks! With kind regards, Brenda -- Brenda Brewer, Projects & Operations Assistant Multistakeholder Strategy & Strategic Initiatives (MSSI) Internet Corporation for Assigned Names and Numbers (ICANN) Skype: brenda.brewer.icann

1 0