<div dir="ltr">If access to whois is going to be closed off from the general public, there isn't going to be any point in charging money for whois privacy anyways. </div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 21, 2017 at 4:08 PM, theo geurts <span dir="ltr"><<a href="mailto:gtheo@xs4all.nl" target="_blank">gtheo@xs4all.nl</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">
<p>Hi all, <br>
<br>
As a Registrar providing P/P services, it is easy to jump to the
idea providing it for free makes a lot of problems go away. <br>
<br>
That being said, I agree with Stephanie in a sense we are getting
ahead of ourselves. <br>
Also, we need to consider that the PPSAI IRT is currently
drafting, and that outcome might change things, on how "free"
things are going to be. <br><span class="HOEnZb"><font color="#888888">
<br>
Theo <br>
</font></span></p><div><div class="h5">
<br>
<div class="m_8276335440618621142moz-cite-prefix">On 21-3-2017 20:49, Stephanie Perrin
wrote:<br>
</div>
<blockquote type="cite">
<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="m_8276335440618621142moz-cite-prefix">On 2017-03-21 15:18, allison nixon
wrote:<br>
</div>
<blockquote type="cite">
<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 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="m_8276335440618621142HOEnZb">
<div class="m_8276335440618621142h5"><br>
> On Mar 21, 2017, at 13:55, "<a href="mailto:ajs@anvilwalrusden.com" target="_blank">ajs@anvilwalrusden.com</a>"
<<a href="mailto:ajs@anvilwalrusden.com" target="_blank">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 href="mailto:ajs@anvilwalrusden.com" target="_blank">ajs@anvilwalrusden.com</a><br>
> ______________________________<wbr>_________________<br>
> gnso-rds-pdp-wg mailing list<br>
> <a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
> <a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/l<wbr>istinfo/gnso-rds-pdp-wg</a><br>
<br>
______________________________<wbr>_________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/l<wbr>istinfo/gnso-rds-pdp-wg</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="m_8276335440618621142gmail_signature" data-smartmail="gmail_signature">______________________________<wbr>___<br>
Note to self: Pillage BEFORE burning.</div>
</div>
<br>
<fieldset class="m_8276335440618621142mimeAttachmentHeader"></fieldset>
<br>
<pre>______________________________<wbr>_________________
gnso-rds-pdp-wg mailing list
<a class="m_8276335440618621142moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>
<a class="m_8276335440618621142moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a></pre>
</blockquote>
<br>
<br>
<fieldset class="m_8276335440618621142mimeAttachmentHeader"></fieldset>
<br>
<pre>______________________________<wbr>_________________
gnso-rds-pdp-wg mailing list
<a class="m_8276335440618621142moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>
<a class="m_8276335440618621142moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a></pre>
</blockquote>
<br>
</div></div></div>
<br>______________________________<wbr>_________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
<a 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></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>