<div dir="ltr"><div class="gmail_default" 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. </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" 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. </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" 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.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Greg </div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><p style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><font size="3" face="Times New Roman"><span style="font-size:12pt;font-family:'Times New Roman',serif"> <u></u></span></font></p><div style="font-size:12.8px"><table border="0" cellspacing="0" cellpadding="0" width="800" style="width:600pt"><tbody><tr><td width="100" valign="top" style="width:75pt;padding:0in"><p style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><font size="3" face="Times New Roman"><span style="font-size:12pt;font-family:'Times New Roman',serif"><img width="100" height="43" src="cid:image001.jpg@01D1842F.8BD05270" alt="http://hilweb1/images/signature.jpg"></span></font><font size="3" face="Times New Roman"><span style="font-size:12pt;font-family:'Times New Roman',serif"><u></u><u></u></span></font></p></td><td width="8" style="width:6pt;padding:0in"><p style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><font size="3" face="Times New Roman"><span style="font-size:12pt;font-family:'Times New Roman',serif"> <u></u><u></u></span></font></p></td><td style="padding:0in"><p style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><b><font size="1" color="#002e62" face="Arial"><span style="font-size:8.5pt;font-family:Arial,sans-serif">Gregory S. Shatan | Partner<br></span></font></b><font size="1" color="black" face="Arial"><span style="font-size:7.5pt;font-family:Arial,sans-serif">McCARTER & ENGLISH, LLP<br><br>245 Park Avenue, 27th Floor | New York, New York 10167<br>T: <a href="tel:212-609-6873" value="+12126096873" style="color:rgb(17,85,204)" target="_blank">212-609-6873</a><br>F: <a href="tel:212-416-7613" value="+12124167613" style="color:rgb(17,85,204)" target="_blank">212-416-7613</a><br><a href="mailto:gshatan%20@mccarter.com" style="color:rgb(17,85,204)" target="_blank"><font color="#225599">gshatan @mccarter.com</font></a> | <a href="http://www.mccarter.com/" style="color:rgb(17,85,204)" target="_blank"><font color="#225599">www.mccarter.com</font></a> <br><br></span></font><font size="1" color="#777777" face="Arial"><span style="font-size:7pt;font-family:Arial,sans-serif">BOSTON | HARTFORD | STAMFORD | NEW YORK | NEWARK <br>EAST BRUNSWICK | PHILADELPHIA | WILMINGTON | WASHINGTON, DC</span></font><font size="3" face="Times New Roman"><span style="font-size:12pt;font-family:'Times New Roman',serif"><u></u><u></u></span></font></p></td></tr></tbody></table></div><p style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><font size="2" face="Calibri"><span style="font-size:11pt"><u></u> </span></font></p></div></div></div></div></div>
<br><div class="gmail_quote">On Sun, Apr 3, 2016 at 11:50 PM, Kathy Kleiman via gnso-rds-pdp-purpose <span dir="ltr"><<a href="mailto:gnso-rds-pdp-purpose@icann.org" target="_blank">gnso-rds-pdp-purpose@icann.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
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> </i><i>expressly barred </i><i>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>
<br>
<div>On 4/2/2016 4:31 AM, Maryan Rizinski
via gnso-rds-pdp-purpose wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Hi All,</div>
<div><br>
</div>
<div>I hope that you are all having a great week so far!</div>
<div><br>
</div>
<div>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:</div>
<div><br>
</div>
<div>
<ol>
<li>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")<br>
</li>
<li>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<br>
</li>
</ol>
</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>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:</div>
<div><br>
</div>
<blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<div><i>What should the over-arching purpose be of collecting,
maintaining, and providing access to gTLD registration
data?</i></div>
</blockquote>
<div><br>
</div>
<div>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):</div>
<div><br>
</div>
<blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<div><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-color:rgb(255,255,0)">promote
consumer trust.</span>" (page 6)</i></div>
<div><br>
</div>
<div><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-color:rgb(255,255,0)">knowing the
entity with whom they are dealing, and being able to
find reliable contact information.</span>" (page 9)</i></div>
</blockquote>
<div><br>
</div>
<blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<div><i>"...the current implementation of WHOIS services does
not help to <span style="background-color:rgb(255,255,0)">build
consumer trust</span>, and more could be done to raise
awareness of the service, and to improve its
user-friendliness." (page 10)</i></div>
<div><br>
</div>
<div><i>"<span style="background-color:rgb(255,255,0)">The low
level of accurate WHOIS data is unacceptable, and
decreases consumer trust in WHOIS</span>..." (page 12)</i></div>
<div><br>
</div>
<div><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></div>
<div><br>
</div>
<div><i>"The Review Team found the <span style="background-color:rgb(255,255,0)">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-color:rgb(255,255,0)">particularly
challenging</span>. Consumer Trust can be narrowly
construed to mean the <span style="background-color:rgb(255,255,0)">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></div>
<div><br>
</div>
<div><i>"Thus, <span style="background-color:rgb(255,255,0)">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-color:rgb(255,255,0)">it is relevant
in the context of Consumer Trust.</span>" (page 46-47)</i></div>
<div><br>
</div>
<div><i>"The Review Team was clearly told in written and oral
comments that <span style="background-color:rgb(255,255,0)">inaccurate WHOIS
data can also significantly impact consumer trust and
confidence in the Internet.</span>" (page 51)</i></div>
<div><br>
</div>
<div><i>"Consumers engaged in online purchases, in our
Consumer Research Study agreed: findings showed that <span style="background-color:rgb(255,255,0)">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></div>
<div><br>
</div>
<div><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></div>
<div><br>
</div>
<div><i>"The GAC WHOIS Principles similarly note that <span style="background-color:rgb(255,255,0)">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></div>
<div><br>
</div>
<div><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-color:rgb(255,255,0)">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></div>
</blockquote>
<div><br>
</div>
<div>I hope that this input would be helpful for our small team
and I am looking forward to working with all of you.</div>
<div><br>
</div>
<div>Best regards,</div>
<div><br>
</div>
<div>Maryan</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
gnso-rds-pdp-purpose mailing list
<a href="mailto:gnso-rds-pdp-purpose@icann.org" target="_blank">gnso-rds-pdp-purpose@icann.org</a>
<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></pre>
</blockquote>
<br>
</div>
<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" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-purpose</a><br></blockquote></div><br></div>