You are here: Home > Publications > RIPE Document Store > Autonomous System (AS) Number Assignment Policies

Changes to Autonomous System (AS) Number Assignment Policies

Legend	(+) Added	(-) Deleted
Changed	Tag Added	Tag Deleted

ripe-638: 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. ripe-085: Guidelines For The Delegation Of Zones In The 193.in-addr.arpa Domai

delete: <h3> delete:  Abstract delete:  delete: </h3> delete:  insert: 

Introduction insert:  
insert:  
This document describes the policies for procedures for the delegation of au- insert:  
thority of zones in the 193.in-addr.arpa domain. As of March insert:  
16th 1993 the RIPE NCC has been delegated the authority for the insert:  
193.in-addr.arpa domain from the root. Due to the fact that in insert:  
the 193.x.y address space blocks of 256 class C network numbers insert:  
are further delegated to local registries , the possibility ex- insert:  
ists to also delegate the zone for these blocks in the 193.in- insert:  
addr.arpa domain. This document describes some guidelines and insert:  
procedures for this type of delegation and the delegation of re- insert:  
verse zones for individual class C networks in 193.x.y. insert:  
insert:  
insert:  
A bit more explained insert:  
insert:  
With the assignment of globally unique Autonomous class C network numbers following the CIDR insert:  
(RFC 1338) model, in which large chunks of the address space are insert:  
delegated to one region, and within that region blocks of class C insert:  
network numbers are delegated to service providers and non- insert:  
provider registries, some hierarchy in the address space is insert:  
created, similar to the hierarchy in the domain name space. Due insert:  
to this hierarchy the reverse Domain Name System (AS) Numbers within the RIPE NCC service region. These policies are developed by the RIPE Community following the RIPE Policy Development Process. delete:  delete:  delete:  delete: <h3> delete:  Contents delete:  delete: </h3> delete:  1.0 delete: <a class="anchor-link" title="" href="#Definition" target="_self"> Definition delete: </a> delete:  delete:  2.0 delete: <a class="anchor-link" title="" href="#AssignmentCriteria" target="_self"> Assignment Criteria delete: </a> delete:  delete:  3.0 delete: <a class="anchor-link" title="" href="#Returning" target="_self"> Returning AS Numbers delete: </a> delete:  delete:  4.0 delete: <a class="anchor-link" title="" href="#Transferring" target="_self"> Transferring AS Numbers delete: </a> delete:  delete:  5.0 delete: <a class="anchor-link" title="" href="#ASnumbers" target="_self"> 32-bit AS Numbers delete: </a> delete:  delete:  6.0 delete: <a class="anchor-link" title="" href="#Registration" target="_self"> Registration delete: </a> delete:  delete:  7.0 delete: <a class="anchor-link" title="" href="#References" target="_self"> References delete: </a> delete:  delete:  8.0 delete: <a class="anchor-link" title="" href="#Attribution" target="_self"> Attribution delete: </a> delete:  delete:  delete:  delete: <h3> delete: <a name="Definition"> delete: </a> 1.0 Definition delete: </h3> delete:  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 delete: <a href="ftp://ftp.ripe.net/rfc/rfc1771.txt"> RFC1771 delete: </a> , "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. delete:  delete:  delete:  delete: <h3> delete: <a name="AssignmentCriteria"> delete: </a> 2.0 Assignment Criteria delete: </h3> delete:  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 delete: <a href="ftp://ftp.ripe.net/rfc/rfc1930.txt"> RFC1930 delete: </a> . delete:  delete:  A network must be multihomed in order to qualify for an AS Number. delete:  delete:  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, mapping can also insert:  
be delegated in a similar model as used in the RIPE Database. delete:  delete:  for the normal Domain insert:  
Name System. For instance, the RIPE NCC has been assigned the insert:  
complete class C address space starting with 193. It is there- insert:  
fore possible to delegate the 193.in-addr.arpa domain completely insert:  
to the RIPE NCC, instead of each and every reverse mapping in the insert:  
193.in-addr.arpa domain to be registered with the INTERNIC. This insert:  
implies that all 193.in-addr.arpa resistrations will be done by insert:  
the RIPE NCC. Even better, since service providers receive com- insert:  
plete class C network blocks from the RIPE NCC, the RIPE NCC can insert:  
delegate the reverse registrations for such complete blocks to insert:  
these local registries. This implies that customers of these insert:  
service providers no longer have to register their reverse domain insert:  
mapping with the root, but the service provider have authority insert:  
over that part of the reverse mapping. This decreases the work- insert:  
load on the INTERNIC and the RIPE NCC, and at the same time in- insert:  
crease the service a provider can offer its customers by improve insert:  
response times for reverse mapping changes . However there are insert:  
some things that need to be examined a bit more closely to avoid insert:  
confusion and inconsistencies. These issues are covered in the insert:  
next section. insert:  
insert:  
insert:  
Procedures for the delegation of direct subdomains of 193.in- insert:  
addr.arpa insert:  
insert:  
1. A secondary nameserver at ns.ripe.net is mandatory for all insert:  
blocks of class C network numbers delegated in the 193.in- insert:  
addr.arpa domain. insert:  
insert:  
2. Because of the increasing importance of correct reverse ad- insert:  
dress mapping, for all delegated blocks a good set of secondaries insert:  
must be defined. There should be at least 2 nameservers for all insert:  
blocks delegated, excluding the RIPE NCC secondary. insert:  
insert:  
3. The delegation of a class C block in the 193.in-addr.arpa insert:  
domain can be requested by sending in a domain object for the insert:  
RIPE database to <[email protected]> with all necessary contact insert:  
and nameserver information. The RIPE NCC will assign the AS Number directly to the End User upon a request properly submitted to the RIPE then forward all insert:  
current reverse zones inside this block to the registry, and insert:  
after addition of these by the registry, the NCC either directly or through a sponsoring LIR. AS Number assignments will check the insert:  
working of the reverse server. Once everything is setup proper- insert:  
ly, the NCC will delegate the block, and submit the database ob- insert:  
ject for inclusion in the database. An example domain object can insert:  
be found at the end of this document. insert:  
insert:  
4. All reverse servers for blocks must be reachable from the insert:  
whole of the Internet. In short, all servers must meet similar insert:  
connectivity requirements as top-level domain servers. insert:  
insert:  
5. Running the reverse server for class C blocks does not imply insert:  
that one controls that part of the reverse domain, it only im- insert:  
plies that one administers that part of the reverse domain. insert:  
insert:  
6. Before adding individual nets, the administrator of a reverse insert:  
domain must check wether all servers to be added for these nets insert:  
are subject to the policies described in the RIPE NCC document entitled “ delete: <a href="http://www.ripe.net/ripe/docs/contract-req"> Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region delete: </a> ”. delete:  delete:  delete:  delete: <h3> delete:  delete: <a name="Returning"> delete: </a> 3.0 Returning AS Numbers delete:  delete: </h3> delete:  If an organisation indeed setup properly. insert:  
insert:  
7. There are some serious implications when a customer of a ser- insert:  
vice provider that uses address space out of the service provider insert:  
class C blocks, moves to another service provider. The previous insert:  
service provider cannot force its ex-customer to change network insert:  
addresses, and will have to continue to provide the appropriate insert:  
delegation records for reverse mapping of these addresses, even insert:  
though it they are no longer uses the AS Number, it belonging to a customer. insert:  
insert:  
8. The registration of the reverse zones for individual class C insert:  
networks will usually be done by the registry administering the insert:  
class C block this network has been assigned from. The registry insert:  
will make the necessary changes to the zone, and update the net- insert:  
work objects in the RIPE database for these networks, to reflect insert:  
the correct "rev-srv" fields. In case the RIPE NCC receives a insert:  
request for the reverse zone of an individual class C network out insert:  
of a block that has been delegated, the request will be forwarded insert:  
to the zone contact for this reverse block. insert:  
insert:  
9. The NCC advises the following timers and counters for direct insert:  
subdomains of 193.in-addr.arpa: 8 hours refresh (28800 seconds), insert:  
2 hours retry (7200 seconds), 7 days expire (604800 seconds) and insert:  
1 day Time To Live (86400 seconds). The retry counter should be returned to the public pool of AS Numbers. insert:  
lowered where connectivity is unstable. insert:  
insert:  
Above procedures are defined to ensure the necessary high availa- insert:  
bility for the 193 reverse domains, and to minimize confusion. insert:  
The RIPE NCC can then reassign the AS Number to another organisation. delete:  delete:  delete:  delete: <h3> delete:  delete: <a name="Transferring"> delete: </a> 4.0 Transferring AS Numbers delete:  delete: </h3> delete:  Any holder of Autonomous System (AS) Numbers is allowed to re-assign AS Numbers that were previously assigned to them by the RIPE NCC or otherwise through the Regional Internet Registry System. delete:  delete:  AS Numbers may only be re-assigned in accordance with the RIPE Policy, “ delete: <a href="http://www.ripe.net/ripe/docs/contract-req"> Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region delete: </a> ”. delete:  delete:  Re-assignments must be reflected in the RIPE Database. This re-assignment can either be on a permanent or non-permanent basis. delete:  delete:  The RIPE NCC will record the change of AS Numbers after the transfer. delete:  delete:  ensure fast repsonse times for addition requests, insert:  
and will in principle update the 193.in-addr.arpa domain at least insert:  
once per working day. insert:  
insert:  
Example domain object to request a block delegation insert:  
insert:  
domain: 202.193.in-addr.arpa insert:  
descr: Pan European Organisations class C block insert:  
admin-c: Daniel Karrenberg insert:  
tech-c: Marten Terpstra insert:  
zone-c: Marten Terpstra insert:  
nserver: ns.eu.net insert:  
nserver: sunic.sunet.se insert:  
nserver: ns.ripe.net insert:  
changed: [email protected] 930319 insert:  
source: RIPE insert:  
insert:  
insert:  
insert:  
Procedures for the delegation of individual network zones by the insert:  
RIPE NCC. insert:  
insert:  
The registration of the reverse zones for individual class C net- insert:  
works will usually be done by the registry administering the insert:  
class C block this network has been assigned from. In case the insert:  
zone corresponding to the class C block has not been delegated, insert:  
the RIPE NCC will publish a separate list of automatically add the reverse nameserver as insert:  
specified in the "rev-srv" attribute of the RIPE database object insert:  
for this network, using the following procedures: insert:  
insert:  
1. Because of the increasing importance of correct reverse ad- insert:  
dress mapping, for all AS Numbers transferred under delegated networks a good set of secon- insert:  
daries must be defined. There should be at least two nameservers insert:  
for all networks delegated. insert:  
insert:  
2. The "rev-srv" field should ONLY contain one fully qualified insert:  
domain name of a nameserver which is authoritative for the re- insert:  
verse zone for this section. network. insert:  
insert:  
3. If a network has or is going to have any external connectivi- insert:  
ty, it is strongly recommended that it has at least one reverse insert:  
nameserver that can be reached from all of the Internet. insert:  
insert:  
4. The publication shall occur on monthly basis or more frequently if the RIPE checking and addition of the reverse zones for single net- insert:  
works is completely automated at the RIPE NCC. Although we do insert:  
our best to check the setup of the nameservers, these does not insert:  
receive the same level of scrutiny as nameservers for blocks of insert:  
class C network numbers. It is the responsibility of the network insert:  
contacts to ensure proper operation. insert:  
insert:  
5. Any problems regarding the reverse zones in 193.in-addr.arpa insert:  
should be directed to <[email protected]>. insert:  
insert:  
The NCC so chooses. also suggests that similar procedures are set up for the insert:  
delegation of reverse zones for individual class C networks from insert:  
the registries to individual organisations.

