[arin-ppml] ARIN-2018-1: Allow Inter-regional ASN Transfers

[Owen DeLong]

> On Aug 13, 2018, at 14:42 , Job Snijders <job at ntt.net> wrote:
> 
> I agree with the proposal.
> 
> I think this proposal is needed and addresses practical concerns: the alternative to transfers is “renumbering”, and renumbering ASNs is a very costly and operationally risky proposition. There is no upside to restricting or forbidding this type of resource transfer.
> 
> A question that remains: if you don’t want to transfer your ASN in or out of ARIN, then don’t, but why forbid others from doing it? All resources should be transferable.

We can agree to disagree.

I remain of the opinion that the transfer of IPv4 resources was, for lack of a better term, a necessary evil to meet the expediencies of a (hopefully unusual) situation (namely the end of the IPv4 free pool prior to the ubiquitous deployment of IPv6).

Similarly to the mission creep of NAT (which was deployed for largely the same reason and which is now mistakenly widely perceived to be a security tool), transfers are now seeing this sort of mission creep.

Having been through several ASN renumbering processes, I found them neither particularly costly (compared to the other tasks related to the event triggering the need for the ASN renumber), nor operationally risky.

For the most part, networks themselves don’t move from one continent to another, so the need for migratory ASNs seems rather dubious in the vast majority of cases.

Owen