[ARIN-consult] [ARIN-Suggestions] New Suggestion - ACSP 2016.4 - Waiting List for 2 Byte ASNs

[David Huberman]

I think everything Andrew wrote cries out for the PDP not the ACSP :)

> On Apr 2, 2016, at 2:02 PM, Andrew Dul <andrew.dul at quark.net> wrote:
> 
> 
> On 4/1/2016 1:35 PM, Robert Seastrom wrote:
>>> On Apr 1, 2016, at 11:59 AM, Andrew Dul <andrew.dul at quark.net> wrote:
>>> 
>>> I'm happy to write a policy proposal to start that process if others believe that would be beneficial to the community.
>> Could we start with a problem statement that describes what problem we would be solving that isn't already adequately addressed by having ASNs be 8.3-transferable number resources?
> The problem as I understand it is that 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.
> 
> Will 8.3 ASNs transfers meet the needs of some organizations, yes. The question is what to do with the 2-byte ASNs that will end up in ARIN's inventory for various reasons.
> 
> 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?)  Should they 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 ASNs?
> 
> Andrew