<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
+1<br>
Kathy<br>
<br>
<span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-US">I am in favor of Lynn’s proposal.<o:p></o:p></span>
<blockquote
cite="mid:71B38F372F86D940B9C644A99264FA313E7545@M2EMBS1.mail.msk"
type="cite">
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-US">Option 2.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-US">Rgds,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-US">Michael<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif""
lang="EN-US">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif""
lang="EN-US"> <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><a class="moz-txt-link-abbreviated" href="mailto:lynn@goodsecurityconsulting.com">lynn@goodsecurityconsulting.com</a><br>
<b>Sent:</b> Thursday, December 01, 2011 6:53 PM<br>
<b>To:</b> Emily Taylor<br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:rt4-whois@icann.org">rt4-whois@icann.org</a><br>
<b>Subject:</b> Re: [Rt4-whois] GETTING TO CLOSURE: A
ROADMAP<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">I
am in favor of #2: adopt the text drafted by Susan and
James which includes good practices.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">This
is a good and fair compromise and will make a realistic
step forward in improving the abusive activities<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">which
ultimately harm everyone in the domain name industry.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">As
an independent expert on this team, I feel it is important
for us to be mindful that the AoC review requirement is an
alternative to formal government regulation and it is a
form of self-regulation. I have fully supported that
approach. But it will fail if we do not consider the
public interest and the trend of escalating fraud on the
Internet.
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">Lynn<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black"> <o:p></o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid blue
1.5pt;padding:0cm 0cm 0cm
6.0pt;margin-left:6.0pt;margin-top:5.0pt;margin-bottom:5.0pt"
id="replyBlockquote">
<div id="wmQuoteWrapper">
<p class="MsoNormal" style="margin-bottom:12.0pt"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">--------
Original Message --------<br>
Subject: [Rt4-whois] GETTING TO CLOSURE: A ROADMAP<br>
From: Emily Taylor <<a moz-do-not-send="true"
href="mailto:emily@emilytaylor.eu">emily@emilytaylor.eu</a>><br>
Date: Thu, December 01, 2011 10:18 am<br>
To: <a moz-do-not-send="true"
href="mailto:rt4-whois@icann.org">rt4-whois@icann.org</a><br>
<br>
Hi <br>
<br>
I went to bed last night thinking that we were nearly in
agreement on the proxy recommendations that James, Susan
and Kathy have been working on over the past weeks.<br>
<br>
In the middle of the night, I awoke to find new text on
the table.<br>
<br>
You all know that our cut off date was yesterday, and we
are now on negative time. However, I do want to go
through the time zones so that we all have a chance to
consider the options.
<br>
<br>
Broadly, we have three alternatives. <br>
<br>
1. Adopt the very brief text agreed in Dakar and no more<br>
2. Adopt the relatively stable text drafted by that
small group which includes good practices<br>
3. Adopt the new text, drafted last night by Seth on
behalf of another small team.<br>
<br>
We act by consensus. But we also have a deadline. I'm
therefore going to call it before I go to sleep tonight,
and in default of an alternative agreement we will have
to go back to what we agreed in Dakar. I know that some
people are not happy with it, but it has a simplicity,
and avoids confusion about whether or not the good
practices conflicts with the idea of liability.<br>
<br>
Alternatively, we can adopt different text, but it has
to be by consensus. Remember, folks, that's difficult
to achieve, and leaves everyone feeling a little bit
frustrated, and like they could have got more if they
pushed harder.<br>
<br>
Please try to bear in mind that we have a very, very
strong full report. This is one part of the whole
puzzle, which has to be seen within its own context.
There will be further studies on proxies/privacy. There
will be another review team on WHOIS which will kick off
in less than 2 years. To speak for a moment in support
of voluntary good practices, this is a well known
regulatory step. It's what you do when you're not happy
with the current situation (check), but you're not quite
sure what will be an effective regulatory intervention
(check). So, you explore the landscape - as I think the
draft recommendations (alternative 2 below) very
eloquently do. I should emphasise that good practices
are not the final word. They are an interim plug, a
step in the right direction. If, having gone through
that, Bill and others are right and it's all still a
mess, that's when you go for the next incremental step -
but the important bit is, industry has been given a
chance to clean out the stables after being told in no
uncertain terms that there's a problem . That's where we
are now. <br>
<br>
The third choice is that we adopt the new text, maybe
with tweaks or changes. If that's what we're doing, I
would be failing in my duties as your Chair if I did not
set some deadline for this. We have known the issues
for a long time, we have been wrestling with them, and
reaching consensus is hard. I don't think that this is
a case of "just a bit more time", but I'm very willing
to be proved wrong.<br>
<br>
So, my challenge to you is - tell me what you have <b>all</b>
agreed on proxies by 10pm UTC. If the answer is
"nothing" we go with what we agreed in Dakar.<br>
<br>
Whatever the outcome, we have done a wonderful job on
this report. Take it in its entirety, it represents a
lot of work, and a lot of willpower and cooperation,
plus - importantly - a willingness to step outside of
one's individual, commercial interests and think about
the public interest. I have been marvelling at the
sheer energy that has been focused on this mailing list
and the incredible progress we have made since the
weekend (remember, I'm a Brit, not American, so I don't
say these sort of things easily!).<br>
<br>
Keep up this discussion. But please focus your thoughts
and exchanges on the give and take that's necessary for
consensus.<br>
<br>
To assist those who may not be fully up to speed, the
text for the three alternatives are below. Whatever
happens, we are closing this discussion in just under 7
hours. Good luck!<br>
<br>
Kind regards<br>
<br>
Emily<br>
<br>
---------<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black;background:#FEFA51">Alternative
1</span><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black"><br>
the text we agreed in Dakar on proxy definition and
proxy liability</span><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">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><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black;background:#FEFA51">Alternative
2<br>
</span><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">The
text on best practices worked on by Susan, James and
Kathy last night (latest version)</span><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><b><span
style="font-family:"Calibri","sans-serif";color:black">Data
Access- Proxy Service</span></b><span
style="color:black"><o:p></o:p></span></p>
</div>
<div style="margin-left:36.0pt">
<p class="MsoNormal"><span
style="font-size:9.0pt;color:black">1.</span><span
style="font-size:7.0pt;color:black"> </span><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">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><span
style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
</div>
<div style="margin-left:36.0pt">
<p class="MsoNormal"><span
style="font-size:9.0pt;color:black">2.</span><span
style="font-size:7.0pt;color:black"> </span><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">Registrars
should be required to disclosure their relationship
with any Affiliated Retail proxy service provider to
ICANN.</span><span
style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
</div>
<div style="margin-left:36.0pt">
<p class="MsoNormal"><span
style="font-size:9.0pt;color:black">3.</span><span
style="font-size:7.0pt;color:black"> </span><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">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><span
style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">Such
voluntary guidelines may include:</span><span
style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
</div>
<div style="margin-left:35.3pt">
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">+
Proxy services provide full contact details as
required by the Whois</span><span
style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
</div>
<div style="margin-left:35.3pt">
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">+
Publication by the proxy service of its process for
revealing and relaying information</span><span
style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
</div>
<div style="margin-left:35.3pt">
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">+
Standardization of reveal and relay processes and
timeframes, consistent with national laws</span><span
style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
</div>
<div style="margin-left:35.3pt">
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">+
Maintenance of a dedicated abuse point of contact
for the proxy service provider</span><span
style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
</div>
<div style="margin-left:35.3pt">
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">+
Due diligence checks on licensee contact
information.</span><span
style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
</div>
<div style="margin-left:36.0pt">
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">5.
ICANN should encourage and incentivize registrars to
interact with the retail service providers that
adopt the best practices.</span><span
style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
</div>
<div style="margin-left:36.0pt">
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">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><span
style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">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><span
style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
</div>
<div style="margin-left:14.4pt">
<p class="MsoNormal"><span
style="font-size:9.0pt;color:black">- <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></span><span
style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
</div>
<div style="margin-left:14.4pt">
<p class="MsoNormal"><i><span
style="font-size:9.0pt;color:black">- </span></i><b><u><span
style="font-size:9.0pt;color:black">Affiliated
Registrar </span></u></b><u><span
style="font-size:9.0pt;color:black">- </span></u><span
style="font-size:9.0pt;color:black">another ICANN
accredited registrar that operates under a common
controlling interest (2009 Registrar Accreditation
Agreement, Section 1.20)</span><span
style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
</div>
<div style="margin-left:14.4pt">
<p class="MsoNormal"><span
style="font-size:9.0pt;color:black">- <b>Affiliate
retail proxy service provider </b>– entity
operating under a common controlling interest of a
registrar.</span><span
style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
</div>
<div style="margin-left:14.4pt">
<p class="MsoNormal"><span
style="font-size:9.0pt;color:black">- <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.</span><span
style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">- <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><span
style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Verdana","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black"><br>
<span style="background:#FEFA51">Alternative 3</span><br>
Seth's proposal.</span><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">Data
Access- Proxy Service</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">1. The
Review Team considers a Proxy Service as a
relationship in which</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">the
registrant is acting on behalf of another. The WHOIS
data is that of the</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">agent/proxy
service and the agent/proxy service alone obtains
all rights and</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">assumes
all responsibility for the domain name and its
manner of use.</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">2. ICANN
should clarify that any registrant that may be
acting as a</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">proxy
service for another is in all respects still the
registrant and, in</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">ICANN's
view, should be held fully responsible for the use
of the domain</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">name
including for any and all harm that results from the
use of the domain</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">name.</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">2. Because
of ICANN's position on proxy services to date, which</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">tolerates
the proxy service industry that has arisen and which
through RAA</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">provisions
gives recognition and attempts to regulate that
industry, has</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">been
used by courts and others to allow proxy services to
escape liability</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">for
bad acts of the proxy service customers, ICANN
should either delete or</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">amend
those provisions of the RAA that can or have been
used to allow proxy</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">services
to escape liability.</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">3. The
Review Team acknowledges that there may be
legitimate reasons</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">for
the occasional use of a proxy service, as for
example to protect a</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">valuable
trade secret at product launch. At the same time
proxy services</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">should
not be viewed or used as a substitute for privacy
services that are</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">designed
to shield an individual's personal contact
information. The</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">legitimate
use a proxy service would be the exception and not
widespread.</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">4. A
proxy service industry willing to accept full risks
and liabilities</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">for
the manner in which domain names through its service
will be used will</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">take
the necessary precautionary measures, in its
relationship with its</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">customers,
such that domain names so registered are unlikely to
be misused</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">and,
if misused, a remedy for those victimized will more
likely be</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:black">available.</span><span
style="font-size:10.5pt;font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black;border:solid
windowtext 1.0pt;padding:0cm"><img
id="Picture_x0020_1"
src="cid:part1.08020603.08060107@kathykleiman.com"
alt="Description: Image removed by sender."
border="0" height="100" width="100"></span><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black"><br
clear="all">
<br>
-- <br>
<br>
<br>
<span style="border:solid windowtext
1.0pt;padding:0cm"><img id="Picture_x0020_2"
src="cid:part1.08020603.08060107@kathykleiman.com"
alt="Description: Image removed by sender."
border="0" height="100" width="100"></span><o:p></o:p></span></p>
<div style="margin-left:60.0pt">
<p class="MsoNormal"><u><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#CC33CC">
</span></u><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#993399"><br>
</span><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black"><br>
</span><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#999999">76
Temple Road, Oxford OX4 2EZ UK<br>
t: <a moz-do-not-send="true"
href="tel:%2B44%20%280%291865%20582%20811"
target="_blank">+44 (0)1865 582 811</a> • m:
<a moz-do-not-send="true"
href="tel:%2B44%20%280%297540%20049%20322"
target="_blank">+44 (0)7540 049 322</a><br>
<a moz-do-not-send="true"
href="mailto:emily@emilytaylor.eu" target="_blank">emily@emilytaylor.eu</a>
<br>
<br>
<b><a moz-do-not-send="true"
href="http://www.etlaw.co.uk/" target="_blank">www.etlaw.co.uk</a></b><br>
<br>
Emily Taylor Consultancy Limited is a company
registered in England and Wales No. 730471. VAT No.
114487713.</span><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black"><o:p> </o:p></span></p>
<div class="MsoNormal" style="text-align:center"
align="center"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">
<hr align="center" size="2" width="100%">
</span></div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">_______________________________________________<br>
Rt4-whois mailing list<br>
<a moz-do-not-send="true"
href="mailto:Rt4-whois@icann.org">Rt4-whois@icann.org</a><br>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/rt4-whois">https://mm.icann.org/mailman/listinfo/rt4-whois</a><o:p></o:p></span></p>
</div>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Rt4-whois mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Rt4-whois@icann.org">Rt4-whois@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/rt4-whois">https://mm.icann.org/mailman/listinfo/rt4-whois</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
</pre>
</body>
</html>