<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@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:Verdana;
panose-1:2 11 6 4 3 5 4 4 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";}
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;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I want to echo and support Greg’s response below. Milton’s position that an existing 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 mission 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. <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><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> accountability-cross-community-bounces@icann.org [mailto:accountability-cross-community-bounces@icann.org] <b>On Behalf Of </b>Greg Shatan<br><b>Sent:</b> Sunday, November 22, 2015 3:01 AM<br><b>To:</b> Mueller, Milton L<br><b>Cc:</b> Accountability Cross Community<br><b>Subject:</b> Re: [CCWG-ACCT] Board comments on the Mission statement<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal><span style='font-family:"Verdana","sans-serif"'>Milton,<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Verdana","sans-serif"'>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.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Verdana","sans-serif"'>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?<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Verdana","sans-serif"'>Thanks.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Verdana","sans-serif"'>Greg<o:p></o:p></span></p></div></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Sat, Nov 21, 2015 at 5:56 PM, Mueller, Milton L <<a href="mailto:milton@gatech.edu" target="_blank">milton@gatech.edu</a>> wrote:<o:p></o:p></p><p class=MsoNormal><br><br>> -----Original Message-----<br>><br>> See section 3.7.7 of the registrar accreditation agreement (RAA):<br>> <a href="https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en" target="_blank">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?<o:p></o:p></p><div><div><p class=MsoNormal><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" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><o:p></o:p></p></div></div></div><p class=MsoNormal><o:p> </o:p></p></div><p>=================================================================<br><b><i><span style='color:red'>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> </span></i></b><o:p></o:p></p><p><br>=================================================================<o:p></o:p></p></div>
<P>=================================================================<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/>
</P></body></html>