[arin-ppml] Draft Policy ARIN-2022-2: Remove Barrier to BGP Uptake in ASN Policy

ARIN info at arin.net
Mon May 2 11:44:20 EDT 2022

On 27 April 2022, the ARIN Advisory Council (AC) accepted "ARIN-prop-307: Remove Barrier to BGP Uptake in ASN Policy" as a Draft Policy.


Draft Policy ARIN-2022-2 is below and can be found at:




You are encouraged to discuss all Draft Policies on PPML. The AC will evaluate the discussion to assess the conformance of this draft policy with ARIN's Principles of Internet number resource policy as stated in the Policy Development Process (PDP). Specifically, these principles are:


* Enabling Fair and Impartial Number Resource Administration

* Technically Sound

* Supported by the Community


The PDP can be found at:




Draft Policies and Proposals under discussion can be found at: https://www.arin.net/participate/policy/drafts/




Sean Hopkins

Senior Policy Analyst

American Registry for Internet Numbers (ARIN)




Draft Policy ARIN-2022-2: Remove Barrier to BGP Uptake in ASN Policy


Problem Statement:


The current requirements for getting an ASN have resulted in confusion particularly for new entrants who have their hands more than full with the mechanics of getting BGP up and running.


Four octet (32 bit) ASNs were defined in May 2007 in RFC 4893. It has taken several years for routing equipment in general use to catch up, but today 32 bit ASNs are generally accepted and it is rare that an organization which has been issued a 32 bit ASN comes back to ARIN and says they need a 16 bit ASN instead.


The austerity measure of requiring extensive documentation to get an ASN is left over from the days of 16 bit ASNs (total space 65000). It is no longer appropriate and we should align our conservation requirements with those found in other 32-bit spaces (total space four billion). Consider:


* A /32 of IPv6 space is the default allocation and will be assigned to any ISP that requests it.


* Temporary assignment of a /32 of IPv4 space can be acquired on most residential ISPs by issuing a DHCP request.


We propose making issuance of the first 32 bit ASN for any ORGID (or each site for organizations that have number resources under multiple discrete networks policy) be pro-forma upon request. If an org’s technical people think they need a public ASN, they probably do!


Vetting as embodied in existing policy or evolved in ARIN-2021-3 should be reserved for those requesting more than one ASN per organization or discrete network.


Note that this proposal is non-interfering with ARIN-2021-3 which is intended to make the NRPM more understandable.


Policy statement:


Insert the following paragraph at the beginning of section 5:


Any organization may be issued a single four-octet (32 bit) Autonomous System Number (ASN) upon request. Organizations that have space issued under Multiple Discrete Networks policy may be issued a four-octet (32 bit) ASN per discrete network upon request.


Replace the introductory sentence:


There are a limited number of available Autonomous System Numbers (AS Numbers), therefore, it is important to determine which sites require unique AS Numbers and which do not.




Issuance of ASNs outside of the scope outlined above is subject to the following constraints:


Timetable for implementation: Immediate

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20220502/90d71ae1/attachment-0001.htm>

More information about the ARIN-PPML mailing list