<html 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">
<head>
<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:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 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;}
/* 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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.xmsonormal, li.xmsonormal, div.xmsonormal
{mso-style-name:x_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.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1547567243;
mso-list-type:hybrid;
mso-list-template-ids:580428350 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I think there are two ways of looking at this:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Requiring consensus makes it harder to do separation. As Christopher says, that is a big step so maybe it should be harder. That is in essence why
I opposed only requiring a simple majority of those present in a meeting instead of a simple majority of all members whether they are in attendance or not.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Requiring consensus also makes it easier for a small group to essentially veto a separation recommendation. If a small group of the members oppose
a separation while a strong majority favor it, simply by preventing consensus, separation could be stopped.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I don’t know where I come out on this but I definitely we should weigh both points before deciding.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Chuck<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> cwg-stewardship-bounces@icann.org [mailto:cwg-stewardship-bounces@icann.org]
<b>On Behalf Of </b>Christopher Wilkinson<br>
<b>Sent:</b> Tuesday, April 05, 2016 2:41 PM<br>
<b>To:</b> accountability-cross-community@icann.org Accountability<br>
<b>Cc:</b> cwg-stewardship@icann.org IANA<br>
<b>Subject:</b> [CWG-Stewardship] Fwd: [CCWG-ACCT] [bylaws-coord] DRAFT NEW ICANN BYLAWS - 2 April 2016 version - SCWG<br>
<b>Importance:</b> High<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:13.0pt">Good evening:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.0pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.0pt">With reference to the Sidley draft of April 2, 2016 ("Questions and Clarifications for Bylaws Coordination Group"), I wish to make a specific comment relating to Question 22 referring to Section 19 of the
draft Bylaws concerning the SCWG ("Separation Cross Community Working Group".)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.0pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.0pt">Section 19.5 addresses the Composition of the SCWG and the voting rights of its members and liaisons.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.0pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.0pt">Section 19.7 (a) addresses the SCWG decision-making procedure.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.0pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.0pt">During the CWG conference call on April 4, Sidley raised the issue of how to define the majority of the SCWG (Section 19.7(a)) in the absence of a consensus. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.0pt">The bar of 50+1% was proposed. (Question 22.)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.0pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:13.0pt">I submit that this bar is far too low, and that the general principle of consensus must be maintained.</span></b><span style="font-size:13.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.0pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.0pt">Section 19.5 of the draft Bylaws provides for SCWG to be composed of 13 voting members, 5 non voting liaisons and unlimited other participants. Among the voting members, GNSO and the ccTLDs would hold 9 votes;
more than a majority of 7.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.0pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.0pt">However, eventual separation of the IANA/PTI function from ICANN would have far reaching implications for many stakeholders which go well beyond the specific interests of DNS Registries and Registrars.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.0pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.0pt">It would not be appropriate for the representatives of the Registries and Registrars to be able to determine a separation decision, acting alone, absent consensus in the SCWG. If the proposed composition and
voting rights in an SCWG are maintained, it is absolutely essential that the SCWG act by consensus and not by a majority vote.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.0pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.0pt">Regards<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.0pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.0pt">Christopher Wilkinson<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Begin forwarded message:<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<p class="MsoNormal"><b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">From:
</span></b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">Mathieu Weill <<a href="mailto:mathieu.weill@afnic.fr">mathieu.weill@afnic.fr</a>></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">Subject: [CCWG-ACCT] Fwd: [bylaws-coord] DRAFT NEW ICANN BYLAWS - 2 April 2016 version</span></b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">Date:
</span></b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">3 Apr 2016 14:16:21 GMT+02:00</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">To:
</span></b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">CCWG Accountability <<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>></span><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<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<span style="font-family:"Tahoma","sans-serif"">�</span>sol<span style="font-family:"Tahoma","sans-serif"">�</span> pour le style<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
D<span style="font-family:"Tahoma","sans-serif"">�</span>but du message transf<span style="font-family:"Tahoma","sans-serif"">�</span>r<span style="font-family:"Tahoma","sans-serif"">�</span> :<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b>Exp</b><b><span style="font-family:"Tahoma","sans-serif"">�</span></b><b>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>
<b>Cc:</b> "Flanagan, Sharon" <<a href="mailto:sflanagan@sidley.com">sflanagan@sidley.com</a>>, "Cc: Zagorin, Janet S." <<a href="mailto:jzagorin@sidley.com">jzagorin@sidley.com</a>>, "Hilton, Tyler" <<a href="mailto:thilton@sidley.com">thilton@sidley.com</a>>,
ICANN-Adler <<a href="mailto:ICANN@adlercolvin.com">ICANN@adlercolvin.com</a>>, "Hofheimer, Joshua T." <<a href="mailto:jhofheimer@sidley.com">jhofheimer@sidley.com</a>>, "Mohan, Vivek" <<a href="mailto:vivek.mohan@sidley.com">vivek.mohan@sidley.com</a>>,
"Clark, Michael A." <<a href="mailto:mclark@sidley.com">mclark@sidley.com</a>>, "Boucher, Rick" <<a href="mailto:rboucher@sidley.com">rboucher@sidley.com</a>>, Sidley ICANN CCWG <<a href="mailto:sidleyicannccwg@sidley.com">sidleyicannccwg@sidley.com</a>>,
"Kerry, Cameron" <<a href="mailto:ckerry@sidley.com">ckerry@sidley.com</a>>, "McNicholas, Edward R." <<a href="mailto:emcnicholas@sidley.com">emcnicholas@sidley.com</a>>, Daniel Halloran <<a href="mailto:daniel.halloran@icann.org">daniel.halloran@icann.org</a>>,
Amy Stathos <<a href="mailto:amy.stathos@icann.org">amy.stathos@icann.org</a>>, "Boelter, Jessica C.K." <<a href="mailto:jboelter@sidley.com">jboelter@sidley.com</a>>, "Fuller, Miles" <<a href="mailto:wfuller@sidley.com">wfuller@sidley.com</a>>, "Tam, Tennie
H." <<a href="mailto:tennie.tam@sidley.com">tennie.tam@sidley.com</a>><br>
<b>Objet:</b> <b>[bylaws-coord] DRAFT NEW ICANN BYLAWS - 2 April 2016 version</b><br>
<b>R</b><b><span style="font-family:"Tahoma","sans-serif"">�</span></b><b>pondre </b>
<b><span style="font-family:"Tahoma","sans-serif"">�</span></b><b>:</b> John Jeffrey <<a href="mailto:john.jeffrey@icann.org">john.jeffrey@icann.org</a>><o:p></o:p></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="xmsonormal">Dear Bylaws Coordination Group,<o:p></o:p></p>
<p class="xmsonormal">Please find attached a document <span style="font-family:"Tahoma","sans-serif"">
�</span> DRAFT NEW ICANN BYLAWS (vers. 2Apr) (<span style="font-family:"Tahoma","sans-serif"">�</span>DRAFT BYLAWS<span style="font-family:"Tahoma","sans-serif"">�</span>) 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="xmsonormal"> 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="xmsonormal"><b><u>Recent Work</u></b> <span style="font-family:"Tahoma","sans-serif"">
�</span> During the past two weeks the legal drafting group, made up of Sidley<span style="font-family:"Tahoma","sans-serif"">�</span>s team, Adler<span style="font-family:"Tahoma","sans-serif"">�</span>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="xmsonormal"><b><u>More Work to Do</u></b> <span style="font-family:"Tahoma","sans-serif"">
�</span> 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="xmsonormal"><b><u>Legal Teams have not yet </u></b><b><u><span style="font-family:"Tahoma","sans-serif"">�</span>certified</u></b><b><u><span style="font-family:"Tahoma","sans-serif"">�</span></u></b>
<span style="font-family:"Tahoma","sans-serif"">�</span> 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 <span style="font-family:"Tahoma","sans-serif"">�</span> 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="xmsonormal">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="xmsonormal"><b><u>Next Steps</u></b> <span style="font-family:"Tahoma","sans-serif"">
�</span><o:p></o:p></p>
<p class="xmsonormal">1) <i>Now until 13 April</i> <span style="font-family:"Tahoma","sans-serif"">
�</span> 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="xmsonormal">2) <i>Now until 18 April</i>, (with particular focus during week of 13-18 April)
<span style="font-family:"Tahoma","sans-serif"">�</span> legal teams to update DRAFT BYLAWS working in coordination with the Bylaws Drafting Group;<o:p></o:p></p>
<p class="xmsonormal">3) <i>20 April</i> <span style="font-family:"Tahoma","sans-serif"">
�</span> posting date for public comment period for new proposed bylaws <span style="font-family:"Tahoma","sans-serif"">
�</span> with legal teams supporting that the new proposed bylaws meets the proposal recommendations.<o:p></o:p></p>
<p class="xmsonormal"><span style="font-family:"Tahoma","sans-serif"">���</span><o:p></o:p></p>
<p class="xmsonormal">As before, we look forward to working with all of you in the coming days, to get ICANN<span style="font-family:"Tahoma","sans-serif"">�</span>s Bylaws in the best form possible to effectuate these important changes.<o:p></o:p></p>
<p class="xmsonormal">We hope these views of the documents are useful and that you receive them in the spirit that they are offered<span style="font-family:"Tahoma","sans-serif"">�</span> to help all of us to be able to collaborate and work through these Bylaws
changes in the most effective way possible <span style="font-family:"Tahoma","sans-serif"">
�</span> to enable the creation of a new and stronger, community empowered ICANN.<o:p></o:p></p>
<p class="xmsonormal">John Jeffrey, Holly Gregory, and Rosemary Fei<o:p></o:p></p>
</div>
</blockquote>
</div>
</div>
</div>
</div>
<div>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<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>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">_______________________________________________<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></p>
</blockquote>
</div>
</div>
<p class="MsoNormal">_______________________________________________<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">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>
</body>
</html>