<html>
<body>
At 10:03 AM 11/23/2015, Burr, Becky wrote:<br><br>
<blockquote type=cite class=cite cite="">Are we seriously arguing that
RAA 3.7.7.9 is outside the picket fence? </blockquote><br>
No, I don't think this was out of scope, because it concerns the
"registration" of the name and the manner in which THE NAME is
used. 3.7.7.9 does not say, in my opnion, that the registrant has
to promise that it is not doing anything at a website that is infringing;
the promise is that the name is not being used in an infringing
manner.<br><br>
D<br><br>
At 10:03 AM 11/23/2015, Burr, Becky wrote:<br><br>
<blockquote type=cite class=cite cite="">Are we seriously arguing that
RAA 3.7.7.9 is outside the picket fence? <br><br>
Section 3.7.7.9 of the RAA has been in place from the beginning of
time. Here is the language from the 2001 RAA:<br><br>
<dl>
<dd>3.7.7.9 The Registered Name Holder shall represent that, to the best
of the Registered Name Holder's knowledge and belief, neither the
registration of the Registered Name nor the manner in which it is
directly or indirectly used infringes the legal rights of any third
party.<br><br>
</dl>Here it is in the <font color="#FF0000">1999 RAA</font>:<br><br>
<dl>
<dd>7. g. The SLD holder shall represent that, to the best of the SLD
holder's knowledge and belief, neither the registration of the SLD name
nor the manner in which it is directly or indirectly used infringes the
legal rights of a third party.<br><br>
</dl><br>
<font face="Calibri">As someone who was part of the team drafting and
negotiating the 1999 RAA, I can assure you that the inclusion of this
requirement in the RAA was intended to be within the scope of ICANN’s
Mission.<br>
</font><br>
<br>
J. Beckwith Burr <br>
Neustar, Inc. </b>/ </b>Deputy General Counsel & Chief Privacy
Officer<br>
1775 Pennsylvania Avenue NW, Washington D.C. 20006<br>
Office: </b>+1.202.533.2932 Mobile: </b>+1.202.352.6367 /</b>
<a href="http://www.neustar.biz">neustar.biz</a><br>
</b><br>
From: Alan Greenberg
<<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a>
><br>
Date: Sunday, November 22, 2015 at 10:06 PM<br>
To: "Silver, Bradley"
<<a href="mailto:Bradley.Silver@timewarner.com">
Bradley.Silver@timewarner.com</a>>, Greg Shatan
<<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a>
>, "Mueller, Milton L"
<<a href="mailto:milton@gatech.edu">milton@gatech.edu</a>><br>
Cc: Accountability Community
<<a href="mailto:accountability-cross-community@icann.org">
accountability-cross-community@icann.org</a>><br>
Subject: Re: [CCWG-ACCT] Board comments on the Mission statement<br><br>
I rarely fill people's mailboxes just to do this, but in this
case;<br><br>
+1<br><br>
Alan<br><br>
<br>
At 22/11/2015 08:31 PM, Silver, Bradley wrote:<br><br>
<blockquote type=cite class=cite cite="">I want to echo and support
Greg̢۪s resposponse below. Milton̢۪s position that an
existinting provision of the RAA is out of the scope of ICANNâ€ââ„¢s
mission is illuminating. I had been operating on the (hopeful)
presumption that what we were attempting to do was find a way to describe
ICANN̢۪s missionion in a manner that reflects its current activities,
and avoid drafting anything that could adversely impact its continued
ability to do so while clearly preventing any undue
expansion. If those who support the language in the second
sentence are seeking a way to attack the validity or enforceability of
existing contractual provisions, then the concerns of the board are not
only well founded, they are grossly understated. <br>
<br>
From:</b>
<a href="mailto:accountability-cross-community-bounces@icann.org">
accountability-cross-community-bounces@icann.org</a> [
<a href="mailto:accountability-cross-community-bounces@icann.org" eudora="autourl">
mailto:accountability-cross-community-bounces@icann.org</a>] On Behalf Of
</b>Greg Shatan<br>
Sent:</b> Sunday, November 22, 2015 3:01 AM<br>
To:</b> Mueller, Milton L<br>
Cc:</b> Accountability Cross Community<br>
Subject:</b> Re: [CCWG-ACCT] Board comments on the Mission statement<br>
<br>
Milton,<br>
<br>
I strongly disagree that 3.7.7 is out of scope of ICANN's mission.
I also don't think it's useless, nor is it an uncommon provision in many
terms of service and similar agreements. 3.7.7 only asks for the
registrant's "knowledge and belief" -- so they are not required
to know whether they are infringing anywhere under any
jurisdiction. They are only required to make reference to what they
already know -- an entirely reasonable and ordinary requirement.<br>
<br>
Is it your intent that the new provision we are discussing places 3.7.7
out of scope, and thus serves as a basis for an IRP or other challenge
seeking to nullify 3.7.7? Since 3.7.7 is only an
"example," what other sections are you trying to place out of
scope?<br>
<br>
Thanks.<br>
<br>
Greg<br>
<br>
On Sat, Nov 21, 2015 at 5:56 PM, Mueller, Milton L
<<a href="mailto:milton@gatech.edu">milton@gatech.edu</a>>
wrote:<br><br>
<br>
> -----Original Message-----<br>
><br>
> See section 3.7.7 of the registrar accreditation agreement
(RAA):<br>
>
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources_pages_approved-2Dwith-2Dspecs-2D2013-2D09-2D17-2Den&d=CwMFaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=11R4XkcvGwOIsQkhhyE47Z7B829g9E2Cip1amJSBQu0&s=5ThaiusaRSYwZuxG3vlUf8hTsMh251yjw_-T7i4DOFg&e=">
https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en</a>
<br>
><br>
> 3.7.7.9 The Registered Name Holder shall represent that, to the best
of the<br>
> Registered Name Holder's knowledge and belief, neither the
registration of<br>
> the Registered Name nor the manner in which it is directly or
indirectly used<br>
> infringes the legal rights of any third party.<br><br>
Bruce: this is a good example of how the RAA is currently out of scope.
To begin with, it is a completely useless element of the RAA. This
statement does not stop anyone from doing anything, and it does not
require ICANN to determine whether a registrant is infringing someone's
rights. And how is anyone supposed to know whether the way they use a
domain infringes the legal rights of a third party - anywhere in the
world, under any jurisdiction? They cannot know this until
and unless someone asserts those rights against them in a legal
system which has jurisdiction and can make a legal determination. Or do
we want ICANN to be making this determination? Most would agree that we
do not. So what is the purpose, other than to invite ICANN to impose
controls or regulations on virtually anything that happens on the
internet?<br><br>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org">
Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" eudora="autourl">
https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
<br>
<br><br>
=================================================================<br>
Reminder: Any email that requests your login credentials or that asks you
to click on a link could be a phishing attack. If you have any
questions regarding the authenticity of this email or its sender, please
contact the IT Service Desk at 212.484.6000 or via email at
<a href="mailto:ITServices@timewarner.com">ITServices@timewarner.com</a>
<br>
</i></b><br><br>
=================================================================<br><br>
=================================================================<br>
This message is the property of Time Warner Inc. and is intended only for
the use of the<br>
addressee(s) and may be legally privileged and/or confidential. If the
reader of this message<br>
is not the intended recipient, or the employee or agent responsible to
deliver it to the intended<br>
recipient, he or she is hereby notified that any dissemination,
distribution, printing, forwarding,<br>
or any method of copying of this information, and/or the taking of any
action in reliance on<br>
the information herein is strictly prohibited except by the intended
recipient or those to whom<br>
he or she intentionally distributes this message. If you have received
this communication in<br>
error, please immediately notify the sender, and delete the original
message and any copies<br>
from your computer or storage system. Thank you.<br>
=================================================================<br>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org">
Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" eudora="autourl">
https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
</blockquote>_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
Accountability-Cross-Community@icann.org<br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" eudora="autourl">
https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
</blockquote><br>
*******************************<br>
David G Post - Senior Fellow, Open Technology Institute/New America
Foundation<br>
blog (Volokh Conspiracy)
<a href="http://www.washingtonpost.com/people/david-post" eudora="autourl">
http://www.washingtonpost.com/people/david-post<br>
</a>book (Jefferson's Moose)
<a href="http://tinyurl.com/c327w2n%A0%A0%A0%A0%A0%A0%A0" eudora="autourl">
http://tinyurl.com/c327w2n </a> <br>
music
<a href="http://tinyurl.com/davidpostmusic%A0" eudora="autourl">
http://tinyurl.com/davidpostmusic </a> publications etc.
<a href="http://www.davidpost.com /" eudora="autourl">
http://www.davidpost.com
</a> <br>
******************************* </body>
</html>