<!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://37/">
<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>
<DIV><FONT size=2 face=Arial>Torture the language any way you wish, call it
"less than ideal", imagine conforming to it through a succession of transfers,
claim it only applies to the need assessment. I leave it to the community to
decide the meaning of this short paragraph:</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV>
<P>In addition to transfers under section 8.2, IPv4 number resources within the
ARIN region may be released to ARIN by the authorized resource holder, in whole
or in part, for transfer to another specified organizational recipient. Such
transferred number resources may only be received under RSA by organizations
that are within the ARIN region and can demonstrate the need for such resources,
as a single aggregate, in the exact amount which they can justify under current
ARIN policies.</P>
<P><FONT size=2 face=Arial>You ignore the requirement to return the resources to
ARIN, you claim "received as a single aggregate" to mean something other than
that, and you break ground in considering an LRSA an RSA.</FONT></P>
<P><FONT size=2 face=Arial>I remain unconvinced, and I note that you wish us to
continue to believe that the arbitrary assortment of addresses which Microsoft
contracted to buy from Nortel prior to ARIN's involvement in the deal turned out
to be the exact amount required in the ex post facto needs analysis of the
deal.</FONT></P></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Regards,</FONT></DIV><FONT size=2 face=Arial>
<DIV><BR>Mike</DIV>
<DIV></FONT> </DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV></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> ; <A title=mike@sum.net
href="mailto:mike@sum.net">Mike Burns</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=rudi.daniel@gmail.com
href="mailto:rudi.daniel@gmail.com">Rudolph Daniel</A> ; <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> Friday, April 29, 2011 10:54
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [arin-ppml] ARIN-PPML
Digest, Vol 70, Issue 141</DIV>
<DIV><BR></DIV>
<DIV>
<DIV>On Apr 29, 2011, at 10:28 AM, 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>And if the deal was per policy, as you say, can
we make the assumption that it is entirely within ARIN policy for legacy IP
addresses to transfer as a result of mergers and acquistions without any
notice to ARIN?</FONT></DIV></DIV></SPAN></BLOCKQUOTE>
<DIV><BR></DIV>Mike - </DIV>
<DIV> </DIV>
<DIV> ARIN does recognize M&A mergers under the policies that
were applicable</DIV>
<DIV> the time of the merger. Prior to May 2010, this means
that an organization </DIV>
<DIV> that acquires substantially all of the the operations of
another organization</DIV>
<DIV> would result in the transfer of the resources per NRPM 8.2.
We often have</DIV>
<DIV> to perform such updating of registration records when an
organization that</DIV>
<DIV> hasn't been maintaining records comes to ARIN for the first
time. (Note that</DIV>
<DIV> demonstrated need applies to transfers for M&A's after
May 2010 due to the</DIV>
<DIV> revision of the NRPM 8.2 which occurred at that time)</DIV>
<DIV><BR></DIV>
<DIV> With respect to the single aggregate, please refer to the
attached email to </DIV>
<DIV> ppml. As it is, the phrase applies to the assessment
of need as opposed </DIV>
<DIV> to the transferred number resources. </DIV>
<DIV><BR></DIV>
<DIV>FYI,</DIV>
<DIV>/John</DIV>
<DIV><BR></DIV>
<DIV>John Curran</DIV>
<DIV>President and CEO</DIV>
<DIV>ARIN</DIV>
<DIV><BR></DIV>
<DIV>
<DIV>Begin forwarded message:</DIV><BR class=Apple-interchange-newline>
<BLOCKQUOTE type="cite">
<DIV style="MARGIN: 0px"><SPAN
style="FONT-FAMILY: Helvetica; COLOR: rgb(0,0,0); FONT-SIZE: medium"><B>From: </B></SPAN><SPAN
style="FONT-FAMILY: Helvetica; FONT-SIZE: medium">John Curran <<A
href="mailto:jcurran@arin.net">jcurran@arin.net</A>><BR></SPAN></DIV>
<DIV style="MARGIN: 0px"><SPAN
style="FONT-FAMILY: Helvetica; COLOR: rgb(0,0,0); FONT-SIZE: medium"><B>Date: </B></SPAN><SPAN
style="FONT-FAMILY: Helvetica; FONT-SIZE: medium">April 18, 2011 9:49:42 PM
EDT<BR></SPAN></DIV>
<DIV style="MARGIN: 0px"><SPAN
style="FONT-FAMILY: Helvetica; COLOR: rgb(0,0,0); FONT-SIZE: medium"><B>To: </B></SPAN><SPAN
style="FONT-FAMILY: Helvetica; FONT-SIZE: medium">Benson Schliesser <<A
href="mailto:bensons@queuefull.net">bensons@queuefull.net</A>><BR></SPAN></DIV>
<DIV style="MARGIN: 0px"><SPAN
style="FONT-FAMILY: Helvetica; COLOR: rgb(0,0,0); FONT-SIZE: medium"><B>Cc: </B></SPAN><SPAN
style="FONT-FAMILY: Helvetica; FONT-SIZE: medium">ARIN-PPML List <<A
href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</A>><BR></SPAN></DIV>
<DIV style="MARGIN: 0px"><SPAN
style="FONT-FAMILY: Helvetica; COLOR: rgb(0,0,0); FONT-SIZE: medium"><B>Subject: </B></SPAN><SPAN
style="FONT-FAMILY: Helvetica; FONT-SIZE: medium"><B>[arin-ppml]
Implementation of NRPM 8.3</B><BR></SPAN></DIV><BR>
<DIV>On Apr 18, 2011, at 8:57 PM, Benson Schliesser wrote:<BR><BR>
<BLOCKQUOTE type="cite">Thanks for clarifying. Combining this with
your other recent messages, here is what I conclude about ARIN's
implementation of NRPM 8.3:<BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite"><BR></BLOCKQUOTE>
<BLOCKQUOTE type="cite">1) ARIN will accept any legally enforceable
document confirming ownership and the desire to
transfer.<BR></BLOCKQUOTE><BR>ARIN requires the seller to attest to being
the valid address holder and <BR>that they desire to transfer to the
recipient. <BR><BR>
<BLOCKQUOTE type="cite">2) ARIN will accept any form of RSA with the
buyer, including the standard LRSA or a negotiated LRSA, and the actual
agreement language will be kept private without disclosure to the ARIN
membership or community.<BR></BLOCKQUOTE><BR>Not quite. The resources
transferred must come under a registration services <BR>agreement; this
will usually be a standard RSA, unless otherwise required by<BR>nature of
the transfer. If legacy resources are involved, the result
could <BR>be an LRSA, just as can occur during the assignment of an
LRSA during an 8.2<BR>M&A transfer.<BR><BR>
<BLOCKQUOTE type="cite">3) ARIN will accept justification of need from
buyers, in private and without disclosure to the ARIN membership or
community.<BR></BLOCKQUOTE><BR>Correct. <BR><BR>
<BLOCKQUOTE type="cite">4) ARIN will accept the transfer of any arbitrary
collection of address blocks, as long as the total is in compliance with
justified need.<BR></BLOCKQUOTE><BR>ARIN has to implement NRPM 8.3 as
written, and while it does not <BR>support "any arbitrary collection of
address blocks", the existing<BR>existing NRPM 8.3 language may be less than
ideal when compared to <BR>some goals in the rational of the policy. At
the San Juan PPM, the<BR>Policy Experience report noted that there was
nothing to prevent <BR>transfers of resources received back out of the
receiving organization, <BR>and similarly it does not appear to
preclude multiple successive <BR>transfers (depending on the particular
utilization situation).<BR>The above issues are compounded by the
"single-aggregate" language<BR>applying to the demonstrated need as the
policy is presently written. <BR><BR>While I've mentioned some of
these issues individually, I appreciate<BR>your question and the opportunity
to put these all in one place as<BR>it may help folks in determining
possible next steps for refinement<BR>of the
policy.<BR><BR>Thanks!<BR>/John<BR><BR>John Curran<BR>President and
CEO<BR>ARIN<BR><BR>_______________________________________________<BR>PPML<BR>You
are receiving this message because you are subscribed to<BR>the ARIN Public
Policy Mailing List (<A
href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</A>).<BR>Unsubscribe or
manage your mailing list subscription at:<BR><A
href="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</A><BR>Please
contact info@arin.net if you experience any issues.<BR></DIV></BLOCKQUOTE>
<DIV>
<DIV><BR></DIV></DIV></DIV></BLOCKQUOTE></BODY></HTML>