Very well reasoned. I agree completely.<div><br></div><div>Greg<span></span><br><br>On Tuesday, July 21, 2015, Flanagan, Sharon <<a href="mailto:sflanagan@sidley.com">sflanagan@sidley.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<p></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Dear Client Committee,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">On the CCWG call today the question below was raised as to whether the Separation Review and PTI should be referenced in the CCWG list of fundamental bylaws.
Our view is that both the Separation Review and PTI should be listed among the fundamental bylaws for the following reasons:
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal" style="text-indent:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">1. The Separation Review is part of the IFR, but we believe it should be specifically called out by referencing the Special IFR, the
Separation Process and the SCWG.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal" style="text-indent:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">2. With respect to PTI, unlike CSC and IFR which are
<b><i>created by</i></b> the ICANN bylaws, PTI will have a separate legal existence and will not be created by the ICANN bylaws. Notwithstanding PTI’s separate legal existence, there are still implementation mechanisms that relate to PTI that should be contemplated
by the ICANN bylaws. For example, as the sole member of PTI, ICANN will have certain statutory rights relative to PTI . In order to appropriately limit and direct the
</span><span style="font-family:"Calibri","sans-serif";color:#1f497d">transfer and
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">exercise of these membership rights by ICANN, provisions will need to be included in ICANN’s bylaws. These should be fundamental bylaws so that
</span><span style="font-family:"Calibri","sans-serif";color:#1f497d">they</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> cannot be easily changed. <u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">For example,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">- ICANN should not be able to change the composition of the PTI Board that is specified in the PTI articles and bylaws (it can change the people but not the
designated seats); <u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">- ICANN should not be able to transfer the assets of PTI back to ICANN or to a new entity (absent a separation process that mandates a transfer);
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">- ICANN should not be able to dissolve PTI, etc.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">In terms of how the Separation Process and PTI could be implemented in the CCWG proposal fundamental bylaw description attached, we have reflected our comments
for CWG’s consideration.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#1f497d">In addition, attached is a portion of the CCWG proposal that relates to the NTIA and CWG dependencies reflecting our proposed comments to the CWG dependencies section.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Please let us know if you would like to discuss.
</span><span style="font-family:"Calibri","sans-serif";color:#1f497d"> </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Kinds regards,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Sharon<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">SHARON</span></b><span style="font-size:10.0pt;font-family:"Arial","sans-serif""> <b>FLANAGAN</b></span><br>
<span style="font-size:9.0pt;font-family:"Arial","sans-serif"">Partner</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">Sidley Austin LLP<br>
555 California Street<br>
Suite 2000<br>
San Francisco, CA 94104<br>
+1.415.772.1271</span><br>
<span style="font-size:9.0pt;font-family:"Arial","sans-serif""><a href="javascript:_e(%7B%7D,'cvml','sflanagan@sidley.com');" title="Click to send email to Flanagan, Sharon" target="_blank">sflanagan@sidley.com</a></span><br>
<a href="http://www.sidley.com" title="www.sidley.com" target="_blank"><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">www.sidley.com</span></a><u></u><u></u></p>
<p class="MsoNormal"><a href="http://www.sidley.com/" target="_blank"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";text-decoration:none"><img border="0" width="35" height="35" src="http://www.sidley.com/files/upload/signatures/SA-autosig.png" alt="http://www.sidley.com/files/upload/signatures/SA-autosig.png"></span></a><span style="font-size:10.0pt;font-family:"Arial","sans-serif""> <b>SIDLEY
AUSTIN LLP</b></span><span style="font-size:10.0pt"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1f497d">SHARON</span></b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#1f497d"> </span><b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1f497d">FLANAGAN</span></b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#1f497d"><br>
Partner<br>
<br>
</span><b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1f497d">Sidley Austin LLP</span></b><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#1f497d"><br>
</span></b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#1f497d">+1.415.772.1271<br>
<a href="javascript:_e(%7B%7D,'cvml','sflanagan@sidley.com');" title="Click to send email to Flanagan, Sharon" target="_blank">sflanagan@sidley.com</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1f497d"> </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u><u></u></span></p>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><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""> Jordan Carter [mailto:<a href="javascript:_e(%7B%7D,'cvml','jordan@internetnz.net.nz');" target="_blank">jordan@internetnz.net.nz</a>]
<br>
<b>Sent:</b> Tuesday, July 21, 2015 3:55 PM<br>
<b>To:</b> Jonathan Robinson; Lise Fuhr; Flanagan, Sharon<br>
<b>Cc:</b> ACCT-Staff; Thomas Rickert; León Felipe Sánchez Ambía; Mathieu Weill; Becky Burr; Steve DelBianco; Cheryl Langdon-Orr; Accountability Cross Community<br>
<b>Subject:</b> CWG Confirmation - Fundamental Bylaws inclusions<u></u><u></u></span></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
<div>
<p class="MsoNormal" style="margin-left:.5in">Dear Jonathan, Lise, Sharon<u></u><u></u></p>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">On the CCWG-Accountability call today, we discussed the fundamental bylaws paper and the relationship with the requirements of the CWG-Stewardship's proposal.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">There has been some discussion as to whether we should reference the PTI structure, and the Separation review, alongside the CSC and the IANA Functions Review in our Second Public Comment Report.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">The last two items have been in the draft for a while. The first two have come in and out and as you can see from the
<b>attached</b>, are currently out.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">We are relaxed I think about including them or not including them but seek your formal guidance on the question -- and if you have any, specific guidance as to the right way to reference if they are included.<br clear="all">
<u></u><u></u></p>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">I'd appreciate your feedback by close of play Wednesday UTC if possible so we can resolve this on the CCWG-Accountability's next call on Thursday 23rd.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Many thanks,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Jordan Carter<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Rapporteur, Work Party 1 (Community Empowerment)<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">CCWG-Accountability<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<p class="MsoNormal" style="margin-left:.5in">-- <u></u><u></u></p>
</div>
</div>
</div>
<p></p>
<p> </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>
</div>
</blockquote></div>