<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#330033">
<br>
<br>
<div class="moz-cite-prefix">On 19-Apr-15 13:37, Milton L Mueller
wrote:<br>
</div>
<blockquote
cite="mid:ce7b8aa5abc846e98d5b50e7f05ed1c2@EX13-MBX-13.ad.syr.edu"
type="cite">
<p><span style="font-family:"Calibri",sans-serif">The
IANA portion of the ICANN budget
<b>related to naming</b> would be subject to.......<o:p></o:p></span></p>
<p><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">MM:
Again, it makes no sense to keep the other parts of the IANA
functions separate from the naming parts. The entire
department must be legally separation.
<o:p></o:p></span></p>
</blockquote>
<br>
As the other operational communities are clients of ICANN, is
ICANN's internal construction an issue for them? Isn't this just an
implementation issue? Does the IETF contract/MOU specify how ICANN
is organized internally? And as long as ICANN keeps delivering the
service they want, they won't need to resort to their remedy of
finding another provider and ICANN can be organized as it wants. <br>
<br>
Personally, I would have preferred a solution where the other
operational communities jointly owned/controlled the affiliate, but
that idea was not treated favorably by those operational
communities, so now we have a possible solution that leaves them
with the status quo for their relationships with ICANN.<br>
<br>
avri<br>
<br /><br />
<hr style='border:none; color:#909090; background-color:#B0B0B0; height: 1px; width: 99%;' />
<table style='border-collapse:collapse;border:none;'>
<tr>
<td style='border:none;padding:0px 15px 0px 8px'>
<a href="http://www.avast.com/">
<img border=0 src="http://static.avast.com/emails/avast-mail-stamp.png" alt="Avast logo" />
</a>
</td>
<td>
<p style='color:#3d4d5a; font-family:"Calibri","Verdana","Arial","Helvetica"; font-size:12pt;'>
This email has been checked for viruses by Avast antivirus software.
<br><a href="http://www.avast.com/">www.avast.com</a>
</p>
</td>
</tr>
</table>
<br />
</body>
</html>