<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=utf-8">
<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;}
/* 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">
<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"> You are doing yeoman’s work trying to advance the work! However, I think the current situation (the significant “evolution” of the ICANN Board’s
role in the development of this proposal) is a strong indicator of why relying on an internal process to ensure a change to a membership model may not be viable.<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 current environment we find ourselves in was certainly foresaw. In their Joint Comments from SO-AC-SG-C Leaders towards the development of the process, the
Joint Commenter’s stated: “</span><i><span style="font-size:10.0pt">We believe that in the context of the Accountability Process this fiduciary duty creates the possibility of tension between the interests of the ICANN Board and those of the ICANN community.
New or strengthened accountability mechanisms may impose new requirements upon ICANN as an organization. These requirements may be deemed cumbersome, restrictive, or otherwise undesirable by representatives of the organization. In these circumstances, the
ICANN Board could find the organization’s interests at odds with those of the community and be led to reject such recommendations</span></i>.<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>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Accordingly the final charter articulated a process (and limit) for Board interaction: “</span><i><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#333333">CCWG-Accountability
will include a liaison from the ICANN Board, who would be an active member of the CCWG-Accountability, bringing the voice of the Board and Board experience to activities and deliberations. The CCWG-Accountability will also include an ICANN Staff representative
to provide input into the deliberations and who is able to participate in this effort in the same way as other members of the CCWG-Accountability. Should there be a need for any consensus call(s),
<span style="background:yellow;mso-highlight:yellow">neither the Board liaison nor the Staff representative would participate in such a consensus call</span></span></i><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#333333">.</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">”(my
highlighting)<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">Moreover, the Board’s own resolution on their “interaction” contained the threshold you’ve copied in your proposal. “</span><em><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#333333">If
the Board believes it is not in the global public interest to implement a recommendation from the Cross Community Working Group on Enhancing ICANN Accountability and Governance (CCWG Recommendation), it must initiate a dialogue with the CCWG. A determination
that it is not in the global public interest to implement a CCWG Recommendation requires a 2/3 majority of the Board</span></em><em><span style="font-size:10.5pt;font-family:"Arial",sans-serif;color:#333333">.</span></em><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>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">However we now have apparently reached a point, as stated by Steve Crocker in the Sept 2 meeting where: “</span><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">NTIA
has made it very clear that they do not want a proposal from the community in which the
<span style="background:yellow;mso-highlight:yellow">board has not reached consensus on</span> as well</span></i><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>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">We have moved from a documented position (identical to what you’re proposing) requiring a 2/3rds rejection of a proposal on a strict finding of “</span><em><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#333333">not
in the global public interest</span></em><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">”, to where apparently now the proposal has to be developed in consensus with the board, ex anti, even before its submission to the SO/ACs.
And this “evolution” has happened in the presence of the strongest external pressure that is likely to exist for quite a while.<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">So it is hard to imagine how, in the absence of the IANA Transition stick, the old “2/3rds majority- it’s not in the global interest” requirement will actually
be complied with. <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">Mike<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"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></a></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> accountability-cross-community-bounces@icann.org [mailto:accountability-cross-community-bounces@icann.org]
<b>On Behalf Of </b>Steve DelBianco<br>
<b>Sent:</b> Thursday, October 8, 2015 12:26 PM<br>
<b>To:</b> Kieren McCarthy; Accountability Cross Community<br>
<b>Subject:</b> Re: [CCWG-ACCT] A path to Dublin and beyond<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">Kieren — as to your first question, I do assume the board would likely resist an attempt to activate the enforcemnet powers of Membership. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">As to your second question, see the Plan B text I proposed last weekend (below) If it’s not strong enuogh please suggest ways to improve it! <o:p></o:p></span></p>
</div>
<div>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">But there’s one more we have to add before losing the leverage of this IANA transition:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">Let’s put into ICANN bylaws a method where the community can show consensus to undertake a review of ICANN's governance structure, either because the powers above aren’t working,
or just because the community overwhelmingly wants to review governance. The goal of the Governance Review is to recommend a new governance model that might even include moving to Membership. To Bruce’s point, any proposal emerging from this Governance
Review would include assurances that ACs and SOs are representative of global internet users and protected from capture. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">This same bylaw could describe a process for board acceptance of a consensus proposal emerging from the Governance Review: it would take 2/3 board majority to object to the proposal
on the grounds that it is not in the global public interest, triggering a board-community consultation. After consultation, a new community proposal would take 3/4 board majority to object. If the board objected a second time, we would have the power to
recall that entire board, or to pursue binding arbitration. <o:p></o:p></span></p>
</div>
</blockquote>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:"Calibri",sans-serif;color:black">From:
</span></b><span style="font-family:"Calibri",sans-serif;color:black">Kieren McCarthy<br>
<b>Date: </b>Thursday, October 8, 2015 at 12:08 PM<br>
<b>To: </b>Accountability Cross Community, Steve DelBianco<br>
<b>Subject: </b>Re: [CCWG-ACCT] A path to Dublin and beyond<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">Serious question: why would you imagine that the Board would do anything but block future governance changes given what it has done this time and in numerous previous accountability
reviews?<br>
<br>
And related to that: if the Board blocked it, what mechanism would exist to force the changes? Why would we not end up in the exact same possible as now but five years down the road?<br>
<br>
<br>
Kieren<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">On Sat, Oct 3, 2015 at 1:33 PM Steve DelBianco <<a href="mailto:sdelbianco@netchoice.org">sdelbianco@netchoice.org</a>> wrote:<o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">Here are my own thoughts on a path to Dublin and beyond. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">I was thinking about Jonathan Zuck’s suggestion (<a href="http://mm.icann.org/pipermail/accountability-cross-community/2015-September/005764.html" target="_blank">link</a>) that
a change to Membership model could be done in Work Stream 2 — if we create lasting leverage for community to enact a change despite board resistance. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">Then I read Bruce Tonkin's recent post (<a href="http://mm.icann.org/pipermail/accountability-cross-community/2015-October/006098.html" target="_blank">link</a>) describing why
our present AC/SO participation falls short of representing the global M-S community, and suggesting this is why the board might not approve a move to Membership at this time. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">Their posts, along with responses on list, suggest a way we can deliver by Dublin on enforceable accountability enhancements, thereby giving us powers to impose reforms to the AC/SO
model after the IANA transition. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">Consider this:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">Let’s use the leverage of the IANA transition to get bylaws changes give the current AC/SO community the powers we require, with adequate enforceability. Plus, we ensure those
powers are enough to force a future change to ICANN governance structure and/or Membership, if the community comes to consensus around what that new ICANN governance structure look like. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">That would mean we focus CCWG on finishing details and bylaws language for these enforceable powers exercised by supermajority of ACs and SOs:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">1. Power to block a proposed Operating Plan/Strat Plan/Budget<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">2. Power to approve changes to Fundamental Bylaws and Articles of Incorporation<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">3. Power to block changes to regular bylaws.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">4. Power to appoint and remove individual board directors<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">5. Power to recall the entire board of directors<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">6. Mechanism for binding IRP where a panel decision is enforceable in any court recognizing international arbitration results — even if ICANN’s board refused to participate in the
binding arbitration. (assuming CCWG lawyers verify this works without activating a Membership model)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">I think we are close enough to get consensus around the above powers before we leave Dublin. And based on what we’ve heard recently, the board will support the powers described
above. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">But there’s one more we have to add before losing the leverage of this IANA transition:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">Let’s put into ICANN bylaws a method where the community can show consensus to undertake a review of ICANN's governance structure, either because the powers above aren’t working,
or just because the community overwhelmingly wants to review governance. The goal of the Governance Review is to recommend a new governance model that might even include moving to Membership. To Bruce’s point, any proposal emerging from this Governance
Review would include assurances that ACs and SOs are representative of global internet users and protected from capture. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">This same bylaw could describe a process for board acceptance of a consensus proposal emerging from the Governance Review: it would take 2/3 board majority to object to the proposal
on the grounds that it is not in the global public interest, triggering a board-community consultation. After consultation, a new community proposal would take 3/4 board majority to object. If the board objected a second time, we would have the power to
recall that entire board, or to pursue binding arbitration. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">Again, these are my personal thoughts about a way forward that is based on what others have said recently. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">—Steve DelBianco<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"> <o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><o:p></o:p></span></p>
</div>
</body>
</html>