Hi Jean-Baptiste, I was in the second slot but had issues with the Adobe Connect all the way, was only on the voice bridge. Were there any questions, especially on Data Accuracy, and Plan&report? Thank you! Lili From: Jean-Baptiste Deroulez [mailto:jean-baptiste.deroulez@icann.org] Sent: Monday, 17 September, 2018 5:16 PM To: SUN Lili <L.SUN@interpol.int> Cc: rds-whois2-rt@icann.org Subject: Re: [Ext] RE: Webinar: Registration Directory Service (RDS)-WHOIS2 Review Draft Report | 17 September 2018 | 15:00 UTC - 21:00 UTC Hi Lili, Thank you for your feedback. I have updated the slides accordingly. Please find the updated version attached. Regarding your suggested update to Data Accuracy findings section, I reread the report and there seems to be a difference between what appears in the Executive Summary and what stands in the body of the report (see below). I have included your suggested edits in the slides deck. “Data Accuracy: WHOIS1 Recommendations #5-9 dealt with several issues related to RDS (WHOIS) accuracy. The implementation of these recommendations resulted in a significant effort on behalf of ICANN Org and there is now a better understanding. However, there are still many gaps in our understanding of accuracy issues. Although the syntactic accuracy of data has improved, it is less clear what the impact has been on whether the data allows identification of and contact with registrants. GDPR may ultimately obscure accuracy even more by making it more difficult to assess whether the data within the RDS (WHOIS) repository is accurate or not. Two of the recommendations were deemed to be fully implemented and three were partially or not implemented.” [cid:image001.png@01D44E77.D3CE62A0] Kind regards, Jean-Baptiste From: SUN Lili <L.SUN@interpol.int<mailto:L.SUN@interpol.int>> Date: Sunday, September 16, 2018 at 6:42 AM To: Jean-Baptiste Deroulez <jean-baptiste.deroulez@icann.org<mailto:jean-baptiste.deroulez@icann.org>> Cc: "rds-whois2-rt@icann.org<mailto:rds-whois2-rt@icann.org>" <rds-whois2-rt@icann.org<mailto:rds-whois2-rt@icann.org>> Subject: [Ext] RE: Webinar: Registration Directory Service (RDS)-WHOIS2 Review Draft Report | 17 September 2018 | 15:00 UTC - 21:00 UTC Hi Jean-Baptiste, A typo on slide 6, in Dec 2018 we’ll have the #4 F2F meeting, not #3. I proposed new text for Data Accuracy on slide 16, and Planning/Reports on slide 18 as below, for consideration: Data Accuracy WHOIS1 Recommendations #5-9 dealt with several issues related to RDS (WHOIS) accuracy. • Fully Implemented: 1 rec. • Registrant education on the requirements for accurate RDS (WHOIS) data has been duly conducted through the RDS (WHOIS) Informational Website, 2009/2013 RAA, and Registrar’s website. • Partially implemented : 3 recs. • An enforceable chain of contractual agreements with registries, registrars, and registrants to require the provision and maintenance of accurate RDS (WHOIS) data has been enacted. · The Accuracy Reporting System (ARS) project has been launched to proactively identify inaccurate RDS (WHOIS) data, and forward to registrars for action, but only on a sample basis. Syntax and operability accuracy have been improved. · RDS (WHOIS) identity accuracy checks have not yet been implemented within ARS project, not clear whether the data allows identification of and contact with registrants. · Considerable ARS-generated tickets closed with no action because the RDS (WHOIS) record changed in a relatively short period of time (4-5 months). · Registrar’s contractual obligations for RDS (WHOIS) accuracy have only been passively enforced. · RDS (WHOIS) accuracy for domain names that utilize Privacy and Proxy Services is unknown. · GDPR may ultimately obscure data accuracy within the RDS (WHOIS) · Not implemented: 1 rec. o No metrics-based assessment of RDS (WHOIS) data quality improvements. Planning/Reports • WHOIS1 Recommendations #15-16: addressed the need for planning and reporting to carry out and track implementation of WHOIS1 recommendations. • Partially implemented: Plans and reports were done. • Not as complete/useful as intended, the reports were more activity-based than outcome-based, without sufficient underlying facts, figures and analyses. Thanks, Lili From: RDS-WHOIS2-RT [mailto:rds-whois2-rt-bounces@icann.org] On Behalf Of Jean-Baptiste Deroulez Sent: Saturday, 15 September, 2018 7:05 AM To: Cathrin Bauer via RDS-WHOIS2-RT <rds-whois2-rt@icann.org<mailto:rds-whois2-rt@icann.org>> Subject: [RDS-WHOIS2-RT] Webinar: Registration Directory Service (RDS)-WHOIS2 Review Draft Report | 17 September 2018 | 15:00 UTC - 21:00 UTC Dear review team members, In anticipation of the webinar scheduled for Monday 17 September at 15:00 and 21:00 UTC, please find the latest version of the slides attached. Alan, Cathrin and Susan will be presenting the slides, however, you may be invited to step in and answer questions from the participants during the Q&A. We would appreciate if you could confirm before 16 September 23:59 UTC to me and MSSI Secretariat (mssi-secretariat@icann.org<mailto:mssi-secretariat@icann.org>) whether you’ll be able to attend both sessions. More information on the webinar and registration details: https://community.icann.org/x/ZgmNBQ. Kind regards, Jean-Baptiste *************************************************************************************************** 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. *************************************************************************************************
