This document describes the policies for the assignment of globally unique Autonomous System (AS) Numbers within the RIPE NCC service region. These policies are developed by the RIPE Community following the RIPE Policy Development Process.
An Autonomous System (AS) is a group of IP networks run by one or more network operators with a single clearly defined routing policy. When exchanging exterior routing information, each AS is identified by a unique number. Exterior routing protocols such as BGP, described in RFC1771, "A Border Gateway Protocol 4 (BGP-4)", are used to exchange routing information between Autonomous Systems. An AS will normally use some interior gateway protocol to exchange routing information on its internal networks.
In order to help decrease global routing complexity, a new AS Number should be used only if a new external routing policy is required, see RFC1930.
A network must be multihomed in order to qualify for an AS Number.
When requesting an AS Number the routing policy of the Autonomous System must be provided. The new unique routing policy should be defined in RPSL language, as used in the RIPE Database.
The RIPE NCC will assign the AS Number directly to the End User upon a request properly submitted to the RIPE NCC either directly or through a sponsoring LIR. AS Number assignments are subject to the policies described in the RIPE NCC document entitled “Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region”.
If an organisation no longer uses the AS Number, it should be returned to the public pool of AS Numbers. The RIPE NCC can then reassign the AS Number to another organisation.
The transfer of Internet number resources is governed by the RIPE Document, "RIPE Resource Transfer Policies".
The RIPE NCC assigns 32-bit AS Numbers according to the following timeline:
The RIPE NCC will register the resources issued in the RIPE Database.
[RFC1771] "A Border Gateway Protocol 4 (BGP-4)" http://www.ietf.org/rfc/rfc1771.txt
[RFC1930] " Guidelines for creation, selection, and registration of an Autonomous System (AS)" http://www.ietf.org/rfc/rfc1930.txt
[RFC2026] "The Internet Standards Process -- Revision 3 IETF Experimental RFC http://www.ietf.org/rfc/rfc2026.txt see Sec. 4.2.1
This document is compiled from policies developed by the RIPE community.
The following people actively contributed by making proposals through the RIPE Policy Development Process:
Nick Hilliard, Geoff Huston