<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#330033">
Hi,<br>
<br>
On this issue the ICANN names solution should presume that ICANN
remain the service contractor with the other operational communities
in any model. It is only if these other operational communities
initiate a request for a change to a direct service contract with
IANA that it becomes an issue. As far as I know they have neither
done so, nor desire to do so.<br>
<br>
I do not see an ambiguity in this. While there may be an
opportunity for them to think about it, there is no requirement or
implication that they do so.<br>
<br>
avri<br>
<br>
<div class="moz-cite-prefix">On 19-Apr-15 00:53, Andrew Sullivan
wrote:<br>
</div>
<blockquote cite="mid:20150419045336.GB3826@mx2.yitter.info"
type="cite">
<pre wrap="">Unstated in the above is that, depending on whether we have
fundamental bylaws or an affiliate, there are either one or two
options for other communities. ICANN can be indifferent to how to
proceed on this, but the other communities may need to make a
decision:
• Continue the agreement with ICANN, who then undertake to have PTI do
the work for those other communities. This is the only option
available if PTI is a department of ICANN under some fundamental
bylaw(s), but it remains available in case PTI is an affiliate.</pre>
</blockquote>
<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>