RIPE NCC – the RIR overview and main terms IP subnets owners should know

RIPE NCC history

RIPE NCC (Réseaux IP Européens Network Coordination Centre) is the regional Internet registry (RIR) for Europe, the Middle East and parts of Central Asia headquartered in Amsterdam, Netherlands.

RIPE NCC history begins in November, 1989, when the first collaborative forum RIPE opened its doors to all parties interested in IP networks . The first document describing the RIPE NCC was published in September 1990. Later in March, 1992 in the Dutch National Institute for High Energy Physics the first two servers of the RIPE NCC were set up. Starting from April, 1992 RIPE NCC began their operations with only 3 employees. The first major task for the RIR was to act as a Regional Internet Registry (RIR) and maintain the so-called RIPE Database, created and supported by volunteers. The aim of the RIPE database was to collect the information about address space usage in the European region. As a legal entity it was established in November 1997 when the Dutch version of the articles of association was deposited with the Amsterdam Chamber of Commerce.

Main documents:

There’re a lot of different policies, but the key ones are:

RIPE-733. The latest IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region that became effective after the IPv4 shortage.
RIPE-738. IPv6 Address Allocation and Assignment Policy
RIPE-757. Independent Internet Number Resources – Contractual Relationship Changes Between Sponsoring LIR and End User
RIPE-682. RIPE Resource Transfer Policies
RIPE-767. Requirements for the RIPE Database

All you need to know about internet address space management in RIPE NCC service region:

IPv4 Subnet types

There’re four IPv4 parent subnet types:

ALLOCATED PA – IPv4 subnet allocated by RIPE NCC to LIR
ASSIGNED PI – IPv4 subnet allocated by RIPE NCC to end user
LEGACY – IPv4 subnet allocated by IANA to end user (IANA allocated IPv4 networks directly before RIRs were established)
ASSIGNED ANYCAST – IPv4 subnet has been assigned by RIPE NCC for use in TLD anycast networks.

And there’re four IPv4 assignment types available for IPv4 owners:

ASSIGNED PA – an assignment made by LIR to end user from ALLOCATED PA. Assigned PA is always smaller than parent ALLOCATED PA
SUB-ALLOCATED PA – a sub-allocation made by LIR to downstream network operator. A downstream network operator is authorized to create smaller assignments (ASSIGNED PA)
LIR-PARTITIONED PA –This status is set when LIR would like to document distribution and delegate management of allocated space within their organisation. IPv4 LIR-PARTITIONED network is not considered used.
LEGACY – a subnet assigned from parent LEGACY has LEGACY status

IPv4 transfer terms

Main IPv4 transfer terms and restrictions are:

An IPv4 subnet cannot be transferred the next 2 years after it’s last allocation or transfer
An IPv4 PA transfer request is made by offering party.
An IPv4 PI transfer request is made by Sponsoring LIR of the offering party or by offering party if it’s a LIR
An IPv4 Legacy transfer request can be made by both parties.
Both parties shall provide a valid company registration document which shows the person authorized to act on behalf of the company and a transfer agreement. There’re several transfer agreement types depending on the IPv4 subnet type.

IPv4 assignment restrictions:

At least a part of IPv4 subnet allocated by RIPE NCC (ALLOCATED PA) shall be announced within RIPE NCC service region
An ASSIGNED PI IPv4 subnet can only be used for the end user’s own infrastructure and can’t be leased out.

IPv6 subnet types

There’re two IPv6 parent subnet types:

ALLOCATED-BY-RIR – IPv6 subnet allocated by RIPE NCC to LIR
ASSIGNED PI – IPv6 subnet allocated by RIPE NCC to end user

And there’re three IPv6 assignment types available for IPv6 owners:

ALLOCATED-BY-LIR – an assignment made by LIR to end user from ALLOCATED-BY-RIR. ALLOCATED-BY-LIR is always smaller than parent ALLOCATED-BY-RIR
AGGREGATED-BY-LIR – is an aggregate of several smaller assignments of the size specified in the “assignment-size:” attribute.
ASSIGNED – An assignment can only be used for the internal network and network services of the End User holding the assignment.

IPv6 transfer restrictions

The minimum PA allocation allowed for IPv6 transfer is /32.
The minimum PI allocation allowed for IPv6 transfer is /48.

IPv6 assignment restrictions

At least a part of IPv6 subnet allocated by RIPE NCC (ALLOCATED-BY-RIR) shall be announced within RIPE NCC service region
An ASSIGNED PI subnet can only be used for the end user’s own infrastructure and can’t be leased out.

ASN registration overview

To register an ASN at least 2 peering partner required
ASN shall be registered for use in the RIPE NCC service region.
ASN can be registered by LIR for his own use or by LIR for his customer (Sponsoring LIR).

LIR registration overview

A legal entity, individual entrepreneur or a natural person can become a LIR
RIPE NCC IPv4 addresses pool is empty. After you request a /24 you will be placed to waiting list and then you have to wait for a /24 IPv4 allocation for more than 229 calendar days (data on 8.09.2022)
If you’re registered outside RIPE NCC service region, you have to provide additional documents showing you have an IT infrastructure in RIPE NCC service region.

Address space you can receive after the LIR registration.

On 25 November 2019, RIPE NCC announced the IPv4 shortage. Starting from 25.11.2019, RIPE-733 became effective and an IPv4 /24 allocation is made through the waiting list.

Without additional documents, as a LIR you can request a /29 IPv6 PA network and an ASN. For ASN registration 2 peering partners are required.

Main requirements for IPv4 allocations

The subnet size of IPv4 allocation you can request is /24
PI IPv4 assignment requests are not accepted
A /24 allocated PA shall be used within RIPE NCC service region

Main requirements for IPv6 allocations

The minimum IPv6 allocation size in the RIPE NCC service region is a /32.
For IPv6 subnets larger than /29 an explanation and a description of use required.