<div dir="ltr"><div class="gmail_extra"><div><div><br></div></div>
<br><div class="gmail_quote">On Wed, Nov 11, 2015 at 12:13 AM, Avri Doria <span dir="ltr"><<a href="mailto:avri@acm.org" target="_blank">avri@acm.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi,<br>
<br>
Thanks for this review.<br>
<br>
I have just had the opportunity to read the so-clle "Executive summary"<br>
and appreciate many of the comments that are being made. I am obviously<br>
too late to review this in any detail and did a quick read through of<br>
this commented version. I do want to add to the impression that is a<br>
long way from being ready for distribution.<br>
<br>
Some areas that troubled me in my quick read:<br>
<br>
- the absence of any discussion of how these changes complete the<br>
requirements for transition in terms of separability and enforcing<br>
separability decisions by the empowered community.<br></blockquote><div><br></div><div><br></div><div>Thanks Avri for noting this and to both counsel for highlighting it. The abscence of discussion of this community power in the draft, with only a single line mentioning it and no explanation (or even a reference) of how it is proposed to work is a huge gap. </div><div><br></div><div>Thank you,</div><div><br></div><div>Brenden Kuerbis</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
- the lack of discussion of how, without statutory authority, the<br>
empowered community still has recourse to the courts if necessary that<br>
can withstand the withering influence of so-called fiduciary decisions<br>
by the board<br>
- the absence of any discussion of how the statutory membership right of<br>
inspection is to be included under the empowered community model<br>
- a reference in regard to human rights that while there were no<br>
statutory obligations on ICANN, the backstop of NTIA was assurance that<br>
human rights, especially those for freedom of expression and free flow<br>
in information on the Internet, would be respected, and that the bylaw<br>
is a way to attempt to replace that NTIA backstop.<br>
<br>
As this document stands I do not see it as explaining why these<br>
accountability issues are necessary when, and if, the NTIA backstop is<br>
lost. I think that is essential in an "executive summary", not matter<br>
what its length.<br>
<br>
Thanks<br>
<br>
avri<br>
<div><div><br>
<br>
On 10-Nov-15 22:53, Rosemary E. Fei wrote:<br>
><br>
> Dear Co-Chairs:<br>
><br>
> Adler & Colvin’s comments on the Executive Summary are attached; our<br>
> apologies for missing the deadline (by 110 minutes). As Holly noted,<br>
> these comments have not been reviewed by or coordinated with Sidley.<br>
> Similarly, we have not had time to go back through proposals, emails,<br>
> and meeting notes to confirm our recollection of how various decisions<br>
> have been made to date, so some comments may reflect the wrong<br>
> understanding and should be ignored. The mark-up includes both some<br>
> line edits, and comments in bubbles. We attach a PDF, to ensure the<br>
> comment bubbles will be visible regardless of users’ software.<br>
><br>
> We agree with Sidley’s overall comments on length and duplication, and<br>
> more substantively on how particular community powers will be<br>
> exercised. Given that this is an Executive Summary, you might<br>
> consider presenting a single full escalation pathway as an<br>
> illustration only, and then note that the paths will vary as<br>
> appropriate for the exercise of other community powers. A chart<br>
> comparing escalation pathways across powers and noting the differing<br>
> required thresholds for approval at each stage by power, might be more<br>
> useful to understanding than the separate detailed descriptions of<br>
> each escalation path provided in this draft.<br>
><br>
> Please let us know how we may assist you further.<br>
><br>
> Rosemary<br>
><br>
> Rosemary E. Fei<br>
> Adler & Colvin<br>
> 235 Montgomery Street, Suite 1220<br>
> San Francisco, CA 94104<br>
> <a href="tel:415%2F421-7555" value="+14154217555" target="_blank">415/421-7555</a> (phone)<br>
> <a href="tel:415%2F421-0712" value="+14154210712" target="_blank">415/421-0712</a> (fax)<br>
> <a href="mailto:rfei@adlercolvin.com" target="_blank">rfei@adlercolvin.com</a><br>
> <a href="http://www.adlercolvin.com" rel="noreferrer" target="_blank">www.adlercolvin.com</a><br>
><br>
><br>
><br>
><br>
><br>
> _____________________________<br>
><br>
> Adler & Colvin is a San Francisco Green Business certified by the City<br>
> and County of San Francisco. Please consider the environment before<br>
> you print this email.<br>
><br>
><br>
><br>
</div></div>> *From: *<<a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank">accountability-cross-community-bounces@icann.org</a><br>
> <mailto:<a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank">accountability-cross-community-bounces@icann.org</a>>> on behalf<br>
> of "Gregory, Holly" <<a href="mailto:holly.gregory@sidley.com" target="_blank">holly.gregory@sidley.com</a><br>
> <mailto:<a href="mailto:holly.gregory@sidley.com" target="_blank">holly.gregory@sidley.com</a>>><br>
> *Date: *Tuesday 10 November 2015 at 8:37 p.m.<br>
> *To: *"<a href="mailto:mathieu.weill@afnic.fr" target="_blank">mathieu.weill@afnic.fr</a> <mailto:<a href="mailto:mathieu.weill@afnic.fr" target="_blank">mathieu.weill@afnic.fr</a>>"<br>
> <<a href="mailto:mathieu.weill@afnic.fr" target="_blank">mathieu.weill@afnic.fr</a> <mailto:<a href="mailto:mathieu.weill@afnic.fr" target="_blank">mathieu.weill@afnic.fr</a>>>,<br>
> "<a href="mailto:thomas@rickert.net" target="_blank">thomas@rickert.net</a> <mailto:<a href="mailto:thomas@rickert.net" target="_blank">thomas@rickert.net</a>>" <<a href="mailto:thomas@rickert.net" target="_blank">thomas@rickert.net</a><br>
> <mailto:<a href="mailto:thomas@rickert.net" target="_blank">thomas@rickert.net</a>>>, "<a href="mailto:leonfelipe@sanchez.mx" target="_blank">leonfelipe@sanchez.mx</a><br>
> <mailto:<a href="mailto:leonfelipe@sanchez.mx" target="_blank">leonfelipe@sanchez.mx</a>>" <<a href="mailto:leonfelipe@sanchez.mx" target="_blank">leonfelipe@sanchez.mx</a><br>
> <mailto:<a href="mailto:leonfelipe@sanchez.mx" target="_blank">leonfelipe@sanchez.mx</a>>><br>
> *Cc: *Sidley ICANN CCWG <<a href="mailto:sidleyicannccwg@sidley.com" target="_blank">sidleyicannccwg@sidley.com</a><br>
> <mailto:<a href="mailto:sidleyicannccwg@sidley.com" target="_blank">sidleyicannccwg@sidley.com</a>>>, "ACCT-Staff<br>
> (<a href="mailto:acct-staff@icann.org" target="_blank">acct-staff@icann.org</a> <mailto:<a href="mailto:acct-staff@icann.org" target="_blank">acct-staff@icann.org</a>>)"<br>
> <<a href="mailto:acct-staff@icann.org" target="_blank">acct-staff@icann.org</a> <mailto:<a href="mailto:acct-staff@icann.org" target="_blank">acct-staff@icann.org</a>>>,<br>
> "<a href="mailto:ICANN@adlercolvin.com" target="_blank">ICANN@adlercolvin.com</a> <mailto:<a href="mailto:ICANN@adlercolvin.com" target="_blank">ICANN@adlercolvin.com</a>>"<br>
> <<a href="mailto:ICANN@adlercolvin.com" target="_blank">ICANN@adlercolvin.com</a> <mailto:<a href="mailto:ICANN@adlercolvin.com" target="_blank">ICANN@adlercolvin.com</a>>>, Accountability<br>
> Cross Community <<a href="mailto:accountability-cross-community@icann.org" target="_blank">accountability-cross-community@icann.org</a><br>
> <mailto:<a href="mailto:accountability-cross-community@icann.org" target="_blank">accountability-cross-community@icann.org</a>>><br>
> *Subject: *[CCWG-ACCT] Sidley Comments on Executive Summary Draft<br>
<span>><br>
><br>
><br>
> Dear Co-Chairs and CCWG,<br>
><br>
><br>
><br>
> Attached please find Sidley’s comments on the draft Executive<br>
> Summary. Given the very short window for review we have not had time<br>
> to coordinate our comments with the Adler firm and apologize for<br>
> that. Adler will be sending their comments separately. Please note<br>
> also that given the very short time frame we have not been able to go<br>
> back and check against the transcripts of the various meetings and<br>
> therefore are relying on memory for our understanding of where the<br>
> CCWG has formed consensus (or near consensus) on various issues.<br>
><br>
><br>
><br>
> Overall we find the Executive Summary overly long with significant<br>
> redundancies. We think it would benefit from a thorough edit by your<br>
> professional writers. We also believe that the summary is inaccurate<br>
> in its description of the community processes with respect to the<br>
> decisions to: (1) remove individual directors and (2) approve<br>
> Fundamental Bylaws. (We agree with Jordan’s comments on the<br>
> Fundamental Bylaws.) We also recommend that a more pointed discussion<br>
> of the CWG dependencies be added so that the reader can understand the<br>
> broader context in which the Proposal has been developed. We have<br>
> also edited errors in the description of the legal framework that<br>
> applies. We have noted these comments in the draft.<br>
><br>
><br>
><br>
> Please let us know if you would like to discuss or if we can be of<br>
> further assistance with this draft.<br>
><br>
><br>
><br>
> Kind regards,<br>
><br>
> Holly<br>
><br>
><br>
><br>
</span>> *HOLLY* *J. GREGORY*<br>
<span>> Partner and Co-Chair<br>
> Corporate Governance & Executive Compensation Practice Group<br>
><br>
</span>> *Sidley Austin LLP*<br>
<span>> 787 Seventh Avenue<br>
> New York, NY 10019<br>
> <a href="tel:%2B1%20212%20839%205853" value="+12128395853" target="_blank">+1 212 839 5853</a><br>
</span>> <a href="mailto:holly.gregory@sidley.com" target="_blank">holly.gregory@sidley.com</a> <mailto:<a href="mailto:holly.gregory@sidley.com" target="_blank">holly.gregory@sidley.com</a>><br>
> <a href="http://www.sidley.com" rel="noreferrer" target="_blank">www.sidley.com</a> <<a href="http://www.sidley.com/" rel="noreferrer" target="_blank">http://www.sidley.com/</a>><br>
><br>
> <a href="http://www.sidley.com/files/upload/signatures/SA-autosig.png" rel="noreferrer" target="_blank">http://www.sidley.com/files/upload/signatures/SA-autosig.png</a><br>
> <<a href="http://www.sidley.com/" rel="noreferrer" target="_blank">http://www.sidley.com/</a>> *SIDLEY AUSTIN LLP*<br>
<span>><br>
><br>
><br>
><br>
><br>
><br>
><br>
> ****************************************************************************************************<br>
> This e-mail is sent by a law firm and may contain information that is<br>
> privileged or confidential.<br>
> If you are not the intended recipient, please delete the e-mail and<br>
> any attachments and notify us<br>
> immediately.<br>
><br>
> ****************************************************************************************************<br>
><br>
><br>
><br>
</span>> _______________________________________________<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://mm.icann.org/mailman/listinfo/accountability-cross-community" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br>
<br>
---<br>
This email has been checked for viruses by Avast antivirus software.<br>
<a href="https://www.avast.com/antivirus" rel="noreferrer" target="_blank">https://www.avast.com/antivirus</a><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://mm.icann.org/mailman/listinfo/accountability-cross-community" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
</blockquote></div><br></div></div>