<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 16px; font-family: Calibri, sans-serif;">
<div>
<div>
<div><font face="Calibri">I’d like to add an additional question to the 34 circulated by our attorneys on Sunday. </font></div>
<div><font face="Calibri"><br>
</font></div>
<div><font face="Calibri">I believe the bylaws draft implies that the Human Rights Framework of Interpretation (FOI-HR)
<i>should</i> be a basis for IRP challenges on ICANN action or inaction. I do not believe that is what the CCWG final proposal reflected in <a href="https://community.icann.org/pages/viewpage.action?pageId=58723827&preview=/58723827/58726370/Annex%2006%20-%20FINAL-Revised.pdf" style="color: purple;">Annex
6</a>, where we </font><span style="font-family: Calibri;">proposed this specific bylaws language (para 07):</span></div>
<div><span style="font-family: Calibri;"><br>
</span></div>
<blockquote style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<div><font face="Calibri"><i>“Within its Core Values, ICANN will commit to respect internationally recognized Human Rights as required by applicable law. <span style="background-color: rgb(255, 255, 0);">This provision does not create any additional obligation
for ICANN to respond to or consider any complaint, request, or demand seeking the enforcement of Human Rights by ICANN</span>.”</i><i> </i></font></div>
</blockquote>
<div><font face="Calibri"><br>
</font></div>
<div><font face="Calibri">The new draft bylaws that we are now reviewing has a different implication, at 27.3.(c):</font></div>
<div><span id="OLK_SRC_BODY_SECTION">
<div 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">
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1" style="page: WordSection1;"><font face="Calibri">
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Calibri, sans-serif;">
<o:p></o:p></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<font face="Calibri,sans-serif"> </font><o:p></o:p></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;">
<i><font face="Calibri">No person or entity shall be entitled to invoke the reconsideration process provided in Section 4.2 or the independent review process provided in Section 4.3 with respect to this Section 27.3 for any actions by ICANN or the Board <span style="background-color: rgb(255, 255, 0);">occurring
prior to the date that the conditions set forth in Section 27.3(b) are satisfied</span></font></i></p>
</font></div>
</div>
</div>
</span></div>
<span id="OLK_SRC_BODY_SECTION">
<div dir="auto">
<blockquote type="cite"><font face="Calibri">
<div></div>
</font></blockquote>
</div>
</span>
<div><font face="Calibri">This bylaws draft text implies that the IRP and reconsideration can be used to challenge ICANN actions/inactions based on FOI-HR after it is developed. </font><span style="font-family: Calibri;">I can see why the legal team may
have assumed something like this, because our final report Annex 6 para 19 explanatory text says:</span></div>
<div><font face="Calibri"><br>
</font></div>
<font face="Calibri"><span id="OLK_SRC_BODY_SECTION">
<div 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">
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1" style="page: WordSection1;">
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;">
<i><font face="Calibri">The proposed draft Bylaw also clarifies that no IRP challenges can be made on the grounds of this Bylaw until an <span style="background-color: rgb(255, 255, 0);">FOI-HR is developed and approved as part of Work Stream 2 activities</span>.
It further clarifies that acceptance of the FOI-HR will require the same process as for Work Stream 1 recommendations (as agreed for all Work Stream 2 recommendations</font>).</i></p>
</div>
</div>
</div>
</span><span id="OLK_SRC_BODY_SECTION">
<div 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">
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1" style="page: WordSection1;">
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;">
<br>
</p>
</div>
</div>
</div>
</span><span id="OLK_SRC_BODY_SECTION" style="font-family: Calibri, sans-serif;">
<div 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">
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1" style="page: WordSection1;">But I believe that CCWG made its position clear in our suggested bylaws text, repeated here for convenience:</div>
</div>
</div>
</span>
<div style="font-family: Calibri, sans-serif;"><br>
</div>
</font>
<blockquote style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<div><font face="Calibri"><i>“Within its Core Values, ICANN will commit to respect internationally recognized Human Rights as required by applicable law.<span style="background-color: rgb(255, 255, 0);"> This provision does not create any additional obligation
for ICANN to respond to or consider any complaint, request, or demand seeking the enforcement of Human Rights by ICANN.</span></i><i><span style="background-color: rgb(255, 255, 0);"> </span></i><i>“</i></font></div>
<div><i><font face="Calibri"><br>
</font></i></div>
<div><i><font face="Calibri"><br>
</font></i></div>
</blockquote>
</div>
<div>
<div id="MAC_OUTLOOK_SIGNATURE"></div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:12pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span><<a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a>> on behalf of Mathieu Weill <<a href="mailto:mathieu.weill@afnic.fr">mathieu.weill@afnic.fr</a>><br>
<span style="font-weight:bold">Date: </span>Sunday, April 3, 2016 at 8:16 AM<br>
<span style="font-weight:bold">To: </span>CCWG Accountability <<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>[CCWG-ACCT] Fwd: [bylaws-coord] DRAFT NEW ICANN BYLAWS - 2 April 2016 version<br>
</div>
<div><br>
</div>
<div>
<div dir="auto">
<div><span></span></div>
<div>
<div>Dear colleagues, </div>
<div><br>
</div>
<div>In anticipation of our calls this week, please find below a note from the lawyers group, the draft bylaws as well as an issue list. </div>
<div><br>
</div>
<div>It is important to read the lawyers notes as they quite efficiently describe the context and status of the work. Please review them for any process related question. </div>
<div><br>
</div>
<div>The purpose of our calls this week will be to address the issue list questions (questions 1-7 & 25-34 are for the CCWG, the others for CWG). </div>
<div><br>
</div>
<div>Should any other issue be added to the list based on your respective reviews, please raise your questions on the list for transparency. </div>
<blockquote type="cite">
<div><b>Expéditeur:</b> John Jeffrey via bylaws-coord <<a href="mailto:bylaws-coord@icann.org">bylaws-coord@icann.org</a>><br>
<b>Date:</b> 3 avril 2016 13:16:28 UTC+2<br>
<b>Destinataire:</b> <a href="mailto:bylaws-coord@icann.org">bylaws-coord@icann.org</a><br>
Dear Bylaws Coordination Group,</div>
</blockquote>
<blockquote type="cite">
<div class="">
<p class="MsoNormal">Please find attached a document – DRAFT NEW ICANN BYLAWS (vers. 2Apr) (“DRAFT BYLAWS”) for your review and discussion. As you will recall the last full draft was provided to you on 18 March, with the promise to provide another full turn
of the DRAFT BYLAWS for your review today on 2 April. The DRAFT BYLAWS attached is the current working draft among the legal drafting group. There is also an Issue List attached, which are a set of additional questions and clarifications requested from the
Bylaws Coordination Group.<o:p class=""></o:p></p>
<p class="MsoNormal"><o:p class=""> </o:p>We ask that you share the attachments with your CCWG, ICG and CWG colleagues who will be reviewing this during this critical work week</p>
<p class="MsoNormal"><o:p class=""></o:p></p>
<p class="MsoNormal"><b class=""><u class="">Recent Work</u></b> – During the past two weeks the legal drafting group, made up of Sidley’s team, Adler’s team and ICANN's Legal team reviewed and worked through mark ups and redrafts of the various sections of
new ICANN Bylaws. Also, we have held four separate meetings with the Bylaws Coordination Group during this two-week period asking questions and incorporating that feedback into the new draft. There is likely to be the need for some additional discussions
as we work toward a public comment version of the new ICANN bylaws.</p>
<p class="MsoNormal"><o:p class=""></o:p></p>
<p class="MsoNormal"><b class=""><u class="">More Work to Do</u></b> – There is still work to do on the DRAFT BYLAWS, in identifying and working through any remaining provisions in the draft that are not clear, finding any remaining open issues, improving the
provisions, and polishing the draft before publication for public comment. The legal teams remain engaged in review mode and are available for questions and comments during this period.</p>
<p class="MsoNormal"><o:p class=""></o:p></p>
<p class="MsoNormal"><b class=""><u class="">Legal Teams have not yet “certified”</u></b> – Since a) the Bylaws Coordination Group, CWG and CCWG have not yet reviewed and reacted to these DRAFT BYLAWS, b) there are still remaining open issues, and c) there
is still review and polishing to be done by the legal teams – the legal teams have not indicated yet that the current DRAFT BYLAWS fully meets the recommendations within the Proposals.</p>
<p class="MsoNormal"><o:p class=""></o:p></p>
<p class="MsoNormal">As we have indicated above there is still work to be done, including receiving the feedback from those reviewing these DRAFT BYLAWS this week before the legal teams will be in a position to certify the posting version for Public Comment</p>
<p class="MsoNormal"><o:p class=""></o:p></p>
<p class="MsoNormal"><b class=""><u class="">Next Steps</u></b> –</p>
<p class="MsoNormal"><o:p class=""></o:p></p>
<p class="MsoNormal">1) <i class="">Now until 13 April</i> – members of CCWG, CWG, Bylaws Coordination Group, Board and ICG to complete review of these DRAFT BYLAWS and provide feedback to legal teams;</p>
<p class="MsoNormal"><o:p class=""></o:p></p>
<p class="MsoNormal">2) <i class="">Now until 18 April</i>, (with particular focus during week of 13-18 April) – legal teams to update DRAFT BYLAWS working in coordination with the Bylaws Drafting Group;</p>
<p class="MsoNormal"><o:p class=""></o:p></p>
<p class="MsoNormal">3) <i class="">20 April</i> – posting date for public comment period for new proposed bylaws – with legal teams supporting that the new proposed bylaws meets the proposal recommendations.</p>
<p class="MsoNormal"><o:p class=""></o:p></p>
<p class="MsoNormal">———</p>
<p class="MsoNormal">As before, we look forward to working with all of you in the coming days, to get ICANN’s Bylaws in the best form possible to effectuate these important changes.</p>
<p class="MsoNormal"><o:p class=""></o:p></p>
<p class="MsoNormal">We hope these views of the documents are useful and that you receive them in the spirit that they are offered… to help all of us to be able to collaborate and work through these Bylaws changes in the most effective way possible — to enable
the creation of a new and stronger, community empowered ICANN.</p>
<p class="MsoNormal">John Jeffrey, Holly Gregory, and Rosemary Fei</p>
<p class="MsoNormal"><o:p class=""></o:p></p>
</div>
</blockquote>
<blockquote type="cite">
<div></div>
</blockquote>
</div>
<div></div>
</div>
</div>
</span>
</body>
</html>