delete:  The list will contain information about approved and non-approved transfers. delete:  delete:  The following information will be published for approved transfers: delete:  delete: <ul> delete: <li> The name of the transferring party delete: </li> delete: <li> The name(s) of the receiving party or parties delete: </li> delete: <li> The transferred AS Number delete: </li> delete: <li> The date each AS Number was transferred delete: </li> delete: </ul> delete:  Non-approved transfers will be published in aggregate statistics. In the statistics the following information will be published: delete:  delete: <ul> delete: <li> The Number of requested transfers not approved after the RIPE NCC's evaluation delete: </li> delete: <li> The sum of the AS Numbers included in the requested transfers delete: </li> delete: </ul> delete:  Neither the AS Numbers nor the organisations involved will be identified in these statistics. delete:  delete:  Please note that the transferring party always remains responsible for the AS Number it receives from the RIPE NCC until the transfer of the resource to another party is completed or if the resource is returned. delete:  delete:  Re-assigned AS Numbers are no different from AS Numbers assigned directly by the RIPE NCC and so must be used by the receiving party according to the policies described in this document. delete:  delete:  delete:  delete: <h3> delete:  delete: <a name="ASnumbers"> delete: </a> 5.0 32-bit AS Numbers delete:  delete: </h3> delete:  The RIPE NCC assigns 32-bit AS Numbers according to the following timeline: delete:  delete: <ul> delete: <li> From 1 January 2007 the RIPE NCC will process applications that specifically request 32-bit only AS Numbers (AS Numbers that can not be represented with 16 bits) and assign such AS Numbers as requested by the applicant. In the absence of any specific request for a 32-bit only AS Number, the RIPE NCC will assign a 16-bit AS Number. delete: </li> delete: </ul> delete: <ul> delete: <li> From 1 January 2009 the RIPE NCC will process applications that specifically request 16-bit AS Numbers and assign such AS Numbers as requested by the applicant. In the absence of any specific request for a 16-bit AS Number, the RIPE NCC will assign a 32-bit only AS Number. delete: </li> delete: </ul> delete: <ul> delete: <li> From 1 January 2010 the RIPE NCC will cease to make any distinction between 16-bit AS Numbers and 32-bit only AS Numbers, and it will operate AS Number assignments from an undifferentiated 32-bit AS Number allocation pool. delete: </li> delete: </ul> delete:  delete:  delete: <h3> delete:  delete: <a name="Registration"> delete: </a> 6.0 Registration delete:  delete: </h3> delete:  The RIPE NCC will register the resources issued in the RIPE Database. delete:  delete:  delete:  delete: <h3> delete:  delete: <a name="References"> delete: </a> 7.0 References delete:  delete: </h3> delete:  [RFC1771] "A Border Gateway Protocol 4 (BGP-4)" delete: <a href="http://www.ietf.org/rfc/rfc1771.txt"> http://www.ietf.org/rfc/rfc1771.txt delete: </a> delete:  delete:  [RFC1930] " Guidelines for creation, selection, and registration of an Autonomous System (AS)" delete: <a href="http://www.ietf.org/rfc/rfc1930.txt"> http://www.ietf.org/rfc/rfc1930.txt delete: </a> delete:  delete:  [RFC2026] "The Internet Standards Process -- Revision 3 IETF Experimental RFC delete: <a href="http://www.ietf.org/rfc/rfc2026.txt"> http://www.ietf.org/rfc/rfc2026.txt delete: </a> see Sec. 4.2.1 delete:  delete:  delete:  delete: <h3> delete:  delete: <a name="Attribution"> delete: </a> 8.0 Attribution delete:  delete: </h3> delete:  This document is compiled from policies developed by the RIPE community. delete:  delete:  The following people actively contributed by making proposals through the RIPE Policy Development Process: delete:  delete:  Nick Hilliard, Geoff Huston delete:  delete:  delete:  delete:  delete:  delete:  delete: 

Autonomous System (AS) Number Assignment Policies Guidelines For The Delegation Of Zones In The 193.in-addr.arpa Domain