<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<base href="x-msg://37/">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>
<div>On Apr 29, 2011, at 10:28 AM, 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">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-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">
<span style="font-family: Helvetica; font-size: medium; color: rgb(0, 0, 0); "><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-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">
<span style="font-family: Helvetica; font-size: medium; color: rgb(0, 0, 0); "><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-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">
<span style="font-family: Helvetica; font-size: medium; color: rgb(0, 0, 0); "><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-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">
<span style="font-family: Helvetica; font-size: medium; color: rgb(0, 0, 0); "><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-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">
<span style="font-family: Helvetica; font-size: medium; color: rgb(0, 0, 0); "><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>
</body>
</html>