<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<base href="x-msg://301/">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>
<div>
<div>On May 2, 2011, at 9:57 PM, Mike Burns wrote:</div>
<blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">
<div bgcolor="#ffffff" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<font class="Apple-style-span" color="#000000"><br>
</font>
<div><font size="2" face="Arial">I don't believe that there has been an answer to those of us who said that while it is grammatically acceptable to decide that a "single aggregate" relates to the needs justification, it is nonsensical to do that, as all needs
analyses result in a single aggregate. You don't have a needs analysis at any time where it is found that a need is outside CIDR boundaries. Need assessment has always rounded up to that boundary.</font></div>
</div>
</span></blockquote>
<div><br>
</div>
<div>Mike - </div>
<div><br>
</div>
Actually, that is not the case. Internally, we calculate need based on the </div>
<div> information provided and that is more granular than a CIDR boundary.</div>
<div><br>
<blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">
<div bgcolor="#ffffff" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div><font size="2" face="Arial"></font><span class="Apple-style-span" style="font-family: Arial; font-size: small; ">No, the only way to interpret the language of 8.3 is that the reception of the addresses should occur as a single aggregate, which is clear
has not occurred with 8.3.</span></div>
<div><font size="2" face="Arial">To say the staff or the board acted outside of policy is correct in the MS/Nortel case.</font></div>
</div>
</span></blockquote>
<div><br>
</div>
</div>
<div>
<div><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">
<div bgcolor="#ffffff" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div> We follow the policies as written and do not have the freedom reinterpret policy</div>
<div> contrary to the adopted language. I indicated this before, but am happy to repeat</div>
<div> it if that helps you.</div>
<div> </div>
<div>Thanks!</div>
<div>/John</div>
<div><br>
</div>
<div>John Curran</div>
<div>President and CEO</div>
<div>ARIn</div>
<div><br>
</div>
</div>
</span></div>
</div>
</div>
</body>
</html>