<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#330033">
<br>
<div class="moz-cite-prefix">On 27-Oct-14 00:31, Milton L Mueller
wrote:<br>
</div>
<blockquote
cite="mid:f08f7df4fe2e45129d58cd9f5b4fd79e@EX13-MBX-13.ad.syr.edu"
type="cite">
<pre wrap="">C.2.4. Assumes that all of the IANA functions are in the same entity. This assumption is not warranted at the present time.</pre>
</blockquote>
<br>
<br>
Except that the assumption of this exercise is to change as few
things as possible and an assumption that they can or even should be
moved to seperate entities is not warranted. The solition does not
need to match the structure of the operational communities doing the
recommendations.<br>
<br>
Without an anaylisis of the effect of seperation, I think it unwise
to assume they can or should be split.<br>
<br>
I therefore would rather assume that the unity of IANA should be
preserved until such time as it is proved that sperating them is the
better solution. And until it is proven that sperating them
invovles no risk. Even the IETF which is assuming it can pull out
of IANA at any time has not done a complete analysis of the risks of
doing so. Until we are sure that it does not pose a risk to the
Internet, we ought to be careful about dumping this requirement.<br>
<br>
avri<br>
<br>
</body>
</html>