<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;">
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<div>Just a quick update on work in the ICANN Accountability Working Group (CCWG).</div>
</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 week, CCWG member Eric Brunner-Williams circulated draft scenarios to help design and evaluate accountability mechanisms.</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;">
Earlier, I had circulated the ten BC <a href="http://bizconst.org/stresstests">stress tests</a> as a starting point for scenarios. But Eric included only 3 of our stress tests in his list. </div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</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; color: rgb(0, 0, 0); font-size: 16px; font-family: Calibri, sans-serif;">
<div>
<div>So today I added the missing scenarios from what the BC submitted in in May-2014. See my attached markup, or list below, where numbers 14-21 are the ones I added.</div>
</div>
</div>
</div>
</span>
<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;">
If you have other ideas for stress tests, please pass them along soon.</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;">
—Steve</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<div>
<div><font face="Calibri,sans-serif">Scenarios for the CCWG to consider:</font></div>
<div><font face="Calibri,sans-serif">1.<span class="Apple-tab-span" style="white-space:pre">
</span>Change authority for the IANA Root Zone ceases to function, in part or in whole.</font></div>
<div><font face="Calibri,sans-serif">Consequence: significant interference with existing policy (or policies) relating to the content of the IANA Root Zone and/or prejudice to the security and stability of one or several TLDs.</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">2.<span class="Apple-tab-span" style="white-space:pre">
</span>Delegation authority for the IANA Root Zone ceases to function, in part or in whole. </font></div>
<div><font face="Calibri,sans-serif">Consequence: significant interference with existing policy (or policies) relating to the delegation from the IANA Root Zone and/or prejudice to the security and stability of one or several TLDs.</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">3.<span class="Apple-tab-span" style="white-space:pre">
</span>Litigation arising from existing public policy, e.g., Anti-Trust (Sherman Act, et. seq.).</font></div>
<div><font face="Calibri,sans-serif">Consequence: significant interference with existing policy (or policies) and/or policy development relating to one or more relevant activities.</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">4.<span class="Apple-tab-span" style="white-space:pre">
</span>New regulation or legislation (see above).</font></div>
<div><span style="font-family: Calibri, sans-serif;">Consequence: significant interference with existing policy (or policies) and/or policy development relating to one or more relevant activities.</span></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">5.<span class="Apple-tab-span" style="white-space:pre">
</span>Domain industry financial crisis.</font></div>
<div><font face="Calibri,sans-serif"> Consequence: significant reduction in domain sales generated revenues and significant increase in registrar and registry continuity costs, threatening Icann’s ability to continue operating.</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">6.<span class="Apple-tab-span" style="white-space:pre">
</span>General financial crisis.</font></div>
<div><font face="Calibri,sans-serif">Consequence: loss affecting reserves sufficient to threaten business continuity .</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">7.<span class="Apple-tab-span" style="white-space:pre">
</span>Litigation arising from private contract, e.g., Breach of Contract.</font></div>
<div><font face="Calibri,sans-serif"> Consequence: significant loss of contracted party fees. </font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">8.<span class="Apple-tab-span" style="white-space:pre">
</span>Technology competing with DNS</font></div>
<div><font face="Calibri,sans-serif">Consequence: significant reduction in domain sales generated revenues and significant increase in registrar and registry continuity costs.</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">9.<span class="Apple-tab-span" style="white-space:pre">
</span>Major corruption of fraud</font></div>
<div><font face="Calibri,sans-serif">Consequence: major impact on corporate reputation, significant litigation and loss of some or all reserves</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">10.<span class="Apple-tab-span" style="white-space:pre">
</span>Chairman, CEO or major officer acting in a manner inconsistent with the organization’s mission.</font></div>
<div><font face="Calibri,sans-serif">Consequence: major impact on corporate reputation, significant litigation.</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">11.<span class="Apple-tab-span" style="white-space:pre">
</span>Compromise of credentials.</font></div>
<div><font face="Calibri,sans-serif">Consequence: major impact on corporate reputation, significant loss of authentication and/or authorization capacities.</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">12.<span class="Apple-tab-span" style="white-space:pre">
</span>Capture by one or several groups of stakeholders</font></div>
<div><font face="Calibri,sans-serif">Consequence : major impact on trust in multistakeholder model, prejudice to other stakeholders</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">13.<span class="Apple-tab-span" style="white-space:pre">
</span>One or several stakeholders excessively rely on accountability mechanism to “paralyze” Icann</font></div>
<div><font face="Calibri,sans-serif">Consequence : major impact on corporate reputation, inability to take decisions, instability of governance bodies, loss of key staff, …</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">14. ICANN or NTIA choose to terminate the Affirmation of Commitments. </font></div>
<div><font face="Calibri,sans-serif">Consequence: ICANN would no longer be held to its Affirmation commitments, including the conduct of community reviews and required implementation of review team recommendations. This consequence could be avoided if Affirmation
reviews and commitments are added to ICANN’s bylaws.</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">15. ICANN terminates its legal presence in a nation where Internet users or domain registrants are seeking legal remedies for ICANN’s failure to enforce contracts, or other actions.</font></div>
<div><font face="Calibri,sans-serif">Consequence: affected parties could be prevented from seeking legal redress for commissions or omissions by ICANN.</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">16. ICANN uses fee revenue or reserve funds to expand its scope beyond its technical mission, through grants for developing nations or other causes. </font></div>
<div><font face="Calibri,sans-serif">Consequence: ICANN has the power to determine fees charged to TLD applicants, registries, registrars, and registrants, so it presents a large target for any Internet-related cause seeking funding sources.</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">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. </font></div>
<div><font face="Calibri,sans-serif">Consequence: DNS security and stability could be undermined, and ICANN actions could impose costs and risks upon external parties. </font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">18. Governments in ICANN’s Government Advisory Committee (GAC) amend their operating procedures to change from consensus decisions to majority voting for approving advice to ICANN’s board.</font></div>
<div><font face="Calibri,sans-serif">Consequence: Under current bylaws, ICANN must consider and respond to GAC advice, even if that advice were not supported by consensus. A majority of governments could thereby approve GAC advice that restricted free online
expression, for example.</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">19. ICANN attempts to re-delegate a gTLD because the registry operator is determined to be in breach of its contract, but the registry operator challenges the action and obtains an injunction from a national court.</font></div>
<div><font face="Calibri,sans-serif">Consequence: The entity charged with root zone maintenance could face the question of whether to follow ICANN re-delegation request or to follow the court order.</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">20. A court order is issued to block ICANN’s delegation of a new TLD, because of complaint by existing TLD operators or other aggrieved parties.</font></div>
<div><font face="Calibri,sans-serif">Consequence: ICANN’s decision about whether to honor such a court order could bring liability to ICANN and its contract parties.</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">21. A government telecom minister instructs ICANN to re-delegate a country-code top-level domain (ccTLD), despite objections from many current registrants and user communities in the country concerned. </font></div>
<div><font face="Calibri,sans-serif">Consequence: Faced with this re-delegation request, ICANN lacks measures to resist re-delegation while awaiting the bottom-up consensus decision of affected stakeholders. </font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><br>
</div>
</div>
</body>
</html>