<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>this is interesting but I am confused about whether it is really a practical concern. In fact, the Board has never removed a Director. NOR refused to embrace whomever we, the community put forward. <div><br></div><div>I agree with Thomas that refusing to accept a Board member placed by the community by the rest of the Board would represent a 'rogue' Board and then the Community would undoubtedly fully protest.</div><div><br></div><div>Let's look back at our history of placing Board members. </div><div>And let's be frank with each other, and honest. We, the community have sent forward some Board members who have limited expertise in ICANN issues; we have sent forward some who were even ICANN critics; we have sent forward some who sleep through meetings. So far, the Board members have embraced each and every one and all have then tried to work on our behalf. </div><div><br></div><div>If we, the community elect or the NomComm selects a Board member, I seriously doubt that the rest of the Board will work to reject them or him or her. So, I find this an extremely unlikely occurrence.</div><div><br></div><div><br><br><div><hr id="stopSpelling">From: thomas@rickert.net<br>Date: Sat, 9 Apr 2016 09:23:34 +0200<br>To: seun.ojedeji@gmail.com<br>CC: accountability-cross-community@icann.org<br>Subject: Re: [CCWG-ACCT] CCWG - Bylaws Drafting - Questions<br><br>Hi Seun, all,<div>in the document circulated by Bernie a while ago, we have offered a reworded answer to the EC consent question:</div><div><br></div><div>***</div><div>
<div class="ecxpage" title="Page 2">
<div class="ecxlayoutArea">
<div class="ecxcolumn"><span style="font-size:11.000000pt;font-family:'ArialMT';">The Board always had the power to remove directors. The CCWG recommends two
community powers on removing individual directors and recalling the entire Board.
However, the previously existing right of the Board to remove directors was neither
removed nor altered by the CCWG recommendations. The CCWG asks the lawyers to
ensure that this right for the Board will remain in tact and include required language in
the Bylaws.
</span><BR><span style="font-size:11.000000pt;font-family:'ArialMT';">However, concerns have been expressed that there might be issues when the
community tries to seat Board members and then the Board removes those board
members instantly. We kindly ask the lawyers to comment on ways, if any, to mitigate
that risk without changing the substance of the recommendations. </span><BR>
</div>
</div>
</div></div><div>***</div><div><br></div><div>As we are working on the implementation of our recommendations and since our report did not include changes to the Board’s power to remove colleagues, still struggle with the notion of requiring active participation of the EC.</div><div><br></div><div>Having said that, I understand the issue raised about immediate removal of those directors by the Board that the EC tries to place on the Board. However, I am not sure our response should be to change the Board process. If a rogue Board tries to prevent the EC from seating Board members of their liking by removing them straight away, we should remove the Board. </div><div><br></div><div>I think that changing the Board process would not address the root cause of the issue, which would be a Board not playing by the rules. </div><div><br></div><div>Best,</div><div>Thomas</div><div><br></div><div><br></div><div><div><div><blockquote><div>Am 09.04.2016 um 06:23 schrieb Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com">seun.ojedeji@gmail.com</a>>:</div><br class="ecxApple-interchange-newline"><div><p dir="ltr">Hi,</p><p dir="ltr">This implies that you(some) don't think board should be able to remove it's members. While I wonder why you have such view, I don't think that its a question/response we should be sending to the lawyers as it is a decision the CCWG has to made.</p><p dir="ltr">In the past, we have pushed so much question to the lawyers without actually indicating what we want. It is my hope that we will avoid that at this stage; we should always indicate what we want so layers can advice on how we may go about it (if at all possible).</p><p dir="ltr">That said, I think we need to recognise the implication of what you've said; it implies that a community process will need to be put in place to get the EC's approval and I wonder how long that would take. The other question from that is what the status of the menber would be during that process. I don't know of any organisation that makes its board so dependent in the manner you are proposing. </p><p dir="ltr">Andrew raised a valid concern about possibility of board removing a member that was re-appointed (within the same term). While I believe such scenario would be so extreme and close to impossible, as I have earlier said a way to approach it could be to subject subsequent removal to actual approval of EC. However the Co-Chairs in their wisdom has thrown the question of "how to achieve what we want" to the lawyers which I believe is in order. I do think we should be setting processes that helps the board know the consequences of their actions and not the one that always prevents them from acting.</p><p dir="ltr">Regards<br>
Sent from my LG G4<br>
Kindly excuse brevity and typos</p>
<div class="ecxgmail_quote">On 8 Apr 2016 10:49 p.m., "Chartier, Mike S" <<a href="mailto:mike.s.chartier@intel.com">mike.s.chartier@intel.com</a>> wrote:<br><blockquote class="ecxgmail_quote" style="border-left:1px #ccc solid;padding-left:1ex;">
<div lang="EN-US">
<div><p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d;">RE: Q6<u></u><u></u></span></p><p class="ecxMsoNormal" style=""><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d;">“</span>concerns have been expressed that there might be issues when the community tries to seat Board members and then the Board removes
those board members instantly.<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d;">”<u></u><u></u></span></p><p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d;">I’m not sure that captures the whole concern. Some expressed the desire that the EC consent be real and not perfunctory.<u></u><u></u></span></p><p class="ecxMsoNormal"><a name="m_-6870899358421142799__MailEndCompose" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d;"><u></u> <u></u></span></a></p><p class="ecxMsoNormal"><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;"> <a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank">accountability-cross-community-bounces@icann.org</a> [mailto:<a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank">accountability-cross-community-bounces@icann.org</a>]
<b>On Behalf Of </b>Bernard Turcotte<br>
<b>Sent:</b> Friday, April 8, 2016 5:35 PM<br>
<b>To:</b> Accountability Cross Community <<a href="mailto:accountability-cross-community@icann.org" target="_blank">accountability-cross-community@icann.org</a>><br>
<b>Subject:</b> [CCWG-ACCT] CCWG - Bylaws Drafting - Questions<u></u><u></u></span></p><p class="ecxMsoNormal"><u></u> <u></u></p>
<div>
<div><p class="ecxMsoNormal">All,<u></u><u></u></p>
</div>
<div><p class="ecxMsoNormal"><u></u> <u></u></p>
</div>
<div><p class="ecxMsoNormal">Please find attached 2 documents.<u></u><u></u></p>
</div>
<div><p class="ecxMsoNormal"><u></u> <u></u></p>
</div>
<div><p class="ecxMsoNormal">The first is the compilation of the answers provided to lawyers on Thursday April 7th.<u></u><u></u></p>
</div>
<div><p class="ecxMsoNormal"><u></u> <u></u></p>
</div>
<div><p class="ecxMsoNormal">The second is a list of remaining open questions. For some of these questions the CCWG co-chairs and rapporteurs have reviewed the original proposed replies or added some new replies - these are clearly indicated in the document.<u></u><u></u></p>
</div>
<div><p class="ecxMsoNormal"><u></u> <u></u></p>
</div>
<div><p class="ecxMsoNormal">Co-chairs, rapporteurs and staff have tried to be dutiful in capturing the questions from the list but it is possible some were missed. If you have submitted a question or issue please verify it is included in this version of the document.<u></u><u></u></p>
</div>
<div><p class="ecxMsoNormal"><u></u> <u></u></p>
</div>
<div><p class="ecxMsoNormal">Please remember that the deadline for submitting questions and issues is 23:59 UTC Saturday April 9 2016.<u></u><u></u></p>
</div>
<div><p class="ecxMsoNormal"><u></u> <u></u></p>
</div>
<div><p class="ecxMsoNormal">We are looking forward to continuing the process of addressing these issues and questions at our Monday April 11th meeting at 19:00 UTC.<u></u><u></u></p>
</div>
<div><p class="ecxMsoNormal"><u></u> <u></u></p>
</div>
<div><p class="ecxMsoNormal">Bernard Turcotte<u></u><u></u></p>
</div>
<div><p class="ecxMsoNormal">ICANN Staff Support for the CCWG Co-Chairs<u></u><u></u></p>
</div>
<div><p class="ecxMsoNormal">Thomas Rickert, Mathieu Weill, Leon Sanchez<u></u><u></u></p>
</div>
</div>
</div>
</div>
<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" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br></blockquote></div>
_______________________________________________<br>Accountability-Cross-Community mailing list<br><a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>https://mm.icann.org/mailman/listinfo/accountability-cross-community<br></div></blockquote></div><br></div></div><br>_______________________________________________
Accountability-Cross-Community mailing list
Accountability-Cross-Community@icann.org
https://mm.icann.org/mailman/listinfo/accountability-cross-community</div></div> </div></body>
</html>