<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Dec 22, 2009, at 3:00 PM, Joe Maimon wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><br><br>Owen DeLong wrote:<br><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">In the event that number resources of the acquired/merged<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">organization(s) are no longer efficiently utilized at the time ARIN<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">becomes aware of the transaction, through a transfer request or<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">otherwise, ARIN will work with the resource holder(s) to return or<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">aggregate resources as appropriate via the processes outlined in<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">sections 4.6, 4.7, or 12 of the NRPM.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite">I think that there's an issue here. I think that we need to talk about<br></blockquote><blockquote type="cite">the number resources of the resultant combined organization rather<br></blockquote><blockquote type="cite">than of the acquired/merged organization... Here's why...<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">The term acquired/merged could be construed to refer only to the<br></blockquote><blockquote type="cite">resources that were acquired without regard for the resources already<br></blockquote><blockquote type="cite">held by the acquiring organization. Let's say that two organizations<br></blockquote><blockquote type="cite">A and B merge. Prior to merger, A efficiently used 17 /24s and held<br></blockquote><blockquote type="cite">a /19, while B efficiently used a /23 and held a /22. The combined<br></blockquote><blockquote type="cite">usage is 19 /24s which would justify a /19, but, would not justify the<br></blockquote><blockquote type="cite">/22 of additional space. The /22 should be returned in this case and<br></blockquote><blockquote type="cite">be renumbered into the /19.<br></blockquote><blockquote type="cite"><br></blockquote><br><br>I think that bringing the possibility of renumbering and reclamation is somewhat of a disincentive to getting people into the door in the first place. If you are buying a network that you may have to renumber, you might want to think twice about it - or wait until you finish renumbering it before going to 8.3.<br><br></div></blockquote>I don't see the connection, necessarily.</div><div><br><blockquote type="cite"><div>What is the priority for the goals of 8.2 and how much efficiency should we let slide to achieve them?<br><br></div></blockquote>Primarily to make it clear that number resources are not transferable away from their original intended</div><div>purpose without justified need under ARIN policy. 8.3 is not particularly useful for the merger/acquisition</div><div>of company scenario.</div><div><br><blockquote type="cite"><div>These changes could make 8.3 more attractive than 8.2<br><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" color="#144FAE"><br></font></font></div></blockquote>As a point of information, I am proposing changes to a proposal to bring its effect closer to</div><div>existing policy, not changes to the implementation of existing policy.</div><div><br></div><div>Since this proposal is billed as a "simplified" M&A transfer policy and intended, as I understand it</div><div>to provide a clearer wording for essentially current policy effect, I think that is desirable. I do not</div><div>think that relaxing efficiency requirements is desirable for 8.2.</div><div><br></div><div>Further, 8.3 is not a substitute for 8.2, since, 8.3 would require the acquiring organization to</div><div>completely justify their need for all the space coming from the organization to be acquired</div><div>without using the network assets/utilization of the organization being acquired.</div><div><br></div><div>Both policies preserve the same requirement that you adhere to ARIN needs-based policy</div><div>to effectuate a legitimate transfer.</div><div><br></div><div>Owen</div><div><br></div></body></html>