<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Copying this to the rest of the Legal Sub Team.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Greg</div><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Greg Shatan</b> <span dir="ltr"><<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a>></span><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><br><div dir="ltr"><div 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.</div><div style="font-family:verdana,sans-serif"><br></div><div 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.</div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">There are 3 groupings at play:</div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">1. The "Current Selectors": the 5 organizations that currently choose Board Members.</div><div style="font-family:verdana,sans-serif">2. The proposed Members or Designators.</div><div style="font-family:verdana,sans-serif">3. The "Empowered Community" (shown on each XPlane slide).</div><div style="font-family:verdana,sans-serif"><br></div><div 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.</div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">The "Current Selectors" are:</div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">GNSO: 2 board seats</div><div style="font-family:verdana,sans-serif">ccNSO: 2 board seats</div><div style="font-family:verdana,sans-serif">ASO: 2 board seats</div><div style="font-family:verdana,sans-serif">ALAC: 1 board seat</div><div style="font-family:verdana,sans-serif">NomCom: 8 board seats*</div><div style="font-family:verdana,sans-serif">GAC, RSSAC, SSAC: 0 Board seats (each has one non-voting liaison)</div><div style="font-family:verdana,sans-serif">----</div><div 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)</div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif"><br></div><div 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.</div><div style="font-family:verdana,sans-serif"><br></div><div 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).</div><div style="font-family:verdana,sans-serif"><br></div><div 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. </div><div style="font-family:verdana,sans-serif"><br></div><div 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)?</div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">This needs to be figured out, and quickly....</div><div style="font-family:verdana,sans-serif"><br></div><div 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.</div><div style="font-family:verdana,sans-serif"><br></div><div 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.</div><div style="font-family:verdana,sans-serif"><br></div><div 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. </div><span class="HOEnZb"><font color="#888888"><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">Greg</div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif"><br></div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, May 2, 2015 at 9:10 PM, Gregory, Holly <span dir="ltr"><<a href="mailto:holly.gregory@sidley.com" target="_blank">holly.gregory@sidley.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<p></p>
<div>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><span>
<br>
<br>
<br>
Sent with Good (<a href="http://www.good.com" target="_blank">www.good.com</a>)<br>
<strong>
<div><font face="Tahoma" color="#000000" size="2"> </font></div>
</strong>
<hr>
</span><font face="Tahoma" size="2"><span><b>From:</b> 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>
</span><b>Subject:</b> RE: XPLANE update - please review<br>
</font><br>
<div></div>
</div><div><div>
<font size="2"><span style="font-size:10pt">
<div>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>
<br>
</div>
</span></font>
<p></p>
<p> </p>
</div></div><p>****************************************************************************************************<span><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>
****************************************************************************************************</span></p>
</div>
</blockquote></div><br></div>
</div></div></div><br></div>