This documents obsoletes ripe-65, version 0.6 of this document
Abstract
This document describes the procedures for the reassignment of IP
network numbers from blocks obtained from the RIPE Network Coordination
Centre. It deals with items as providing information for the RIPE
database, as well as reassignment of IP addresses in light of
the "Supernetting" proposal, as documented in RFC 1338, by Vince Fuller
et al.
Introduction
Since May 1st 1992, the RIPE Network Coordination Centre (NCC) is
acting as a delegated registry for IP networks numbers to NICs and NOCs
in Europe. It is RIPE NCC policy not to give out network numbers to
individual organisations, who should refer in turn, to their IP network
service provider.
The mission of the RIPE NCC is to give network numbers to the various
service providers and NICs. The NICs and NOCs can then reassign the
actual IP network numbers to organisations requesting IP network
numbers.
Class B Network Number Allocation Procedure
Service providers can request Class B network numbers on a one-by-one
basis from the RIPE NCC. Because class B address space is a critical
resource, a request for a class B network number must be accompanied by
a justification in terms of the requesting organisation's size, current
network and expected network growth. The requestor should also make
clear why they cannot use a block of class C network numbers to achieve
their goals. The RIPE NCC will review requests using the same standards
as any other Internet Registry, particularly the US NIC.
Class C Allocation Procedures
NICs and NOCs accepting a block of class C numbers agree to adhere to
the following procedures:
A) 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.
1.0 Definition Link: #1
2.0 Assignment Criteria Link: #2
3.0 Assignments for Internet Experiments Link: #3
3.1 Defining the Experiment Link: #31
3.2 Non-commercial Basis Link: #32
3.3 Period of the Resource Registration Link: #33
4.0 Returning AS Numbers Link: #4
5.0 32-bit AS Numbers Link: #5
6.0 Registration Link: #6
7.0 References Link: #7
8.0 Attribution Link: #8
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 RFC 1771 Link: ftp://ftp.ripe.net/rfc/rfc1771.txt , "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 RFC 1930 Link: ftp://ftp.ripe.net/rfc/rfc1930.txt .
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.
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.
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 RFC 2026 Link: ftp://ftp.ripe.net/rfc/rfc2026.txt , 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.
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.
Resources issued for an experiment must not be used for commercial purposes.
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.
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.
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 Link: 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 Link: http://www.ietf.org/rfc/rfc1930.txt
[RFC2026] "The Internet Standards Process -- Revision 3 IETF Experimental RFC http://www.ietf.org/rfc/rfc2026.txt Link: 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