<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">I think this addresses a piece of the problem, and its good as far as it goes. However, it leaves most of the problem untouched. Aside from the IRP, how is ICANN supposed to determine if its conduct violates the Bylaw before the Framework of Interpretation is available? How is the community (or portions of the community) supposed to determine if its conduct violates the Bylaw before the FoI is available? What happens if new policies or programs or reviews are proposed based on the new HR Bylaw? What happens when the Framework of Interpretation comes on the scene after a year of ad hoc interpretation of the Bylaw?</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">While there are not an unlimited number of variables, there were sufficient and significantly different possibilities discussed in WP4 and the CCWG that the work of WS2, and particularly the FoI, was commissioned.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">One answer is that the Human Rights bylaw simply should not be applied until its implementation is clarified by the FoI. But what if there is a truly egregious Human Rights violation being considered, where there is no disagreement in the community that it is indeed a violation, no matter what standard or interpretation is being used? (It's kind of hard to believe that ICANN would consider such an egregious violation, but nothing's impossible.) That would seem to be an easy case. But what if the ICANN Board believes and demonstrates to its own satisfaction that it is not heading into a Human Rights violation? Does the Board get the final word (at least until the FOI is in place)? What if some stakeholders see a Bylaws violation and others don't? How is this resolved? Does the Bylaw change how that difference would be resolved today?</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">I suppose the answer could be that (1) we are reaffirming ICANN's commitment to Human Rights, not asking it to make new and different commitments to Human Rights, and (2) we are replacing the backstop of the US Government (as Avri points out) rather than creating a new and different Human Rights regime within ICANN. Both of the tenets indicate that what ICANN has been doing to date is consistent with its Human Rights obligations, and thus that extensive new work is not called for. At the same time, it maintains ICANN's Human Rights commitments as a bulwark against degradation of ICANN's [existing] Human Rights standards. These two tenets could be used to guide both WS2 and any interpretation of the Bylaw during the interim period before the FoI is in place. While these two tenets seem solidly consistent with our work to date, I don't believe they are stated as guidance in our Proposal. (If they are, that's great.) However, if these seem controversial to some, perhaps we need to wait until the FoI is in place and there is an agreement on how to interpret the Bylaw before we use it at all. I think this all feeds back into our discussion of Options "a", "b" and "c."</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Greg</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 20, 2016 at 9:59 PM, León Felipe Sánchez Ambía <span dir="ltr"><<a href="mailto:leonfelipe@sanchez.mx" target="_blank">leonfelipe@sanchez.mx</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Dear Holly, dear Rosemary,<div><br></div><div>Thank you very much for this update.</div><div><br></div><div>I believe the suggested amendment does address concerns on both sides but I would like to, of course, hear the feedback from the larger group.</div><div><br></div><div>All,</div><div><br></div><div>The suggested text would, in my view, guarantee that a commitment to respect human rights is in place as part of WS1 and would also provide the safeguard to avoid the abuse of the bylaw in the meantime the FOI is developed. </div><div><br></div><div>Please share your feedback at your earliest convenience so we can continue our way forward on this issue and hopefully finalize it in the next call we include the item as part of our agenda.</div><div><br></div><div>Thanks to our legal team and ICANN’s legal team for helping us understand the different concerns around the issue and proposing a way forward.</div><div><br><div>
<div>Saludos,</div><div><br></div><div><br></div><div><br></div><div>León</div>
</div>
<br><div><blockquote type="cite"><span class=""><div>El 20/01/2016, a las 8:40 p.m., Gregory, Holly <<a href="mailto:holly.gregory@sidley.com" target="_blank">holly.gregory@sidley.com</a>> escribió:</div><br></span><div><p style="margin:0cm 0cm 0pt;font-size:12pt;font-family:'Times New Roman',serif;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"></p><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span class=""><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:16pt;font-family:Calibri,sans-serif">Dear CCWG-ACCT Co-Chairs, Members, Participants and ICANN Staff, <u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:16pt;font-family:Calibri,sans-serif"><u></u> <u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:16pt;font-family:Calibri,sans-serif">We had a good discussion with ICANN lawyers (Sam and John) and with Kevin Espinola of Jones Day today as was certified to us regarding the Board’s understanding of the Human Rights language that we had proposed (set forth below). As we now understand the Board’s concern, while the language we proposed would not create any additional responsibilities beyond what currently exists in applicable law, providing a Human Rights commitment in the Bylaws opens the range of human rights topics to IRP challenge where Board action or inaction is perceived by someone to be out of line with human rights obligations under applicable law. Without benefit of the further definition around the scope of ICANN’s human rights obligations (the Framework for Interpretation) planned for Work Stream 2, in the interim there could be a slew of IRP challenges that have little actual merit from a legal perspective, placing the IRP panel (which may be comprised of persons without significant human rights law understanding) in a position of arbitrating a wide range of issues that may be driven by divergent interests that have little relevance to ICANN. This could result in a significant use of ICANN time and attention and scarce IRP resources with little actual added value in holding ICANN accountable. <u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:16pt;font-family:Calibri,sans-serif">This is a legitimate concern. One solution that is in line with the discussion around options from the last CCWG call is to assure that the IRP process is not available until the Work Stream 2 effort to further articulate the human rights Framework for Interpretation is finished. <u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:16pt;font-family:Calibri,sans-serif"><u></u> <u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:16pt;font-family:Calibri,sans-serif">The CCWG may wish to consider including in the Bylaws something along the following lines (the language in<span> </span><b><span style="color:rgb(192,0,0)">red</span></b><span> </span>is new; the language in black is essentially what we had proposed originally) :<u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:16pt;font-family:Calibri,sans-serif"><u></u> <u></u></span></div></span><div style="margin:0in 0in 0.0001pt 0.5in;font-size:12pt;font-family:'Times New Roman',serif"><i><span style="font-size:16pt;font-family:Calibri,sans-serif">Within its Mission and in its operations, ICANN will respect</span></i><span style="font-size:16pt;font-family:Calibri,sans-serif"><i>internationally recognized Human Rights. This commitment shall not</i><span> </span><i>in any way create an obligation for ICANN, or any entity having a</i><span> </span><i>relationship with ICANN, to protect or enforce Human Rights beyond</i><span> </span><i>what may be required by applicable law. In particular, this does not</i><span> </span><i>create any additional obligation for ICANN to respond to or consider</i><span> </span><i>any complaint, request, or demand seeking the enforcement of</i><span> </span><i>Human Rights by ICANN.<span> </span><b><span style="color:rgb(192,0,0)">This Bylaw provision<span> </span></span></b></i><b><span style="color:rgb(192,0,0)">is not a valid basis for, and shall not give rise to, any IRP<i><span> </span>process</i><span> </span><i>until a Framework of Interpretation is developed as part of “Work Stream 2” by the CCWG-Accountability or another Cross Community Working Group chartered for such</i><span> </span><i>purpose by one or more Supporting Organizations or Advisory Committees.<span> </span></i><i>I</i></span></b></span><b><i><span style="font-size:16pt;font-family:Calibri,sans-serif;color:rgb(192,0,0)">CANN shall support the establishment and work of such a Group to facilitate development of the Framework of Interpretation as promptly as possible.</span></i></b><b><span style="font-size:16pt;font-family:Calibri,sans-serif;color:rgb(192,0,0)"><u></u><u></u></span></b></div><span class=""><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><b><span style="font-size:16pt;font-family:Calibri,sans-serif;color:rgb(192,0,0)"><u></u> <u></u></span></b></div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:16pt;font-family:Calibri,sans-serif">Note that if the CCWG decides to move in this direction, Annex 12 (Work Stream 2) should include a reference to the commitment in the last sentence.<u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:16pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:16pt;font-family:Calibri,sans-serif">Kind regards,<u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><b><i><span style="font-size:16pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></i></b></div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:16pt;font-family:Calibri,sans-serif">Holly and Rosemary<u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt 0.5in;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:16pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></div><div style="margin:0in 0in 0.0001pt 0.5in;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:16pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></div><div style="margin:0in 0in 0.0001pt 1.5in;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:16pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><b><span style="font-size:16pt;font-family:Arial,sans-serif;color:rgb(31,73,125)">HOLLY J. GREGORY</span></b><span style="font-size:16pt;font-family:Arial,sans-serif;color:rgb(31,73,125)"><br>Partner and Co-Chair<br>Global Corporate Governance & Executive Compensation Practice<u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><b><span style="font-size:16pt;font-family:Arial,sans-serif;color:rgb(31,73,125)">Sidley Austin LLP<br></span></b><span style="font-size:16pt;font-family:Arial,sans-serif;color:rgb(31,73,125)"><a href="tel:%2B1%20212%20839%205853" value="+12128395853" target="_blank">+1 212 839 5853</a><br><a href="mailto:holly.gregory@sidley.com" title="Click to send email to Gregory, Holly" style="color:purple;text-decoration:underline" target="_blank">holly.gregory@sidley.com</a></span><span style="font-size:16pt"><u></u><u></u></span></div><p style="margin-right:0in;margin-left:2.5in;font-size:12pt;font-family:'Times New Roman',serif"><u></u> <u></u></p><p style="margin-right:0in;margin-left:2.5in;font-size:12pt;font-family:'Times New Roman',serif"><u></u> <u></u></p></span></div><span class=""><div style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:'Times New Roman',serif;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br></div><p style="margin:0cm 0cm 0pt;font-size:12pt;font-family:'Times New Roman',serif;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"> </p><p style="margin-right:0in;margin-left:0in;font-size:12pt;font-family:'Times New Roman',serif;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">****************************************************************************************************<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></span></div></blockquote></div><br></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></div>