[arin-ppml] Draft Policy 2012-3: ASN Transfers

[Martin Hannigan]

On Mon, Mar 26, 2012 at 4:17 PM, Michael Sinatra
<michael+ppml at burnttofu.net> wrote:
> On 3/26/12 12:51 PM, Martin Hannigan wrote:
>
>> I've said similar things in this thread and I'll simply add +1.
>>
>> What we seem to be talking about here, at least from the counter
>> argument perspective, is a desire to regulate business process instead
>> of providing a technically sound and useful mechanism to enable ASN
>> transfers.  As someone involved in peering with literally hundreds of
>> networks, I'm not convinced that there is a risk that I need to be so
>> concerned about that I would want to disallow ASN transfers,
>> especially without a single real life incident that is compelling
>> enough to warrant a change in thought.
>>
>> Adopting this policy will allow ARIN to "get out of the way" and
>> legitimize what's already transpiring on a regular basis.  This is a
>> good thing.
>
> Hi Marty:
>
> Can you (or perhaps ARIN staff) shed some light on what is already
> transpiring with respect to ASN transfers other than via M&A?  I have to
> admit that I am pretty out of the loop when it comes to actual demand
> for ASN transfers other than the use cases identified by Chris G. a
> while back.  The only other thing I see is a quick note by the staff
> analysis to the effect that it would expedite bankruptcy proceedings.
> Is that the main focus here or are there other use cases (other than the
> ones Chris identified)?
>


Michael,

That would be the at least part of the idea. The other would be to
insure that transfers that occur for reasons not related to bankruptcy
are fully documented and as transparent as they need to be.  The legal
comments in the ARIN staff clarity and understanding would have most
infer that legacy ASN's and IP addresses are in a similar legal state.

This proposal would remove what is currently an ambiguity, provide a
useful policy to those who do want to transfer an ASN for a multitude
of legitimate reasons and to help improve the accuracy of our
documentation.

I don't know what the staff experience is, it wasn't contained in the
C/U. I would be interested to hear it.

Best,

-M<