You are here: Home > Publications > RIPE Document Store > RIPE NCC Internet Numbers Registration Procedures

Changes to RIPE NCC Internet Numbers Registration Procedures

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-065: ripe-496: This document describes the policies for the assignment of globally unique Autonomous System (AS) Numbers within the RIPE NCC Internet Numbers Registration Procedures service region. These policies are developed by the RIPE Community following the RIPE Policy Development Process.
delete: <p> delete: <b> insert: <h2>

Abstract insert: </h2>

insert: <p>

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. insert: </p>

insert: <h2>

Contents insert: </h2>

insert: <p>

1.0 insert: <a href="#1"> Definition insert: </a> insert: <br />
2.0 insert: <a href="#2"> Assignment Criteria insert: </a> insert: <br />
3.0 insert: <a href="#3"> Assignments for Internet Experiments insert: </a> insert: <br />
3.1 insert: <a href="#31"> Defining the Experiment insert: </a> insert: <br />
3.2 insert: <a href="#32"> Non-commercial Basis insert: </a> insert: <br />
3.3 insert: <a href="#33"> Period of the Resource Registration insert: </a> insert: <br />
4.0 insert: <a href="#4"> Returning AS Numbers insert: </a> insert: <br />
5.0 insert: <a href="#5"> 32-bit AS Numbers insert: </a> insert: <br />
6.0 insert: <a href="#6"> Registration insert: </a> insert: <br />
7.0 insert: <a href="#7"> References insert: </a> insert: <br />
8.0 insert: <a href="#8"> Attribution insert: </a> insert: </p>

insert: <h2>

insert: <a id="1" name="1"> insert: </a> 1.0 Definition insert: </h2>

insert: <p>

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 insert: <a href="ftp://ftp.ripe.net/rfc/rfc1771.txt"> RFC 1771 insert: </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. insert: </p>

insert: <h2>

insert: <a id="12" name="2"> insert: </a> 2.0 Assignment Criteria insert: </h2>

insert: <p>

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 insert: <a href="ftp://ftp.ripe.net/rfc/rfc1930.txt"> RFC 1930 insert: </a> . insert: </p>

insert: <p>

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. insert: </p>

insert: <p>

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 “ insert: <a href="http://www.ripe.net/ripe/docs/contract-req.html"> Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region insert: </a> ”. insert: </p>

insert: <h2>

insert: <a id="13" name="3"> insert: </a> 3.0 Assignments for Internet Experiments insert: </h2>

insert: <p>

Organisations often require deployment tests for new Internet services and technologies. These require numbering resources for the duration of the test. The policy goal of resource conservation is of reduced importance when resources are issued on a temporary basis. insert: </p>

insert: <h2>

insert: <a id="14" name="31"> insert: </a> 3.1 Defining the Experiment insert: </h2>

insert: <p>

