<p dir="ltr">Dear Co-Chairs,</p>
<p dir="ltr">I have had a second read on the legal team statement and like to raise a process issue here:</p>
<p dir="ltr"><Quote><br>
</p>
<blockquote><p dir="ltr">the legal teams have not indicated yet that the current DRAFT BYLAWS fully meets the recommendations within the Proposals<br>
</p>
</blockquote>
<p dir="ltr"><End quote></p>
<p dir="ltr">I believe the essence of encouraging a combination of CCWG legal and ICANN legal is to ensure that the spirit/intent of proposal is adequately covered in that the CCWG legal ensures the bylaw reflects the intent of the proposal while ICANN legal ensures that the draft bylaw DID not exceed the scope that has been defined by the proposal approved by the ICANN board for onward forwarding to NTIA.</p>
<p dir="ltr">I don't think it's all helpful to be reviewing a document that has not be agreed to by the DUO to accurately reflect the intent of the proposal(s). The idea is that if such action has happened prior to the CCWG/CWG looking at the draft then there will be less possibility of missing critical parts of the document.</p>
<p dir="ltr">In view of this, I will strongly suggest at least 1 week between the certification by legal team and publication for public comments. Based on the timeline indicated, this will mean that publication for PC will happen 27th at the earliest. This is to ensure that the CCWG and CWG looks into the certified copy before publishing for PC. (Infact that has usually been the approach during the proposal development as the CCWG always have time for review before publishing)</p>
<p dir="ltr">Regards</p>
<p dir="ltr">Sent from my LG G4<br>
Kindly excuse brevity and typos</p>
<div class="gmail_quote">On 3 Apr 2016 15:45, "Seun Ojedeji" <<a href="mailto:seun.ojedeji@gmail.com">seun.ojedeji@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Thanks for sharing this Mathieu, considering the signatories in the footer it implies that the draft document shared was prepared in conjunction with ICANN legal. It's really important approach and hopefully will save us lots of time at this stage. </p>
<p dir="ltr">On another note, I will also like to add my voice (as tiny as it may be) to request a side by side comparison of current vs proposed bylaw changes.</p>
<p dir="ltr">Regards</p>
<p dir="ltr">Sent from my LG G4<br>
Kindly excuse brevity and typos</p>
<div class="gmail_quote">On 3 Apr 2016 13:17, "Mathieu Weill" <<a href="mailto:mathieu.weill@afnic.fr" target="_blank">mathieu.weill@afnic.fr</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><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><div><br></div><div>Best regards,<br><br><div>Mathieu</div><div>---------------</div><div>Depuis mon mobile, désolé pour le style</div></div><div><br>Début du message transféré :<br><br></div><blockquote type="cite"><div><b>Expéditeur:</b> John Jeffrey via bylaws-coord <<a href="mailto:bylaws-coord@icann.org" target="_blank">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" target="_blank">bylaws-coord@icann.org</a><br><b>Cc:</b> "Flanagan, Sharon" <<a href="mailto:sflanagan@sidley.com" target="_blank">sflanagan@sidley.com</a>>, "Cc: Zagorin, Janet S." <<a href="mailto:jzagorin@sidley.com" target="_blank">jzagorin@sidley.com</a>>, "Hilton, Tyler" <<a href="mailto:thilton@sidley.com" target="_blank">thilton@sidley.com</a>>, ICANN-Adler <<a href="mailto:ICANN@adlercolvin.com" target="_blank">ICANN@adlercolvin.com</a>>, "Hofheimer, Joshua T." <<a href="mailto:jhofheimer@sidley.com" target="_blank">jhofheimer@sidley.com</a>>, "Mohan, Vivek" <<a href="mailto:vivek.mohan@sidley.com" target="_blank">vivek.mohan@sidley.com</a>>, "Clark, Michael A." <<a href="mailto:mclark@sidley.com" target="_blank">mclark@sidley.com</a>>, "Boucher, Rick" <<a href="mailto:rboucher@sidley.com" target="_blank">rboucher@sidley.com</a>>, Sidley ICANN CCWG <<a href="mailto:sidleyicannccwg@sidley.com" target="_blank">sidleyicannccwg@sidley.com</a>>, "Kerry, Cameron" <<a href="mailto:ckerry@sidley.com" target="_blank">ckerry@sidley.com</a>>, "McNicholas, Edward R." <<a href="mailto:emcnicholas@sidley.com" target="_blank">emcnicholas@sidley.com</a>>, Daniel Halloran <<a href="mailto:daniel.halloran@icann.org" target="_blank">daniel.halloran@icann.org</a>>, Amy Stathos <<a href="mailto:amy.stathos@icann.org" target="_blank">amy.stathos@icann.org</a>>, "Boelter, Jessica C.K." <<a href="mailto:jboelter@sidley.com" target="_blank">jboelter@sidley.com</a>>, "Fuller, Miles" <<a href="mailto:wfuller@sidley.com" target="_blank">wfuller@sidley.com</a>>, "Tam, Tennie H." <<a href="mailto:tennie.tam@sidley.com" target="_blank">tennie.tam@sidley.com</a>><br><b>Objet:</b> <b>[bylaws-coord] DRAFT NEW ICANN BYLAWS - 2 April 2016 version</b><br><b>Répondre à:</b> John Jeffrey <<a href="mailto:john.jeffrey@icann.org" target="_blank">john.jeffrey@icann.org</a>><br><br></div></blockquote><div><span></span></div><blockquote type="cite"><div>
<div>
<p class="MsoNormal">Dear Bylaws Coordination Group,</p><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.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u>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"><u></u><u></u></p><p class="MsoNormal"><b><u>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"><u></u><u></u></p><p class="MsoNormal"><b><u>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"><u></u><u></u></p><p class="MsoNormal"><b><u>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"><u></u><u></u></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"><u></u><u></u></p><p class="MsoNormal"><b><u>Next Steps</u></b> –</p><p class="MsoNormal"><u></u><u></u></p><p class="MsoNormal">1) <i>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"><u></u><u></u></p><p class="MsoNormal">2) <i>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"><u></u><u></u></p><p class="MsoNormal">3) <i>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"><u></u><u></u></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"><u></u><u></u></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"><u></u><u></u></p></div></div></blockquote><blockquote type="cite"><div></div></blockquote></div><div></div></div><br><div dir="auto"><div></div><div><blockquote type="cite"><div></div></blockquote><blockquote type="cite"><div>
<div></div></div></blockquote><blockquote type="cite"><div></div></blockquote></div><div></div></div><br><div dir="auto"><div></div><div><blockquote type="cite"><div></div></blockquote><blockquote type="cite"><div>
<div>
</div>_____________________<div>____________________</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>bylaws-coord mailing list</span><br><span><a href="mailto:bylaws-coord@icann.org" target="_blank">bylaws-coord@icann.org</a></span><br><span><a href="https://mm.icann.org/mailman/listinfo/bylaws-coord" target="_blank">https://mm.icann.org/mailman/listinfo/bylaws-coord</a></span><br></div></blockquote></div></div><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>
<br></blockquote></div>
</blockquote></div>