Hello team, Sincere apologies for the tardiness of the two of the final review documents. Below are the EWG Tutorial and FAQ content related to Purpose. EWG Tutorial, Pages 17-20, 37-41 http://london50.icann.org/en/schedule/mon-ewg-final-overview/presentation-ew... Associated audio & transcript: http://audio.icann.org/meetings/london2014/ewg-final-overview-23jun14-en.mp3 https://london50.icann.org/en/schedule/mon-ewg-final-overview/transcript-ewg... Page 17 This page presents the purposes surfaced through EWG work. It is noted in the audio and on the presentation the purposes presented may not meet *all* use cases. Any solution must be flexible to allow for future purpose needs. Page 18 Recognition is made every permissible purpose as data needs, but they vary. Some may be widely used with minimal control standards whereas others will require higher scrutiny and authority for access. Also introduced are the potential provisions for whowas (history) or reverse (related domains) queries. Page 19 Purpose based contact (PBC) is a proposal to offer better control of personal information and more efficient portability of contact data. Page 20 Workflow example of Gate access in a legal action is presented. It walks through how the process would operate with authentication service. If the requestor was authorized for access and to what level, then provide data only relevant to their need and their approval level. Page 21 Presentation page contains what could be in PBC data, noting that PBC may still be a proxy service. It offers users choices to determine what they want for contact information, what information willing to share at what level, and ability to update information once not across multiple platforms. (not on audio or transcript I could find): Page 38 Provides a chart with identified Purpose and associated Task for each. Page 39 Purposed Based Contacts (PBC) examples are provided as backup to the presentation. The EWG supplied three specific examples of use as Individual using own data, Individual or Org using a Privacy service and a Business using 3rd party PBC. Page 40 The table of Purposes and Needs is provided as backup to the presentation. The table defines the query scope, type of contacts needed based on purpose, registrant data availability level and other queries that may be needed for specific purposes, such as Reverse and WhoWas. Page 41 The PBC and their responsibilities are defined and provided as backup to the presentation. These are the proposed referenced throughout the presentation. ~~~~~ Expert Working Group on gTLD Directory Services (EWG) Frequently Asked Questions (FAQs) – 2014 Final Report Update https://community.icann.org/display/EWG/EWG+FAQs Five (5) FAQ’s specifically addressed Purpose, captured below. (Page 5) *Registration Data Users and Purposes * 9) Who are the users of the RDS? How did the EWG determine this? The EWG analyzed previous reports and use cases to identify users who want access to gTLD registration data, including registrants, protected registrants, on-line service providers, business Internet users, intellectual property owners, law enforcement agencies and OpSec staff, Internet technical staff, individual Internet users, Internet researchers, non-LEA investigators of malicious activity, the general public, and bad actors. 10) Why do those users need access to registration data? Use cases also shed light on rationale and purposes served by gTLD registration data, including domain name control, regulatory/contract enforcement, academic/public interest domain name research, domain name purchase/sale, personal data protection, individual Internet use, technical issue resolution, domain name certification, legal action, regulatory and contractual enforcement, criminal investigation and DNS abuse mitigation, DNS transparency, and malicious Internet activities. 11) Which purposes should not be permissible? Given no rationale for accommodating the needs of some users but not others that access WHOIS today, the EWG recommended the RDS accommodate all non-malicious uses. 12) Why didn’t the EWG consider user X or purpose Y? Use cases examined by the EWG were not exhaustive, but representative enough of existing and potential uses to establish RDS needs. The EWG also recommended a process for adding new purposes as may be required to address future global Internet needs. 67) How will members of the press and bloggers gain access to RDS data? The DNS Transparency purpose was intended to cover media needs for registration data. However, if the data available for that permissible purpose does not prove sufficient, the EWG also recommended an on-going process for users to suggest new permissible purposes. ~~~~ Susan Prosser VP, Client Services DomainTools, LLC T: (206) 838-9060 E: susan@domaintools.com PGP: A2C4D2A4