<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 16px; font-family: Calibri, sans-serif;">
<div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
Per a request from Adam Peake, we applied another of our stress tests against the draft package of proposed accountability measures. </div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
This is for stress test #17, shown below and on page 2 of the attached document. </div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<b>Stress Test:</b></div>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
#17. ICANN attempts to add a new top-level domain in spite of security and stability concerns expressed by technical community or other stakeholder groups. </div>
</blockquote>
<div>
<div id="">
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div id=""><span style="font-family: Calibri, sans-serif;">Consequence: DNS security and stability could be undermined, and ICANN actions could impose costs and risks upon external parties.</span></div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
</blockquote>
<div><font face="Calibri,sans-serif"><b>Existing Accountability Measures:</b></font></div>
<div><font face="Calibri,sans-serif">
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div>In 2013-14 the community demonstrated that it could eventually prod ICANN management to attend to risks identified by SSAC (security certificates and name collisions such as .mail, .home, etc.).</div>
<div><br>
</div>
<div>NTIA presently gives clerical approval for each delegation to indicate that ICANN has followed its processes. NTIA could delay a delegation if its finds that ICANN has not followed its processes. Not clear if that would/could have been a finding if ICANN
attempted to delegate a new TLD such as .mail or .home</div>
<div><br>
</div>
</blockquote>
<div><b>CCWG Proposed Accountability Measures:</b></div>
</font></div>
<div><font face="Calibri,sans-serif">
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div>One proposed measure is to empower the community to force ICANN’s board to implement a recommendation arising from an AoC Review – namely, 9.2 Review of Security, Stability, and Resiliency.</div>
<div><br>
</div>
<div>Another possibility is to empower the community to force ICANN to respond to recommendations from advisory committees like as SSAC. </div>
<div><br>
</div>
<div>If the board took a decision to reject or only partially accept SSAC recommendations, the community could be empowered to challenge that board decision and/or refer to IRP.</div>
<div><br>
</div>
</blockquote>
<div><b>Preliminary Conclusions:</b></div>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div>This threat is partially related to the transition of IANA stewardship</div>
<div><br>
</div>
<div>Existing measures were adequate to mitigate the risks of this scenario.</div>
<div><br>
</div>
<div>Proposed measures enhance community’s power to mitigate the risks of this scenario.</div>
<div><br>
</div>
</blockquote>
</font></div>
</div>
</div>
</div>
<span id="OLK_SRC_BODY_SECTION" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div class="">
<div apple-content-edited="true" class="">
<div class=""></div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>