Autonomous system (Internet)

Last updated

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 and clearly defined routing policy to the Internet. [1] Each AS is assigned an autonomous system number (ASN), for use in Border Gateway Protocol (BGP) routing. Autonomous System Numbers are assigned to Local Internet Registries (LIRs) and end user organizations by their respective Regional Internet Registries (RIRs), which in turn receive blocks of ASNs for reassignment from the Internet Assigned Numbers Authority (IANA). The IANA also maintains a registry of ASNs which are reserved for private use (and should therefore not be announced to the global Internet).

Contents

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. [2] In March 1996, the newer definition came into use because multiple organizations can run 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 ASN.

Until 2007, AS numbers were defined as 16-bit integers, which allowed for a maximum of 65,536 assignments. Since then, [3] the IANA has begun to also assign 32-bit AS numbers to regional Internet registries (RIRs). These numbers are written preferably as simple integers, in a notation referred to as "asplain", [4] ranging from 0 to 4,294,967,295 (hexadecimal 0xFFFF FFFF). Or, alternatively, 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 special 16-bit ASN 23456 ("AS_TRANS") [5] 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. [6]

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 [7] [8] [9] and should not be used by operators; AS0 is used by all five RIRs to invalidate unallocated space. [10] 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. [11] 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. [12]

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. [13] The number of allocated ASNs exceeded 100,000 as of March 2021. [14]

Assignment

AS numbers are assigned in blocks by Internet Assigned Numbers Authority (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 RIR, LIR or upstream service provider [15] [16] and be approved before being assigned an ASN. Current IANA ASN assignments to RIRs can be found on the IANA website. [17] RIRs, as part of NRO, can revoke AS numbers as part of their Internet governance abilities. [18]

There are other sources for more specific data:

ASN table

A complete table of 16-bits and 32-bits ASN available: [17]

NumberBitsDescriptionReference
016Reserved for RPKI unallocated space invalidation [19] RFC   6483, RFC  7607
1–2345516Public ASNs
2345616Reserved for AS Pool TransitionRFC  6793
23457–6449516Public ASNs
64496–6451116Reserved for use in documentation and sample codeRFC  5398
64512–6553416Reserved for private useRFC  1930, RFC  6996
6553516ReservedRFC  7300
65536–6555132Reserved for use in documentation and sample codeRFC  5398, RFC  6793
65552–13107132Reserved
131072–419999999932Public 32-bit ASNs
4200000000–429496729432Reserved for private useRFC  6996
429496729532ReservedRFC  7300

Types

Autonomous systems (AS) can be grouped into four categories, depending on their connectivity and operating policy.

  1. 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.
  2. 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.
  3. transit : An AS that acts as a router between two ASes is called a transit. Since not all ASes are directly connected with every other AS, a transit AS carries data traffic between one AS to another AS to which it has links. [20]
  4. 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). These are often groups of local ISPs that band together to exchange data by splitting the costs of a local networking hub, avoiding the higher costs (and bandwidth charges) of a Transit AS. IXP ASNs are usually transparent. By having presence in an IXP, ASes shorten transit path to other participating ASes, thereby reducing network latency and improving round-trip delay. [20] [21]

AS-SET

Autonomous systems can be included in one or more AS-SETs, for example AS-SET of RIPE NCC "AS-12655" has AS1, AS2 and AS3 as its members, [22] but AS1 is also included in other sets in ARIN (AS-INCAPSULA) and APNIC (AS-IMCL). Another AS-SET sources can be RADB, LEVEL3 (tier 1 network now called Lumen Technologies) and also ARIN has ARIN-NONAUTH source of AS-SETs. [23] AS-SETs are created by network operators in an Internet Routing Registry (IRR), like other route objects, and can be included in other AS-SETs and even form cycles. [24] [25]

AS-SET names usually start with "AS-", but can also have a hierarchical name. For example, the administrator of AS 64500 may create an AS-SET called "AS64500:AS-UPSTREAMS", to avoid conflict with other similarly named AS-SETs. [26]

AS-SETs are often used to simplify management of published routing policies. A routing policy is published in the IRR using "import" and "export" (or the newer "mp-import" and "mp-export") attributes, which each contain the source or destination AS number and the AS number imported or exported. Instead of single AS numbers, AS-SETs can be referenced in these attributes, which simplifies management of complex routing policies.

See also

Related Research Articles

<span class="mw-page-title-main">Internet Protocol version 4</span> Fourth version of the Internet Protocol

Internet Protocol version 4 (IPv4) is the fourth version of the Internet Protocol (IP). It is one of the core protocols of standards-based internetworking methods in the Internet and other packet-switched networks. IPv4 was the first version deployed for production on SATNET in 1982 and on the ARPANET in January 1983. It is still used to route most Internet traffic today, even with the ongoing deployment of Internet Protocol version 6 (IPv6), its successor.

<span class="mw-page-title-main">IPv6</span> Version 6 of the Internet Protocol

