<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:784277433;
mso-list-template-ids:1857312026;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Please remember that we are not yet at the point where we are deciding what the purposes are. That will come and the full WG will work on that. The task of
the purpose team is to identify sources that may be helpful for the WG when we discuss purposes and to provide summaries of those resources that will facilitate full WG use of those resources.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Chuck<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> gnso-rds-pdp-purpose-bounces@icann.org [mailto:gnso-rds-pdp-purpose-bounces@icann.org]
<b>On Behalf Of </b>Greg Shatan via gnso-rds-pdp-purpose<br>
<b>Sent:</b> Monday, April 04, 2016 5:35 PM<br>
<b>To:</b> gnso-rds-pdp-purpose@icann.org<br>
<b>Subject:</b> Re: [gnso-rds-pdp-purpose] Purpose of registration data: Whois Review Team never assessed<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">I question the need for and appropriateness of dividing purposes into "primary" and "secondary" purposes. I think it is premature, at best, to create a hierarchy or taxonomy of purposes.
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">Going back through the emails where this has been proposed, this appears to be tied to a clear tendency towards, if not an explicit goal of, de-emphasizing and ultimately de-legitimizing
certain purposes categorized as secondary. Furthermore, this categorization seems intertwined with the type of user, and a tendency to de-emphasize and de-legitimize certain users. I think these are both dangerous tendencies, particularly at this point in
our work. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">We may well have discussions about those concepts (indeed, we almost certainly will), but baking them into our methodology will only prejudice, and ultimately de-legitimize, the work of this
Working Group. At this point in the process, where we are collecting data, we really need to avoid characterizing purposes or uses.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">Greg <o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<p style="margin:0in;margin-bottom:.0001pt"> <span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
<div>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="800" style="width:600.0pt">
<tbody>
<tr>
<td width="100" valign="top" style="width:75.0pt;padding:0in 0in 0in 0in">
<p style="margin:0in;margin-bottom:.0001pt"><img width="100" height="43" id="_x0000_i1025" src="cid:image001.jpg@01D18EA8.1E1C8310" alt="http://hilweb1/images/signature.jpg"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</td>
<td width="8" style="width:6.0pt;padding:0in 0in 0in 0in">
<p style="margin:0in;margin-bottom:.0001pt"> <span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</td>
<td style="padding:0in 0in 0in 0in">
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#002E62">Gregory S. Shatan | Partner<br>
</span></b><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:black">McCARTER & ENGLISH, LLP<br>
<br>
245 Park Avenue, 27th Floor | New York, New York 10167<br>
T: <a href="tel:212-609-6873" target="_blank"><span style="color:#1155CC">212-609-6873</span></a><br>
F: <a href="tel:212-416-7613" target="_blank"><span style="color:#1155CC">212-416-7613</span></a><br>
<a href="mailto:gshatan%20@mccarter.com" target="_blank"><span style="color:#225599">gshatan @mccarter.com</span></a> | <a href="http://www.mccarter.com/" target="_blank"><span style="color:#225599">www.mccarter.com</span></a> <br>
<br>
</span><span style="font-size:7.0pt;font-family:"Arial","sans-serif";color:#777777">BOSTON | HARTFORD | STAMFORD | NEW YORK | NEWARK <br>
EAST BRUNSWICK | PHILADELPHIA | WILMINGTON | WASHINGTON, DC</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
</div>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> <o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Sun, Apr 3, 2016 at 11:50 PM, Kathy Kleiman via gnso-rds-pdp-purpose <<a href="mailto:gnso-rds-pdp-purpose@icann.org" target="_blank">gnso-rds-pdp-purpose@icann.org</a>> wrote:<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hi Maryan and All,<br>
Tx you for your analysis, and I would like to provide some additional background on the Whois Review Team Final Report. The Whois Review Team was<i> expressly barred from looking at the purpose of the Whois system</i>. It was allowed to look only at ICANN's
"existing policy relating to WHOIS" per the Affirmation of Commitments signed between US Department of Commerce and ICANN in 2009.
<br>
<br>
Even within that scope, the Whois Review Team recommended protection of privacy for commercial companies, noncommercial organizations and individials (finding that each shared with us legal and legitimate reasons for privacy including as-yet-unannounced mergers,
new movie names, unpopular religious, ethnic and policy views, etc). The Whois Review Team further advised ICANN to work towards a standard of contactability - reaching the registrant by some means rather than all means - which we wrote as: "ICANN should take
appropriate measures to reduce the number of WHOIS registrations that fall into the accuracy groups Substantial Failure and Full Failure (as defined by the NORC Data Accuracy Study, 2009/10..." p. 87.<br>
<br>
This history means that our RDS Working Group remains the only group I know -- since the 1980s -- to look at domain name registration data anew and ask the key questions:<br>
1. What is the primary purpose for which domain name registration data is collected, and<br>
2. To what secondary purposes (such as directories) may this data be used and pursuant to what requirements of law?
<br>
<br>
We are creating a new process/system and it falls to us to determine Purpose.<br>
<br>
Best,<br>
Kathy (Kleiman)<br>
Formerly, Vice-Chair of the Whois Review Team. <br>
<br>
<o:p></o:p></p>
<div>
<p class="MsoNormal">On 4/2/2016 4:31 AM, Maryan Rizinski via gnso-rds-pdp-purpose wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal">Hi All,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I hope that you are all having a great week so far!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I spent some time reviewing the WHOIS Policy Review Team's Final Report from May 2012 with the goal of extracting relevant information regarding the purpose of registration data. This has been a challenging task because of two reasons:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
There is a lack of clearly defined purpose for collecting registration data within the existing WHOIS system (it is not surprising that the SSAC's report SAC055 is entitled "Blind Men and An Elephant")<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Significant emphasis is given on topics such as compliance, data accuracy and data access which all seem to share an intangible common underlying (or over-arching) purpose/principle<o:p></o:p></li></ol>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I have the impression that the purpose implicitly evolves around the concept of achieving and ensuring "trust" - a term that is used a number of times throughout the document.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Many, if not all, stakeholders involved with or affected by WHOIS, may be interested in achieving and ensuring trust in the online environment (which may in turn represent a reasonable basis for achieving consensus regarding purpose), but
as Chuck said, at this point we should restrain from deliberating on that topic even though it may look like a tempting starting point for discussing the fundamental question:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<div>
<p class="MsoNormal"><i>What should the over-arching purpose be of collecting, maintaining, and providing access to gTLD registration data?</i><o:p></o:p></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">In this context, I compiled some relevant excerpts from the final report regarding trust that we may want to consider when preparing our concise summary. The excerpts are given as follows (some parts are highlighted for improved readability
and navigation throughout the excerpts):<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<div>
<p class="MsoNormal"><i>"The WHOIS Review Team’s scope, guided by the Affirmation of Commitments was to review the extent to which ICANN’s WHOIS policy and its implementation are effective, meet the legitimate needs of law enforcement and
<span style="background:yellow">promote consumer trust.</span>" (page 6)</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><i>"Part of the WHOIS Review Team’s scope was to evaluate the extent to which ICANN’s current WHOIS policy and implementation “promotes consumer trust”... This found that drivers of consumer trust include
<span style="background:yellow">knowing the entity with whom they are dealing, and being able to find reliable contact information.</span>" (page 9)</i><o:p></o:p></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<div>
<p class="MsoNormal"><i>"...the current implementation of WHOIS services does not help to
<span style="background:yellow">build consumer trust</span>, and more could be done to raise awareness of the service, and to improve its user-friendliness." (page 10)</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><i>"<span style="background:yellow">The low level of accurate WHOIS data is unacceptable, and decreases consumer trust in WHOIS</span>..." (page 12)</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><i>"ICANN will organize a review of WHOIS policy and its implementation to assess the extent to which WHOIS policy is effective and its implementation meets the legitimate needs of law enforcement and promotes consumer trust." (page 20)</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><i>"The Review Team found the <span style="background:yellow">
definition of Consumer Trust</span>, something the ICANN Community is also exploring in the context of its policy-making processes, to be
<span style="background:yellow">particularly challenging</span>. Consumer Trust can be narrowly construed to mean the
<span style="background:yellow">level of trust Internet users have in available WHOIS data</span>; or more broadly as the level of trust consumers have in Internet information and transactions in general." (page 23)</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><i>"Thus, <span style="background:yellow">lack of support of non-ASCII characters</span> introduces an additional barrier for non-ASCII users to provide accurate and consistent domain name registration data. This has implications for their
tractability for law enforcement and associated organizations. Further, many people attach some pride and fondness to the correct representation of their name and other data. While this is not a purely technical or administrative requirement,
<span style="background:yellow">it is relevant in the context of Consumer Trust.</span>" (page 46-47)</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><i>"The Review Team was clearly told in written and oral comments that
<span style="background:yellow">inaccurate WHOIS data can also significantly impact consumer trust and confidence in the Internet.</span>" (page 51)</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><i>"Consumers engaged in online purchases, in our Consumer Research Study agreed: findings showed that
<span style="background:yellow">factors which positively supported consumer trust included knowing the company with whom they were dealing with, and being able to verify their contact details online.</span>" (page 51)</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><i>"A significant number of public responses to the WHOIS discussion paper, and input from law enforcement agencies via the review team’s targeted questionnaire, argued that privacy and proxy services undermine the effectiveness of the
WHOIS service, both in terms of its ability to meet the legitimate needs of law enforcement and to promote consumer trust." (page 61)</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><i>"The GAC WHOIS Principles similarly note that <span style="background:yellow">
WHOIS data can contribute: to user confidence in the Internet ... by helping users identify persons or entities responsible for content and services online</span>" (page 67)</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><i>"Part of the WHOIS Review Team’s scope was to evaluate the extent to which ICANN’s current WHOIS policy and implementation “promotes consumer trust”. Having struggled with what “consumer” means in the context of WHOIS, and aware of the
Affirmation of Commitments’ observation that there are key stakeholders who do not engage in the ICANN environment, the WHOIS Review Team commissioned consumer research. This found that
<span style="background:yellow">drivers of consumer trust include knowing the entity with whom they are dealing, and being able to find reliable contact information.</span> The vast majority of consumers were unaware of the existence of the WHOIS service, and
many struggled to understand the format of WHOIS outputs. This led us to conclude that the current implementation of WHOIS services does not help to build consumer trust, and more could be done to raise awareness of the service, and to improve its user-friendliness."
(page 84)</i><o:p></o:p></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I hope that this input would be helpful for our small team and I am looking forward to working with all of you.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Maryan<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>gnso-rds-pdp-purpose mailing list<o:p></o:p></pre>
<pre><a href="mailto:gnso-rds-pdp-purpose@icann.org" target="_blank">gnso-rds-pdp-purpose@icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-purpose" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-purpose</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><br>
_______________________________________________<br>
gnso-rds-pdp-purpose mailing list<br>
<a href="mailto:gnso-rds-pdp-purpose@icann.org">gnso-rds-pdp-purpose@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-purpose" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-purpose</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>