<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>
<!-- Template generated by Exclaimer Mail Disclaimers on 12:11:14 Wednesday, 27 January 2016 -->
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css">P.08896adb-c2fb-4148-844c-9246cce7fcdc {
        MARGIN: 0cm 0cm 0pt
}
LI.08896adb-c2fb-4148-844c-9246cce7fcdc {
        MARGIN: 0cm 0cm 0pt
}
DIV.08896adb-c2fb-4148-844c-9246cce7fcdc {
        MARGIN: 0cm 0cm 0pt
}
TABLE.08896adb-c2fb-4148-844c-9246cce7fcdcTable {
        MARGIN: 0cm 0cm 0pt
}
DIV.Section1 {
        page: Section1
}
</style>
<meta name="Generator" content="Microsoft Word 12 (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;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 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;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
span.EmailStyle18
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;}
@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">
<p class="08896adb-c2fb-4148-844c-9246cce7fcdc"></p>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">We agree that the language that ALAC points to (reproduced directly below) &nbsp;could be clarified:
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">“
</span>3. On page 14, item 2 of the draft proposal (and on page 5 of Annex <br>
1), it says &quot;The members of the unincorporated association would be <br>
representatives of ICANN's Supporting Organizations and Advisory <br>
Committees that wish to participate.&quot; We have never discussed how <br>
such members are identified. Presumably we should to specify that <br>
each participating AC/SO must identify who it's representative will be.<span style="font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">”<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span style="font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">The notion is that some persons are needed to ensure that the decisions of the Empowered Community are implemented.&nbsp; While the participating SOs and ACs will be members of the
 unincorporated association, &nbsp;each participating SO and AC should have a representative , &nbsp;and for simplicity we recommend that in each instance it be the chair of the AC or SO.&nbsp; We have addressed this notion in our memo about implementation of the unincorporated
 association, which we circulated a link to last week in our high level comments regarding the IRP.
<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#1F497D">HOLLY</span><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;J. GREGORY</span><span style="font-size:9.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#1F497D"><br>
Partner and Co-Chair<br>
Global Corporate Governance &amp; Executive Compensation Practice<br>
<br>
</span><b><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#1F497D">Sidley Austin LLP</span></b><b><span style="font-size:9.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#1F497D"><br>
</span></b><span style="font-size:9.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#1F497D">&#43;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><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p></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:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> accountability-cross-community-bounces@icann.org [mailto:accountability-cross-community-bounces@icann.org]
<b>On Behalf Of </b>Seun Ojedeji<br>
<b>Sent:</b> Wednesday, January 27, 2016 9:47 AM<br>
<b>To:</b> Kavouss Arasteh<br>
<b>Cc:</b> accountability-cross-community@icann.org<br>
<b>Subject:</b> Re: [CCWG-ACCT] Open ALAC Issues<o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><o:p>&nbsp;</o:p></p>
<p style="margin-left:.5in">Well even if we don't need it now. It will be good to recognise that it's yet to be discussed. However considering that the UA is required once board approves the proposal then it may be good to determine and conclude on this soon
 enough. <o:p></o:p></p>
<p style="margin-left:.5in">That said, it may be good to be sure that those member representatives have no power to act unilaterally. I would have thought using 1 stone to kill to birds will be good i.e making the various chairs/leaders of SO/AC to serve is
 such capacity. That gives some level of responsibility and security on that various SO/AC can always boot out their leader whenever required.<o:p></o:p></p>
<p style="margin-left:.5in">Regards<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-left:.5in">On 27 Jan 2016 15:02, &quot;Kavouss Arasteh&quot; &lt;<a href="mailto:kavouss.arasteh@gmail.com">kavouss.arasteh@gmail.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Dear All,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">I think people contuinue to go to the last milimiter of the road and generate a new discussion and debate about the number of représentatives in Unincorprated associattion&nbsp; représentatives and start a new round
 of bebates and dispute<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Do we need this information now pls ?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Kavouss <o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p>&nbsp;</o:p></p>
<div>
<p class="MsoNormal" style="margin-left:.5in">2016-01-27 6:14 GMT&#43;01:00 Alan Greenberg &lt;<a href="mailto:alan.greenberg@mcgill.ca" target="_blank">alan.greenberg@mcgill.ca</a>&gt;:<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">As per my comment in the CCWG meeting earlier today, here is a list of the issues still to be resolved from the ALAC statement on the 3rd Draft Proposal.<br>
<br>
<br>
There are three issues currently under discussion.<br>
<br>
1. ICANN Mission and ensuring that contract provisions will not be invalidated or be unenforceable.<br>
<br>
2. The issue regarding market mechanisms.<br>
<br>
3. Human Rights (original issue resolved but pending final wording).<br>
<br>
<br>
Issues to be addressed.<br>
<br>
<br>
1. The first is a relatively trivial one and easily addressed. Rec# 4, in the section on replacing the Interim Board states:<br>
<br>
&quot;SOs, ACs, and the Nominating Committee will develop replacement processes that ensure the Interim Board will not be in place for more than 120 days.&quot;<br>
<br>
The ALAC request that this be changed to:<br>
<br>
&quot;SOs, ACs, and the Nominating Committee will develop processes designed to replace Interim Board members within 120 days.&quot;<br>
<br>
By removing the word &quot;ensure&quot;, this change, while not altering the intent, goes along with the recent practice of not putting hard deadlines in the Bylaws, deadlines that for one reason or another may not be met in a particular instance.<br>
<br>
<br>
2. Rec# 10, AoC. The Recommendation suggests that as part of organizational reviews, the AC/SO's accountability be included in the review. The ALAC suggests that this be enshrined in Article IV, Section 4.1 of the ICANN Bylaws.<br>
<br>
<br>
3. On page 14, item 2 of the draft proposal (and on page 5 of Annex 1), it says &quot;The members of the unincorporated association would be representatives of ICANN's Supporting Organizations and Advisory Committees that wish to participate.&quot; We have never discussed
 how such members are identified. Presumably we should to specify that each participating AC/SO must identify who it's representative will be.<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<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://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_accountability-2Dcross-2Dcommunity&amp;d=CwMFaQ&amp;c=Od00qP2XTg0tXf_H69-T2w&amp;r=1-1w8mU_eFprE2Nn9QnYf01XIV88MOwkXwHYEbF2Y_8&amp;m=VWflpiUtgdiywujOIhhFEf6PRwUiyMJNZSuP3-Vr7Kw&amp;s=JExKN_zNPIAPgqvkqpXn8EaVYDwgZJQdIQKUqOvVj4A&amp;e=" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><o:p>&nbsp;</o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<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://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_accountability-2Dcross-2Dcommunity&amp;d=CwMFaQ&amp;c=Od00qP2XTg0tXf_H69-T2w&amp;r=1-1w8mU_eFprE2Nn9QnYf01XIV88MOwkXwHYEbF2Y_8&amp;m=VWflpiUtgdiywujOIhhFEf6PRwUiyMJNZSuP3-Vr7Kw&amp;s=JExKN_zNPIAPgqvkqpXn8EaVYDwgZJQdIQKUqOvVj4A&amp;e=" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><o:p></o:p></p>
</div>
</div>
<p></p>
<p class="08896adb-c2fb-4148-844c-9246cce7fcdc">&nbsp;</p>
<p>****************************************************************************************************<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>
</body>
</html>