<html><body><span style="font-family:Arial; color:#000000; font-size:10pt;"><div><span><span style="font-family: Arial; color: rgb(0, 0, 0); font-size: 10pt; clear: both;" mce_style="font-family:Arial;color:#000000;font-size:10pt;"><span style="font-family:Arial;color:#000000;font-size:10pt;" mce_style="font-family:Arial;color:#000000;font-size:10pt;"><div>Peter, Emily, and Team:<br><br>Thanks for getting this thread started. I have numerous comments on this chapter, and have organized them in to two categories (below). I look forward to a longer discussion of this (and other) chapters between now and our meeting in MdR.</div><div><br>Thanks--</div><div><br></div><div>J.</div><div><br></div><div><br></div><div><br></div><div><u><b>Concerns with the Approach:</b></u><br>* This chapter represents an unbalanced perspective of the Privacy/Proxy issue. It emphasizes the views of governments, law enforcement, and others opposed to P&P services, while marginalizing the positions of those supporting, offering, or using these services.</div><div><br></div><div>* It proceeds from the default LE & Gov't position that some registrants, under certain conditions, have legitimate needs for privacy. While the civil tradition in most democracies (and on the Internet) is that privacy is a right enjoyed by everyone unless/until their conduct abuses this.</div><div><br></div><div>* The ICANN Policy that resolves conflicts between WHOIS requirements and local law is a protection for Registries and Registrars---not for Registrants. For Registrants, their only option to enhanced privacy protection (beyond that required by their local laws) is to engage a P&P service.</div><div><br></div><div>* It is not appropriate to cite a 2009 study by ICANN without noting that more specific studies have been approved by the Board (at Singapore) and may or may not be completed in time for their findings to be referenced by this report.</div><div><br></div><div>* It is not appropriate to cite a study by Knujon, or any other commercially-interested third-party that is engaged in the promotion of their products & services.</div><div><br></div><div>* The quotes by Law Enforcement do not include those who have neutral or uncritical views of P&P services, or those in LE who frequently and publicly make the distinction between the "good" or "model" P&P operators, versus the "bad actors."</div><div><br></div><div>* Proxy registrations do not "hide" or "shield" registrant contact data. The proxy service IS the registrant. Law Enforcement & Gov'ts and other interested parties are, in effect, demanding disclosure of the business relationship between the Proxy provider and its customer(s).</div><div><br></div><div><br></div><div><span><u style="clear: both;" mce_style="clear: both;" mce_=""><b>Concerns with the Recommendations:</b></u></span><br></div><div><br></div><div>* Overall: Many of these recommendations exceed "Policy Review" and fall in to the realm of "Policy Recommendation."<br></div><div><br></div><div>* Rec #1: Because it is not a regulator, ICANN cannot prohibit services offered by firms with which it does not have a contract. And it cannot compel business to enter in to contracts unless there is a clear incentive for them to do so.<br></div><div><br></div><div>* Rec #2: ICANN could offer a voluntary accreditation program for P&P providers. But it would by necessity be a voluntary program, so there should be clear benefits for P&P providers to gain ICANN accreditation, and clear benefits for registrars to use accredited P&P services.</div><div><br></div><div>* Rec #3: Accredited Registrars could use Accredited P&P Providers, presuming they were -aware- when a non-accredited service was being used. For example, if I contact my lawyer and ask him to register a domain name on my behalf, I do not expect the registrar to know that the lawyer is functioning as a Proxy for me in this example.</div><div><br></div><div>* Rec #4: It is not within ICANN's mission to examine how a domain name is used. Domain names are not synonymous with websites. Registrars are often, but not necessarily, the web content hosts for the names they manage. As an organization, ICANN is and must remain "content neutral."</div><div><br></div><div>* Rec #5 - #7: These recommendations seem to ouline the charter of a desired Policy Development Process (PDP), which is beyond the remit of this review team.<br></div><div><br></div><div><br></div></span></span></span><br><br></div>
<blockquote id="replyBlockquote" webmail="1" style="border-left: 2px solid blue; margin-left: 8px; padding-left: 8px; font-size:10pt; color:black; font-family:verdana;">
<div id="wmQuoteWrapper">
-------- Original Message --------<br>
Subject: Re: [Rt4-whois] Report input - privacy/proxy 'gaps'<br>
[SEC=UNCLASSIFIED]<br>
From: Emily Taylor <<a href="mailto:emily@emilytaylor.eu">emily@emilytaylor.eu</a>><br>
Date: Wed, August 17, 2011 6:17 am<br>
To: "Nettlefold, Peter" <<a href="http://Peter.Nettlefold@dbcde.gov.au">Peter.Nettlefold@dbcde.gov.au</a>><br>
Cc: "<a href="mailto:rt4-whois@icann.org">rt4-whois@icann.org</a>" <<a href="mailto:rt4-whois@icann.org">rt4-whois@icann.org</a>><br>
<br>
Dear Peter,<br><br>Many thanks for your work on this draft. I really like the way that you have based your commentary on a bottom-up analysis of what the comments said. It shows that we have been listening to, and carefully analysing the inputs that people have taken the trouble to give us. <br> <br>I'm sure we'll be discussing it on today's call, and it's a pity that the scheduling prevents you joining us. I hope we will be able to have you on our next call after this one, and we'll ensure that we have a good turn out.<br> <br>My question in reading the proxy/privacy section is - apart from NCUC which you referenced - did we have contrary views. We have a lot of references from law enforcement and IP constituency, but nothing at all from registry/registrars or NCUC apart from that one quote. I'm keen to ensure that we present a balanced view of the inputs received, because it will give a range of views.<br> <br>All - please can we look out our notes of our face-to-face meetings. I for one took away a strong message from our call with the IPC that they had *good* experiences of data release from a number of the larger providers, and (while in a perfect world they may not want proxy/privacy services) were able to live with them if they could have a predictable outcome. This is well captured in one of the recommendations, but doesn't quite come through in the supporting text yet.<br> <br>For the more radical recommendations - I'm not sure that I heard them being asked for, even by the communities that you would expect to support them, and therefore we need much more argumentation in the text to justify some of the recommendations (if, indeed, the team can reach consensus on them).<br> <br>Thank you again for a thorough and thoughtful piece of work Peter. It provides us with an excellent first draft on which to focus our discussions.<br><br>Kind regards<br><br>Emily<br><br>Kind regards<br><br>Emily<br> <br><br><div class="gmail_quote">On 17 August 2011 10:16, Mikhail Yakushev <span dir="ltr"><<a target="_blank" href="mailto:m.yakushev@corp.mail.ru">m.yakushev@corp.mail.ru</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div link="blue" vlink="purple" lang="RU"> <div> <div class="MsoNormal" style="font-size:12pt;"><span style="color:#1F497D" lang="EN-US">Dear Peter, colleagues,<u></u><u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span style="color:#1F497D" lang="EN-US">I have carefully reviewed Peter’s draft and mostly agree with the provided analysis. I also would mostly agree with the suggested recommendations – but I think we need to discuss each of them separately to achieve the highest possible level of consensus within our team.<u></u><u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span style="color:#1F497D" lang="EN-US">Kind regards,<u></u><u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span style="color:#1F497D" lang="EN-US">Michael<u></u><u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span style="color:#1F497D" lang="EN-US"><u></u> <u></u></span></div> <div> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"> <div class="MsoNormal" style="font-size:12pt;"><b><span style="font-size:10.0pt" lang="EN-US">From:</span></b><span style="font-size:10.0pt" lang="EN-US"> <a href="mailto:rt4-whois-bounces@icann.org" target="_blank">rt4-whois-bounces@icann.org</a> [mailto:<a href="mailto:rt4-whois-bounces@icann.org" target="_blank">rt4-whois-bounces@icann.org</a>] <b>On Behalf Of </b>Nettlefold, Peter<br> <b>Sent:</b> Tuesday, August 16, 2011 11:48 AM<br> <b>To:</b> <a href="mailto:rt4-whois@icann.org" target="_blank">rt4-whois@icann.org</a><br> <b>Subject:</b> [Rt4-whois] Report input - privacy/proxy 'gaps' [SEC=UNCLASSIFIED]<u></u><u></u></span></div> </div> </div><div><div></div><div class="h5"> <div class="MsoNormal" style="font-size:12pt;"><u></u> <u></u></div> <div class="MsoNormal" style="font-size:12pt;"><span lang="EN-AU">Hello all,<u></u><u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span lang="EN-AU"><u></u> <u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span lang="EN-AU">Attached is the first section of the draft ‘gaps’ chapter, for review and comment.<u></u><u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span lang="EN-AU"><u></u> <u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span lang="EN-AU">As you’ll see, this section covers accessibility and privacy issues, and it still has some gaps.<u></u><u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span lang="EN-AU"><u></u> <u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span lang="EN-AU">I’ve also drafted and included some recommendations on this issue, building on the public and law enforcement input and our own discussions. I hope these are helpful.<u></u><u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span lang="EN-AU"><u></u> <u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span lang="EN-AU">As you’ll see, I’ve drawn a distinction between proxy and privacy services in the draft chapter, and this will need some further work (but I didn’t want to delay getting this out to you any further while I worked on this). I’ve tried to unpack this distinction in the draft chapter, but also wanted to also explain my thinking to you. <u></u><u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span lang="EN-AU"><u></u> <u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span lang="EN-AU">The main challenge identified by responses to our consultation processes, and in our own discussions, is to find a way to balance any legitimate privacy concerns with the interests of other stakeholders. The position I’ve put forward in the draft chapter is that this can be achieved through the regulated use of <i>privacy</i> services (i.e. services that make the identity of the registrant known, but limit availability to other personal data – at least in the first instance). <i>Proxy</i> services, which replace the name of the registrant with that of another entity, are quite different in nature, and I think that these services raise serious questions about ICANN’s ability to enforce its AoC obligations. <u></u><u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span lang="EN-AU"><u></u> <u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span lang="EN-AU">I have drafted the chapter with this distinction in mind, although some parts of the argument need a bit more work.<u></u><u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span lang="EN-AU"><u></u> <u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span lang="EN-AU">I’m aiming to circulate the next section of the draft chapter - on accuracy - in a day or two, and the section on compliance shortly after that.<u></u><u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span lang="EN-AU"><u></u> <u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span lang="EN-AU">Unfortunately the next call is now scheduled for 1am my time, so I won’t be attending.<u></u><u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span lang="EN-AU"><u></u> <u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span lang="EN-AU">I look forward to discussing this further as we work towards our Marina del Ray meeting.<u></u><u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span lang="EN-AU"><u></u> <u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span lang="EN-AU">Cheers,<u></u><u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span lang="EN-AU"><u></u> <u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span lang="EN-AU">Peter<u></u><u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span lang="EN-AU"><u></u> <u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span lang="EN-AU"><u></u> <u></u></span></div> <div><span lang="EN-AU"><br> <b>-------------------------------------------------------------------------------</b><u></u><u></u></span></div> <div><span lang="EN-AU">The information transmitted is for the use of the intended recipient only and may contain confidential and/or legally privileged material. Any review, re-transmission, disclosure, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited and may result in severe penalties.<u></u><u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span style="font-size:12.0pt;font-family:"Times New Roman","serif"" lang="EN-AU"><u></u> <u></u></span></div> <div><span lang="EN-AU">If you have received this e-mail in error please notify the Security Advisor of the Department of Broadband, Communications and the Digital Economy, 38 Sydney Ave, Forrest ACT 2603, telephone (02) 6271-1376 and delete all copies of this transmission together with any attachments.<u></u><u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span style="font-size:12.0pt;font-family:"Times New Roman","serif"" lang="EN-AU"><u></u> <u></u></span></div> <div><span lang="EN-AU">Please consider the environment before printing this email.<u></u><u></u></span></div> <div class="MsoNormal" style="font-size:12pt;"><span style="font-size:12.0pt;font-family:"Times New Roman","serif"" lang="EN-AU"><br> <b>-------------------------------------------------------------------------------</b><u></u><u></u></span></div> </div></div></div> </div> <br>_______________________________________________<br> Rt4-whois mailing list<br> <a target="_blank" href="mailto:Rt4-whois@icann.org">Rt4-whois@icann.org</a><br> <a href="https://mm.icann.org/mailman/listinfo/rt4-whois" target="_blank">https://mm.icann.org/mailman/listinfo/rt4-whois</a><br> <br></blockquote></div><br><br clear="all"><br>-- <br><br><br><span style="color:rgb(153, 51, 153)"></span> <img src="http://www.etlaw.co.uk/images/stories/etlaw/etclogo250x60.gif"><br><br><div style="margin-left:80px"> <u style="color:rgb(204, 51, 204)"> </u><br style="color:rgb(153, 51, 153)"><br><span style="color:rgb(153, 153, 153)">76 Temple Road, Oxford OX4 2EZ UK</span><br style="color:rgb(153, 153, 153)"> <span style="color:rgb(153, 153, 153)">t: +44 (0)1865 582 811 • m: +44 (0)7540 049 322</span><br style="color:rgb(153, 153, 153)"><span style="color:rgb(153, 153, 153)"><a href="mailto:emily@emilytaylor.eu" target="_blank">emily@emilytaylor.eu</a> </span><br style="color:rgb(153, 153, 153)"> <br style="color:rgb(153, 153, 153)"><b style="color:rgb(153, 153, 153)"><a href="http://www.etlaw.co.uk" target="_blank">www.etlaw.co.uk</a></b><br style="color:rgb(153, 153, 153)"><br style="color:rgb(153, 153, 153)"><span style="color:rgb(153, 153, 153)">Emily Taylor Consultancy Limited is a company registered in England and Wales No. 730471. VAT No. 114487713.</span><br> </div><br> <hr>_______________________________________________<br>
Rt4-whois mailing list<br>
<a href="mailto:Rt4-whois@icann.org">Rt4-whois@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/rt4-whois">https://mm.icann.org/mailman/listinfo/rt4-whois</a><br>
</div>
</blockquote></span></body></html>