[arin-ppml] An article of interest to the community....
owen at delong.com
Wed Sep 14 21:57:28 EDT 2011
On Sep 14, 2011, at 8:51 AM, Matthew Kaufman wrote:
> On 9/14/11 3:25 PM, Owen DeLong wrote:
>> On Sep 14, 2011, at 5:58 AM, Matthew Kaufman wrote:
>>> On 9/14/11 2:46 PM, Owen DeLong wrote:
>>>>> Which just leads to the question: Why does 8.3 have a restriction to just IPv4? I know of at least one case where some limited assets and an AS number were transferred, but nothing else... 8.3 should be usable for AS numbers as well.
>>>> Why? What is the point of being able to transfer an ASN outside of M&A? Just get a new ASN from ARIN.
>>> I can't believe that this one isn't obvious.
>>> Matthew Kaufman
>> It really isn't. What would be the advantage of transferring an ASN vs. simply applying for one unless you are also transferring the underlying network resources (in which case 8.2 would apply).
> ISP A has thousands of customers. ISP B also has thousands of customers.
> ISP A has peering established at a dozen public peering points but wishes to give that up in favor of buying transit.
> ISP B wants to have peering at a dozen public peering points with those same peers and knows that their network footprint and traffic mix is sufficient to keep all or nearly all of those peers comfortable with simply continuing the peering arrangement with their entity. (Rather than the contractually safer, and 8.2-compilant process, but extra cost and overhead of having to move the peering agreements and the contracts into a subsidiary that one then sells via the M&A transfer process).
> So ISP B buys from ISP A the AS number, the right to use the circuits, and maybe some rack space. And possibly a few of the border routers. Nothing more.
> Shouldn't that transfer be able to happen under 8.3?
> Matthew Kaufman
More information about the ARIN-PPML