<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>
<!-- Template generated by Exclaimer Mail Disclaimers on 02:47:32 Friday, 19 February 2016 -->
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css">P.90ee7c49-625a-40f7-a446-19f7d81ef5de {
MARGIN: 0cm 0cm 0pt
}
LI.90ee7c49-625a-40f7-a446-19f7d81ef5de {
MARGIN: 0cm 0cm 0pt
}
DIV.90ee7c49-625a-40f7-a446-19f7d81ef5de {
MARGIN: 0cm 0cm 0pt
}
TABLE.90ee7c49-625a-40f7-a446-19f7d81ef5deTable {
MARGIN: 0cm 0cm 0pt
}
DIV.Section1 {
page: Section1
}
</style>
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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="blue" vlink="purple">
<p class="90ee7c49-625a-40f7-a446-19f7d81ef5de"></p>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Steve,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">First, like Phil and Alan, I found your e-mail confusing. You seem to suggest a WS2 item to consider “how advice from ALL parties is appropriately considered
within ICANN” at one point. But it could also read as a proposal to kick the matter of thresholds and the GAC carve-out to WS2. I don’t see how the CCWG-Accountability proposal could be seriously taken as a final product as that would leave fundamental aspects
of ICANN governance unresolved. Samantha Eisner later clarified that your position was just a reiteration of Bruce’s proposal earlier this week.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I will note that there is one option that would resolve this issue far more simply: if the GAC’s privileged advisory power were eliminated, we would no longer
need the GAC carve-out. If we are opening this discussion up again, perhaps we should revisit that. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Second, I view with skepticism your statement that this is “not about Board removal, but about maintaining the balanced multistakeholder model.” Funny, but
I don’t recall that point being made by Bruce when he initially voiced the Board’s concerns about the GAC carve-out. Those discussions centered entirely around the threshold for recalling the Board under the GAC carve-out.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Samantha Eisner’s e-mail also casts doubt on the statement. She confirmed that the Board is fine with the GAC carve-out language except for the 3 SOAC threshold
to remove the Board.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">It is hard not to see your e-mail as: (1) a self-interested effort to capitalize on the current time-crunch to pressure the CCWG to accede to the Board’s demands;
(2) a kowtow to the 10-12 governments raising an objections on this matter, while ignoring countervailing objections from non-government participants; or (3) using the minority GAC objection as an excuse to excise the GAC carve-out to address your initial
concern indirectly. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I don’t know which is accurate, but none reflect well on the Board. In particular, the Board’s statement following so closely on the heels of objections raised
by a handful of governments and should ring alarm bells in NTIA and Congress about ICANN’s ability to resist government influence post-transition and illustrates why the GAC carve-out was proposed in the first place. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Finally, the Board’s repeated tendency to insert itself at the 11<sup>th</sup> hour has cost all of us countless hours of time and effort by forcing us to reargue
painful compromises and, in my view, violates the Board’s commitment to send the transition proposals forward as drafted “promptly and without modification” even if it contains provisions that the Board opposes.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">The experiences over the past week only solidifies my conviction that the EC must to retain reasonable ability – not requiring unanimous support among the decisional
participants – to recall the Board both for decisions that violate ICANN Bylaws and Articles and for other matters.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Brett<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div></div>
</div>
<p></p>
<p class="90ee7c49-625a-40f7-a446-19f7d81ef5de"></p>
<hr align="left" color="#58595b" width="200">
<span style="font-size:x-small; color: #004B8D; font-weight: bold; ">Brett</span><span style="font-size:x-small; color: #004B8D; font-weight: bold; "></span>
<span style="font-size:x-small; color: #004B8D; font-weight: bold; ">Schaefer</span><span style="font-size:x-small; color: #58595B; font-weight: normal; font-style: italic; "><br>
Jay Kingham Senior Research Fellow in International Regulatory Affairs</span><span style="font-size:x-small; color: #58595B; font-weight: normal; font-style: italic; "></span><span style="font-size:x-small; color: #58595B; font-weight: normal; font-style: italic; "><br>
Margaret Thatcher Center for Freedom Davis Institute for National Security and Foreign Policy</span><br>
<font color="#58595b" size="2">The Heritage Foundation<br>
214 Massachusetts Avenue, NE<br>
Washington, DC 20002</font><span style="font-size:x-small; color: #58595B; "><br>
202-608-6097</span><br>
<font color="#004b8d" size="2"><a style="COLOR: #004b8d; TEXT-DECORATION: none" href="http://heritage.org/">heritage.org</a><br>
<span style="font-size:x-small; "></span><span style="font-size:x-small; "></span>
<p></p>
</font>
<p></p>
<div class="WordSection1">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> accountability-cross-community-bounces@icann.org [mailto:accountability-cross-community-bounces@icann.org]
<b>On Behalf Of </b>Steve Crocker<br>
<b>Sent:</b> Friday, February 19, 2016 11:28 AM<br>
<b>To:</b> Mathieu Weill; León Felipe Sánchez Ambía; Thomas Rickert<br>
<b>Cc:</b> Steve Crocker; Icann-board ICANN; Accountability Community<br>
<b>Subject:</b> [CCWG-ACCT] Board position re the GAC carve out<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">CCWG Colleagues,<br>
<br>
The Board has a serious and continued concern about the issues being raised that may result in the reduction of the GAC’s ability to participate in community decision making. This is most noticeable in the question of thresholds for board removal, however this
is not an issue about removal or even thresholds, it is one part of the community being (or perceiving that it is being) sidelined. The Board’s concerns with this issue are not about Board removal, but about maintaining the balanced multistakeholder model.
<br>
<br>
The Board is against any changes to the long established equilibrium and fairness among the different stakeholders within ICANN. The Board has long supported a threshold of four participants for Board removal in the ultimate escalation method proposed by the
CCWG. Selecting one portion of the ICANN community and removing them from the equation - just through the ability to say that the community is unhappy with the acceptance of GAC advice that is within ICANN’s bylaws - raises significant concerns about how the
multistakeholder model, and the ultimate stability of ICANN as an organization, can be maintained. This carved out exception undercuts the established role of governments within the multi stakeholder process, and could introduce new issues with the acceptance
of ICANN’s model undermining the work of the CCWG. <br>
<br>
We understand that there are concerns with this path from within other parts of ICANN community, including members of the GAC and ALAC. The best course, in our opinion, would be a careful and objective discussion of the whole matter of how advice from ALL parties
is appropriately considered within ICANN. If there is a graceful way to remove this matter from the immediate pressure of the deadline of submitting this proposal and make it a priority matter for either the implementation phase or Work Stream 2, we think
there will be a solution which is genuinely good for everyone.<br>
<br>
We encourage you to share the CCWG’s proposal with the Chartering Organizations while the dialog on this outstanding point continues.<br>
<br>
Thank you,<br>
<br>
Steve Crocker<br>
Chair, ICANN Board of Directors<br>
<br>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><o:p></o:p></p>
</div>
<p></p>
</body>
</html>