Dear All, Thank you for the work that has gone into the drafting of this statement of purpose. I wanted to briefly share some comments on version 6 of the draft Statement of Purpose and express support to some of the suggestions put forward by Greg Aaron, Marc Anderson and Stephanie Perrin. First, on “specific purposes”: I believe that the specific purposes currently listed under 3a) and 3b) should not be regarded as secondary to 1) and 2). They should therefore be listed as 3) and 4) as suggested by Marc Anderson and Greg Aaron. There is certainly a TLD Operations perspective to the purpose of an RDS, but we must also recognize that operations of TLDs have socio-economic impacts that lead to other purposes of an RDS, as is the case for: · facilitating contact with registrants, · registrars and proxy/privacy service providers enabling release of accurate gTLD registration data. Second, on the notion of accuracy: Although I support the simplification to the language of specific purposes 3a) and 3b) (which should be renumbered 3 and 4), as proposed by Marc, I share Greg’s views that the notion of “accurate” gTLD registration data should not just be deemed a feature, but rather an integral part of the purpose considering the importance of maintaining a repository of accurate data form a public policy perspective. As you know, the GAC has consistently advised that gTLD WHOIS services “should provide sufficient and accurate data about domain name registrations and registrants subject to national safeguards for individuals’ privacy” (per its 2007 GAC WHOIS Principles<https://gacweb.icann.org/download/attachments/28278834/WHOIS_principles.pdf>, which it referred to in its 2015 comments on the RDS PDP Preliminary Issue Report<https://forum.icann.org/lists/comments-rds-prelim-issue-13jul15/msg00012.htm...>). I therefore support Greg Aaron’s suggestion to add a fifth purpose: “A purpose of a system to collect, maintain, and provide access to gTLD registration data (hereafter referred to as “the RDS”) is to collect and provide information that is accurate.” I am also supportive of the simplification to the goals and criteria proposed by Stephanie Perrin as I see value in keeping this statement of purpose as succinct as possible. Best Regards Greg Mounier Europol – EC3 From: gnso-rds-pdp-wg-bounces@icann.org [mailto:gnso-rds-pdp-wg-bounces@icann.org] On Behalf Of Marika Konings Sent: 28 September 2016 19:12 To: gnso-rds-pdp-wg@icann.org Subject: [gnso-rds-pdp-wg] For your review - updated RDS Statement of Purpose Dear All, Please find attached for your review the updated statement of purpose which aims to reflect the changes discussed during yesterday’s meeting. You are all encouraged to review this version, especially the section ‘Specific Purposes for Registration Data and Registration Directory Services’, and share your input with the mailing list prior to next week’s meeting. Also note that a couple of WG members (Marc & Fabrizio) volunteered to provide updated language for two specific parts of the document which have been flagged accordingly, so please hold your comments on those parts until the proposed language has been circulated. Best regards, Marika Marika Konings Senior Policy Director & Team Leader for the GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings@icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-e...>. ******************* DISCLAIMER : This message is sent in confidence and is only intended for the named recipient. If you receive this message by mistake, you may not use, copy, distribute or forward this message, or any part of its contents or rely upon the information contained in it. Please notify the sender immediately by e-mail and delete the relevant e-mails from any computer. This message does not constitute a commitment by Europol unless otherwise indicated. *******************