Autonomous system (Internet)
An autonomous system (AS) is a collection of connected Internet Protocol (IP) routing prefixes under the control of one or more network operators on behalf of a single administrative entity or domain that presents a common, clearly defined routing policy to the internet.
Originally the definition required control by a single entity, typically an Internet service provider (ISP) or a very large organization with independent connections to multiple networks, that adhered to a single and clearly defined routing policy, as originally defined in RFC 1771. The newer definition in RFC 1930 came into use because multiple organizations can run Border Gateway Protocol (BGP) using private AS numbers to an ISP that connects all those organizations to the internet. Even though there may be multiple autonomous systems supported by the ISP, the internet only sees the routing policy of the ISP. That ISP must have an officially registered autonomous system number (ASN).
A unique ASN is allocated to each AS for use in BGP routing. ASNs are important because the ASN uniquely identifies each network on the Internet.
Until 2007, AS numbers were defined as 16-bit integers, which allowed for a maximum of 65,536 assignments. RFC 4893 introduced 32-bit AS numbers, which the Internet Assigned Numbers Authority (IANA) has begun to allocate to regional Internet registries (RIRs), although this proposed standard has now been replaced by RFC 6793. These numbers are written preferably as simple integers (in a notation sometimes referred to as "asplain") ranging from 0 to 4,294,967,295 (hexadecimal 0xFFFF FFFF), or in the form called "asdot" which looks like x.y, where x and y are 16-bit numbers. Numbers of the form 0.y are exactly the old 16-bit AS numbers. The accepted textual representation of autonomous system numbers is defined in RFC 5396 as "asplain". The special 16-bit ASN 23456 ("AS_TRANS") was assigned by IANA as a placeholder for 32-bit ASN values for the case when 32-bit-ASN capable routers ("new BGP speakers") send BGP messages to routers with older BGP software ("old BGP speakers") which do not understand the new 32-bit ASNs.
The first and last ASNs of the original 16-bit integers (0 and 65,535) and the last ASN of the 32-bit numbers (4,294,967,295) are reserved and should not be used by operators. ASNs 64,496 to 64,511 of the original 16-bit range and 65,536 to 65,551 of the 32-bit range are reserved for use in documentation by RFC 5398. ASNs 64,512 to 65,534 of the original 16-bit AS range, and 4,200,000,000 to 4,294,967,294 of the 32-bit range are reserved for Private Use by RFC 6996, meaning they can be used internally but should not be announced to the global Internet. All other ASNs are subject to assignment by IANA.
The number of unique autonomous networks in the routing system of the Internet exceeded 5,000 in 1999, 30,000 in late 2008, 35,000 in mid-2010, 42,000 in late 2012, 54,000 in mid-2016 and 60,000 in early 2018.
The number of allocated ASNs exceeded 84,000 in early 2018.
AS numbers are assigned in blocks by IANA to regional Internet registries (RIRs). The appropriate RIR then assigns ASNs to entities within its designated area from the block assigned by IANA. Entities wishing to receive an ASN must complete the application process of their local RIR and be approved before being assigned an ASN. Current IANA ASN assignments to RIRs can be found on the IANA website.
There are other sources for more specific data:
- APNIC: https://ftp.apnic.net/stats/apnic/
- RIPE NCC: ftp://ftp.ripe.net/ripe/stats/
- AFRINIC: ftp://ftp.afrinic.net/pub/stats/afrinic/
- ARIN: ftp://ftp.arin.net/pub/stats/arin/
- LACNIC: ftp://ftp.lacnic.net/pub/stats/lacnic/
A complete table of 16-bits and 32-bits ASN available:
|1 - 23455||16||Public ASN's|
|23456||16||Reserved for AS Pool Transition||RFC6793|
|23457 - 64534||16||Public ASN's|
|64000 - 64495||16||Reserved by IANA|
|64496 - 64511||16||Reserved for use in documentation/sample code||RFC5398|
|64512 - 65534||16||Reserved for private use|
|65536 - 65551||32||Reserved for use in documentation and sample code||RFC4893, RFC5398|
|65552 - 131071||32||Reserved|
|131072 - 4199999999||32||Public 32-bit ASN's|
|4200000000 - 4294967294||32||Reserved for private use||RFC6996|
Autonomous systems (AS) can be grouped into four categories, depending on their connectivity and operating policy.
- multihomed: An AS that maintains connections to more than one other AS. This allows the AS to remain connected to the internet in the event of a complete failure of one of their connections. However, unlike a transit AS, this type of AS would not allow traffic from one AS to pass through on its way to another AS.
- stub: An AS that is connected to only one other AS. This may be an apparent waste of an AS number if the network's routing policy is the same as its upstream AS's. However, the stub AS may have peering with other autonomous systems that is not reflected in public route-view servers. Specific examples include private interconnections in the financial and transportation sectors.
- transit: An AS that provides connections through itself to other networks. That is, network A can use network B, the transit AS, to connect to network C. If one AS is an ISP for another, then the former is a transit AS.[clarification needed]
- Internet Exchange Point (IX or IXP): A physical infrastructure through which ISPs or content delivery networks (CDNs) exchange internet traffic between their networks (autonomous systems). IXP ASNs are usually transparent.[clarification needed]
- Administrative distance
- INOC-DBA — a hotline communications system between the network operations centers of major Autonomous Systems
- Internet Routing Registry
- PeeringDB - a freely available web-based database of networks that are interested in peering
- Routing Assets Database (RADB)
- Hawkinson, John; Bates, Tony (March 1996). Guidelines for creation, selection, and registration of an Autonomous System (AS). IETF. sec. 3. doi:10.17487/RFC1930. RFC 1930. https://tools.ietf.org/html/rfc1930#section-3. Retrieved 2018-12-31.
- Rekhter, Yakov; Li, Tony (March 1995). A Border Gateway Protocol 4 (BGP-4). IETF. doi:10.17487/RFC1771. RFC 1771. https://tools.ietf.org/html/rfc1771. Retrieved 2018-12-31. (obsoleted by RFC 4271)
- Hudson, Geoff; Michaelson, George (December 2008). Textual Representation of Autonomous System (AS) Numbers. IETF. doi:10.17487/RFC5396. RFC 5396. https://tools.ietf.org/html/rfc5396. Retrieved 2018-12-31.
- Vohra, Quaizar; Chen, Enke (May 2007). BGP Support for Four-octet AS Number Space. IETF. doi:10.17487/RFC4893. RFC 4893. https://tools.ietf.org/html/rfc4893. Retrieved 2018-12-31.
- "Using AS 23456: How BGP Uses Conversion or Truncation For Compatibility". 2008-07-21. Archived from the original on 2016-10-29. Retrieved 2018-12-31.
- Bates, Tony; Smith, Philip; Huston, Geoff. "CIDR report". Retrieved 2018-12-31.
- "World - Autonomous System Number statistics - Sorted by number". Regional Internet Registries Statistics. Retrieved 2018-12-31.
- "Autonomous System (AS) Numbers". IANA.org. 2018-12-07. Retrieved 2018-12-31.