[arin-ppml] 2-byte ASN policy

Andrew Dul andrew.dul at quark.net
Sun Apr 3 13:59:37 EDT 2016


I am starting a new thread in PPML, as a follow up to the ARIN 
suggestion and consultation which recently started regarding creating a 
2-byte ASN waiting list.

The original suggestion is here:


ARIN opened a consultation on this suggestion on the arin-consult 
mailing-list.  This thread starts here for those who are not subscribed 
to arin-consult.



As the thread evolved it has been suggested that this issue should be 
resolved via the policy development process rather than through a 

There are a number of questions that have been raised by this thread.  I 
am copying them here to continue the discussion on PPML.


Working problem statement: ARIN will receive 2-byte ASNs as  returns 
over time, and these ASNs have perceived or additional value to
organizations compared to 4-byte ASNs.  How should ARIN allocate these 
2-byte ASNs?


Should they be given to the next requester, regardless of technical need 
for a 2-byte ASN? (What are the technical qualifications we should use 
if there is a specific technical need?  e.g. provides transit to more 
than 1 ASN?)

If there is really a technical need for 2-byte ASNs, shouldn't we 
attempt to build an inventory of 2-byte ASNs?

Should returns be held in reserve?

Should ARIN hold them for some period of time  before reallocating them?

Should they be put up for auction to  qualified organizations?

Should they be given to the 1st organization  on a wait-list for 2-byte 

Would an organization looking for a 2-byte ASN have the option to 
receive a 4-byte ASN in the interim?  If they did would they have to 
return it?

Should the waiting list be closed to organizations that already have a 
2-byte ASNs?

I and the AC would appreciate your comments on these questions so that 
we can start to build a draft policy that best matches with what the 
community would like to see implemented by ARIN.


More information about the ARIN-PPML mailing list