RIPE NCC: descripción general de RIR y términos principales que los propietarios de subredes IP deben conocer

Historia de RIPE NCC

RIPE NCC (Réseaux IP Européens Network Coordination Centre) es el registro regional de Internet (RIR) para Europa, Oriente Medio y partes de Asia Central con sede en Ámsterdam, Países Bajos.

La historia de RIPE NCC comienza en noviembre de 1989, cuando el primer foro colaborativo RIPE abrió sus puertas a todas las partes interesadas en las redes IP. El primer documento que describe el RIPE NCC se publicó en septiembre de 1990. Posteriormente, en marzo de 1992, en el Instituto Nacional Holandés de Física de Altas Energías se instalaron los dos primeros servidores del RIPE NCC. A partir de abril de 1992 RIPE NCC inició sus operaciones con sólo 3 empleados. La primera tarea importante del RIR fue actuar como un Registro Regional de Internet (RIR) y mantener la denominada Base de datos RIPE, creada y respaldada por voluntarios. El objetivo de la base de datos RIPE era recopilar información sobre el uso del espacio de direcciones en la región europea. Como entidad legal, se estableció en noviembre de 1997 cuando la versión holandesa de los estatutos se depositó en la Cámara de Comercio de Ámsterdam.

Documentos principales:

Hay muchas políticas diferentes, pero las claves son:

RIPE-733. Las últimas Políticas de la Distributión y Asignación de Direcciones IPv4 para la Región de Servicio RIPE NCC que entraron en vigencia después de la escasez de IPv4.
RIPE-738. Política de la Distributión y Asignación de Direcciones IPv6
RIPE-757. Recursos de números de Internet independientes: cambios en la relación contractual entre el LIR patrocinador y el usuario final
RIPE-682.Políticas de transferencia de recursos RIPE
RIPE-767. Requisitos para la base de datos RIPE

Todo lo que necesita saber sobre la gestión del espacio de direcciones de Internet en la región de servicio de RIPE NCC:

Tipos de subred IPv4

Hay cuatro tipos de subredes principales IPv4:

ALLOCATED PA – subred IPv4 asignada por RIPE NCC a LIR
ASSIGNED PI – subred IPv4 asignada por RIPE NCC al usuario final
LEGACY – subred IPv4 asignada por la IANA al usuario final (IANA asignó las redes IPv4 directamente antes de que se establecieran los RIR)
ASSIGNED ANYCAST –RIPE NCC asignó la subred IPv4 para su uso en redes anycast de TLD.

Y hay cuatro tipos de asignaciones de IPv4 disponibles para propietarios de IPv4:

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.