<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type><BASE
href="x-msg://301/">
<META name=GENERATOR content="MSHTML 8.00.6001.19046">
<STYLE></STYLE>
</HEAD>
<BODY
style="WORD-WRAP: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space"
bgColor=#ffffff>
<DIV><FONT size=2 face=Arial>><FONT size=3 face="Times New Roman">Actually,
that is not the case. Internally, we calculate need based on
the </FONT>
<DIV> information provided and that is more granular than a CIDR
boundary.</DIV>
<DIV> </DIV>
<DIV>Yes, the needs assessment is more granular, but since you can't dole out
/32s, you round up, isn't that accurate?</DIV>
<DIV>And since you seek aggregation, you will always allocate as a single
netblock?</DIV>
<DIV>I wonder what the rounding error was on that recent Comcast /9.</DIV>
<DIV> </DIV>
<DIV>My example made it clear that the language could be interpreted two ways,
why do you say you would need to "reinterpret contrary to the adopted
language"?</DIV>
<DIV>I, and others, have pointed out that the modification of "be received" by
the phrase "in a single aggregate" makes eminent sense and conforms to
history.</DIV>
<DIV> </DIV>
<DIV>But interpreting the clause to apply to the "demonstrated need" section of
the predicate leaves one scratching one's head.</DIV>
<DIV>I mean,. who goes to ARIN and gets justified for anything other than a
single aggregate?</DIV>
<DIV>Isn't that what Owen was saying he believed the intent to be?</DIV>
<DIV> </DIV>
<DIV>>We follow the policies as written and do not have the freedom
reinterpret policy
<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> </DIV></DIV>
<DIV>Repeating it doesn't help much, I'm afraid.The phrase digging yourself
deeper comes to mind.</DIV>
<DIV> </DIV>
<DIV>Regards,</DIV>
<DIV> </DIV>
<DIV>Mike</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV></FONT></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px"
dir=ltr>
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=jcurran@arin.net href="mailto:jcurran@arin.net">John Curran</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=mike@nationwideinc.com
href="mailto:mike@nationwideinc.com">Mike Burns</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=arin-ppml@arin.net
href="mailto:arin-ppml@arin.net List">arin-ppml@arin.net List</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Monday, May 02, 2011 5:45 PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [arin-ppml] NRPN 8.2 &
2.3</DIV>
<DIV><BR></DIV>
<DIV>
<DIV>
<DIV>On May 2, 2011, at 9:57 PM, Mike Burns wrote:</DIV>
<BLOCKQUOTE type="cite"><SPAN
style="WIDOWS: 2; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; BORDER-COLLAPSE: separate; FONT: medium Helvetica; WHITE-SPACE: normal; ORPHANS: 2; LETTER-SPACING: normal; 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"
class=Apple-style-span>
<DIV
style="WORD-WRAP: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space"
bgcolor="#ffffff"><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
style="WIDOWS: 2; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; BORDER-COLLAPSE: separate; FONT: medium Helvetica; WHITE-SPACE: normal; ORPHANS: 2; LETTER-SPACING: normal; 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"
class=Apple-style-span>
<DIV
style="WORD-WRAP: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space"
bgcolor="#ffffff">
<DIV><FONT size=2 face=Arial></FONT><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: small" class=Apple-style-span>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
style="WIDOWS: 2; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; BORDER-COLLAPSE: separate; FONT: medium Helvetica; WHITE-SPACE: normal; ORPHANS: 2; LETTER-SPACING: normal; 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"
class=Apple-style-span>
<DIV
style="WORD-WRAP: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space"
bgcolor="#ffffff">
<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></BLOCKQUOTE></BODY></HTML>