<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style>
<!--
@font-face
{font-family:Wingdings}
@font-face
{font-family:Wingdings}
@font-face
{font-family:Calibri}
@font-face
{font-family:Tahoma}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
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:0cm;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif"}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif"}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif"}
span.EmailStyle18
{font-family:"Calibri","sans-serif";
color:#1F497D}
span.TextedebullesCar
{font-family:"Tahoma","sans-serif"}
span.EmailStyle22
{font-family:"Calibri","sans-serif";
color:#1F497D}
.MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:72.0pt 72.0pt 72.0pt 72.0pt}
div.WordSection1
{}
ol
{margin-bottom:0cm}
ul
{margin-bottom:0cm}
-->
</style>
</head>
<body lang="FR" link="blue" vlink="purple">
Dear Mathieu and Sam, We understand and will work with Sam to try and come to agreement on a path forward. If we cannot, we will provide a targeted set of questions for consideration on the Tuesday call. Sam, please let us know what time works best for a
call tomorrow, over the weekend or on Monday. Given the time frame, the earlier the better. Kind regards, Holly<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> Mathieu Weill<br>
<b>Sent:</b> Thursday, February 04, 2016 03:06:17 PM<br>
<b>To:</b> Gregory, Holly; thomas@rickert.net; León Felipe Sánchez Ambía; Accountability Cross Community; ACCT-Staff<br>
<b>Cc:</b> icann@adlercolvin.com; Sidley ICANN CCWG; Samantha Eisner; Kevin Espinola<br>
<b>Subject:</b> RE: Recommendation 4 - Board Removal Liability - Proposed Indemnification Language<br>
</font><br>
<div></div>
<div>
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Dear Holly, Dear Sam,
</span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">The current status on this waiver / indemnification language is :</span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"><span style="">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">The Board heard the concerns raised by the CCWG and has agreed in principle to indemnification but is still in objection to a waiver</span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"><span style="">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Icann Legal and CCWG Independent Legal Advisors obviously have different perspectives on the indemnification, the relevant causes of action,
level of protection, etc. </span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Our group will have to come to a conclusion, at the requirement level at least, during our next meeting on Tuesday. Until then, can Icann Legal
and Sidley and/or Adler coordinate to try and resolve their differences ahead of the call ? At the very least, jointly highlighting in advance of the meeting which requirement questions should be addressed by the CCWG would be very helpful to a constructive
discussion. </span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Best regards,</span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Mathieu</span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<div>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">De :</span></b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> Gregory, Holly [mailto:holly.gregory@sidley.com]
<br>
<b>Envoyé :</b> jeudi 4 février 2016 15:00<br>
<b>À :</b> thomas@rickert.net; mathieu.weill@afnic.fr; 'León Felipe Sánchez Ambía'; 'Accountability Cross Community'; 'ACCT-Staff'<br>
<b>Cc :</b> icann@adlercolvin.com; Sidley ICANN CCWG; 'Samantha Eisner'; Kevin Espinola<br>
<b>Objet :</b> Recommendation 4 - Board Removal Liability - Proposed Indemnification Language</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:18.0pt; font-family:"Calibri","sans-serif"">Dear Co-Chairs, Members, Participants and Staff,
<br>
<br>
We have reviewed the proposed language sent by ICANN Legal yesterday regarding a new indemnification bylaw designed at protecting certain participants in efforts to remove directors or recall the full Board from legal claims. We have also reviewed the sample
Guidelines for Due Diligence in Board Removal Discussions that ICANN Legal provided. We have the following concerns and observations: </span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:18.0pt; font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:18.0pt; font-family:"Calibri","sans-serif"">1. The indemnification language in the current ICANN bylaws (pasted below for your reference) largely tracks the statutory limits and standards for indemnification
for a California nonprofit public benefit corporation and is broader – and therefore more protective to the covered persons – than the proposed new additional provision. Under the new additional provision proposed by ICANN Legal covered persons would have
<i>less</i> protection with respect to claims resulting from efforts to remove directors and recall the full Board than would be provided under the current provision to protect covered persons from claims. In our view, the concerns raised by the CCWG-Accountability
about protection from claims brought by directors is better served by relying on the current bylaw provision (with some minor clarifications explained below). The current bylaw already provides significant indemnification from legal claims:</span></p>
<p class="MsoNormal" align="center" style="text-align:center"><i><span lang="EN-US" style="font-size:18.0pt; font-family:"Calibri","sans-serif"">ARTICLE XIV: INDEMNIFICATION OF DIRECTORS, OFFICERS, EMPLOYEES, AND OTHER AGENTS</span></i></p>
<p class="MsoNormal" style="margin-left:36.0pt"><i><span lang="EN-US" style="font-size:18.0pt; font-family:"Calibri","sans-serif"">ICANN shall, to maximum extent permitted by the CNPBCL, indemnify each of its agents against expenses, judgments, fines, settlements,
and other amounts actually and reasonably incurred in connection with any proceeding arising by reason of the fact that any such person is or was an agent of ICANN, provided that the indemnified person's acts were done in good faith and in a manner that the
indemnified person reasonably believed to be in ICANN's best interests and not criminal. For purposes of this Article, an "agent" of ICANN includes any person who is or was a Director, Officer, employee, or any other agent of ICANN (including a member of any
Supporting Organization, any Advisory Committee, the Nominating Committee, any other ICANN committee, or the Technical Liaison Group) acting within the scope of his or her responsibility; or is or was serving at the request of ICANN as a Director, Officer,
employee, or agent of another corporation, partnership, joint venture, trust, or other enterprise. The Board may adopt a resolution authorizing the purchase and maintenance of insurance on behalf of any agent of ICANN against any liability asserted against
or incurred by the agent in such capacity or arising out of the agent's status as such, whether or not ICANN would have the power to indemnify the agent against that liability under the provisions of this Article.</span></i></p>
<p class="MsoNormal" style="text-autospace:none"><b><span lang="EN-US" style="font-size:18.0pt; font-family:"Calibri","sans-serif"">We recommend that, rather than adding the proposed new provision that would provide less protection for claims
<i> </i>relating to efforts to remove directors or recall the full Board, this current language be clarified to add in the list of covered persons / entities in the first parenthetical, “any person acting in his or her capacity as a representative of the
Empowered Community,” thereby clarifying that the Empowered Community and its representatives are indemnified agents. We also recommend clarifying that an indemnified agent includes any person who is or was serving as an appointed member of an ICANN body
(such as a member of a cross-community working group or a Review Team). </span></b><span lang="EN-US" style="font-family:"Calibri","sans-serif"; background:yellow"></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:18.0pt; font-family:"Calibri","sans-serif"">2. If a new provision is added – which as indicated above would
<i><u>not</u></i> be our preference – we recommend broadening that new provision to include
<i><u>all</u></i> causes of action and removing the qualifications contained in paragraphs 2-5 (see the attached markup). The indemnification process in this section should be parallel to that applicable to ICANN officers and directors; for example, an SO/AC
chair who is sued for defaming a director should not have to jump through more hoops than an ICANN officer would if they were sued for defaming an SO/AC chair. Note also that if an agent has been successful on the merits in defending a suit brought by a
director, he or she would be entitled to indemnification related to the expenses associated with that defense pursuant to Section 5238(d) of the California Corporations Code regardless of the bylaw; any attempt to impose additional qualifications in the
Bylaws in that scenario would not be valid.</span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:18.0pt; font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:18.0pt; font-family:"Calibri","sans-serif"">3. We note that providing Guidelines for expected behavior of community participants may have positive benefits but care must be taken that they are not drafted
to discourage community participants from taking action in a specific area. To avoid any potential chill on efforts to seek removal of directors or recall the full Board – and in the interests of encouraging positive behavior from community participants generally
– consider whether it would be beneficial to have the Guidelines (as may be revised by CCWG-Accountability after due consideration) apply to <i><u>all</u></i> discussions within ICANN, not just a carved-out set of circumstances where the community is participating
in the director removal<b><i> </i></b>or Board recall processes.</span></p>
<p class="MsoNormal" style="margin-left:108.0pt"><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoNormal" style="margin-left:108.0pt"><span lang="EN-US" style="font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:18.0pt; font-family:"Calibri","sans-serif"">Kind regards,</span></p>
<p class="MsoNormal" style="margin-left:108.0pt"><span lang="EN-US" style="font-size:18.0pt; font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:18.0pt; font-family:"Calibri","sans-serif"">Holly and Rosemary</span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-size:11.0pt; color:#1F497D"> </span></p>
<p class="MsoNormal" style=""><b><span lang="EN-US" style="font-size:9.0pt; font-family:"Arial","sans-serif"; color:#1F497D">HOLLY J. GREGORY</span></b><span lang="EN-US" style="font-size:9.0pt; font-family:"Arial","sans-serif"; color:#1F497D"><br>
Partner and Co-Chair<br>
Global Corporate Governance & Executive Compensation Practice</span></p>
<p class="MsoNormal" style=""><b><span lang="EN-US" style="font-size:10.0pt; font-family:"Arial","sans-serif"; color:#1F497D">Sidley Austin LLP</span></b><b><span lang="EN-US" style="font-size:9.0pt; font-family:"Arial","sans-serif"; color:#1F497D"><br>
</span></b><span lang="EN-US" style="font-size:9.0pt; font-family:"Arial","sans-serif"; color:#1F497D">+1 212 839 5853<br>
<a href="mailto:holly.gregory@sidley.com" title="Click to send email to Gregory, Holly">holly.gregory@sidley.com</a></span><span lang="EN-US"></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt; font-family:"Arial","sans-serif"; color:#1F497D"> </span><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"></span></p>
<div>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:36.0pt"><b><span lang="EN-US" style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> Samantha Eisner [mailto:Samantha.Eisner@icann.org]
<br>
<b>Sent:</b> Wednesday, February 03, 2016 7:06 AM<br>
<b>To:</b> accountability-cross-community@icann.org<br>
<b>Cc:</b> icann@adlercolvin.com; Sidley ICANN CCWG<br>
<b>Subject:</b> Recommendation 4 - Board Removal Liability - Proposed Indemnification Language</span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"> </span></p>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-size:10.5pt; font-family:"Calibri","sans-serif"; color:black">Dear CCWG - </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-size:10.5pt; font-family:"Calibri","sans-serif"; color:black"> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-size:10.5pt; font-family:"Calibri","sans-serif"; color:black">To further the discussion on Recommendation 4, Board Removal Liability, I am providing two documents on behalf of ICANN.</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-size:10.5pt; font-family:"Calibri","sans-serif"; color:black"> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-size:10.5pt; font-family:"Calibri","sans-serif"; color:black">First is a proposed addition to ICANN’s Bylaws that specifically allows for indemnification for statements made in the
Board removal process (in initiation of the Community Forum, during the Community Forum, or in written rationale) that were made in good faith and with due diligence as to veracity. This language reflects the CCWG’s suggestions made during the 26 January
call that limiting indemnification only to written rationale was probably not enough.</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-size:10.5pt; font-family:"Calibri","sans-serif"; color:black"> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-size:10.5pt; font-family:"Calibri","sans-serif"; color:black">Second, we are providing some thoughts on how we can assist community members participating in a removal process in
assessing the good faith nature of their assertions as they are participating. We think that developing some guidelines will give participants confidence in working through the Board removal process.</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-size:10.5pt; font-family:"Calibri","sans-serif"; color:black"> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-size:10.5pt; font-family:"Calibri","sans-serif"; color:black">Thanks, </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-size:10.5pt; font-family:"Calibri","sans-serif"; color:black"> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-size:10.5pt; font-family:"Calibri","sans-serif"; color:black">Sam Eisner</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-size:10.5pt; font-family:"Calibri","sans-serif"; color:black"> </span></p>
</div>
<p class="12f8c011-ea17-4b13-91eb-a69af88e2d55"><span lang="EN-US"> </span></p>
<p><span lang="EN-US">****************************************************************************************************<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>
</div>
</body>
</html>