<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Except that is not the only approach to the problem nor the ones exclusively used by DP authorities (i.e. Twitter). That is why I asked the question I did and why I will be lobbying them directly for whois privacy for free. </div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">The question of whether fields are optional or can be "masked" is inherently part of this discussion. </div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">That being said I would like to add purposes to why data is collected in RDS. Some suggestions:</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">To enable third-parties to communicate directly to resolve and troubleshoot problems. </div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">To enable third-parties to report abuse or security incidents so they may be resolved. </div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">To enable users and entities to have information to adjudicate an entity is who they say they are (for instance phishing, scams, fake news). </div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">ICANN isn't just a business to confer domain names. Its a quasi-regulatory body over a "commons" and a natural monopoly. The purposes must be viewed beyond the prism of the mere registrar-consumer relationship as many interests are relevant and just as important. </div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">J<br><br>Sent from my iPhone</div><div><br>On Mar 21, 2017, at 14:49, Stephanie Perrin <<a href="mailto:stephanie.perrin@mail.utoronto.ca">stephanie.perrin@mail.utoronto.ca</a>> wrote:<br><br></div><blockquote type="cite"><div>
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type">
<p><font size="+1"><font face="Lucida Grande">Indeed, the WHOIS
disclosure instrument may be the thing that sticks in
everybody's mind, but it is not the first place to start in
addressing a comprehensive approach to RDS privacy. First you
have to address why you are collecting each data element. Is
the core purpose justifiable and proportionate? etc, we spent
an hour on it with Mr. Canatacci and we are not done yet....</font></font></p>
<p><font size="+1"><font face="Lucida Grande">Yes, privacy proxy
services have been the stop gap over the years. The data is
still being collected without a clear statement of purpose,
disclosed in a variety of ways that may not pass muster, retained
in violation of at least EU law and likely others, data subject
access and disclosure rights inadequately addressed......</font></font></p>
<p><font size="+1"><font face="Lucida Grande">Lets wait till we get
our answers to the questions before we start discussing
possible solutions. I think we are jumping ahead quite a bit.</font></font></p>
<p><font size="+1"><font face="Lucida Grande">Stephanie Perrin</font></font><br>
</p>
<br>
<div class="moz-cite-prefix">On 2017-03-21 15:18, allison nixon
wrote:<br>
</div>
<blockquote cite="mid:CACLR7w+RmDFk+60MbuTwqrLGTV11OxO6sX5tTYDB=xOYjRyFkg@mail.gmail.com" type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div dir="ltr">I find myself in agreement with the free whois
privacy idea. It renders a lot of these privacy concerns moot,
and it isn't a big leap to make because many registrars already
offer it for free. It also won't break the many security systems
used by companies and law enforcement every day. It will also
resolve the spam issue. And it does seem that giving users a
true, zero-cost, choice as to how they want their data
disseminated will resolve a lot of the legal issues as well.</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Mar 21, 2017 at 3:06 PM, John
Bambenek via gnso-rds-pdp-wg <span dir="ltr"><<a moz-do-not-send="true" href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">And part
of the "if so" includes whether the individual chooses to
protect it in some free privacy regime. It's the same
question.<br>
<br>
Its why Twitter can exist. If you post publicly knowing you
are doing so and having a true choice, then privacy issues
become greatly reduced.<br>
<br>
Here we have (1) you MUST provide "all this stuff" and (2)
you MUST pay extra or we broadcast it to the world.<br>
<br>
It isn't an ancillary question. Its the fundamental one.<br>
<br>
Sent from my iPhone<br>
<div class="HOEnZb">
<div class="h5"><br>
> On Mar 21, 2017, at 13:55, "<a moz-do-not-send="true" href="mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a>"
<<a moz-do-not-send="true" href="mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a>>
wrote:<br>
><br>
>> On Tue, Mar 21, 2017 at 01:22:18PM -0500, John
Bambenek wrote:<br>
>> I think we should also discuss at a higher
level that if privacy services were free from the
registrars if that would largely resolve all of this.<br>
><br>
> I don't see how. The experts last week were quite
clear that the<br>
> first question is about collection, and our PDP is
chartered to talk<br>
> about that too, so we have to discuss whether some
of this data should<br>
> be collected at all, and if so by whom.<br>
><br>
> A<br>
><br>
> --<br>
> Andrew Sullivan<br>
> <a moz-do-not-send="true" href="mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a><br>
> ______________________________<wbr>_________________<br>
> gnso-rds-pdp-wg mailing list<br>
> <a moz-do-not-send="true" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
> <a moz-do-not-send="true" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a><br>
<br>
______________________________<wbr>_________________<br>
gnso-rds-pdp-wg mailing list<br>
<a moz-do-not-send="true" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
<a moz-do-not-send="true" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature" data-smartmail="gmail_signature">_________________________________<br>
Note to self: Pillage BEFORE burning.</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
gnso-rds-pdp-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></pre>
</blockquote>
<br>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>gnso-rds-pdp-wg mailing list</span><br><span><a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a></span><br><span><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></span></div></blockquote></body></html>