Internet Protocol version 6 (IPv6) is the most recent version of the Internet Protocol (IP), the communications protocol that provides an identification and location system for computers on networks and routes traffic across the Internet. IPv6 was developed by the Internet Engineering Task Force (IETF) to deal with the long-anticipated problem of IPv4 address exhaustion, and was intended to replace IPv4. In December 1998, IPv6 became a Draft Standard for the IETF, which subsequently ratified it as an Internet Standard on 14 July 2017.

Classless Inter-Domain Routing is a method for allocating IP addresses and for IP routing. The Internet Engineering Task Force introduced CIDR in 1993 to replace the previous classful network addressing architecture on the Internet. Its goal was to slow the growth of routing tables on routers across the Internet, and to help slow the rapid exhaustion of IPv4 addresses.

<span class="mw-page-title-main">Border Gateway Protocol</span> Protocol for communicating routing information on the Internet

Border Gateway Protocol (BGP) is a standardized exterior gateway protocol designed to exchange routing and reachability information among autonomous systems (AS) on the Internet. BGP is classified as a path-vector routing protocol, and it makes routing decisions based on paths, network policies, or rule-sets configured by a network administrator.

<span class="mw-page-title-main">APNIC</span> Regional Internet registry for the Asia Pacific region

APNIC is the regional Internet address registry (RIR) for the Asia-Pacific region. It is one of the world's five RIRs and is part of the Number Resource Organization (NRO).

<span class="mw-page-title-main">Internet Assigned Numbers Authority</span> Standards organization overseeing IP addresses

The Internet Assigned Numbers Authority (IANA) is a standards organization that oversees global IP address allocation, autonomous system number allocation, root zone management in the Domain Name System (DNS), media types, and other Internet Protocol–related symbols and Internet numbers.

InterNIC, known as the Network Information Center (NIC) until 1993, was the organization primarily responsible for Domain Name System (DNS) domain name allocations and X.500 directory services. From its inception in 1972 until October 1, 1991, it was run by the Stanford Research Institute, now known as SRI International, and led by Jake Feinler. From October 1991 until September 18, 1998, it was run by Network Solutions. Thereafter, the responsibility was assumed by the Internet Corporation for Assigned Names and Numbers (ICANN).

Bogon filtering is the practice of filtering bogons, which are bogus (fake) IP addresses of a computer network. Bogons include IP packets on the public Internet that contain addresses that are not in any range allocated or delegated by the Internet Assigned Numbers Authority (IANA) or a delegated regional Internet registry (RIR) and allowed for public Internet use. The areas of unallocated address space are called the bogon space.

<span class="mw-page-title-main">Regional Internet registry</span> Organization responsible for managing network numbering

A regional Internet registry (RIR) is an organization that manages the allocation and registration of Internet number resources within a region of the world. Internet number resources include IP addresses and autonomous system (AS) numbers.

RIPE NCC is the regional Internet registry (RIR) for Europe, the Middle East and parts of Central Asia. Its headquarters are in Amsterdam, Netherlands, with a branch office in Dubai, UAE.

In Internet routing, the default-free zone (DFZ) is the collection of all Internet autonomous systems (AS) that do not require a default route to route a packet to any destination. Conceptually, DFZ routers have a "complete" Border Gateway Protocol table, sometimes referred to as the Internet routing table, global routing table or global BGP table. However, internet routing changes rapidly and the widespread use of route filtering ensures that no router has a complete view of all routes. Any routing table created would look different from the perspective of different routers, even if a stable view could be achieved.

WHOIS is a query and response protocol that is used for querying databases that store an Internet resource's registered users or assignees. These resources include domain names, IP address blocks and autonomous systems, but it is also used for a wider range of other information. The protocol stores and delivers database content in a human-readable format. The current iteration of the WHOIS protocol was drafted by the Internet Society, and is documented in RFC 3912.

<span class="mw-page-title-main">IPv4 address exhaustion</span> Depletion of unallocated IPv4 addresses

IPv4 address exhaustion is the depletion of the pool of unallocated IPv4 addresses. Because the original Internet architecture had fewer than 4.3 billion addresses available, depletion has been anticipated since the late 1980s when the Internet started experiencing dramatic growth. This depletion is one of the reasons for the development and deployment of its successor protocol, IPv6. IPv4 and IPv6 coexist on the Internet.

An Internet Routing Registry (IRR) is a database of Internet route objects for determining, and sharing route and related information used for configuring routers, with a view to avoiding problematic issues between Internet service providers.

<span class="mw-page-title-main">Prefix WhoIs</span>

Prefix WhoIs is an open source project that develops and operates a free whois-compatible framework for stockpiling and querying various routing and registry information. Prefix WhoIs uses global BGP routing data learned from many ISP backbone routers. Other information sources are also supported, such as imported data from every regional Internet registry and geocoding information.

<span class="mw-page-title-main">IPv6 address</span> Label to identify a network interface of a computer or other network node

An Internet Protocol Version 6 address is a numeric label that is used to identify and locate a network interface of a computer or a network node participating in a computer network using IPv6. IP addresses are included in the packet header to indicate the source and the destination of each packet. The IP address of the destination is used to make decisions about routing IP packets to other networks.

