<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=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
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.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Dear NCSG members:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In the next email I will send a proposed statement about domain abuse. Those of you involved with NCUC will recognize it, it has been circulated on the NCUC list and discussed extensively there.
<o:p></o:p></p>
<p class="MsoNormal">We would also like to get the endorsement of NCSG as a whole for this statement. So I send it to the NCSG list for you to review.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">--------<o:p></o:p></p>
<p class="MsoNormal">Proposed statement on domain abuse and content regulation<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:15.0pt;margin-left:0in;text-align:justify">
<span style="font-size:11.5pt;font-family:"Arial",sans-serif;color:black;background:white">As civil society stakeholders concerned about individual rights and freedom of expression on the Internet, we think it is important to maintain a clear distinction between
illegal content and domain name abuse. We wish to clarify and reaffirm ICANN’s limited mission.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:15.0pt;margin-left:0in;text-align:justify">
<span style="font-size:11.5pt;font-family:"Arial",sans-serif;color:black;background:white">Domain abuse involves cases in which the domain itself is causing problems, such as domains that facilitate fraud and exploit confusion, support phishing via confusing
or deceptive strings, or domains that support botnet command and control operations.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:15.0pt;margin-left:0in;text-align:justify">
<span style="font-size:11.5pt;font-family:"Arial",sans-serif;color:black;background:white">We are concerned that the concept of “domain abuse” is being stretched to include various forms of allegedly “illegal” or “undesirable” content on webpages, listservs
and email addresses associated with domain names. This includes the use of domain names for political speech, personal expression and competitive discussions. An overly-broad definition of “domain abuse” would require ICANN to enter the realm of decision-maker
or judge on whether the webpage was a copyright-infringement or fair use, involved legal use of a trademark to criticize a company’s products or practices or trademark infringement, and whether
</span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;background:white">hate speech, whose definition and legal status varies from country to country, was legitimate or not.
</span><span style="font-size:11.5pt;font-family:"Arial",sans-serif;color:black;background:white"> </span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:15.0pt;margin-left:0in;text-align:justify">
<span style="font-size:11.5pt;font-family:"Arial",sans-serif;color:black;background:white">We believe that content that is allegedly illegal or objectionable is not “domain abuse” and is best addressed through other, well-established legal and regulatory methods,
or through cooperative and self-regulatory action by Internet service providers. Neither ICANN nor its contracted parties should try to make DNS policy become the nexus for global content regulation.
</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:15.0pt;margin-left:0in;text-align:justify">
<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black;background:white">We remind all participants that
</span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black">ICANN’s mission, as defined in Section 1.1.(a)(i) of its bylaws, is narrowly confined to policies “for which uniform or coordinated resolution is reasonably necessary to facilitate
the openness, interoperability, resilience, security and/or stability of the DNS.” That clearly does not include content regulation. Moreover, the bylaws contain a specific prohibition on regulating “s</span><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#333333;background:white">ervices
that use the Internet's unique identifiers or the content that such services carry or provide, outside the express scope of
<u>Section 1.1(a)</u>.”</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:15.0pt;margin-left:0in;text-align:justify">
<span style="font-size:11.5pt;font-family:"Arial",sans-serif;color:black;background:white">Expansion of ICANN’s mission into content regulation will further politicize ICANN, and overload DNS policy with extraneous concerns that threaten the openness and interoperability
of the DNS.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:15.0pt;margin-left:0in;text-align:justify">
<span style="font-size:11.5pt;font-family:"Arial",sans-serif;color:black;background:white">Accordingly, we call upon the ICANN board and all ICANN policy processes to adopt a precise and narrow definition of domain abuse, one that is consistent with ICANN’s
limited mission. </span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Dr. Milton L. Mueller<o:p></o:p></p>
<p class="MsoNormal">Professor, School of Public Policy<o:p></o:p></p>
<p class="MsoNormal">Georgia Institute of Technology<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>