<html>
<head>
<!-- Template generated by Exclaimer Mail Disclaimers on 08:26:57 Wednesday, 13 April 2016 -->
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css">P.6b122071-efbf-411a-ac9c-6ea26856e8ab {
        MARGIN: 0cm 0cm 0pt
}
LI.6b122071-efbf-411a-ac9c-6ea26856e8ab {
        MARGIN: 0cm 0cm 0pt
}
DIV.6b122071-efbf-411a-ac9c-6ea26856e8ab {
        MARGIN: 0cm 0cm 0pt
}
TABLE.6b122071-efbf-411a-ac9c-6ea26856e8abTable {
        MARGIN: 0cm 0cm 0pt
}
DIV.Section1 {
        page: Section1
}
</style><style>
<!--
@font-face
        {font-family:Wingdings}
@font-face
        {font-family:Wingdings}
@font-face
        {font-family:Calibri}
@font-face
        {font-family:"Source Sans Pro"}
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif"}
h1
        {margin-right:0cm;
        margin-left:0cm;
        font-size:24.0pt;
        font-family:"Times New Roman","serif";
        font-weight:bold}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
        {color:purple;
        text-decoration:underline}
p
        {margin-right:0cm;
        margin-left:0cm;
        font-size:12.0pt;
        font-family:"Times New Roman","serif"}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {margin-top:0cm;
        margin-right:0cm;
        margin-bottom:0cm;
        margin-left:36.0pt;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif"}
span.Titre1Car
        {font-family:"Cambria","serif";
        color:#365F91;
        font-weight:bold}
span.fa
        {}
span.EmailStyle20
        {font-family:"Calibri","sans-serif";
        color:#1F497D}
.MsoChpDefault
        {font-size:10.0pt}
@page WordSection1
        {margin:70.85pt 70.85pt 70.85pt 70.85pt}
div.WordSection1
        {}
ol
        {margin-bottom:0cm}
ul
        {margin-bottom:0cm}
-->
</style>
</head>
<body lang="FR" link="blue" vlink="purple">
<p class="6b122071-efbf-411a-ac9c-6ea26856e8ab">Matthieu, we are feeding our significant edits to ICANN Legal to include in next draft. I have no clear idea when the next draft will circulate and I don't know how close to final it will be -- that depends on
whether our edits are accepted as is or whether there is negotiation. It also depends on when we get the comments from CCWG. We will need at least 48 hours to review a very close to final draft before we can certify. Holly.
<br>
<br>
<br>
<br>
Sent with Good (www.good.com)<br>
<strong></p>
<div><font face="Tahoma" color="#000000" size="2"> </font></div>
</strong>
<hr tabindex="-1">
<font face="Tahoma" size="2"><b>From:</b> bylaws-coord-bounces@icann.org on behalf of Mathieu Weill via bylaws-coord<br>
<b>Sent:</b> Wednesday, April 13, 2016 07:17:33 AM<br>
<b>To:</b> bylaws-coord@icann.org<br>
<b>Subject:</b> [bylaws-coord] Update requested on overall project plan<br>
</font><br>
<div></div>
<div>
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Dear Colleagues,</span><span lang="EN-US"></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">As we finalize our feedbacks to the legal teams on the draft Bylaws, and the legal teams are working full steam, the respective groups rightfully
start asking questions about the next steps. I read with interest Akram’s blog (</span><span style="font-size:10.5pt; font-family:"Source Sans Pro","sans-serif"; color:black"><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blog_building-2Dan-2Denhanced-2Dcommunity-2Dempowered-2Dicann&d=CwMFaQ&c=Od00qP2XTg0tXf_H69-T2w&r=1-1w8mU_eFprE2Nn9QnYf01XIV88MOwkXwHYEbF2Y_8&m=BeMR2NiW9uUNVm2x0LKEAykzMvoeRpFg8nC9kdxYgIk&s=jvdDDgKA-8tJMLSyfUGyOpZ9YO0TgcBInon1UtOa3lQ&e="><span lang="EN-US">https://www.icann.org/news/blog/building-an-enhanced-community-empowered-icann</span></a></span><span lang="EN-US" style="font-size:10.5pt; font-family:"Source Sans Pro","sans-serif"; color:#1F497D">),
which confirms the previous plan of launching a call for comments on the draft Bylaws on April 20. I assume this was taking into account the various comments from the CWG and CCWG.
</span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">In order to avoid any miscommunication when responding to community members requests, I believe we would benefit from an update on the overall
project plan, including (and maybe not limited to) : </span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"><span style="">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Whether the groups or leaderships will be given an opportunity to review the next version of Bylaws before publication on Apr 20 ?</span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"><span style="">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">When in the process would the lawyers be in a position to provide a certification to the groups that the Bylaws accurately reflect the reports’
requirements ? </span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"><span style="">-<span style="font:7.0pt "Times New Roman"">
</span></span></span><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">If and when it will be expected from the CWG and CCWG, as well as the operational communities maybe, to issue a formal statement on the Bylaws
? </span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Finally, a statement in Akram’s blog struck me as a shift from our previous discussions. The blog states “The Bylaws will only become effective
upon the successful completion of the transition.” I was under the impression in Marrakech that only the subset of Bylaws that are related to the IANA contract expiring would see its effectiveness delayed until the transition. I would appreciate clarification
here whether this intent has changes, and what is the rationale. </span></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt; font-family:"Source Sans Pro","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt; font-family:"Source Sans Pro","sans-serif"; color:#1F497D">Thanks in advance for sharing this update with this group, the tighter the deadline, the more critical it is to share up to date information
amongst ourselves. </span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Best,</span></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p></p>
<p class="6b122071-efbf-411a-ac9c-6ea26856e8ab"> </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>