<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style>
<!--
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
@font-face
{font-family:Tahoma}
@font-face
{font-family:Verdana}
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
{color:blue;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline}
p
{margin-right:0in;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif"}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif"}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif"}
span.hoenzb
{}
span.BalloonTextChar
{font-family:"Tahoma","sans-serif"}
span.EmailStyle22
{font-family:"Calibri","sans-serif";
color:#1F497D}
.MsoChpDefault
{}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
div.WordSection1
{}
ol
{margin-bottom:0in}
ul
{margin-bottom:0in}
-->
</style>
</head>
<body lang="EN-US" link="blue" vlink="purple">
For clarity, in No. 4 below, I meant to say "seven SO/ACs" and not "seven GACs". <br>
<br>
Josh<br>
<br>
<br>
<br>
Sent with Good (www.good.com)<br>
<strong>
<div><font face="Tahoma" color="#000000" size="2"> </font></div>
</strong>
<hr tabindex="-1">
<font face="Tahoma" size="2"><b>From:</b> ccwg-accountability5-bounces@icann.org on behalf of List for the work of CCWG-Accountability Legal SubTeam<br>
<b>Sent:</b> Sunday, May 03, 2015 01:38:41 AM<br>
<b>To:</b> ccwg-accountability5@icann.org<br>
<b>Subject:</b> Re: [Acct-Legal] Fwd: XPLANE update - please review<br>
</font><br>
<div></div>
<div>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Greg and CCWG Legal Sub-team,</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Thanks for the note Greg, and we agree with your analysis, but also think the issue can be simplified for discussion and resolved in principle without significant
amendment to the draft Report that will go out for public comment. In addition, for this analysis we can leave the Nominating Committee to the side, as their role is limited to selecting (and removing) Directors, and do not otherwise exercise any of the community
powers. </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">From our prior discussions with CCWG, we have assumed that for various reasons the GAC (and perhaps other SOs and ACs) did not want to form unincorporated
associations, which as we’ve stated precludes them from becoming “Members” of ICANN (Members must be legal persons). Nonetheless, we understood that the CCWG still wanted the GAC and others to have an influential role, and believed that the community group
mechanism articulated in 2.6.1.1 and 2.6.1.2 was designed to give effect to this goal, but without making those ACs Members.
</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Basically, the issue turns on whether three ACs – the GAC, the SSAC, and the RSSAC – should become Members (which entails becoming unincorporated associations)
or should function as part of the community group but not as ICANN Members. Either approach is legally viable and enforceable. </span><span style="font-family:"Calibri","sans-serif"; color:#1F497D"></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"; color:#1F497D">In summary:</span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="color:#1F497D"><span style="">1.<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="color:#1F497D">We have confirmed that ICANN can have classes of Members that do not have the right to select Directors (conversely, no right to remove their individual director either). This applies to the GAC, RSSAC and SSAC.</span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="color:#1F497D"><span style="">2.<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="color:#1F497D">If desired, ICANN could have 7 Member Entities – GNSO, CCNSO, ASO, GAC, At-Large AC, SSAC, and RSSAC.</span></p>
<p class="MsoListParagraph" style="margin-left:1.0in; text-indent:-.25in"><span style="font-family:"Courier New"; color:#1F497D"><span style="">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="color:#1F497D">All 7 Members would share the right to exercise the Community Powers over (a) Budget, (b) Strategic Plan, (c) changes to Fundamental Bylaws, (d) changes to bylaws, and (e) recalling the full Board. These decisions
would be coordinated through the community group, with Members exercising their influence as articulated in Section 2.6.1.2 of the Report (with the weighted votes).</span></p>
<p class="MsoListParagraph" style="margin-left:1.0in; text-indent:-.25in"><span style="font-family:"Courier New"; color:#1F497D"><span style="">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="color:#1F497D">Four members – GNSO, CCNSO, ASO, and At-large AC – have the right to select Directors and recall their selected Directors.</span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="color:#1F497D"><span style="">3.<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="color:#1F497D">Nos. 1 and 2 above assumes that <b>
<u>all</u></b> the AC’s are willing to become unincorporated associations, including the GAC.</span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="color:#1F497D"><span style="">4.<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="color:#1F497D">If the assumption stated in No. 3 is not true for one or more of the seven GACs, then we can still have those Community Powers exercised through the 29 vote community group as proposed by CCWG in this report.
However, there will need to be an additional step for implementation purposes, which will put the decision of the community group to the voting Members. This may necessitate a contract between the Members and the community group, which would require the community
group to create an unincorporated association, or we may be able to achieve it through covenants in the bylaws. To counsel, this is a second-tier implementation detail, and we have allowed for this in our comments to the draft Report
<u>(another copy of which is attached here for convenience)</u>. If the public decides it’s too much to have Members and it would be better to give up full approval/veto rights over the budget and plan, and IANA Function review and recommendations, then
this issue becomes moot (we could achieve the remaining community powers with Designators).
</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Happy to discuss further on Sunday if a call is necessary.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Cheers,</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Josh</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal" style=""><b><span style="font-size:10.0pt; font-family:"Arial","sans-serif"; color:#1F497D">JOSHUA</span></b><span style="font-size:10.0pt; font-family:"Arial","sans-serif"; color:#1F497D"> <b>HOFHEIMER</b></span></p>
<p class="MsoNormal" style=""><span style="font-size:9.0pt; font-family:"Arial","sans-serif"; color:#1F497D">Sidley Austin LLP<br>
+1.213.896.6061 (LA direct)<br>
+1.650.565.7561 (PA direct)<br>
+1.323.708.2405 (cell)<br>
<a href="mailto:jhofheimer@sidley.com" title="Click to send email to Hofheimer, Joshua T.">jhofheimer@sidley.com</a><br>
<a href="http://www.sidley.com/" title="www.sidley.com">www.sidley.com</a></span></p>
<p class="MsoNormal" style=""><a href="http://www.sidley.com/"><span style="font-size:10.0pt; font-family:"Arial","sans-serif"; text-decoration:none"><img border="0" width="35" height="35" id="_x0000_i1026" src="http://www.sidley.com/files/upload/signatures/SA-autosig.png" alt="http://www.sidley.com/files/upload/signatures/SA-autosig.png"></span></a><span style="font-size:10.0pt; font-family:"Arial","sans-serif"; color:#1F497D"> </span><b><span style="font-size:10.0pt; font-family:"Arial","sans-serif"; color:#1F497D">SIDLEY
AUSTIN LLP</span></b><span style="font-size:10.0pt; color:#1F497D"></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><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""> ccwg-accountability5-bounces@icann.org [mailto:ccwg-accountability5-bounces@icann.org]
<b>On Behalf Of </b>List for the work of CCWG-Accountability Legal SubTeam<br>
<b>Sent:</b> Saturday, May 02, 2015 10:01 PM<br>
<b>To:</b> ccwg-accountability5@icann.org<br>
<b>Subject:</b> [Acct-Legal] Fwd: XPLANE update - please review</span></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"> </p>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"">Copying this to the rest of the Legal Sub Team.</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"">Greg</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-right:0in; margin-bottom:12.0pt; margin-left:.5in">
---------- Forwarded message ----------<br>
From: <b>Greg Shatan</b> <<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a>><br>
Date: Sun, May 3, 2015 at 12:25 AM<br>
Subject: Re: XPLANE update - please review<br>
To: "Gregory, Holly" <<a href="mailto:holly.gregory@sidley.com">holly.gregory@sidley.com</a>><br>
Cc: "Rosemary E. Fei" <<a href="mailto:rfei@adlercolvin.com">rfei@adlercolvin.com</a>>, Adam Peake <<a href="mailto:adam.peake@icann.org">adam.peake@icann.org</a>>, "Hofheimer, Joshua T." <<a href="mailto:jhofheimer@sidley.com">jhofheimer@sidley.com</a>>, Leon
Sanchez <<a href="mailto:leonfelipe@sanchez.mx">leonfelipe@sanchez.mx</a>>, Sidley ICANN CCWG <<a href="mailto:sidleyicannccwg@sidley.com">sidleyicannccwg@sidley.com</a>>, ICANN-Adler <<a href="mailto:ICANN@adlercolvin.com">ICANN@adlercolvin.com</a>><br>
<br>
</p>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"">I think there is some confusion -- or at least, disconnection -- across the board here. The XPLANE slides really need to align with the draft proposal. I have not
yet tried to do that -- I've been out today and need to pack and get ready for an early flight tomorrow. I should be able to look at this more carefully on the flight (NY - San Diego, so I'll have some time....). I'm not sure how to align this with everyone
else's schedule and our publication schedule.</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"">I think confusion centers on the different current and proposed community groupings -- their composition and what their powers, and how they relate to each other.</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"">There are 3 groupings at play:</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"">1. The "Current Selectors": the 5 organizations that currently choose Board Members.</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"">2. The proposed Members or Designators.</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"">3. The "Empowered Community" (shown on each XPlane slide).</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"">The problem is that we have not figured out the connection between these 3 groupings, because the composition of these 3 groupings is inconsistent.</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"">The "Current Selectors" are:</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"">GNSO: 2 board seats</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"">ccNSO: 2 board seats</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"">ASO: 2 board seats</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"">ALAC: 1 board seat</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"">NomCom: 8 board seats*</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"">GAC, RSSAC, SSAC: 0 Board seats (each has one non-voting liaison)</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"">----</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"">*NomCom composition: GNSO (7), ALAC (5), ccNSO (1), ASO (1), IAB (for IETF) (1), GAC, RSSAC, SSAC (each 1 non-voting liaison)</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"">If we follow directly from the "Current Selectors" the "Members" or "Designators" of ICANN would be the GNSO, the ccNSO, the ASO, ALAC. and the NomCom. The GAC, RSSAC
and SSAC would not be Members or Designators (whether directly or through voting membership on the NomCom), because they have no voting role in choosing Directors.</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"">This does not align with our ongoing discussion of who the Members or Designators would be. Instead, we have discussed having Members or Designators that align with
all 8 of these groups (although only 5 can choose Directors).</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"">This in turn does not align with the "Empowered Community" that we seem to think should control the 5 community powers. That would be the 7 groups shown on the Xplane
slides, which excludes the NomCom, and gives seats (or at least "weights") to these 7 groups in a manner that does not relate to their power to appoint Directors. Specifically, the GNSO, ccNSO, ASO, ALAC and GAC are given equal weight, the RSSAC and SSAC
are given lesser weight, and the NomCom is disregarded. </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"">We have not contemplated the linkage between "Current Selectors"; the organizations with the <u>right to appoint board members</u> (GNSO/ccNSO/ASO/ALAC/NomCom) and
the <u>Empowered Community</u> (GNSO/ccNSO/ASO/ALAC/GAC/RSSAC/SSAC). If the Current Selectors are the Members/Designators, how does the Empowered Community have the rights we want to give it? If the Empowered Community are the Members/Designators, how do
we deal with the fact that 3 Members/Designators have no right to appoint Directors, while the group that can appoint 8 Directors (i.e., the NomCom) is not a Member or Designator? Would this be dealt with by an agreement among the 7 (or maybe 8) organizations
(or more precisely, UAs aligned with these organizations)?</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"">This needs to be figured out, and quickly....</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"">Aside from this, there are more specific problems with the slides. Slide 4 is particularly troublesome -- the right to remove individual directors should not be
a right of the "Empowered Community." Instead it is a right that belongs to the GNSO, ccNSO, ASO and ALAC (but only as to each organization's own appointments), plus the unsolved case of the NomCom. The "Who Can Initiate A Petition" and "Things Required to
Initiate" sections seems particularly off-target.</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"">Some of the slides have decision thresholds to "approve," while others have thresholds to "reject," making them confusing -- this is particularly true of the Bylaw
and Fundamental Bylaw slides. These rights appear to work in opposite ways -- Bylaws will be changed unless 75% vote to reject, while Fundamental Bylaws will not be changed unless 83% vote to accept. Maybe this is what we intended, but it looks odd when
expressed this way.</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"">On Slide 1, the title refers to "Strategy Operating Plans" -- obviously there is no such thing. ICANN has a Strategic Plan updated every 5 years, a 5 Year Operating
Plan updated annually, and an annual Operating Plan and Budget derived from the 5 Year Operating Plan. These should be referred to accurately. </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"; color:#888888"> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"; color:#888888">Greg</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"; color:#888888"> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"; color:#888888"> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"; color:#888888"> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"; color:#888888"> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"; color:#888888"> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"; color:#888888"> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"; color:#888888"> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"; color:#888888"> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"; color:#888888"> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Verdana","sans-serif"; color:#888888"> </span></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> </p>
<div>
<p class="MsoNormal" style="margin-left:.5in">On Sat, May 2, 2015 at 9:10 PM, Gregory, Holly <<a href="mailto:holly.gregory@sidley.com" target="_blank">holly.gregory@sidley.com</a>> wrote:</p>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Hi Adam, perhaps we should plan on a quick call for the Legal Subteam to clarify to us what the intent is. We found the draft proposal and the slides somewhat confused in the earlier draft and tried to clarify but
apparently without success. <br>
<br>
<br>
<br>
Sent with Good (<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.good.com&d=AwMFaQ&c=Od00qP2XTg0tXf_H69-T2w&r=PyftdYkqjEDMIx5o_kyQ1bCTTkOV655ea67oiCGUI9M&m=CY6emrtO8YpL6GG9tlEQXWKZPzHhsu5uPNwcHDbVb4s&s=ojBeRqT8de6WaHMScv7SsYv8dLO79QtzxPBzAGFtdb0&e=" target="_blank">www.good.com</a>)<strong></strong></p>
<div>
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black"> </span></b></p>
</div>
<div class="MsoNormal" align="center" style="margin-left:.5in; text-align:center">
<hr size="2" width="100%" align="center">
</div>
<p class="MsoNormal" style="margin-right:0in; margin-bottom:12.0pt; margin-left:.5in">
<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""> Rosemary E. Fei<br>
<b>Sent:</b> Saturday, May 02, 2015 06:33:03 PM<br>
<b>To:</b> 'Adam Peake'; Gregory, Holly; Hofheimer, Joshua T.<br>
<b>Cc:</b> Leon Sanchez; Greg Shatan; Sidley ICANN CCWG; ICANN-Adler<br>
<b>Subject:</b> RE: XPLANE update - please review</span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-right:0in; margin-bottom:12.0pt; margin-left:.5in">
<span style="font-size:10.0pt">Dear Adam, we will review.<br>
<br>
However, I'm not available for the next several hours, and I believe most if not all legal counsel team members are similarly engaged at this point in the weekend, so I'm not sure how quickly this review can be accomplished.<br>
<br>
More importantly, I'm unclear what the current member reference model is, since we thought it involved the two groups (a broader community, including both member and non-member groups, and a smaller membership group) described in our prior edits I'm not sure
how to review the slides based on a model I'm not familiar with. Perhaps there's just a misunderstanding about what the two groups can do, and how the broader community/larger group can influence decisions, as opposed to the rights of the smaller member group.
We sent our revisions to the CCWG Draft Proposal a little while ago which attempted to clarify this, so we hope the concerns will be resolved by that.<br>
<br>
Rosemary<br>
<br>
-----Original Message-----<br>
From: Adam Peake [<a href="mailto:adam.peake@icann.org" target="_blank">mailto:adam.peake@icann.org</a>]<br>
Sent: Saturday, May 02, 2015 4:22 PM<br>
To: Holly Gregory; Rosemary E. Fei; Joshua Hofheimer<br>
Cc: Leon Sanchez; Greg Shatan<br>
Subject: XPLANE update - please review<br>
<br>
Dear Rosemary, Holly, Josh:<br>
<br>
Attached is an update from XPLANE of the presentation they gave on the<br>
CCWG call last Thursday (IRP not included, they are taking your comments<br>
onboard).<br>
<br>
Could you please review in light of the current member reference model,<br>
not the A/B approach of the last memo. This is urgent please, we lost a<br>
bit of time while XPLANE looked at the approach described in your memo<br>
<br>
Leon is having a few email problems at the moment and he's not sure if he<br>
can find a connection robust enough to handle these large PDF files, but<br>
he will send a note as soon as he's able to confirm this request. I am<br>
also cc¹ing Greg for consistency.<br>
<br>
All comments on how the graphics usefully represent the "empowered<br>
community" and the powers and mechanisms much appreciated. Individual<br>
board removal/board recall is lacking.<br>
<br>
Jordan, Thomas and others have proposed a few changes. These include:<br>
<br>
Slide "The Community Mechanism: SO/AC Membership Model" there is no (c) in<br>
how does it work. The text under "Influence in the Community Mechanism"<br>
change to "the votes come from ICANNs SOs, ACs and the NomCom. Each SO and<br>
AC has a number of votes in the community mechanism, deciding on the<br>
powers established for the community".<br>
<br>
Slide power 1 should be "Reconsider/Reject Budget, or Strategic /<br>
Operating Plans"<br>
<br>
Slide power 3 (fundamental bylaws) should be 75%.<br>
<br>
Slide power 5 (board recall) should show a petition of 3 SO and AC and at<br>
least one of each. Notion of quorum matters in the sense that every vote<br>
counts.<br>
<br>
And a comment on the IRP (but this before you updates on these slides<br>
which are very clear), but they were: on IRP Slide 7 does the binding<br>
nature need to be modified to mention fiduciary responsibilities?<br>
<br>
Leon will write soon.<br>
<br>
Best,<br>
<br>
Adam<br>
<br>
Adam Peake<br>
ICANN<br>
<br>
<br>
</span></p>
</div>
<p style="margin-left:.5in"> </p>
</div>
</div>
<p style="margin-left:.5in">****************************************************************************************************<br>
This e-mail is sent by a law firm and may contain information that is privileged or confidential.<br>
If you are not the intended recipient, please delete the e-mail and any attachments and notify us<br>
immediately.<br>
<br>
****************************************************************************************************</p>
</div>
</div>
<p class="MsoNormal" style="margin-left:.5in"> </p>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-left:.5in"> </p>
</div>
</div>
</div>
</body>
</html>