[arin-ppml] ASN transfers...

Kevin Blumberg kevinb at thewire.ca
Tue Sep 20 14:07:05 EDT 2011

I guess the question is will we run out of 2 Byte ASN's before wide spread support of 4 Byte ASN's. 

I went over 8.3 and it would be a very modest change.

 Allowing them via 8.3 makes sense.

Kevin Blumberg
T 416.214.9473 x31
F 416.862.9473
kevinb at thewire.ca

-----Original Message-----
From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On Behalf Of Benson Schliesser
Sent: Tuesday, September 20, 2011 2:01 PM
To: Martin Hannigan; arin-ppml at arin.net List
Subject: Re: [arin-ppml] ASN transfers...

On Sep 20, 2011, at 12:46 PM, John Curran wrote:

> On Sep 20, 2011, at 11:00 AM, Martin Hannigan wrote:
>> ARIN?
> IPv4, IPv6, and ASN number resources are potentially transferrable 
> under NRPM 8.2 (M&A).
> Only IPv4 resources are potentially transferrable under NRPM 8.3 
> (specified transfer) given the current language.

I'm curious: do folks see value in being able to transfer an ASN without transferring the underlying business?

IP addresses can be decoupled from the network, transferred independently, and provide value to the recipient.  Perhaps this is also true of an ASN, but an ASN tends to be more coupled to the business relationships that form the network topology, which suggests that it makes more sense as part of a larger M&A activity. And while there are parallels, we're not facing the same kind of shortage of ASNs that we're facing with IPv4 - their effect on growth is of a different order.

So, it's not clear to me why somebody might want to transfer an ASN independently?  Not that this is a reason to disallow it. But I'm curious.


You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
Unsubscribe or manage your mailing list subscription at:
Please contact info at arin.net if you experience any issues.

More information about the ARIN-PPML mailing list