- RDS-WHOIS2-DataAccuracy - lists.icann.org

Re: [RDS-WHOIS2-DataAccuracy] Answers to F2F Mtg #3 questions
by Jean-Baptiste Deroulez Aug. 1, 2018

Aug. 1, 2018

Dear WHOIS1 Rec#4 Subgroup, Dear WHOIS1 Recs #5-9 Subgroup, Please find below answers to questions on ARS you asked during the face-to-face meeting on 26-27 July: --- QUESTION 1: Does ARS have access to non-public data under the Temporary Specification? ANSWER 1: ARS does not have access to non-public data, and this will continue under the Temporary Specification. QUESTION 2: Is the WHOIS data that is sampled by ARS obtained from the Registrar or Registry? ANSWER 2: ARS obtains THICK data from the registries and THIN data from the registrars. QUESTION 3: (for thick TLDs, since under GDPR much contact data is redacted?) ANSWER 3: Because ARS does not currently access non-public data, there would be no change to ARS sampling methods under GDPR. --- Kind regards, Jean-Baptiste From: RDS-WHOIS2-DataAccuracy <rds-whois2-dataaccuracy-bounces(a)icann.org> on behalf of Alice Jansen <alice.jansen(a)icann.org> Date: Tuesday, July 31, 2018 at 7:20 PM To: "rds-whois2-rec4-compliance(a)icann.org" <rds-whois2-rec4-compliance(a)icann.org>, RDS-WHOIS2-DataAccuracy <rds-whois2-dataaccuracy(a)icann.org> Subject: [RDS-WHOIS2-DataAccuracy] Answers to F2F Mtg #3 questions 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 [whois.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__whois.icann.org_en_who…>. --- 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

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

Rec5-9 Subgroup - Draft for updates
by Lisa Phifer July 31, 2018

July 31, 2018

Dear Lili, Attached please find an updated draft of the Rec5-9 Data Accuracy 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. Alice will be distributing the meeting report with a list of action items and due dates separately. Best Regards Lisa

1 0

Re: [RDS-WHOIS2-DataAccuracy] FW: [RDS-WHOIS2-RT] Data Accuracy subgroup draft report
by SUN Lili June 8, 2018

June 8, 2018

