<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=Windows-1252">
<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;}
@font-face
{font-family:"Times New Roman \(Body CS\)";
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
p.qt-msolistparagraph1, li.qt-msolistparagraph1, div.qt-msolistparagraph1
{mso-style-name:qt-msolistparagraph1;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
span.size
{mso-style-name:size;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:12.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:712967094;
mso-list-template-ids:499939958;}
@list l0:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
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="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="qt-msolistparagraph1" style="margin-left:0in"><span class="size"><span style="font-size:11.0pt">The ICANN Business Constituency (BC) supports ICANN Org’s Recommendations for Early Warning for Root Zone Scaling.<o:p></o:p></span></span></p>
<p class="qt-msolistparagraph1" style="margin-left:0in"><span class="size"><span style="font-size:11.0pt"><o:p> </o:p></span></span></p>
<p class="qt-msolistparagraph1" style="margin-left:0in"><span class="size"><span style="font-size:11.0pt">We agree that periodic discussion, initially triggered by rate thresholds and then falling back to a recurring calendar event, is the best way to monitor
the root as it scales.<o:p></o:p></span></span></p>
<p class="qt-msolistparagraph1" style="margin-left:0in"><o:p> </o:p></p>
<p class="MsoNormal">The BC remains concerned with the acute issue of DNS abuse, which was listed among concerns that motivate these recommendations, “Anti-abuse communities and law enforcement agencies could have trouble dealing with a greatly increased number
of new gTLDs”.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">History shows that TLD expansion, in cases involving stunningly lax registry operators, brought an increase in the prevalence of DNS abuse. The BC has learned this is primarily attributable to: intentionally inexpensive registration pricing;
lack of registry self-policing; and ineffectual enforcement of registry contract language by ICANN Compliance.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">ICANN Org now is in a position to take pre-emptive action against DNS abuse. First, ICANN Org should assertively enforce its registry agreement language. Should Compliance find that contract language is ineffectual, such language should
be strengthened as a part of new agreements (and eventually applied retroactively to current registry operators). Further, ICANN Org should consider incorporating abuse mitigation measures (on its own part and on the part of registry operators) as a prerequisite
to or an element of new gTLD applications.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">On the more narrow issue of rate-limiting, ICANN Org should monitor for DNS abuse as an element of any new gTLD rollout. It should do so not
<i>only</i> by monitoring third-party data providers, but also by mandated, frequent and enforceable self-reporting mechanisms from registry operators, and by its own monitoring by the Office of the CTO. These measures would be welcomed by the BC and the broader
community as a demonstration that ICANN is taking abuse mitigation seriously and is committed to namespaces that are as free from abuse as possible.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">--<o:p></o:p></p>
<p class="MsoNormal">This comment was drafted by Mark Svancarek, Mason Cole, and Waudo Siganga.<o:p></o:p></p>
<p class="MsoNormal">It was approved in accord with the BC Charter.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
</div>
</body>
</html>