<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: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:"Calibri Light";
panose-1:2 15 3 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
h5
{mso-style-priority:9;
mso-style-link:"Heading 5 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:10.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";}
span.Heading5Char
{mso-style-name:"Heading 5 Char";
mso-style-priority:9;
mso-style-link:"Heading 5";
font-family:"Calibri Light","sans-serif";
color:#2E74B5;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{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;}
--></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="color:#1F497D">Milton,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Please see my responses below.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Chuck<o:p></o:p></span></p>
<p class="MsoNormal"><span style="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""> Milton L Mueller [mailto:mueller@syr.edu]
<br>
<b>Sent:</b> Thursday, April 09, 2015 2:48 PM<br>
<b>To:</b> Gomes, Chuck; cwg-stewardship@icann.org<br>
<b>Subject:</b> RE: Question for Sidley<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Chuck:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I don’t know about the legal issues, but a “legal separation if needed later” model strikes me as a very poorly thought- out idea.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">There were three key advantages the S-A discussion draft identified for legal separation. One was that creating a legally distinct affiliate now would make it future separation more stable and easy. In other
words, if you don’t lay the groundwork for separability now, it won’t ever happen, or if we try to make it happen t will be very ugly and destabilizing. The other was that there would be an explicit contract between ICANN and IANA. The third was that there
would be a distinct governance body devoted to IANA performance and oversight issues.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">There was also a fourth advantage – an important one that you seem to have overlooked – raised by Mr. Boucher, which is that the legal separation dramatically increases chances of getting Congressional approval.
<o:p></o:p></span></p>
<p class="MsoNormal"><b><i><span style="color:#1F497D">[Chuck Gomes] I haven’t overlooked any of the possible advantages of the legal separation model but instead am also considering possible disadvantages of it in addition to the advantages. One advantage
is that it would involve a simpler transition with lest risk of destabilizing current services. Another is that would likely be less complex. A third is that it could probably be implemented in a more timely manner, assuming of course as you point out below
that the internal accountability mechanisms can be implemented in a timely manner including bylaws changes, an assumption I know is a big one.</span></i></b><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">The idea of “legal separation if needed later” sacrifices all four of those virtues for the present, with a promise that, somehow, we will move to it if needed later. But this doesn’t make sense to me. First,
without Congressional approval there may be no transition at all. Second, assuming we follow this model who would decide if it is “needed”? Your proposal provides no mechanism for actually doing it, so in effect the promise of “if needed” is a hollow one.
Third If it might be needed in the future, why not do it now?<o:p></o:p></span></p>
<p class="MsoNormal"><b><i><span style="color:#1F497D">[Chuck Gomes] It is not impossible that the functional separation model could work out well if the accountability mechanisms are well designed and implemented. If it did, there would be little if any sacrifice.
Of course we don’t know at this point in time. That is one reason why it might make sense to give it a shot. And that could be done in multiple ways; here are a couple ways: 1) implement it and then switch to the legal separation approach if needed; 2) implement
it with the clear understanding that we would switch to the legal separation approach in a specified time period (e.g., 12-18 months). The latter approach would allow plenty of time to do it right while still facilitating a quicker transition.</span></i></b><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Further, the purely internal model that you would propose for the short term would require major by-law changes to be implemented for accountability purposes (people keep sweeping that fact under the rug). These
by-law changes have to be carefully coordinated with the CCWG in a complex process. So apparently you want ICANN and its community to make a lot of complex and interdependent by-law changes and then discard them later or change the rules again?
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="color:#1F497D">No, this idea doesn’t pass the laugh test. We have to choose one or the other.
</span></a><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><b><i><span style="color:#1F497D">[Chuck Gomes] I am not laughing but I am trying to think of alternative ways of achieving what I think we all want in the best way possible considering all variables.</span></i></b><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> <a href="mailto:cwg-stewardship-bounces@icann.org">
cwg-stewardship-bounces@icann.org</a> [<a href="mailto:cwg-stewardship-bounces@icann.org">mailto:cwg-stewardship-bounces@icann.org</a>]
<b>On Behalf Of </b>Gomes, Chuck<br>
<b>Sent:</b> Wednesday, April 8, 2015 9:10 PM<br>
<b>To:</b> <a href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a><br>
<b>Subject:</b> [CWG-Stewardship] Question for Sidley<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Are there any legal issues that the CWG should be concerned with if it considered proposing a functional separation model for the initial transition and a legal separation model if needed at a later date?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Chuck</span><o:p></o:p></p>
<h5><span style="color:gray">“This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed, and may contain information that is non-public, proprietary, privileged, confidential and exempt from disclosure
under applicable law or may be constituted as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this
message in error, notify sender immediately and delete this message immediately.”
<o:p></o:p></span></h5>
</div>
</div>
</body>
</html>