The experiment for which the organisation receives numbering resources must be documented. This may be in the form of a current IETF Experimental RFC (see insert: <a href="ftp://ftp.ripe.net/rfc/rfc2026.txt"> RFC 2026 insert: </a> , Section 4.2.1 or an “experiment proposal” detailing the resources required and the activities to be carried out. A single AS Number will be assigned. If more than one AS Number is required for the experiment, this should be indicated and explained in the request. insert: </p>

insert: <p>

The experiment proposal must be made public (e.g. published on a website), upon registration of the resources by the RIPE NCC. When the experiment is concluded the results must be published free of charge and free from disclosure constraints. insert: </p>

insert: <h2>

insert: <a id="15" name="32"> insert: </a> 3.2 Non-commercial Basis insert: </h2>

insert: <p>

Resources issued for an experiment must not be used for commercial purposes. insert: </p>

insert: <h2>

insert: <a id="16" name="33"> insert: </a> 3.3 Period of the Resource Registration insert: </h2>

insert: <p>

The resources will be issued on a temporary basis for a period of one year. Renewal of the resources' registration is possible on receipt of a new request that details any continuation of the experiment during the extended period. insert: </p>

insert: <p>

The resources issued cannot be used for a commercial service following the conclusion of the experiment. At the end of the assignment period the AS Number must be returned to the RIPE NCC. insert: </p>

insert: <h2>

insert: <a id="17" name="4"> insert: </a> 4.0 Returning AS Numbers insert: </h2>

insert: <p>

If an organisation no longer uses the AS Number, it must be returned to the public pool of AS Numbers. The RIPE NCC can then reassign the AS Number to another organisation. insert: </p>

insert: <h2>

insert: <a id="18" name="5"> insert: </a> 5.0 32-bit AS Numbers insert: </h2>

insert: <p>

The RIPE NCC assigns 32-bit AS Numbers according to the following timeline: insert: </p>

insert: <ul>
    insert: <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. insert: <br />
    insert: <br />
    insert: </li>
  • insert: <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. insert: <br />
    insert: <br />
    insert: </li>
  • insert: <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. insert: </li>
  • insert: </ul>
insert: <h2>

insert: <a id="19" name="6"> insert: </a> 6.0 Registration insert: </h2>

insert: <p>

The RIPE NCC will register the resources issued in the RIPE Database. insert: </p>

insert: <h2>

insert: <a id="110" name="7"> insert: </a> 7.0 References insert: </h2>

insert: <p>

[RFC1771] "A Border Gateway Protocol 4 (BGP-4)" insert: <a href="http://www.ietf.org/rfc/rfc1771.txt"> http://www.ietf.org/rfc/rfc1771.txt insert: <br />
insert: </a>
[RFC1930] " Guidelines for creation, selection, and registration of an Autonomous System (AS)" insert: <a href="http://www.ietf.org/rfc/rfc1930.txt"> http://www.ietf.org/rfc/rfc1930.txt insert: </a> insert: <br />
[RFC2026] "The Internet Standards Process -- Revision 3 IETF Experimental RFC insert: <a href="http://www.ietf.org/rfc/rfc2026.txt"> http://www.ietf.org/rfc/rfc2026.txt insert: </a> see Sec. 4.2.1 insert: </p>

insert: <h2>

insert: <a id="111" name="8"> insert: </a> 8.0 Attribution insert: </h2>

insert: <p>

This document is obsoleted compiled from policies developed by ripe-72, version 0.7 of this documen delete: </b> t delete: </p> delete: <p> This document describes the procedures for the reassignment of IP delete: <br /> network numbers from blocks obtained from the RIPE Network Coordination delete: <br /> Centre. It deals with items as providing information for the RIPE and delete: <br /> US NIC databases, as well as reassignment of IP addresses in light of delete: <br /> the "Supernetting" proposal, as documented in RFC 1338, the RIPE community. insert: </p>

insert: <p>

The following people actively contributed by Vince Fuller delete: <br /> et al. delete: <br /> delete: <br /> delete: <br /> Introduction delete: <br /> delete: <br /> Since May 1st 1992, the RIPE Network Coordination Centre (NCC) is delete: <br /> acting as a delegated registry for IP networks numbers to NICs and NOCs delete: <br /> in Europe. It is RIPE NCC policy not to give out network numbers to delete: <br /> individual organisations, who should refer in turn, to their IP network delete: <br /> service provider. delete: <br /> delete: <br /> The mission of the RIPE NCC is to give network numbers to the various delete: <br /> service providers and NICs. The NICs and NOCs can then reassign the delete: <br /> actual IP network numbers to organisations requesting IP network delete: <br /> numbers. delete: <br /> delete: <br /> delete: <br /> Class B Network Number Allocation Procedure delete: <br /> delete: <br /> Service providers can request Class B network numbers on a one-by-one delete: <br /> basis from the RIPE NCC. Because class B address space is a critical delete: <br /> resource, a request for a class B network number must be accompanied by delete: <br /> a justification in terms of the requesting organisation's size, current delete: <br /> network and expected network growth. The requestor should also make delete: <br /> clear why they cannot use a block of class C network numbers to achieve delete: <br /> their goals. The RIPE NCC will review requests using the same standards delete: <br /> as any other Internet Registry, particularly the US NIC. delete: <br /> delete: <br /> delete: <br /> Class C Allocation Procedures delete: <br /> delete: <br /> delete: <br /> NICs and NOCs accepting a block of class C numbers agree to adhere to delete: <br /> the following procedures: delete: <br /> delete: <br /> A) The RIPE NCC will assign complete class C blocks to individual NICs delete: <br /> and NOCs. They can be requested from <hostmaster@ripe.net>. delete: <br /> delete: <br /> B) In order to prevent implementation problems, network numbers ending delete: <br /> with 0 or 255 should NOT be reassigned. delete: <br /> delete: <br /> C) Full information about reassigned network numbers must be reported delete: <br /> back to the RIPE NCC and the US NIC in full RIPE database format (ref delete: <br /> ripe-13). The complete entries should be sent immediately after delete: <br /> reassignment to <ripe-dbm@ripe.net> and <hostmaster@nic.ddn.mil> delete: <br /> Unfortunately, the RIPE NCC is not yet ready to accept block entries for delete: <br /> the RIPE database, so you must send in each individual entry. delete: <br /> delete: <br /> D) Reassignment of class C network numbers should be done in a manner delete: <br /> that facilitates Supernetting (see next section). delete: <br /> delete: <br /> E) Requests for network numbers should be reasonable. All NICs and NOCs delete: <br /> should prevent stockpiling of network numbers. delete: <br /> delete: <br /> F) On first request from the RIPE NCC, the class C network numbers not delete: <br /> yet reassigned, must be returned to the RIPE NCC. delete: <br /> delete: <br /> delete: <br /> Supernetting delete: <br /> delete: <br /> NICs and NOCs reassigning IP network numbers are urgently requested to delete: <br /> read the Supernetting proposal by Vince Fuller et al. This document can delete: <br /> be obtained from the rfc section of the RIPE document store or other RFC delete: <br /> servers. It is called rfc1338.txt. delete: <br /> The Supernetting proposal was made to reduce the increase of routing delete: <br /> table size in the current Internet. It proposes to create a hierarchy delete: <br /> of IP network numbers, which can then be aggregated resulting in less delete: <br /> routing table entries in routing equipment. While this proposal has not delete: <br /> been formally adopted we expect that something at least along the same delete: <br /> principle will be implemented in the near future. delete: <br /> delete: <br /> Here is how it works: delete: <br /> delete: <br /> If an organisation A needs 8 class C network numbers, the numbers should delete: <br /> be given out in such a way that the routing information for each of delete: <br /> these 8 networks could appear as one entry with the correct mask in delete: <br /> routers. delete: <br /> delete: <br /> More concretely: delete: <br /> delete: <br /> Service provider S hands out networks 192.24.8 making proposals through 192.24.15 to delete: <br /> organisation A. These networks can then appear in routing equipment as a delete: <br /> supernet route to 192.24.8 with mask 255.255.248.0. This way 8 class C delete: <br /> network numbers appear as one routing table entry. delete: <br /> delete: <br /> The guidelines that can be derived from the Supernetting proposal are: delete: <br /> delete: <br /> A) Service providers should reserve blocks of class C network numbers from delete: <br /> their allocation for each organisations requesting class C network numbers. delete: <br /> delete: <br /> B) The size of these blocks should always be a power of 2. delete: <br /> delete: <br /> C) The numbers in these blocks should be contiguous. delete: <br /> delete: <br /> D) The blocks should start on bit boundaries. delete: <br /> (ie powers of 2, AND multiples of the block size) delete: <br /> delete: <br /> E) The blocks reserved for an organisation should be sufficient for a delete: <br /> reasonable expected growth over the next few years. delete: <br /> delete: <br /> F) Multi-homed organizations may obtain address space from one of their delete: <br /> providers, the RIPE NCC, or the global NIC, as is appropriate to their delete: <br /> network configuration. These organisations are strongly encouraged to delete: <br /> contact the RIPE NCC for guidance. delete: <br /> delete: <br /> If you have any questions concerning this, please do not hesitate to delete: <br /> call or mail us at ncc@ripe.net. delete: </p> the RIPE Policy Development Process: insert: <br />
Nick Hilliard, Geoff Huston insert: </p>

RIPE NCC Internet Numbers Registration Procedures Autonomous System (AS) Number Assignment Policies