<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:"Avenir Next";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* 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";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle27
{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:1144355057;
mso-list-type:hybrid;
mso-list-template-ids:84674086 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
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]--></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'>The object of the policy is not purely the domain name registration – it is how that registration is used, which practically means one cannot address an actionable infringement without some sort of infringing use. And without a website (even a blank one), there is a question whether there is any “use” to begin with. We are in agreement that the UDRP is completely consistent with ICANN’s mission. I am worried however, that these distinctions about “domain names per se” and their use in connection with an underlying website don’t translate into what the UDRP is, in reality, or as a matter of policy. <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'>And to Phil Corwin’s point about the relevance of the UDRP to this discussion - since ICANN obliges registrars to comply with the UDRP process, the UDRP must be consistent with ICANN’s mission. <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><ul style='margin-top:0in' type=disc><li class=MsoNormal style='color:#1F497D;mso-list:l0 level1 lfo1'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>3.8 <u>Domain-Name Dispute Resolution</u>. During the Term of this Agreement, Registrar shall have in place a policy and procedures for resolution of disputes concerning Registered Names. Until ICANN adopts an alternative Consensus Policy or other Specification or Policy with respect to the resolution of disputes concerning Registered Names, Registrar shall comply with the Uniform Domain Name Dispute Resolution Policy ("UDRP") identified on ICANN's website (www.icann.org/general/consensus-policies.htm), as may be modified from time to time. Registrar shall also comply with the Uniform Rapid Suspension ("URS") procedure or its replacement, as well as with any other applicable dispute resolution procedure as required by a Registry Operator for which Registrar is providing Registrar Services. <o:p></o:p></span></li></ul><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"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Mueller, Milton L [mailto:milton@gatech.edu] <br><b>Sent:</b> Monday, November 23, 2015 5:50 PM<br><b>To:</b> Silver, Bradley; Burr, Becky; Metalitz, Steven; David Post<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></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Bradley, you seem intent on manufacturing a disagreement where none exists. Of course a UDRP finding of illegitimate domain name use must take into account how the name is used. But the object of policy is not the content of the website per se but the domain name registration; i.e., the UDRP doesn’t tell the web site owner to change the content of their site, it takes away the name. <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 style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> Silver, Bradley [<a href="mailto:Bradley.Silver@timewarner.com">mailto:Bradley.Silver@timewarner.com</a>] <br><b>Sent:</b> Monday, November 23, 2015 5:37 PM<br><b>To:</b> Mueller, Milton L; Burr, Becky; Metalitz, Steven; David Post<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></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Milton, we keep coming back to this - what ICANN does is simply not as neat as all that. As per Becky’s email below, the policies related to the domain name itself can also take into account the <b><u>use</u></b> of the domain name. In a real world UDRP context, that will include consideration of how the domain is used – i.e. evidence of the website, and bad faith etc. If you want to draw a neat distinction between an ICANN policy extending beyond the domain name to include consideration of the website which resolves to that name, then you’d have to issue a directive to every UDRP panelist to not take into account what “content” is resident on that website. For example, EFF recently successfully used a UDRP to capture a domain which was used </span><span lang=EN style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>in connection with a website surreptitiously installing malicious software on the computers of unsuspecting visitors, and redirecting infected visitors to the EFF’s official website. The nature of the content on the website was instructive in the panel finding that the domain name was used in bad faith. See: </span><a href="http://www.wipo.int/amc/en/domains/search/text.jsp?case=D2015-1628"><span lang=EN style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>http://www.wipo.int/amc/en/domains/search/text.jsp?case=D2015-1628</span></a><span lang=EN 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"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Mueller, Milton L [</span><a href="mailto:milton@gatech.edu"><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>mailto:milton@gatech.edu</span></a><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>] <br><b>Sent:</b> Monday, November 23, 2015 5:19 PM<br><b>To:</b> Burr, Becky; Metalitz, Steven; Silver, Bradley; David Post<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></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>It should be evident from everything that has been written by David, myself, Malcolm and many others that the target of the mission limitation is not the UDRP or domain name – trademark conflicts. In the UDRP the object of policy and enforcement is the domain name registration. Our goal is to limit ICANN to policies related to the domain name itself, and to prevent that power from being extended to web site content or other services or activities that might be associated with a domain. <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'>--MM<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 style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><a href="mailto:accountability-cross-community-bounces@icann.org"><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>accountability-cross-community-bounces@icann.org</span></a><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> [</span><a href="mailto:accountability-cross-community-bounces@icann.org"><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>mailto:accountability-cross-community-bounces@icann.org</span></a><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>] <b>On Behalf Of </b>Burr, Becky<br><b>Sent:</b> Monday, November 23, 2015 4:40 PM<br><b>To:</b> Metalitz, Steven; 'Silver, Bradley'; David Post<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></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal><span style='font-family:"Avenir Next","serif"'>I think we agree that the UDRP policy takes into account the use of a registered string to infringe a third party’s rights – either demonstrated by use of the domain, efforts to extort, or a pattern of offending conduct. That falls within the picket fence provision that (Spec 4 in the 2013 RAA) permits ICANN to enforce policies regarding <span style='background:white'>resolution of disputes regarding the registration of domain names<span style='color:#333333'> (as opposed to the use of such domain names</span><span style='color:red'>, but including where such policies take into account use of the domain names.) </span></span></span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:9.0pt;color:black'>J. Beckwith Burr</span></b><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'><o:p></o:p></span></p></div><p class=MsoNormal style='margin-top:12.0pt;mso-margin-bottom-alt:auto'><b><span style='font-size:9.0pt;color:#008656'>Neustar, Inc.</span></b><b><span style='font-size:9.0pt;color:#068658'> </span></b><span style='font-size:9.0pt;color:#7D7D7D'>/</span><b><span style='font-size:9.0pt;color:#068658'> </span></b><span style='font-size:9.0pt;color:#7D7D7D'>Deputy General Counsel & Chief Privacy Officer<br>1775 Pennsylvania Avenue NW, Washington D.C. 20006</span><span style='font-size:9.0pt;color:gray'><br></span><b><span style='font-size:9.0pt;color:#008656'>Office:</span></b><b><span style='font-size:9.0pt;color:#7D7D7D'> </span></b><span style='font-size:9.0pt;color:#7D7D7D'>+1.202.533.2932 </span><b><span style='font-size:9.0pt;color:#008656'>Mobile:</span></b><b><span style='font-size:9.0pt;color:#7D7D7D'> </span></b><span style='font-size:9.0pt;color:#7D7D7D'>+1.202.352.6367 </span><strong><span style='font-size:9.0pt;font-family:"Arial","sans-serif";color:#7D7D7D'>/</span></strong><span style='font-size:9.0pt;color:#068658'> </span><a href="http://www.neustar.biz"><b><span style='font-size:9.0pt;color:#008656'>neustar.biz</span></b></a><span style='color:black'><o:p></o:p></span></p></div></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'><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:11.0pt;font-family:"Calibri","sans-serif";color:black'>From: </span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'><Metalitz>, Steven Metalitz <</span><a href="mailto:met@msk.com"><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>met@msk.com</span></a><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'>><br><b>Date: </b>Monday, November 23, 2015 at 2:50 PM<br><b>To: </b>"'Silver, Bradley'" <</span><a href="mailto:Bradley.Silver@timewarner.com"><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Bradley.Silver@timewarner.com</span></a><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'>>, Becky Burr <</span><a href="mailto:becky.burr@neustar.biz"><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>becky.burr@neustar.biz</span></a><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'>>, David Post <</span><a href="mailto:david.g.post@gmail.com"><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>david.g.post@gmail.com</span></a><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'>><br><b>Cc: </b>Accountability Community <</span><a href="mailto:accountability-cross-community@icann.org"><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>accountability-cross-community@icann.org</span></a><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'>><br><b>Subject: </b>RE: [CCWG-ACCT] Board comments on the Mission statement<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>A successful UDRP case requires proof of bad faith registration AND USE of a domain name. Others are far more expert than I am on UDRP jurisprudence ( as contrasted with its genesis and development), but I thought that jurisprudence clearly established that the activities that take place on (e.g.) a website to which that domain name resolves is highly relevant (indeed, sometimes probative) of whether the domain name has been USED in bad faith. It would be anomalous if, in the provision that is now 3.7.7.9 of the RAA, which as Becky has demonstrated was first included in the RAA almost contemporaneously with the adoption of the UDRP, the phrase “use of a registered name” meant something markedly different than it means in the UDRP, and even odder if it meant something much narrower, especially considering that the RAA provision(in contrast to UDRP) refers to “direct or indirect” use. Finally, as Bradley points out, this is a contract provision, one that has been in place (in the case of 3.7.7.9 at least) ever since there were contracts between ICANN and accredited registrars; so the notion that we would now seek to place the enforcement of that provision off-limits to ICANN under the banner of “enhancing ICANN accountability” suggests to me that we have gone seriously off track here. </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Steve Metalitz </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span style='color:black'><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:black'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'> </span><a href="mailto:accountability-cross-community-bounces@icann.org"><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>accountability-cross-community-bounces@icann.org</span></a><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'> [</span><a href="mailto:accountability-cross-community-bounces@icann.org"><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>mailto:accountability-cross-community-bounces@icann.org</span></a><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>] <b>On Behalf Of </b>Silver, Bradley<br><b>Sent:</b> Monday, November 23, 2015 2:38 PM<br><b>To:</b> Burr, Becky; David Post<br><b>Cc:</b> Accountability Cross Community<br><b>Subject:</b> Re: [CCWG-ACCT] Board comments on the Mission statement</span><span style='color:black'><o:p></o:p></span></p></div></div><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks Becky, </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The question is not whether ICANN’s authority to enforce policies regarding resolutions of domain name disputes can be stretched to websites, the question is whether under the RAA, ICANN can validly require registrars to maintain an abuse contact and take certain steps in response to reports of Illegal Activity – which is defined to include conduct <i>involving</i> use of a Registered Name. Putting aside the issue of defamation and infringement etc, let’s assume for a moment that the Illegal Activity in question is not inherent in the domain name itself but rather <i>involves</i> the use of the name, either directly or indirectly. And let’s further assume that such use is something that a reasonable person might argue impacts ICANN’s ability to ensure the stable and secure operation of the Internet's unique identifier systems. I had thought that the language we were searching for would permit ICANN to act in those circumstances. Unless you are you taking the position that we know all we need to know today about what those circumstances might be, and whether ICANN’s activity could be impinged by the language we have been discussing, then you must acknowledge that we are doing brain surgery in the dark here by trying to constrain ICANN’s mission with language that has imprecise meaning. </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Bradley</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span style='color:black'><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:black'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'> Burr, Becky [</span><a href="mailto:Becky.Burr@neustar.biz"><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>mailto:Becky.Burr@neustar.biz</span></a><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>] <br><b>Sent:</b> Monday, November 23, 2015 1:38 PM<br><b>To:</b> Silver, Bradley; David Post<br><b>Cc:</b> Alan Greenberg; Greg Shatan; Mueller, Milton L; Accountability Cross Community<br><b>Subject:</b> Re: [CCWG-ACCT] Board comments on the Mission statement</span><span style='color:black'><o:p></o:p></span></p></div></div><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><div><div><p class=MsoNormal><span style='font-family:"Avenir Next","serif";color:black'>Bradley, </span><span style='color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;color:black'> </span><span style='color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Avenir Next","serif";color:black'>3.7.7.9 speaks about the registration and use of a “Registered Name.” </span><span style='font-family:"Avenir Next","serif";color:#333333;background:white'>A "Registered Name" refers to a domain name within the domain of a </span><span style='font-family:"Avenir Next","serif";color:black'>gTLD</span><span style='font-family:"Avenir Next","serif";color:#333333;background:white'>…about which a </span><span style='font-family:"Avenir Next","serif";color:black'>gTLD</span><span style='font-family:"Avenir Next","serif";color:#333333;background:white'> Registry Operator (or an Affiliate or subcontractor thereof engaged in providing Registry Services) maintains data in a Registry Database, arranges for such maintenance, or derives revenue from such maintenance.” To me, that refers to registration and use of a string, and not a web site.</span><span style='color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;color:black'> </span><span style='color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Avenir Next","serif";color:black'>That is also consistent with the registrar form of the “picket fence," which allows ICANN to unilaterally obligate registrars to comply with policies (a) covering specific topics and (b) developed in accordance with specified procedures designed to ensure that they are supported by consensus. The RAA spec (Section 4 of the 2001 RAA and Spec 4 in the 2013 RAA) covers policies regarding <span style='background:white'>resolution of disputes regarding the registration of domain names</span></span><span style='font-family:"Avenir Next","serif";color:#333333;background:white'> (as opposed to the use of such domain names</span><span style='font-family:"Avenir Next","serif";color:red;background:white'>, but including where such policies take into account use of the domain names.) </span><span style='font-family:"Avenir Next","serif";color:black'>So, under the Registrar’s form of picket fence, if ICANN has developed a Consensus Policy that covers resolution of <i>disputes about registrations</i> (e.g., the UDRP, the Rapid Suspension policy, etc.), and that policy takes use into account (I.e, in the case of the UDRP for example, registration of a name “in bad faith” as defined in the UDRP), it is within ICANN’s authority. </span><span style='color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;color:black'> </span><span style='color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Avenir Next","serif";color:black'>The question is, could ICANN’s authority to enforce policies regarding <span style='background:white'>resolution of disputes regarding the <i>registration of domain names</i> be stretched to construe use of a <i>web site</i> (as opposed to the string itself) for defamation? I agree with David, </span>I "don't think they have that power at present, I don't think they have had that since the beginning of (ICANN) time, and I sure as heck don't want to them to have it once they are in control of the root and USG oversight is removed.” </span><span style='color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Avenir Next","serif";color:black'>Becky</span><span style='color:black'><o:p></o:p></span></p></div><div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'> </span><span style='color:black'><o:p></o:p></span></p></div><p class=MsoNormal style='margin-top:12.0pt;mso-margin-bottom-alt:auto'><b><span style='font-size:9.0pt;color:black'>J. Beckwith Burr</span></b><b><span style='font-size:9.0pt;color:#3366FF'><br></span></b><b><span style='font-size:9.0pt;color:#008656'>Neustar, Inc.</span></b><span style='font-size:9.0pt;color:#7D7D7D'>/Deputy General Counsel & Chief Privacy Officer<br>1775 Pennsylvania Avenue NW, Washington D.C. 20006</span><span style='font-size:9.0pt;color:gray'><br></span><b><span style='font-size:9.0pt;color:#008656'>Office:</span></b><span style='font-size:9.0pt;color:#7D7D7D'>+1.202.533.2932 </span><b><span style='font-size:9.0pt;color:#008656'>Mobile:</span></b><span style='font-size:9.0pt;color:#7D7D7D'>+1.202.352.6367 </span><strong><span style='font-size:9.0pt;font-family:"Arial","sans-serif";color:#7D7D7D'>/</span></strong><a href="http://www.neustar.biz"><b><span style='font-size:9.0pt;color:#008656'>neustar.biz</span></b></a><span style='color:black'><o:p></o:p></span></p></div></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'> </span><span style='color:black'><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:11.0pt;font-family:"Calibri","sans-serif";color:black'>From: </span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'><Silver>, Bradley <</span><a href="mailto:Bradley.Silver@timewarner.com"><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Bradley.Silver@timewarner.com</span></a><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'>><br><b>Date: </b>Monday, November 23, 2015 at 11:47 AM<br><b>To: </b>David Post <</span><a href="mailto:david.g.post@gmail.com"><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>david.g.post@gmail.com</span></a><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'>><br><b>Cc: </b>Becky Burr <</span><a href="mailto:becky.burr@neustar.biz"><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>becky.burr@neustar.biz</span></a><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'>>, Alan Greenberg <</span><a href="mailto:alan.greenberg@mcgill.ca"><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>alan.greenberg@mcgill.ca</span></a><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'>>, Greg Shatan <</span><a href="mailto:gregshatanipc@gmail.com"><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>gregshatanipc@gmail.com</span></a><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'>>, "Mueller, Milton L" <</span><a href="mailto:milton@gatech.edu"><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>milton@gatech.edu</span></a><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'>>, Accountability Community <</span><a href="mailto:accountability-cross-community@icann.org"><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>accountability-cross-community@icann.org</span></a><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'>><br><b>Subject: </b>RE: [CCWG-ACCT] Board comments on the Mission statement</span><span style='color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'> </span><span style='color:black'><o:p></o:p></span></p></div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>There is a difference between ICANN having power to “enforce local laws”, as you put it, and ICANN’s ability to enforce its agreements, which have as a reference point, the conduct of “illegal activity” via an indirect use of a domain name. Let’s be very clear – we are talking about the latter; the question of whether the enforcement of specific provisions on their face, would amount to the kind of regulation you and others would like to see prohibited. There are a number of forms that enforcement could take which don’t make ICANN a proxy for local law enforcement. For example, one manifestation of this concept is in RAA 3.18.1, which talks about the maintenance of an abuse contact for reports of illegal activity, which will trigger an obligation to investigate and respond appropriately. RAA 3.7.7.9 is a logical companion to this provision, since it ensures that registrars are able, in accordance with their own terms of service, to address abuse complaints involving illegal activity, as between them and the registrant involved. We know there is a broader discussion about what that should entail, but I am concerned that the language being proposed to prohibit any “direct or indirect” regulation will be used to argue that these contractual provisions are outside ICANN’s mission on their face. </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span style='color:black'><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:black'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'> David Post [</span><a href="mailto:david.g.post@gmail.com"><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>mailto:david.g.post@gmail.com</span></a><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>] <br><b>Sent:</b> Monday, November 23, 2015 11:22 AM<br><b>To:</b> Silver, Bradley<br><b>Cc:</b> Burr, Becky; Alan Greenberg; Greg Shatan; Mueller, Milton L; Accountability Cross Community<br><b>Subject:</b> RE: [CCWG-ACCT] Board comments on the Mission statement</span><span style='color:black'><o:p></o:p></span></p></div></div><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span style='color:black'><br>Well, this is illuminating ... <br><br>I take it that at least you and Greg (and perhaps others) think that it is within ICANN's power to enforce, via its power over the DNS entries, local pornography laws, or consumer protection laws, or defamation laws, or ... on the grounds that registrants have to promise not to infringe any rights of any third parties in any activity they undertake "on the website to which the domain points." So ICANN can set up a Pornography Dispute Resolution Procedure, a Consumer Protection Dispute Resolution Procedure, a Defamation Dispute Resolution Procedure, to enforce these promises that registrants have supposedly made and to take down violators. <br><br>My response is: I don't think they have that power at present, I don't think they have had that since the beginning of (ICANN) time, and I sure as heck don't want to them to have it once they are in control of the root and USG oversight is removed. <br><br>David<br><br><br>At 10:51 AM 11/23/2015, Silver, Bradley wrote:<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>David, <br> <br>That’s an overly narrow reading of RAA 3.7.7.9  - its not only that the registration of the Registered Name infringes or its “direct useâ€, but also that the manner in which is <i>indirectly</i> is used. I can’t see how the “indirect†use of the domain cannot also be attributed to infringing uses on the website to which the domain points.  If that’s not at least an “indirect†use, I don’t know what is.   While I agree with your conclusion, I don’t agree with the reasoning, and I expect there are others (like Milton) who would like to see the clear meaning of the language of 3.7.7.9 changed through the application of the “no regulation†sentence. <br> <br>Bradley<br> <br><b>From:</b> David Post [</span><a href="mailto:david.g.post@gmail.com"> mailto:david.g.post@gmail.com</a><span style='color:black'>] <br><b>Sent:</b> Monday, November 23, 2015 10:37 AM<br><b>To:</b> Burr, Becky<br><b>Cc:</b> Alan Greenberg; Silver, Bradley; Greg Shatan; Mueller, Milton L; Accountability Cross Community<br><b>Subject:</b> Re: [CCWG-ACCT] Board comments on the Mission statement<br> <br>At 10:03 AM 11/23/2015, Burr, Becky wrote:<br><br><br>Are we seriously arguing that RAA 3.7.7.9 is outside the picket fence? <br><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><br>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>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>Here it is in the 1999 RAA:<br>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>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><br><br>J. Beckwith Burr <br>Neustar, Inc. / Deputy General Counsel & Chief Privacy Officer<br>1775 Pennsylvania Avenue NW, Washington D.C. 20006<br>Office: +1.202.533.2932 Mobile: +1.202.352.6367 / </span><a href="http://www.neustar.biz">neustar.biz</a><span style='color:black'><br><br>From: Alan Greenberg <</span><a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a><span style='color:black'> ><br>Date: Sunday, November 22, 2015 at 10:06 PM<br>To: "Silver, Bradley" <</span><a href="mailto:Bradley.Silver@timewarner.com"> Bradley.Silver@timewarner.com</a><span style='color:black'>>, Greg Shatan <</span><a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a><span style='color:black'> >, "Mueller, Milton L" <</span><a href="mailto:milton@gatech.edu">milton@gatech.edu</a><span style='color:black'>><br>Cc: Accountability Community <</span><a href="mailto:accountability-cross-community@icann.org"> accountability-cross-community@icann.org</a><span style='color:black'>><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><br>I want to echo and support Greg’s resposposponse below. Milton’s position that an en existinting provision of the RAA is out of the scope of ICANNâ€Ã¢Ã¢„¢s mission is illuminating. sp; 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 refleflects 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: </span><a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a><span style='color:black'> [ </span><a href="mailto:accountability-cross-community-bounces@icann.org">mailto:accountability-cross-community-bounces@icann.org</a><span style='color:black'>] On Behalf Of Greg Shatan<br>Sent: Sunday, November 22, 2015 3:01 AM<br>To: Mueller, Milton L<br>Cc: Accountability Cross Community<br>Subject: 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 <</span><a href="mailto:milton@gatech.edu">milton@gatech.edu</a><span style='color:black'>> wrote:<br><br><br>> -----Original Message-----<br>><br>> See section 3.7.7 of the registrar accreditation agreement (RAA):<br>> </span><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><span style='color:black'> <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></span><a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><span style='color:black'><br></span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_accountability-2Dcross-2Dcommunity&d=CwMGaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=q0We23gB15IOvlVyCxS70PlyFWr7jiJPtk5hUAwJ4-o&s=oykS2Q8NLF_xKkxVSVRyI426vsXT3JE3oEnkpHCKpZs&e=">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><span style='color:black'><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 </span><a href="mailto:ITServices@timewarner.com">ITServices@timewarner.com</a><span style='color:black'><br><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></span><a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><span style='color:black'><br></span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_accountability-2Dcross-2Dcommunity&d=CwMGaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=q0We23gB15IOvlVyCxS70PlyFWr7jiJPtk5hUAwJ4-o&s=oykS2Q8NLF_xKkxVSVRyI426vsXT3JE3oEnkpHCKpZs&e=">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><span style='color:black'><br>_______________________________________________<br>Accountability-Cross-Community mailing list<br></span><a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><span style='color:black'><br></span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_accountability-2Dcross-2Dcommunity&d=CwMGaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=q0We23gB15IOvlVyCxS70PlyFWr7jiJPtk5hUAwJ4-o&s=oykS2Q8NLF_xKkxVSVRyI426vsXT3JE3oEnkpHCKpZs&e=">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><span style='color:black'><br><br>*******************************<br>David G Post - Senior Fellow, Open Technology Institute/New America Foundation<br>blog (Volokh Conspiracy) </span><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.washingtonpost.com_people_david-2Dpost&d=CwMGaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=q0We23gB15IOvlVyCxS70PlyFWr7jiJPtk5hUAwJ4-o&s=sFIVEVRa4d2-50iBD-equxjw7XvbBhYdWLFew_7kOTA&e=">http://www.washingtonpost.com/people/david-post<br></a><span style='color:black'>book (Jefferson's Moose) </span><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__tinyurl.com_c327w2n-25A0-25A0-25A0-25A0-25A0-25A0-25A0&d=CwMGaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=q0We23gB15IOvlVyCxS70PlyFWr7jiJPtk5hUAwJ4-o&s=ywg8uVPfTYGqvglA4unTV31GGxchC7v0aAGWrgZkGwI&e=">http://tinyurl.com/c327w2n </a><span style='color:black'><br>music </span><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__tinyurl.com_davidpostmusic-25A0&d=CwMGaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=q0We23gB15IOvlVyCxS70PlyFWr7jiJPtk5hUAwJ4-o&s=-Riw1v0au2L-2i3gFKAtEkYl56nN9CXxfpAuLQLoMGo&e=">http://tinyurl.com/davidpostmusic </a><span style='color:black'>publications etc. </span><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.davidpost.com-26nbsp-3B-26nbsp-3B-26nbsp-3B-26nbsp-3B-26nbsp-3B-26nbsp-3B-26nbsp-3B-26nbsp-3B-2520_&d=CwMGaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=q0We23gB15IOvlVyCxS70PlyFWr7jiJPtk5hUAwJ4-o&s=C0EhJhpDbLpEFEZrabNoThQ_PqYnGoH9H9Ov6mccnu8&e=">http://www.davidpost.com </a><span style='color:black'><br>******************************* <br><br>=================================================================<br><b><i>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 </i></b></span><a href="mailto:ITServices@timewarner.com"><b><i>ITServices@timewarner.com</i></b></a><b><i><span style='color:black'><br></span></i></b><span style='color:black'><br><br>=================================================================<br><br>=================================================================This message is the property of Time Warner Inc. and is intended only for the use of theaddressee(s) and may be legally privileged and/or confidential. If the reader of this messageis not the intended recipient, or the employee or agent responsible to deliver it to the intendedrecipient, he or she is hereby notified that any dissemination, distribution, printing, forwarding,or any method of copying of this information, and/or the taking of any action in reliance onthe information herein is strictly prohibited except by the intended recipient or those to whomhe or she intentionally distributes this message. If you have received this communication inerror, please immediately notify the sender, and delete the original message and any copiesfrom your computer or storage system. Thank you.================================================================= <o:p></o:p></span></p><p class=MsoNormal><span style='color:black'><br>*******************************<br>David G Post - Senior Fellow, Open Technology Institute/New America Foundation<br>blog (Volokh Conspiracy) </span><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.washingtonpost.com_people_david-2Dpost&d=CwMGaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=q0We23gB15IOvlVyCxS70PlyFWr7jiJPtk5hUAwJ4-o&s=sFIVEVRa4d2-50iBD-equxjw7XvbBhYdWLFew_7kOTA&e=">http://www.washingtonpost.com/people/david-post<br></a><span style='color:black'>book (Jefferson's Moose) </span><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__tinyurl.com_c327w2n-25A0-25A0-25A0-25A0-25A0-25A0-25A0&d=CwMGaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=q0We23gB15IOvlVyCxS70PlyFWr7jiJPtk5hUAwJ4-o&s=ywg8uVPfTYGqvglA4unTV31GGxchC7v0aAGWrgZkGwI&e=">http://tinyurl.com/c327w2n </a><span style='color:black'><br>music </span><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__tinyurl.com_davidpostmusic-25A0&d=CwMGaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=q0We23gB15IOvlVyCxS70PlyFWr7jiJPtk5hUAwJ4-o&s=-Riw1v0au2L-2i3gFKAtEkYl56nN9CXxfpAuLQLoMGo&e=">http://tinyurl.com/davidpostmusic </a><span style='color:black'>publications etc. </span><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.davidpost.com-26nbsp-3B-26nbsp-3B-26nbsp-3B-26nbsp-3B-26nbsp-3B-26nbsp-3B-26nbsp-3B-26nbsp-3B-26nbsp-3B_&d=CwMGaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=q0We23gB15IOvlVyCxS70PlyFWr7jiJPtk5hUAwJ4-o&s=lr-1bErJrSUdw4bKPYQHlyQJnyZmCN5O3BLA8oN7OPY&e=">http://www.davidpost.com </a><span style='color:black'><br>******************************* <o:p></o:p></span></p><p><span style='color:black'>=================================================================<br></span><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 </span></i></b><a href="mailto:ITServices@timewarner.com"><b><i>ITServices@timewarner.com</i></b></a><b><i><span style='color:red'> </span></i></b><span style='color:black'><o:p></o:p></span></p><p><span style='color:black'><br>=================================================================<o:p></o:p></span></p></div></div><p><span style='color:black'>=================================================================<br></span><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 </span></i></b><a href="mailto:ITServices@timewarner.com"><b><i>ITServices@timewarner.com</i></b></a><b><i><span style='color:red'> </span></i></b><span style='color:black'><o:p></o:p></span></p><p><span style='color:black'><br>=================================================================<o:p></o:p></span></p></div></div></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 </span></i></b><a href="mailto:ITServices@timewarner.com"><b><i>ITServices@timewarner.com</i></b></a><b><i><span style='color:red'> </span></i></b><o:p></o:p></p><p><br>=================================================================<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></body></html>