<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Dear Mathieu</div><div>Tks</div><div>I wish to participate at the call on Thursday</div><div>Regards</div><div>Kavouss<br><br>Sent from my iPhone</div><div><br>On 23 May 2016, at 22:17, Mathieu Weill <<a href="mailto:mathieu.weill@afnic.fr">mathieu.weill@afnic.fr</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="Generator" content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Texte de bulles Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.TextedebullesCar
{mso-style-name:"Texte de bulles Car";
mso-style-priority:99;
mso-style-link:"Texte de bulles";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--><div class="WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Dear Colleagues, <o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D">Thank you Bruce, Theresa and John for these clarifications. <o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D">The cochairs and rapporteurs for the CCWG discussed the bylaws finalization process on our coordination call today, following up on our previous discussions and questions to this group.<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D">First, we believe the provision of a redline version of the Bylaws is critical for good decision making. This redline should be provided sufficiently in advance of any meeting to discuss the changes. <o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D">Then, we suggest that there is a straightforward way to give this bylaws coordination group a role in finalizing the bylaws. This would be to change the Board informational call scheduled for 21 UTC on Thursday 26 May into a meeting of this Bylaws Coordination group along with all the members of the ICANN Board.<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D">Then this group and Board together can talk through and agree how to deal with proposed amendments in an informal but open and community-driven way.<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D">We welcome your thoughts on this suggestion. We cannot think of another way to guarantee appropriate community input while preserving the tight timeframes.<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Mathieu, Thomas, Leon<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">CCWG-Accountability co-chairs<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p><div><div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">De :</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:bylaws-coord-bounces@icann.org">bylaws-coord-bounces@icann.org</a> [<a href="mailto:bylaws-coord-bounces@icann.org">mailto:bylaws-coord-bounces@icann.org</a>] <b>De la part de</b> Theresa Swinehart<br><b>Envoyé :</b> lundi 23 mai 2016 18:53<br><b>À :</b> John Jeffrey; Greg Shatan; <a href="mailto:bylaws-coord@icann.org">bylaws-coord@icann.org</a><br><b>Objet :</b> Re: [bylaws-coord] Next steps for Bylaws drafting<o:p></o:p></span></p></div></div><p class="MsoNormal"><o:p> </o:p></p><div><div><div><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black">All, </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black">I echo what John has laid out on the seriousness with which all the public comments will be considered, where we are in the process, and approach to this next important next phase of finalizing the draft bylaws everyone’s been working so hard on. </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black">As we work together in this next phase, and strive to achieve the “timeline” identified already in Marrakech when we all met, a few additional items: </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black">As posted on 21 April, the purpose of the public comments (see: <a href="https://www.icann.org/public-comments/draft-new-bylaws-2016-04-21-en">https://www.icann.org/public-comments/draft-new-bylaws-2016-04-21-en</a>): </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal" style="margin-left:36.0pt"><b><i><span style="font-family:"Cambria","serif";color:#333333;background:white">Purpose:</span></i></b><span style="font-family:"Cambria","serif";color:#333333;background:white"> This Public Comment period seeks community input on the Draft New </span><span style="font-size:10.0pt;font-family:"Cambria","serif";color:black">ICANN</span><span style="font-family:"Cambria","serif";color:#333333;background:white"> Bylaws developed to reflect the recommendations contained in the proposals by the </span><span style="font-size:10.0pt;font-family:"Cambria","serif";color:black">IANA</span><span style="font-family:"Cambria","serif";color:#333333;background:white"> Stewardship Transition Coordination Group (</span><span style="font-size:10.0pt;font-family:"Cambria","serif";color:black">ICG</span><span style="font-family:"Cambria","serif";color:#333333;background:white">) and Cross Community Working Group on Enhancing </span><span style="font-size:10.0pt;font-family:"Cambria","serif";color:black">ICANN </span><span style="font-family:"Cambria","serif";color:#333333;background:white">Accountability (CCWG-Accountability) as provided to the </span><span style="font-size:10.0pt;font-family:"Cambria","serif";color:black">ICANN</span><span style="font-family:"Cambria","serif";color:#333333;background:white"> Board on 10 March 2016 and transmitted to </span><span style="font-size:10.0pt;font-family:"Cambria","serif";color:black">NTIA</span><span style="font-family:"Cambria","serif";color:#333333;background:white">. (See Resolutions </span><span style="font-size:10.0pt;font-family:"Cambria","serif";color:black"><a href="https://www.icann.org/resources/board-material/resolutions-2016-03-10-en#2.b"><span style="font-size:12.0pt;color:#0098D5;background:white;text-decoration:none">2016.03.10.12-15</span></a></span><span style="font-family:"Cambria","serif";color:#333333;background:white"> and </span><span style="font-size:10.0pt;font-family:"Cambria","serif";color:black"><a href="https://www.icann.org/resources/board-material/resolutions-2016-03-10-en#2.c"><span style="font-size:12.0pt;color:#0098D5;background:white;text-decoration:none">2016.03.10.16-19</span></a></span><span style="font-family:"Cambria","serif";color:#333333;background:white">)</span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black">All the public comments can be found at: <a href="https://forum.icann.org/lists/comments-draft-new-bylaws-21apr16/">https://forum.icann.org/lists/comments-draft-new-bylaws-21apr16/</a></span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black">As a reminder, please find below the overview of the next steps: </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p><blockquote style="margin-left:30.0pt;margin-right:0cm"><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black">21 May – public comment period closed</span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black">21-26 May </span><span style="font-family:"Cambria","serif";color:black">– Preparation of public comment analysis/reaction</span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black">25 May - Staff sends out a summary of all comments and any proposed changes to the draft Bylaws to the community and ICANN Board</span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black">26 May – Possible Bylaws Coordination Group call if needed (TBC)</span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black">26 May at 21:00 UTC - Board will hold an information call to review comments received and consider any suggested changes to the draft bylaws</span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black">27 May at 13:00 UTC - Board will hold a formal meeting to vote on the Bylaws.</span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p></blockquote><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black">Should we proceed in scheduling a bylaws coordination call? </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black">Look forward to working together in this next phase, </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black">Kind regards, </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:"Cambria","serif";color:black">Theresa</span><span style="color:black"><o:p></o:p></span></p></div><div><div><p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p></div><div><p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p></div></div></div></div><div><p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p></div><div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class="MsoNormal"><b><span style="font-size:11.0pt;color:black">From: </span></b><span style="font-size:11.0pt;color:black"><<a href="mailto:bylaws-coord-bounces@icann.org">bylaws-coord-bounces@icann.org</a>> on behalf of John Jeffrey <<a href="mailto:john.jeffrey@icann.org">john.jeffrey@icann.org</a>><br><b>Date: </b>Monday, May 23, 2016 6:30 PM<br><b>To: </b>Greg Shatan <<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a>><br><b>Cc: </b>"<a href="mailto:bylaws-coord@icann.org">bylaws-coord@icann.org</a>" <<a href="mailto:bylaws-coord@icann.org">bylaws-coord@icann.org</a>><br><b>Subject: </b>Re: [bylaws-coord] Next steps for Bylaws drafting<o:p></o:p></span></p></div><div><p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p></div><div><div><div><p class="MsoNormal"><span style="color:black">Greg, <o:p></o:p></span></p><p class="MsoNormal"><span style="color:black">Thanks for your note and for your points on where we are this week. The email that Bruce forwarded was a summary of some of the actions (not all) anticipated this week, excerpted out of a much longer discussion of the final stages of the process; that we have all been working toward. We didn’t attempt to set out all the assessments that would be going on by staff, by Sidley, by Adler, by the Bylaws coordination group and others who have been so dedicated to this process throughout, like yourself and the group that you represent in this process.<o:p></o:p></span></p><p class="MsoNormal"><span style="color:black">As we are well aware it was expected that this would be a period with very short deadlines in which to provide meaningful analysis of the public comments. Staff’s summary and assessment will be forwarded to the community as soon as we have completed it. This summary/assessment can be reviewed by the Bylaws Coordination Group (along with Sidley and Adler), and a determination can be made if additional work is needed beyond that. We agree that a call with the Bylaws Coordination Group would be useful this week.<o:p></o:p></span></p><p class="MsoNormal"><span style="color:black">Let’s be certain though, that no one is proposing that we skip over the comments, not take them seriously or not provide bylaws responsive to those comments or with sufficient analysis to allow their approval based upon the community’s proposals and any new issues raised within those comments. <o:p></o:p></span></p><p class="MsoNormal"><span style="color:black">From what we have seen in the comments, Staff’s assessment so far (but we will look to Sidley, Adler, to help assess also) is that -- many of the comments are in line with the proposals or are capable of being resolved in this current stage of the process. Some of the comments are seeking variance to the proposals, and some of the comments are stressing the importance of WS2 items.<o:p></o:p></span></p><p class="MsoNormal"><span style="color:black">Some of the comments provided specific recommended line edits, and those must be carefully considered, to see if the changes are required to enhance the implementation of the proposals or understanding of the Bylaws, or if the language posted for public comments sufficiently meets the intent of the proposals.<o:p></o:p></span></p><p class="MsoNormal"><span style="color:black">Accordingly, let’s not give up on the long proposed tight deadlines at this point. Together, let us see if we can get this done, with all due consideration by those necessary to ensure that we are acting consistent with our promises to the community and to the Commerce to deliver these Bylaws fully reflecting the community’s inputs and request for empowerment and change.<o:p></o:p></span></p><p class="MsoNormal"><span style="color:black">John <o:p></o:p></span></p></div><div><p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p><div><div><div><p class="MsoNormal"><span style="color:black">John Jeffrey<br>General Counsel & Secretary, ICANN<br>12025 Waterfront Drive, Suite 300<br>Los Angeles, California 90094-2536<o:p></o:p></span></p></div><div><p class="MsoNormal"><span style="color:black">direct dial - +1.310.301.5834<br>mobile - +1.310.404.6001<br><a href="mailto:JJ@ICANN.org">JJ@ICANN.org</a><o:p></o:p></span></p></div></div></div><p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p><div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><p class="MsoNormal"><span style="color:black">On May 23, 2016, at 7:23 AM, Greg Shatan <<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a>> wrote:<o:p></o:p></span></p></div><p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p><div><div><div><p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:black">This raises critical questions and serious concerns, which I've put inline. The use of the passive voice in this is quite astounding -- in a number of critical spots, you can't tell who is supposed to be doing what. That makes it quite impossible to understand the process. The timing (or lack of time for any meaningful work or response by anyone but Staff and Board) is deeply troubling.<o:p></o:p></span></p></div><div><p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:black"><o:p> </o:p></span></p></div><div><p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:black">Is this just the Board's review of the comments? Is the community being written out of the process from this point forward? If so, just say so, so that we can react accordingly. Answers that fail to address these issues, failures to respond, and answers that obscure the role of the parties in this process are harmful, not helpful.<o:p></o:p></span></p></div><div><p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:black"><o:p> </o:p></span></p></div><div><p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:black">I have been a defender of this process and this timeline in a variety of contexts, but I am losing faith. <o:p></o:p></span></p></div><div><p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:black"><o:p> </o:p></span></p></div><div><p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:black">I would strongly suggest that a review of the comments and a decision on amendments by the Bylaws Coordination Group should be a step in this process. If that requires another week (or more), so be it.<o:p></o:p></span></p></div><div><p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:black"><o:p> </o:p></span></p></div><div><p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:black">The irony that the community may have no way to hold this process accountable to the community is overwhelming.<o:p></o:p></span></p></div><div><p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:black"><o:p> </o:p></span></p></div><div><p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:black">I'm extremely concerned with where we are in this process -- which was supposed to represent the community's voice in proposing revisions to the Bylaws.<o:p></o:p></span></p></div><div><p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:black"><o:p> </o:p></span></p></div><div><p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:black">Greg<o:p></o:p></span></p></div><div><p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:black"><o:p> </o:p></span></p></div><div><p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:black"><o:p> </o:p></span></p></div><div><p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:black">On Mon, May 23, 2016 at 8:43 AM, Bruce Tonkin <<a href="mailto:Bruce.Tonkin@melbourneit.com.au" target="_blank">Bruce.Tonkin@melbourneit.com.au</a>> wrote:</span><span style="font-family:"Verdana","sans-serif";color:black"><o:p></o:p></span></p></div><div><div><blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"><p class="MsoNormal"><span style="color:black">Hello All,<br><br>Here is my current understanding of the process steps towards the Board meeting on 27 May to consider the new bylaws:<br><br>25 May - Staff sends out a summary of all comments and any proposed changes <o:p></o:p></span></p><div><p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:black"></span><span style="font-family:"Verdana","sans-serif";color:black">[GSS: PROPOSED BY WHOM? WILL THIS INCLUDE EVERY CHANGE PROPOSED IN ALL THE COMMENTS, OR JUST COMMENTS CHOSEN BY SOME BODY? IF ONLY CHOSEN COMMENTS, WHO'S DOING THE CHOOSING? HOW WILL THIS WORK PLAN DEAL WITH COMMENTS THAT DID NOT PROPOSE SPECIFIC LANGUAGE TO IMPLEMENT CONCERNS/CHANGES FROM THOSE COMMENTS?] </span><span style="font-family:"Arial","sans-serif";color:black"></span><span style="font-family:"Verdana","sans-serif";color:black"><o:p></o:p></span></p></div><p class="MsoNormal"><span style="color:black">to the draft Bylaws to the community and ICANN Board, 48 hours before the Board's vote.<o:p></o:p></span></p></blockquote><div><p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p></div><div><div><p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:black"></span><span style="font-family:"Verdana","sans-serif";color:black">[WHAT IS THE COMMUNITY SUPPOSED TO DO WITH THIS SUMMARY IN 48 HOURS? WILL THE BYLAWS COORDINATION GROUP OR ANY OTHER SPECIFIC COMMUNITY</span><span style="font-family:"Arial","sans-serif";color:black"></span><span style="font-family:"Verdana","sans-serif";color:black"><o:p></o:p></span></p></div><p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p><div><p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:black"></span><span style="font-family:"Verdana","sans-serif";color:black">GROUP HAVE A ROLE IN RESPONDING TO AND/OR APPROVING PROPOSED CHANGES?]</span><span style="font-family:"Arial","sans-serif";color:black"></span><span style="font-family:"Verdana","sans-serif";color:black"><o:p></o:p></span></p></div></div><blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"><p class="MsoNormal"><span style="color:black"><br> Sidley and Adler law firms have already suggested proposed changes to the draft bylaws based on the CCWG on Accountability public comments. ICANN staff are now compiling a summary of all the public comments, and then that can be reviewed <o:p></o:p></span></p><div><p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:black"></span><span style="font-family:"Verdana","sans-serif";color:black">[BY WHOM?] </span><span style="font-family:"Arial","sans-serif";color:black"></span><span style="font-family:"Verdana","sans-serif";color:black"><o:p></o:p></span></p></div><p class="MsoNormal"><span style="color:black">with respect to possible amendments <o:p></o:p></span></p><div><p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:black"></span><span style="font-family:"Verdana","sans-serif";color:black"> [WHO WILL DECIDE WHICH COMMENTS GET TURNED INTO POSSIBLE AMENDMENTS? WHO WILL TURN COMMENTS INTO POSSIBLE AMENDMENTS?]</span><span style="font-family:"Arial","sans-serif";color:black"></span><span style="font-family:"Verdana","sans-serif";color:black"><o:p></o:p></span></p></div><p class="MsoNormal"><span style="color:black">to the draft bylaws.<br><br><br>26 May at 21:00 UTC - Board will hold an information call to review comments received since the Board's meeting in Amsterdam, and consider any suggested <o:p></o:p></span></p><div><p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:black"></span><span style="font-family:"Verdana","sans-serif";color:black">[SUGGESTED BY WHOM?] </span><span style="font-family:"Arial","sans-serif";color:black"></span><span style="font-family:"Verdana","sans-serif";color:black"><o:p></o:p></span></p></div><p class="MsoNormal"><span style="color:black">changes to the draft bylaws<br><br><br>27 May at 13:00 UTC - Board will hold a formal meeting to vote on the Bylaws.<br><br><br>If there are any outstanding issues identified <o:p></o:p></span></p><div><p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:black"></span><span style="font-family:"Verdana","sans-serif";color:black"> [BY WHOM?]</span><span style="font-family:"Arial","sans-serif";color:black"></span><span style="font-family:"Verdana","sans-serif";color:black"><o:p></o:p></span></p></div><p class="MsoNormal"><span style="color:black">from the summary of comments and proposed changes to the draft bylaws provided on 25 May, then the Bylaws Coordination Group will be convened <o:p></o:p></span></p><div><p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:black"></span><span style="font-family:"Verdana","sans-serif";color:black">[BY WHOM?] </span><span style="font-family:"Arial","sans-serif";color:black"></span><span style="font-family:"Verdana","sans-serif";color:black"><o:p></o:p></span></p></div><p class="MsoNormal"><span style="color:black">to get guidance.<br><br>I will separately send this to the CCWG on Accountability mailing list.<br><br><br>Regards,<br>Bruce Tonkin<br><br>_______________________________________________<br>bylaws-coord mailing list<br><a href="mailto:bylaws-coord@icann.org">bylaws-coord@icann.org</a><br><a href="https://mm.icann.org/mailman/listinfo/bylaws-coord" target="_blank">https://mm.icann.org/mailman/listinfo/bylaws-coord</a><o:p></o:p></span></p></blockquote></div><p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p></div></div><p class="MsoNormal"><span style="color:black">_______________________________________________<br>bylaws-coord mailing list<br><a href="mailto:bylaws-coord@icann.org">bylaws-coord@icann.org</a><br><a href="https://mm.icann.org/mailman/listinfo/bylaws-coord">https://mm.icann.org/mailman/listinfo/bylaws-coord</a><o:p></o:p></span></p></div></blockquote></div><p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p></div></div></div></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">bylaws-coord@icann.org</a></span><br><span><a href="https://mm.icann.org/mailman/listinfo/bylaws-coord">https://mm.icann.org/mailman/listinfo/bylaws-coord</a></span><br></div></blockquote></body></html>