<p dir="ltr">Perhaps we should get clarification on what "herein" mean in legal terms. However in simple English, I will assume that it means anything provided in the bylaw relating to HR and since no such text is provided yet(pending the FoI) then I don't think any obligation would be applicable.</p>
<p dir="ltr">However, if "herein" implies that ICANN's commitment to HR will/can be tested/challenged upon every action/process defined in the bylaw then I am in strong agreement with Brett.</p>
<p dir="ltr">Regards<br>
Sent from my LG G4<br>
Kindly excuse brevity and typos</p>
<div class="gmail_quote">On 8 May 2016 21:01, "Schaefer, Brett" <<a href="mailto:Brett.Schaefer@heritage.org">Brett.Schaefer@heritage.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm confused. Wouldn't this text allow for the HR WS2 process to create human rights obligations for ICANN?<br>
<br>
<br>
Lawyers’ Comment: The draft CCWG comment letter does not include a recommendation regarding the last sentence of Draft Bylaws Section 1.2(b)(viii), which ends, “except as provided herein.” We suggest that the CCWG recommend that the sentence be modified to refer to Section 27.3 of the Draft Bylaws so that it reads: “This Core Value does not create and shall not be interpreted to create any additional obligations for ICANN and shall not obligate ICANN to respond to or consider any complaint, request or demand seeking the enforcement of human rights by ICANN, except as provided in Section 27.3.”<br>
<br>
I thought that the CCWG was clear that there should be no circumstances in which ICANN should be obligated to respond to or consider any complaint, request or demand seeking the enforcement of human rights. Why are we creating the possibility for exceptions? The clause should be deleted.<br>
<br>
________________________________<br>
Brett Schaefer<br>
Jay Kingham Senior Research Fellow in International Regulatory Affairs<br>
Margaret Thatcher Center for Freedom Davis Institute for National Security and Foreign Policy<br>
The Heritage Foundation<br>
214 Massachusetts Avenue, NE<br>
Washington, DC 20002<br>
202-608-6097<br>
<a href="http://heritage.org" rel="noreferrer" target="_blank">heritage.org</a><<a href="http://heritage.org/" rel="noreferrer" target="_blank">http://heritage.org/</a>><br>
<br>
__________<br>
<br>
On May 7, 2016, at 1:32 PM, Grapsas, Rebecca <<a href="mailto:rebecca.grapsas@sidley.com">rebecca.grapsas@sidley.com</a><mailto:<a href="mailto:rebecca.grapsas@sidley.com">rebecca.grapsas@sidley.com</a>>> wrote:<br>
<br>
Holly Gregory asked that I forward the email below. Please post to the CCWG and BCG lists on her behalf.<br>
<br>
<br>
Dear CCWG-ACCT Co-Chairs, Members, Participants, and ICANN Staff,<br>
<br>
Attached please find comments from Sidley and Adler on the CCWG’s Comments on Draft New ICANN Bylaws (tracked changes in Word and PDF).<br>
<br>
Please note that we have serious concerns around comments 9 and 10 and believe that, as currently stated, they are based on misreadings of the draft Bylaws in the relation to the CCWG Proposal.<br>
<br>
Kind regards,<br>
<br>
Holly and Rosemary<br>
<br>
HOLLY J. GREGORY<br>
Partner and Co-Chair<br>
Corporate Governance & Executive Compensation Practice Group<br>
Sidley Austin LLP<br>
787 Seventh Avenue<br>
New York, NY 10019<br>
<a href="tel:%2B1%20212%20839%205853" value="+12128395853">+1 212 839 5853</a><br>
<a href="mailto:holly.gregory@sidley.com">holly.gregory@sidley.com</a><mailto:<a href="mailto:holly.gregory@sidley.com">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>
<br>
<br>
<br>
****************************************************************************************************<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>
****************************************************************************************************<br>
<br>
<CCWG Comments on Draft New ICANN Bylaws - Sidley Adler Comments May 7, 2016.pdf><br>
<CCWG Comments on Draft New ICANN Bylaws - Sidley Adler Comments, May 7, ....docx><br>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><mailto:<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>
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>
</blockquote></div>