<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 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 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.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
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;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> gnso-rds-pdp-wg-bounces@icann.org [mailto:gnso-rds-pdp-wg-bounces@icann.org]
<b>On Behalf Of </b>nathalie coupet via gnso-rds-pdp-wg<br>
<b>Sent:</b> Monday, February 13, 2017 10:08 AM<br>
<b>To:</b> Michele Neylon - Blacknight <michele@blacknight.com>; benny@nordreg.se; Victoria Sheckler <vsheckler@riaa.com><br>
<b>Cc:</b> gnso-rds-pdp-wg@icann.org<br>
<b>Subject:</b> [EXTERNAL] Re: [gnso-rds-pdp-wg] Dangers of public whois<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div id="yui_3_16_0_ym19_1_1486996986894_17911">
<p class="MsoNormal" style="background:white"><span style="font-family:"Helvetica",sans-serif;color:black">How about puting 'fat' information behind a 'thin' wall? For example, to prevent public viewing of a registrant's personal information, why not require
an email registration or some other light form of identification? It would deter spammers and other frauds, while insuring a certain level of public viewing (also to deter fraud). <o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_ym19_1_1486996986894_17911">
<p class="MsoNormal" style="background:white"><span style="font-family:"Helvetica",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div id="yui_3_16_0_ym19_1_1486996986894_17911">
<p class="MsoNormal" style="background:white"><span style="font-family:"Helvetica",sans-serif;color:black">To the argument that the vast majority of Internet users do not use WHOIS, this might be true now but not in the future. Furthermore, this argument was
also used by people who opposed the paper version of the phone book, and a survey shoed that about 11% of households rely on the phone book to get information. The consensus was that people who do not have access to the Internet need it, therefore it qualifies
as a public service which has to be kept for the public good. <o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_ym19_1_1486996986894_17911">
<p class="MsoNormal" style="background:white"><span style="font-family:"Helvetica",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div id="yui_3_16_0_ym19_1_1486996986894_17911">
<p class="MsoNormal" style="background:white"><span style="font-family:"Helvetica",sans-serif;color:black">Scott Hollenbeck's RDAP project requires exactly that: identification through email (right, Scott?). This is simple enough and everybody could live with
this solution, I think. <o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_ym19_1_1486996986894_17912">
<p class="MsoNormal" style="background:white"><span style="font-family:"Helvetica",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">My implementation does indeed support a basic level of authentication and access control using credentials issued by certain email providers.
Finer-grained access control can be implemented using more rigorous processes for assigning client credentials.<o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Scott
<o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>