<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body dir="auto">
<div>Don and PPSAI Team:</div>
<div><br>
</div>
<div>We have also explored this internally, and the short story is that it isn't acceptable to our customers. </div>
<div><br>
</div>
<div>Especially those holding large portfolios of domains for investment, as it is too easy to cross-reference a Unique ID to compile the entire portfolio, which would otherwise be private. Similarly, if someone purchases a domain name from a P/P customer,
then they immediately know the identity for all private domains associated with the same Unique ID. </div>
<div><br>
</div>
<div>Happy to discuss further on our next call, especially if you believe it will come up again in Public Comments. But generally, this concept of "Privacy Lite" is a non-starter for us....</div>
<div><br>
Thanks--
<div><br>
</div>
<div>J.</div>
<div>____________</div>
<div>James Bladel</div>
<div>GoDaddy</div>
</div>
<div><br>
On Oct 24, 2014, at 10:32 AM, Don Blumenthal <<a href="mailto:dblumenthal@pir.org">dblumenthal@pir.org</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@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:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.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;}
--></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]-->
<div class="WordSection1">
<p class="MsoNormal">I gave a presentation at this week’s conference in Boston. It was a something of a 20 minute version of the ICANN All Things WHOIS program, although with fewer topics and a focus on details that were most likely to be of interest to the
anti abuse community.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Four people raised the same suggestion either before the session or during Q/A: Require providers to assign unique IDs to their customers so that we can identify the p/p registrations held by a given entity even if we don’t know who is
it.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We can explore the idea or not, but I am certain that it will be suggested in public comments to our draft report. FWIW, the suggesters (word?) aren’t affiliated and were an international group.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Don<o:p></o:p></p>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>Gnso-ppsai-pdp-wg mailing list</span><br>
<span><a href="mailto:Gnso-ppsai-pdp-wg@icann.org">Gnso-ppsai-pdp-wg@icann.org</a></span><br>
<span><a href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</a></span></div>
</blockquote>
</body>
</html>