<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Great comments, Seth. I defer to Susan and James, as the experts on
this material.<br>
Best,<br>
Kathy<br>
<br>
:
<blockquote
cite="mid:01e501ccafb4$fabff540$f03fdfc0$@reiss@lex-ip.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 12 (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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 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";
color:black;}
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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
margin-bottom:5.75pt;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.sdfootnote, li.sdfootnote, div.sdfootnote
{mso-style-name:sdfootnote;
mso-margin-top-alt:auto;
margin-right:0in;
margin-bottom:0in;
margin-left:.2in;
margin-bottom:.0001pt;
text-indent:-.2in;
font-size:10.0pt;
font-family:"Times New Roman","serif";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle21
{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;}
/* List Definitions */
@list l0
{mso-list-id:20790778;
mso-list-template-ids:-721355264;}
@list l0:level1
{mso-level-start-at:5;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:40326619;
mso-list-template-ids:-416545350;}
@list l1:level1
{mso-level-start-at:6;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2
{mso-list-id:305090960;
mso-list-template-ids:1830876168;}
@list l3
{mso-list-id:899555846;
mso-list-template-ids:-71266322;}
@list l3:level1
{mso-level-start-at:3;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thank
you Kathy for breaking this out. I have not been good about
reviewing the entire document.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">To
respond to Peter’s question about what would be legally
enforceable, I think if you look at bullet number 6, if this
bullet was implemented in a very clear and unambiguous way,
by itself and without some of the other material being
proposal, then I think there would be reasonable expectation
that national courts would hold the registrant proxy service
fully responsible for harm caused by a website hosted at the
domain name at issue. In other words, the Ninth Circuit
decision that Susan highlighted would have been decided
differently.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Once
you introduce definitions concerning affiliates, retail
services and different flavors of proxy services, the cheap
ones with flimsy relationships, and the expensive ones with
fiduciary type relationships, it will appear to the court
that you do not really mean what you saying in bullet number
6. This will confuse the courts (and the public) and the
registrant proxy services is more likely to be able to
weasel out of being held liable.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">The
current proposal on the table suggests to me a somewhat more
complicated model whereby the registrant proxy service is
fully liable for the use of the domain name but can shield
that liability by adopted and fully complying the a specific
set of reveal and relay processes etc. I voluntary set of
best practices would not do this, but a mandatory set of
provisions to qualify a proxy service for a “safe harbor”
would. Such a safe hard model would in my view be more
difficult to implement and is likely to give rise to a
certain amount of uncertainty and inconsistent outcomes even
if prudently implemented. But this also assumes that we
need to have a proxy service in which proxies may shield
themselves from liability. In all our discussions, I have
still not heard a persuasive argument why a proxy service
industry that can shield itself from liability is necessary
or good or appropriate. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Seth
<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">
<a class="moz-txt-link-abbreviated" href="mailto:rt4-whois-bounces@icann.org">rt4-whois-bounces@icann.org</a>
[<a class="moz-txt-link-freetext" href="mailto:rt4-whois-bounces@icann.org">mailto:rt4-whois-bounces@icann.org</a>] <b>On Behalf Of </b>Kathy
Kleiman<br>
<b>Sent:</b> Wednesday, November 30, 2011 12:24 PM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:rt4-whois@icann.org">rt4-whois@icann.org</a><br>
<b>Subject:</b> [Rt4-whois] streamlined proxy
recommendation language<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi All,<br>
I feel like I am sending altogether too many emails today.
Sorry :-)! Anyway, here's one more. I worked with James, a
little, and Susan, more, on streamlining the Proxy
recommendations to look, sound and flow like the Privacy
recommendations. Of course, proxy is voluntary, and privacy is
a requirement, but the rest is fairly close. <br>
<br>
They are below and attached. If you like them, we'll send them
on to Alice for inclusion. Note: the definitions went into a
footnote which should be easy to see as it will be quite
extensive.<br>
<br>
here's the text:<o:p></o:p></p>
<p style="margin-bottom:0in;margin-bottom:.0001pt"><b><span
style="font-family:"Calibri","sans-serif"">Data
Access- Proxy Service </span></b><o:p></o:p></p>
<p
style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l2
level1 lfo1"><!--[if !supportLists]--><span
style="mso-list:Ignore">1.<span style="font:7.0pt
"Times New Roman""> </span></span><!--[endif]--><span
style="font-family:"Calibri","sans-serif"">ICANN
should facilitate the review of existing practices by
reaching out to proxy providers to create a discussion which
sets out current processes followed by proxy service
providers.</span><o:p></o:p></p>
<p
style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l2
level1 lfo1"><!--[if !supportLists]--><span
style="mso-list:Ignore">2.<span style="font:7.0pt
"Times New Roman""> </span></span><!--[endif]--><span
style="font-family:"Calibri","sans-serif"">Registrars
should be required to disclosure their relationship with any
Affiliated Retail proxy service provider to ICANN. </span><o:p></o:p></p>
<p
style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l3
level1 lfo2"><!--[if !supportLists]--><span
style="mso-list:Ignore">3.<span style="font:7.0pt
"Times New Roman""> </span></span><!--[endif]--><span
style="font-family:"Calibri","sans-serif"">ICANN
should develop and manage a set of voluntary best practice
guidelines for appropriate proxy services [footnote 1]
consistent with national laws. These voluntary guidelines
should strike an appropriate balance between stakeholders
with competing but legitimate interests. At a minimum this
would include privacy, law enforcement and the industry
around law enforcement. </span><o:p></o:p></p>
<p style="margin-bottom:0in;margin-bottom:.0001pt"><span
style="font-family:"Calibri","sans-serif"">Such
voluntary guidelines may include:</span><o:p></o:p></p>
<p
style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:35.3pt;margin-bottom:.0001pt;text-indent:-35.3pt"><span
style="font-family:"Calibri","sans-serif"">+ Proxy
services provide full contact details as required by the
Whois</span><o:p></o:p></p>
<p
style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:35.3pt;margin-bottom:.0001pt;text-indent:-35.3pt"><span
style="font-family:"Calibri","sans-serif"">+
Publication by the proxy service of its process for
revealing and relaying information</span><o:p></o:p></p>
<p
style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:35.3pt;margin-bottom:.0001pt;text-indent:-35.3pt"><span
style="font-family:"Calibri","sans-serif"">+
Standardization of reveal and relay processes and
timeframes, consistent with national laws</span><o:p></o:p></p>
<p
style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:35.3pt;margin-bottom:.0001pt;text-indent:-35.3pt"><span
style="font-family:"Calibri","sans-serif"">+
Maintenance of a dedicated abuse point of contact for the
proxy service provider</span><o:p></o:p></p>
<p
style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:35.3pt;margin-bottom:.0001pt;text-indent:-35.3pt"><span
style="font-family:"Calibri","sans-serif"">+ Due
diligence checks on licensee contact information. </span><o:p></o:p></p>
<p
style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt"><span
style="font-family:"Calibri","sans-serif"">5. ICANN
should encourage and incentivize registrars to interact with
the retail service providers that adopt the best practices.</span><o:p></o:p></p>
<p
style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt"><span
style="font-family:"Calibri","sans-serif"">6. For
the avoidance of doubt, the WHOIS Policy, referred to in
Recommendation 1 above, should include an affirmative
statement that clarifies that a proxy means a relationship
in which the Registrant is acting on behalf of another. The
WHOIS data is that of the agent, and the agent alone obtains
all rights and assumes all responsibility for the domain
name and its manner of use.</span><o:p></o:p></p>
<p style="margin-bottom:0in;margin-bottom:.0001pt"><span
style="font-family:"Calibri","sans-serif"">Footnote
1 (all the remaining text)<br>
As guidance to the Community and as useful background for
the Proxy Service Recommendations, the Review Team provides
its working definitions of proxy service and different types
of proxy service providers:</span><o:p></o:p></p>
<p class="sdfootnote">- <b><u>Proxy Service</u> </b>– a
relationship in which the registrant is acting on behalf of
another The WHOIS data is that of the agent and the agent
alone obtains all rights and assumes all responsibility for
the domain name and its manner of use. <i>[KK: is this the
definition we are using in other places in the Report?]</i><o:p></o:p></p>
<p class="sdfootnote"><i>- </i><b><u>Affiliated Registrar </u></b><u>-
</u>another ICANN accredited registrar that operates under a
common controlling interest (2009 Registrar Accreditation
Agreement, Section 1.20)<o:p></o:p></p>
<p class="sdfootnote">- <b>Affiliate retail proxy service
provider </b>– entity operating under a common controlling
interest of a registrar.<o:p></o:p></p>
<p class="sdfootnote">- <b>Retail proxy service provider </b>-
proxy service with little or no knowledge of the entity or
individual requesting the service beyond their ability to pay
and their agreement to the general terms and conditions.<o:p></o:p></p>
<p style="margin-bottom:0in;margin-bottom:.0001pt"><span
style="font-family:"Calibri","sans-serif"">-
<b><u>Limited proxy service provider </u></b>- proxy
service for an entity or individual in which there is an
ongoing business relationship bound by a contract that is
specific to the relationship.</span><o:p></o:p></p>
<p class="MsoNormal"><br>
<br>
--- end<br>
same text attached<br>
Kathy<br>
<br>
<o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
</div>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
</pre>
</body>
</html>