Dear subgroup members, This is a reminder for you to raise any objections about draft report v3 (https://community.icann.org/download/attachments/71604714/Subgroup1-Rec5-9%…) and also share your thoughts about Volker’s comments by COB 8 June. Thank you! Lili From: RDS-WHOIS2-DataAccuracy [mailto:rds-whois2-dataaccuracy-bounces@icann.org] On Behalf Of SUN Lili Sent: Sunday, 3 June, 2018 10:38 AM To: rds-whois2-dataaccuracy(a)icann.org Subject: [RDS-WHOIS2-DataAccuracy] FW: [RDS-WHOIS2-RT] Data Accuracy subgroup draft report Dear subgroup members, As you can see from below, the draft report of this subgroup was circulated to the whole review team on 25 May. There are not significant updates to this new draft. For those who are familiar with last version, you may need only jump to section 3.5 and 4.5 to check new edits which reflected the discussion of 2nd F2F meeting. From 25 May till now, only Volker sent in some objective comments to this draft report and I responded accordingly. The email communication is also attached for your information. I personally disagree with Volker’s comments, as I took validation and verification of Whois data upon registration, transfer of domain name (contractual obligations of registrars) as first line defense to guarantee Whois accuracy, and effective compliance enforcement measures (WHOIS ARS, Whois Data Reminder Policy, Whois inaccuracy complaints, etc.) as the second line defense to improve Whois accuracy. The above is also the ground for the review of this subgroup. As to the recommendations, it has been a headache for me. Given the measures in effect or have been taken are in ideal logic to improve Whois accuracy, however the reality is still frustrated. Except strict and innovative enforcement, I couldn’t come up with new ideas. This message will serve as the last call for agreement or objections to this draft report. Please confirm by 8 June. Thanks, Lili From: RDS-WHOIS2-RT [mailto:rds-whois2-rt-bounces@icann.org] On Behalf Of SUN Lili Sent: Friday, 25 May, 2018 6:40 PM To: RDS WHOIS2-RT List <rds-whois2-rt(a)icann.org<mailto:rds-whois2-rt@icann.org>> Subject: [RDS-WHOIS2-RT] Data Accuracy subgroup draft report Dear all, Sorry for the late submission. Please refer to attached the revised version of the Data Accuracy subgroup draft report, which incorporated the discussion of 2nd F2F meeting and answers to the follow up questions on Data accuracy and Compliance from ICANN. As to the proposed recommendations, I’ll reflect in Compliance subgroup draft report. Thanks, Lili *************************************************************************************************** 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. *************************************************************************************************

1 0

FW: [RDS-WHOIS2-RT] Data Accuracy subgroup draft report
by SUN Lili June 3, 2018

June 3, 2018

Dear subgroup members, As you can see from below, the draft report of this subgroup was circulated to the whole review team on 25 May. There are not significant updates to this new draft. For those who are familiar with last version, you may need only jump to section 3.5 and 4.5 to check new edits which reflected the discussion of 2nd F2F meeting. From 25 May till now, only Volker sent in some objective comments to this draft report and I responded accordingly. The email communication is also attached for your information. I personally disagree with Volker’s comments, as I took validation and verification of Whois data upon registration, transfer of domain name (contractual obligations of registrars) as first line defense to guarantee Whois accuracy, and effective compliance enforcement measures (WHOIS ARS, Whois Data Reminder Policy, Whois inaccuracy complaints, etc.) as the second line defense to improve Whois accuracy. The above is also the ground for the review of this subgroup. As to the recommendations, it has been a headache for me. Given the measures in effect or have been taken are in ideal logic to improve Whois accuracy, however the reality is still frustrated. Except strict and innovative enforcement, I couldn’t come up with new ideas. This message will serve as the last call for agreement or objections to this draft report. Please confirm by 8 June. Thanks, Lili From: RDS-WHOIS2-RT [mailto:rds-whois2-rt-bounces@icann.org] On Behalf Of SUN Lili Sent: Friday, 25 May, 2018 6:40 PM To: RDS WHOIS2-RT List <rds-whois2-rt(a)icann.org> Subject: [RDS-WHOIS2-RT] Data Accuracy subgroup draft report Dear all, Sorry for the late submission. Please refer to attached the revised version of the Data Accuracy subgroup draft report, which incorporated the discussion of 2nd F2F meeting and answers to the follow up questions on Data accuracy and Compliance from ICANN. As to the proposed recommendations, I’ll reflect in Compliance subgroup draft report. Thanks, Lili *************************************************************************************************** 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. *************************************************************************************************

1 0

Reminder: deadline to submit subgroup report & open action item
by Jean-Baptiste Deroulez May 23, 2018

May 23, 2018

Dear WHOIS1 Rec #5-9: Data Accuracy subgroup members, We would like to kindly remind you that tomorrow – 24 May 23:59 UTC is the agreed deadline to submit your subgroup report to the review team. The latest version of your report is saved here: https://community.icann.org/download/attachments/71604714/Proposed%20Subgro… . Your dedicated subgroup wiki page: https://community.icann.org/x/6plEB . Please find below the open action item for your subgroup: * Lili to look into Compliance actions and link their work to data accuracy subgroup Similar to the preparatory work for the draft report you presented in Brussels, your ICANN support team is available to help you reflect Brussels discussions into your final report. If you need ICANN org to provide suggested language, please reach out to us at rds-whois2-staff(a)icann.org<mailto:rds-whois2-staff@icann.org>. Kind regards, Jean-Baptiste

1 0

Action Needed: Rec #5-9: Data Accuracy: Face-to-Face Meeting #2 Open Action Items
by Jean-Baptiste Deroulez May 1, 2018

May 1, 2018

Dear Rec #5-9: Data Accuracy Subgroup members, Please find below your subgroup open action items identified during the face-to-face meeting #2 in Brussels: * Lili to look into Compliance actions and link their work to data accuracy subgroup Attached to this email, you will find agreements and actions items confirmed in Brussels. Meeting archives can be found at: https://community.icann.org/x/kA_8B. Dedicated subgroup page including background documents, actions items, decisions reached: https://community.icann.org/x/6plEB. Kind regards, Jean-Baptiste

1 0

ICANN compliance input on your questions
by Alice Jansen May 1, 2018

May 1, 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(a)interpol.int> Date: Saturday 21 April 2018 at 08:53 To: "rds-whois2-dataaccuracy(a)icann.org" <rds-whois2-dataaccuracy(a)icann.org> Cc: Alice Jansen <alice.jansen(a)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@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(a)corecom.com>; rds-whois2-dataaccuracy(a)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(a)icann.org<mailto: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%20Subgro…<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_do…> along with questions enumerated in your first pass plan: https://community.icann.org/download/attachments/71604714/First%20Pass%20-%…<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_do…> 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. *************************************************************************************************

1 0

Follow up questions for ICANN Compliance
by SUN Lili April 21, 2018

April 21, 2018

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@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(a)corecom.com>; rds-whois2-dataaccuracy(a)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(a)icann.org<mailto: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%20Subgro… along with questions enumerated in your first pass plan: https://community.icann.org/download/attachments/71604714/First%20Pass%20-%… 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. *************************************************************************************************

1 0

Draft Accuracy slides for Lili to expand
by Lisa Phifer April 12, 2018

April 12, 2018

4 3