<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: 14px; font-family: Calibri, sans-serif;">
<div>
<div>
<div>Steve,with regard to #1 and #2: separation or backup provider seem to me to be in the „really, really last resort options” range, as indicated earlier with the term „nuclear option”. As I said before, executing a nuclear option has, as far as I know, never
led to an improvement of the existing bad situation.</div>
<div><br>
</div>
<div>So I wonder why your stress tests directly jump to these options, as a failure of (part of) the IANA function should „normally" be fixable by (depending on the cause of the failure) rolling in new hardware, replacing IANA staff (e.g. ad interim by cc and/or
g registry staff), replacing ICANN staff and/or replacing the ICANN Board (or part thereof). </div>
<div><br>
</div>
<div>I can think of no situation in which the use of one, some or all the new powers we propose will not fix the malfunctioning of IANA</div>
<div>
<div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri"><br>
</font></font></div>
<div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri">Best,</font></font></div>
<div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri"><br>
</font></font></div>
<div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri">Roelof</font></font></div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Steve DelBianco <<a href="mailto:sdelbianco@netchoice.org">sdelbianco@netchoice.org</a>><br>
<span style="font-weight:bold">Date: </span>dinsdag 3 maart 2015 03:36<br>
<span style="font-weight:bold">To: </span>Accountability Cross Community <<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>><br>
<span style="font-weight:bold">Cc: </span>ACCT-Staff <<a href="mailto:acct-staff@icann.org">acct-staff@icann.org</a>>, "<a href="mailto:ccwg-accountability4@icann.org">ccwg-accountability4@icann.org</a>" <<a href="mailto:ccwg-accountability4@icann.org">ccwg-accountability4@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>[CCWG-ACCT] Additional Stress Tests to discuss<br>
</div>
<div><br>
</div>
<div>
<div 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>
<div>For tomorrow’s call, we applied 4 more of our stress tests against the draft package of proposed accountability measures. </div>
</div>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<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;">
Stress Tests #1 and 2 (together), #24, and #15, are shown below and in the attached draft 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: 0px 0px 0px 40px; border: none; padding: 0px;">
<div><span style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">#</span><font face="Calibri,sans-serif">1. Change authority for the IANA Root Zone ceases to function, in part or in whole. </font></div>
<div><span style="font-family: Calibri, sans-serif;">#2. Delegation authority for the IANA Root Zone ceases to function, in part or in whole.</span></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">Consequence: interference with existing policy relating to IANA Root Zone and/or prejudice to the security and stability of one or several TLDs.</font></div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
</blockquote>
<div>
<div id="">
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<font face="Calibri,sans-serif"><b>Existing Accountability Measures:</b></font></div>
<div><font face="Calibri,sans-serif">
<blockquote style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<div>
<div>Under the present IANA contract, NTIA can revoke ICANN’s authority to perform IANA functions and re-assign to different entity/entities. </div>
<div><br>
</div>
<div>After NTIA relinquishes the IANA contract, this measure will no longer be available.</div>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
</blockquote>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<b>Proposed Accountability Measures:</b></div>
</font></div>
<div><font face="Calibri,sans-serif">
<blockquote style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<div>
<div>The CWG planning the IANA stewardship transition might design mechanisms and structures that enable separation, such that the IANA functions could be readily revoked and re-assigned.</div>
<div><br>
</div>
<div>To manage the revocation of IANA functions, the CWG might also propose an emergency backup provider and procedures, pending re-assignment of the IANA functions.</div>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
</blockquote>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<b>Preliminary Conclusions:</b></div>
<blockquote style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px; margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<div>This threat is directly related to the transition of IANA stewardship</div>
<div><br>
</div>
<div>Existing measures would be inadequate after NTIA terminates the IANA contract.</div>
<div><br>
</div>
<div>At this point, CWG’s recommendations are still in development.</div>
</blockquote>
<div>
<div>———————————————————</div>
</div>
<div><br>
</div>
</font></div>
</div>
</div>
</div>
</div>
</span>
<div>
<div style="font-size: 16px; font-family: Calibri, sans-serif;"><b>Stress Test:</b></div>
<blockquote style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<div><span style="font-family: Calibri, sans-serif; font-size: 16px;">#24</span><font face="Calibri,sans-serif">. </font><font face="Calibri,sans-serif">An incoming Chief Executive institutes a “strategic review” that arrives at a new, extended mission for
ICANN. The Board, having just hired the new CEO, approves the new mission and strategy without community consensus.</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">Consequence: Community ceases to see ICANN as the community’s own mechanism for discharging limited technical functions, and views ICANN as an independent, sui generis entity with its own agenda, not necessarily supported
by the community. Ultimately, community questions why ICANN’s original functions should remain controlled by a body that has acquired a much broader and less widely supported mission.</font></div>
<div><br>
</div>
</blockquote>
<div>
<div id="">
<div style="font-family: Calibri, sans-serif; font-size: 16px;"><font face="Calibri,sans-serif"><b>Existing Accountability Measures:</b></font></div>
<div><font face="Calibri,sans-serif">
<blockquote style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<div>
<div>As long as NTIA controls the IANA contract, ICANN could risk losing IANA functions if it were to expand scope too broadly. </div>
<div><br>
</div>
<div>The Community has some input in ICANN budgeting and Strat Plan, and could register objections to plans and spending on extending ICANN’s mission.</div>
<div><br>
</div>
<div>California’s Attorney General has jurisdiction over non-profit entities acting outside Bylaws or Articles of Incorporation.</div>
</div>
<div><br>
</div>
</blockquote>
<div style="font-size: 16px;"><b>Proposed Accountability Measures:</b></div>
</font></div>
<div><font face="Calibri,sans-serif">
<blockquote style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<div>
<div>
<div>One proposed measure is empowering the community to veto ICANN’s proposed annual budget. This measure could block a proposal by ICANN to increase its expenditure on extending its mission beyond what the community supported.</div>
<div><br>
</div>
<div>If the ICANN board voted to approve the CEO’s plans, one proposed measure would give the community standing to veto a board decision.</div>
<div><br>
</div>
<div>Another proposed measure is empowering the community to challenge a board decision, referring it to an Independent Review Panel (IRP) with the power to issue a binding decision. [What would be the standard used for this review?]</div>
</div>
</div>
<div><br>
</div>
</blockquote>
<div style="font-size: 16px;"><b>Preliminary Conclusions:</b></div>
<blockquote style="font-size: 16px; margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<div>This threat is directly related to the transition of IANA stewardship</div>
<div><br>
</div>
<div>Existing measures would be inadequate after NTIA terminates the IANA contract.</div>
<div><br>
</div>
<div>Proposed measures in combination are adequate.</div>
</blockquote>
<div>———————————————————</div>
<div><b style="font-size: 16px;"><br>
</b></div>
<div><b style="font-size: 16px;">Stress Test:</b></div>
<div>
<blockquote style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<div><span style="font-size: 16px;">#15</span><font face="Calibri,sans-serif">. </font>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. </div>
<div><br>
</div>
<div>Consequence: affected parties could be prevented from seeking legal redress for commissions or omissions by ICANN.</div>
<div><br>
</div>
</blockquote>
<div>
<div id="">
<div style="font-size: 16px;"><font face="Calibri,sans-serif"><b>Existing Accountability Measures:</b></font></div>
<div><font face="Calibri,sans-serif">
<blockquote style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<div>As long as NTIA controls the IANA contract, ICANN could risk losing IANA functions if it were to move in order to avoid legal jurisdiction. </div>
<div><br>
</div>
<div>Paragraph 8 of the AoC requires ICANN to remain headquartered in the US, but the AoC can be terminated by ICANN at any time. As long as NTIA controls the IANA contract, ICANN feels pressure to maintain the AoC.</div>
<div><br>
</div>
</blockquote>
<div style="font-size: 16px;"><b>Proposed Accountability Measures:</b></div>
</font></div>
<div><font face="Calibri,sans-serif">
<blockquote style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<div>
<div>
<div>One proposed measure is to give the community standing to veto a board decision. If ICANN board voted to vacate a legal presence, the community veto could enable reversal of that decision.</div>
<div><br>
</div>
<div>One proposed measure is to import AoC provisions into the ICANN bylaws, and dispense with the bilateral AoC with NTIA. Bylaws would be amended to include AoC commitments 8, requiring it to maintain legal presence in the US, where it is subject to legal
redress by any aggrieved party.</div>
<div><br>
</div>
<div>If ICANN’s board proposed to amend the AoC provisions added to the bylaws, another proposed measure would empower the community to veto that proposed bylaws change.</div>
</div>
</div>
<div><br>
</div>
</blockquote>
<div style="font-size: 16px;"><b>Preliminary Conclusions:</b></div>
<blockquote style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<div style="font-size: 16px;">This threat is directly related to the transition of IANA stewardship</div>
<div style="font-size: 16px;"><br>
</div>
<div style="font-size: 16px;">Existing measures would be inadequate after NTIA terminates the IANA contract.</div>
<div style="font-size: 16px;"><br>
</div>
<div>Proposed measures improve upon existing measures, and may be adequate.</div>
<div><br>
</div>
<div><br>
</div>
</blockquote>
</font></div>
</div>
</div>
</div>
</font></div>
</div>
</div>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<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></div>
</span></div>
</div>
</span>
</body>
</html>