<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>You can always print in hardcopy, I was told.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">el<br><br>-- <span class="Apple-style-span" style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); "></span><div><span class="Apple-style-span" style="font-size: 13pt; -webkit-tap-highlight-color: rgba(26, 26, 26, 0.294118); -webkit-composition-fill-color: rgba(175, 192, 227, 0.231373);">Sent from </span><span style="font-size: 13pt;">Dr Lisse's iPhone 6</span></div><div><br></div></div><div><br>On 3 Apr 2016, at 16:32, Paul Rosenzweig <<a href="mailto:paul.rosenzweig@redbranchconsulting.com">paul.rosenzweig@redbranchconsulting.com</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 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:-webkit-standard;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.hoenzb
{mso-style-name:hoenzb;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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;font-family:"Calibri",sans-serif">Kavouss is absolutely right. A side-by-side or redline comparison is essential ….<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Paul<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Paul Rosenzweig<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><a href="mailto:paul.rosenzweig@redbranchconsulting.com">paul.rosenzweig@redbranchconsulting.com</a><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">O: +1 (202) 547-0660<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">M: +1 (202) 329-9650<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><a href="http://www.redbranchconsulting.com/index.php?option=com_content&view=article&id=19&Itemid=9"><span style="color:#0563C1">My PGP Key</span></a><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p><p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a> [<a href="mailto:accountability-cross-community-bounces@icann.org">mailto:accountability-cross-community-bounces@icann.org</a>] <b>On Behalf Of </b>Kavouss Arasteh<br><b>Sent:</b> Sunday, April 3, 2016 9:52 AM<br><b>To:</b> Matthew Shears <<a href="mailto:mshears@cdt.org">mshears@cdt.org</a>><br><b>Cc:</b> CCWG Accountability <<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>><br><b>Subject:</b> Re: [CCWG-ACCT] Fwd: [bylaws-coord] DRAFT NEW ICANN BYLAWS - 2 April 2016 version<o:p></o:p></span></p><p class="MsoNormal"><o:p> </o:p></p><div><div><p class="MsoNormal">Dear Mathieu,<o:p></o:p></p></div><div><p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:10.0pt;margin-left:0in"><span style="font-size:16.0pt;font-family:"Calibri",sans-serif;color:black">I have not yet started to examine the doc. However, it is a usual practice everywhere, except CCWG , that any revision to an existing document MUST be made with revision mark in order to enable the proper verification of the changes.</span><o:p></o:p></p><p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:10.0pt;margin-left:0in"><span style="font-size:16.0pt;font-family:"Calibri",sans-serif;color:black">Please understand the matter in a positive direction.</span><o:p></o:p></p><p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:10.0pt;margin-left:0in"><span style="font-size:16.0pt;font-family:"Calibri",sans-serif;color:black">On the other hand, we are asked to examine the draft bylaws which is amendments to the existing bylaws IS THE HIGHEST LEVEL OF LEGAL TEXT WHICH GOVERS THE FUNCTIONING OF ICANN.</span><o:p></o:p></p><p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:10.0pt;margin-left:0in"><span style="font-size:16.0pt;font-family:"Calibri",sans-serif;color:black">we therefore need to be very cautious on how to examine that.</span><o:p></o:p></p><p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:10.0pt;margin-left:0in"><span style="font-size:16.0pt;font-family:"Calibri",sans-serif;color:black">I therefore believe, we need more time between 2-3 weeks to do so.</span><o:p></o:p></p><p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:10.0pt;margin-left:0in"><span style="font-size:16.0pt;font-family:"Calibri",sans-serif;color:black">However, if like the supplemental proposal PREOPARATION everything is purposely scheduled to be done in rush that is something else.</span><o:p></o:p></p><p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:10.0pt;margin-left:0in"><span style="font-size:16.0pt;font-family:"Calibri",sans-serif;color:black">Regards</span><o:p></o:p></p><p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:10.0pt;margin-left:0in"><span style="font-size:16.0pt;font-family:"Calibri",sans-serif;color:black">Kavouss </span><o:p></o:p></p></div></div><div><p class="MsoNormal"><o:p> </o:p></p><div><p class="MsoNormal">2016-04-03 15:20 GMT+02:00 Matthew Shears <<a href="mailto:mshears@cdt.org" target="_blank">mshears@cdt.org</a>>:<o:p></o:p></p><blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in"><div><p class="MsoNormal">Agree that if available a comparative doc would be incredibly useful.<br><br>Thanks<o:p></o:p></p><div><div><p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p><div><p class="MsoNormal">On 4/3/2016 9:16 AM, Sébastien Bachollet wrote:<o:p></o:p></p></div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><div><div><p class="MsoNormal">Thanks Mathieu for those documents.<o:p></o:p></p></div><div><p class="MsoNormal">May I ask for the curent version of the bylaws in the same format of the proposed one’s? (it would have been useful to have comparative document, but I am not requesting it now if it is not an already existing document).<o:p></o:p></p></div><div><p class="MsoNormal">And as some will ask for, all the same documents in PDF will be useful too.<o:p></o:p></p></div><div><p class="MsoNormal">All the best<o:p></o:p></p></div><div><p class="MsoNormal">SeB<o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><div><p class="MsoNormal"><i><span style="font-family:"-webkit-standard",serif;color:#007F00">Skills are useful but diversity is essential.</span></i><o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal"><span style="font-family:"Calibri",sans-serif">Sébastien Bachollet</span><o:p></o:p></p></div><div><p class="MsoNormal"><span style="font-family:"Calibri",sans-serif">+33 6 07 66 89 33</span><o:p></o:p></p></div><div><p class="MsoNormal">Blog: <a href="http://sebastien.bachollet.fr" target="_blank">http://sebastien.bachollet.fr</a>/<o:p></o:p></p></div><div><p class="MsoNormal">Mail: <span style="font-size:11.5pt;font-family:"Calibri",sans-serif">Sébastien Bachollet <<a href="mailto:sebastien@bachollet.com" target="_blank">sebastien@bachollet.com</a>></span><o:p></o:p></p></div></div></div></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div style="border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0in 0in 0in;border-color:currentColor currentColor"><p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">De : </span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><<a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank">accountability-cross-community-bounces@icann.org</a>> on behalf of Mathieu Weill <<a href="mailto:mathieu.weill@afnic.fr" target="_blank">mathieu.weill@afnic.fr</a>><br><b>Date : </b>dimanche 3 avril 2016 14:16<br><b>À : </b>CCWG Accountability <<a href="mailto:accountability-cross-community@icann.org" target="_blank">accountability-cross-community@icann.org</a>><br><b>Objet : </b>[CCWG-ACCT] Fwd: [bylaws-coord] DRAFT NEW ICANN BYLAWS - 2 April 2016 version<o:p></o:p></span></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><div><div><div><p class="MsoNormal">Dear colleagues, <o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">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. <o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">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. <o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">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). <o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">Should any other issue be added to the list based on your respective reviews, please raise your questions on the list for transparency. <o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal" style="margin-bottom:12.0pt">Best regards,<o:p></o:p></p><div><p class="MsoNormal">Mathieu<o:p></o:p></p></div><div><p class="MsoNormal">---------------<o:p></o:p></p></div><div><p class="MsoNormal">Depuis mon mobile, désolé pour le style<o:p></o:p></p></div></div><div><p class="MsoNormal" style="margin-bottom:12.0pt"><br>Début du message transféré :<o:p></o:p></p></div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><p class="MsoNormal" style="margin-bottom:12.0pt"><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>><o:p></o:p></p></div></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><div><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Dear Bylaws Coordination Group,<o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">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></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> We ask that you share the attachments with your CCWG, ICG and CWG colleagues who will be reviewing this during this critical work week<o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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.<o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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.<o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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.<o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">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<o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><u>Next Steps</u></b> –<o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">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;<o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">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;<o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">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.<o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">———<o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">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.<o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">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.<o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">John Jeffrey, Holly Gregory, and Rosemary Fei<o:p></o:p></p></div></div></blockquote></div></div></div><div><div><div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><p class="MsoNormal">_____________________ <o:p></o:p></p><div><p class="MsoNormal">____________________<o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div></div></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><p class="MsoNormal">_______________________________________________<br>bylaws-coord mailing list<br><a href="mailto:bylaws-coord@icann.org" target="_blank">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></p></div></blockquote></div></div></div><p class="MsoNormal">_______________________________________________ Accountability-Cross-Community mailing list <a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a> <a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a> <o:p></o:p></p></blockquote><p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p><pre>_______________________________________________<o:p></o:p></pre><pre>Accountability-Cross-Community mailing list<o:p></o:p></pre><pre><a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a><o:p></o:p></pre><pre><a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><o:p></o:p></pre></blockquote><p class="MsoNormal"><o:p> </o:p></p></div></div><pre><span style="color:#888888">-- <o:p></o:p></span></pre><pre><span style="color:#888888"><o:p> </o:p></span></pre><pre><span style="color:#888888">Matthew Shears | Director, Global Internet Policy & Human Rights Project<o:p></o:p></span></pre><pre><span style="color:#888888">Center for Democracy & Technology | <a href="http://cdt.org" target="_blank">cdt.org</a><o:p></o:p></span></pre><pre><span style="color:#888888">E: <a href="mailto:mshears@cdt.org" target="_blank">mshears@cdt.org</a> | T: <a href="tel:%2B44.771.247.2987" target="_blank">+44.771.247.2987</a><o:p></o:p></span></pre><pre><span style="color:#888888"><o:p> </o:p></span></pre><pre><span style="color:#888888">CDT's Annual Dinner, Tech Prom, is April 6, 2016. Don't miss out - register at <a href="http://cdt.org/annual-dinner" target="_blank">cdt.org/annual-dinner</a>.<o:p></o:p></span></pre></div><p class="MsoNormal" style="margin-bottom:12.0pt"><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" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><o:p></o:p></p></blockquote></div><p class="MsoNormal"><o:p> </o:p></p></div></div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Accountability-Cross-Community mailing list</span><br><span><a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a></span><br><span><a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a></span><br></div></blockquote></body></html>