<div dir="ltr"><div>Hello team, </div><div>Sincere apologies for the tardiness of the two of the final review documents. Below are the EWG Tutorial and FAQ content related to Purpose. </div><div><br></div><div>
<p class="MsoNormal"><span style="font-family:Calibri">EWG Tutorial, </span><span style="font-size:10.5pt;font-family:Calibri;color:black;background-image:initial;background-repeat:initial">Pages
17-20, 37-41</span><span style="font-size:10pt;font-family:Times"></span></p>
<p class="MsoNormal"><span style="font-family:Calibri"> </span></p>
<p class="MsoNormal"><span style="font-family:Calibri"><a href="http://london50.icann.org/en/schedule/mon-ewg-final-overview/presentation-ewg-final-overview-23jun14-en.pdf">http://london50.icann.org/en/schedule/mon-ewg-final-overview/presentation-ewg-final-overview-23jun14-en.pdf</a></span></p>
<p class="MsoNormal"><span style="font-family:Calibri"> </span></p>
<p class="MsoNormal"><span style="font-family:Calibri">Associated audio & transcript: </span></p>
<p class="MsoNormal"><span style="font-family:Calibri"><a href="http://audio.icann.org/meetings/london2014/ewg-final-overview-23jun14-en.mp3">http://audio.icann.org/meetings/london2014/ewg-final-overview-23jun14-en.mp3</a></span></p>
<p class="MsoNormal"><span style="font-family:Calibri"><a href="https://london50.icann.org/en/schedule/mon-ewg-final-overview/transcript-ewg-final-overview-23jun14-en">https://london50.icann.org/en/schedule/mon-ewg-final-overview/transcript-ewg-final-overview-23jun14-en</a></span></p>
<p class="MsoNormal"><span style="font-family:Calibri"> </span></p>
<p class="MsoNormal"><span style="font-family:Calibri">Page 17</span></p>
<p class="MsoNormal"><span style="font-family:Calibri">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 <i>all</i> use cases. Any
solution must be flexible to allow for future purpose needs.</span></p>
<p class="MsoNormal"><span style="font-family:Calibri"> </span></p>
<p class="MsoNormal"><span style="font-family:Calibri">Page 18</span></p>
<p class="MsoNormal"><span style="font-family:Calibri">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. </span></p>
<p class="MsoNormal"><span style="font-family:Calibri"> </span></p>
<p class="MsoNormal"><span style="font-family:Calibri">Page 19</span></p>
<p class="MsoNormal"><span style="font-family:Calibri">Purpose based contact (PBC) is a
proposal to offer better control of personal information and more efficient
portability of contact data. </span></p>
<p class="MsoNormal"><span style="font-family:Calibri"> </span></p>
<p class="MsoNormal"><span style="font-family:Calibri">Page 20</span></p>
<p class="MsoNormal"><span style="font-family:Calibri">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. </span></p>
<p class="MsoNormal"><span style="font-family:Calibri"> </span></p>
<p class="MsoNormal"><span style="font-family:Calibri">Page 21</span></p>
<p class="MsoNormal"><span style="font-family:Calibri">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. </span></p>
<p class="MsoNormal"><span style="font-family:Calibri"> </span></p>
<p class="MsoNormal"><span style="font-family:Calibri"> </span></p>
<p class="MsoNormal"><span style="font-family:Calibri">(not on audio or transcript I could find):</span></p>
<p class="MsoNormal"><span style="font-family:Calibri">Page 38 </span></p>
<p class="MsoNormal"><span style="font-family:Calibri">Provides a chart with identified Purpose and
associated Task for each. </span><span style="font-family:Calibri"></span></p>
<p class="MsoNormal"><span style="font-family:Calibri"> </span></p>
<p class="MsoNormal"><span style="font-family:Calibri">Page 39 </span></p>
<p class="MsoNormal"><span style="font-family:Calibri">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 3<sup>rd</sup>
party PBC. </span></p>
<p class="MsoNormal"><span style="font-family:Calibri"> </span></p>
<p class="MsoNormal"><span style="font-family:Calibri">Page 40</span></p>
<p class="MsoNormal"><span style="font-family:Calibri">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. </span></p>
<p class="MsoNormal"><span style="font-family:Calibri"> </span></p>
<p class="MsoNormal"><span style="font-family:Calibri">Page 41</span></p>
<p class="MsoNormal"><span style="font-family:Calibri">The PBC and their responsibilities are
defined and provided as backup to the presentation. These are the proposed referenced throughout
the presentation. </span></p>
<p class="MsoNormal"><span style="font-family:Calibri"> </span></p>
<p class="MsoNormal"><span style="font-family:Calibri"> </span></p>
<p class="MsoNormal"><span style="font-family:Calibri">~~~~~</span></p>
<p class="MsoNormal"><span style="font-family:Calibri">Expert Working Group on gTLD Directory
Services (EWG) Frequently Asked Questions (FAQs) – 2014 Final Report Update</span></p>
<p class="MsoNormal"><span style="font-family:Calibri"><a href="https://community.icann.org/display/EWG/EWG+FAQs">https://community.icann.org/display/EWG/EWG+FAQs</a>
</span></p>
<p class="MsoNormal"><span style="font-family:Calibri"> </span></p>
<p class="MsoNormal"><span style="font-family:Calibri">Five (5) FAQ’s specifically addressed Purpose,
captured below. (Page 5)</span></p>
<p class="MsoNormal"><span style="font-family:Calibri"> </span></p>
<p class="MsoNormal"><u><span style="font-family:Calibri">Registration Data Users and
Purposes </span></u></p>
<p class="MsoNormal"><span style="font-family:Calibri">9) Who are the users of the RDS? How
did the EWG determine this? </span></p>
<p class="MsoNormal"><span style="font-family:Calibri">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. </span></p>
<p class="MsoNormal"><span style="font-family:Calibri"> </span></p>
<p class="MsoNormal"><span style="font-family:Calibri">10) Why do those users need access to
registration data? </span></p>
<p class="MsoNormal"><span style="font-family:Calibri">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. </span></p>
<p class="MsoNormal"><span style="font-family:Calibri"> </span></p>
<p class="MsoNormal"><span style="font-family:Calibri">11) Which purposes should not be
permissible? </span></p>
<p class="MsoNormal"><span style="font-family:Calibri">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. </span></p>
<p class="MsoNormal"><span style="font-family:Calibri"> </span></p>
<p class="MsoNormal"><span style="font-family:Calibri">12) Why didn’t the EWG consider user X
or purpose Y? </span></p>
<p class="MsoNormal"><span style="font-family:Calibri">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. </span></p>
<p class="MsoNormal"><span style="font-family:Calibri"> </span></p>
<p class="MsoNormal"><span style="font-family:Calibri">67) How will members of the press and
bloggers gain access to RDS data? </span></p>
<p class="MsoNormal"><span style="font-family:Calibri">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.</span></p>
<p class="MsoNormal"><span style="font-family:Calibri"> </span></p>
</div><div><br></div><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><font size="1" face="verdana, sans-serif">~~~~<br>Susan Prosser<br>VP, Client Services</font><div><font size="1" face="verdana, sans-serif">DomainTools, LLC<br><br>T: (206) 838-9060<br>E: <a href="mailto:susan@domaintools.com" target="_blank">susan@domaintools.com</a></font></div><div><font size="1" face="verdana, sans-serif">PGP: A2C4D2A4 </font></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
</div>