Resource Public Key Infrastructure (RPKI), also known as Resource Certification, is a specialized public key infrastructure (PKI) framework to support improved security for the Internet's BGP routing infrastructure.

The Registration Data Access Protocol (RDAP) is a computer network communications protocol standardized by a working group at the Internet Engineering Task Force in 2015, after experimental developments and thorough discussions. It is a successor to the WHOIS protocol, used to look up relevant registration data from such Internet resources as domain names, IP addresses, and autonomous system numbers.

In order to ensure proper working of carrier-grade NAT (CGN), and, by doing so, alleviating the demand for the last remaining IPv4 addresses, a /10 size IPv4 address block was assigned by Internet Assigned Numbers Authority (IANA) to be used as shared address space. This block of addresses is specifically meant to be used by Internet service providers that implement carrier-grade NAT, to connect their customer-premises equipment (CPE) to their core routers.

References

  1. ↑ 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.
  2. ↑ Rekhter, Yakov; Li, Tony (March 1995). A Border Gateway Protocol 4 (BGP-4). IETF. doi: 10.17487/RFC1771 . RFC 1771. (obsoleted by RFC   4271)
  3. ↑ Vohra, Quaizar; Chen, Enke (May 2007). BGP Support for Four-octet AS Number Space. IETF. doi: 10.17487/RFC4893 . RFC 4893. (obsoleted by RFC   6793)
  4. ↑ Huston, Geoff; Michaelson, George (December 2008). Textual Representation of Autonomous System (AS) Numbers. IETF. doi: 10.17487/RFC5396 . RFC 5396.
  5. ↑ Q. Vohra; E. Chen (December 2012). BGP Support for Four-Octet Autonomous System (AS) Number Space. IETF. doi: 10.17487/RFC6793 . RFC 6793.
  6. ↑ "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.
  7. ↑ G. Huston; G. Michaelson (February 2012). Validation of Route Origination Using the Resource Certificate Public Key Infrastructure (PKI) and Route Origin Authorizations (ROAs). IETF. doi: 10.17487/RFC6483 . RFC 6483.
  8. ↑ J. Haas; J. Mitchell (July 2014). Reservation of Last Autonomous System (AS) Numbers. IETF. doi: 10.17487/RFC7300 . ISSN   2070-1721. BCP 6. RFC 7300.
  9. ↑ W. Kumari; R. Bush; H. Schiller; K. Patel (August 2015). Codification of AS 0 Processing. IETF. doi: 10.17487/RFC7607 . RFC 7607.
  10. ↑ "IRR explorer". irrexplorer.dashcare.nl. Retrieved 2021-10-24.
  11. ↑ G. Huston (December 2008). Autonomous System (AS) Number Reservation for Documentation Use. Network Working Group. doi: 10.17487/RFC5398 . RFC 5398.
  12. ↑ J. Mitchell (July 2013). Autonomous System (AS) Reservation for Private Use. IETF. doi: 10.17487/RFC6996 . ISSN   2070-1721. BCP 6. RFC 6996.
  13. ↑ Bates, Tony; Smith, Philip; Huston, Geoff. "CIDR report" . Retrieved 2018-12-31.
  14. ↑ "World - Autonomous System Number statistics - Sorted by number". Regional Internet Registries Statistics. Retrieved 2018-12-31.
  15. ↑ "How to setup a LIR". www.afrinic.net. Retrieved 23 March 2020.
  16. ↑ Mar 2017, Publication date: 14. "Autonomous System (AS) Number Assignment Policies". RIPE Network Coordination Centre. Retrieved 23 March 2020.{{cite web}}: CS1 maint: numeric names: authors list (link)
  17. 1 2 "Autonomous System (AS) Numbers". IANA.org. 2018-12-07. Retrieved 2018-12-31.
  18. ↑ "Revocation of Internet Resources allocation". www.lacnic.net. Retrieved 2021-02-17.
  19. ↑ "Policy prop-132 (AS0 for unallocated space) deployed in service". APNIC Blog. 2020-09-02. Retrieved 2020-09-12.
  20. 1 2 Krzyzanowski, Paul (21 March 2016). "Understanding Autonomous Systems: Routing and Peering". Rutgers University, Department of Computer Science. Archived from the original on 3 March 2022. Retrieved 29 March 2022.
  21. ↑ "Glossary: Internet exchange point (IXP)". CloudFlare. Archived from the original on 30 March 2022. Retrieved 29 March 2022.
  22. ↑ "AS-12655 - bgp.he.net". bgp.he.net. Retrieved 2021-10-24.
  23. ↑ "IRR explorer". irrexplorer.nlnog.net. Retrieved 2022-01-30.
  24. ↑ "IRR explorer". irrexplorer.nlnog.net. Retrieved 2022-01-30.
  25. ↑ "IDIDB - Объекты AS-SET". www.ididb.ru. Retrieved 2021-10-24.
  26. ↑ "Descriptions of Primary Objects - RIPE Database Docs" . Retrieved 2023-04-05.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.