<div dir="ltr"><div class="gmail_extra"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">Thanks for sharing, Farzaneh, and thanks Milton for the draft.</div><div dir="ltr"><br></div><div>An earlier draft this morning had a lot of IP related examples of abuse. I guess Milton's comments and reply to Sala, and the document as it is now clarifies it. We have neither a mandate nor an adequate framework at ICANN to address content regulation. I believe we should try to find ways to push the eventual excess of IP enforcement out, and not to bring other content regulation in. I'm happy with the draft</div><div><br></div><div>Claudio</div></div></div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">2017-10-28 4:40 GMT-03:00 Mueller, Milton L <span dir="ltr"><<a href="mailto:milton@gatech.edu" target="_blank">milton@gatech.edu</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div class="m_-8613474709931599242WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Hi, Sala. Thanks for your comments.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div><span class="">
<p class="MsoNormal" style="margin-left:.5in">
In summary, noting that within ICANN, there has been debate on what constitutes domain abuse and where there are two sides of the fence where on one hand you have people advocating for taking down a domain that has any hint of misbehavior and the other side
who feel that Registries and Registrars have no responsibility towards a clean domain space.<u></u><u></u></p>
</span><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Most constituencies, registries and registrars want a clean domain space, the problem is that a lot
of the problems being dumped at ICANN’s doorstep have nothing to do with the domain name space. They are things like copyright enforcement, etc.<u></u><u></u></span></p><span class="">
<p class="MsoNormal" style="margin-left:.5in">
There have been other internet stakeholders that consider other types of domain misuse just as abusive and illegal. Some examples include intellectual property infringement, copyright, trademark violations and certain types of what people may perceive to be
objectionable content.<u></u><u></u></p>
</span><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Right, in this view almost every conceivable form of illegal activity on the internet gets thrown into
the category “domain abuse.” But that’s unclear and inaccurate. It happens because it serves the interests of IPR folks who want the DNS industry to take on the burdens of enforcing their rights. But it’s harmful to the rights of internet users and leads to
mission creep for icann. Of course, almost all forms of internet crime in some way are connected to a domain name at some point or another. But that connection does not mean that, for example, “objectionable content” is a form of domain abuse. Objectionable
content is about the content, not the domain, and action against it is a form of regulating expression, not regulating domains. ICANN is not in any position to regulate content globally, and we need to clearly separate its responsibilities from broader mandates.<u></u><u></u></span></p><span class="">
<p class="MsoNormal" style="margin-left:.5in">
In my personal opinion, abuse causes well defined harm to many organizations and individuals including Registries and Registrars. Consider the abuse of domain names to commit fraud during times of escalated crisis, where fake red cross domains soliciting donations
aside from the spam that exploits one of the Pacific ccTLDs, ".pw" and a host of other "abuse examples"<u></u><u></u></p>
</span><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Those are clear examples of how the domain itself is the problem. We need to draw a bright clean line
between that and things like “objectionable content.” <u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</div>
<br>______________________________<wbr>_________________<br>
Ncuc-discuss mailing list<br>
<a href="mailto:Ncuc-discuss@lists.ncuc.org">Ncuc-discuss@lists.ncuc.org</a><br>
<a href="https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss" rel="noreferrer" target="_blank">https://lists.ncuc.org/cgi-<wbr>bin/mailman/listinfo/ncuc-<wbr>discuss</a><br>
<br></blockquote></div><br></div></div>