You are here: Home > Participate > Policy Development > Policy Proposals > Direct Internet Resource Assignments to End Users from the RIPE NCC

You're looking at an older or unpublished version: 1

1. Modifications

Current:

(from ripe-405):

9.0 PA vs PI Address Space

In contrast, PI address space cannot be aggregated. It can remain assigned to a network as long as the criteria for the original assignment are met. However, PI addresses are expensive to route as no use of aggregation can be made. They might not be globally routable.


New:

In contrast, Provider Independent (PI) address space is assigned to End Users directly and it cannot be aggregated. PI address space cannot be re-assigned or further assigned to other parties. It can only remain assigned to a network as long as the criteria for the original assignment are being met. PI addresses are expensive to route as no use of aggregation can be made. Furthermore, they may not be globally routable.

PI space is assigned after a contractual relationship is realised between the RIPE NCC and the End User. If this contract is terminated, the resources must be returned to the RIPE NCC.


2. Additions

(to ripe-256):

3.0 Policy

Before an assignment can be made to an IXP, a contractual relationship between this organisation and the RIPE NCC must be established. If this contract is terminated the assignment must be returned to the RIPE NCC.

(to ripe-405):

6.9 Anycasting TLD Name servers

If the TLD operator is not an LIR the prefix is assigned after a contractual relationship is realised between the RIPE NCC and the TLD operator. If this contract is terminated, the prefix must be returned to the RIPE NCC.

(to ripe-388):

7. Assignments for Anycasting TLD Nameservers

If the TLD operator is not an LIR, the prefix is assigned after a contractual relationship is realised between the RIPE NCC and the TLD operator. If this contract is terminated, the prefix must be returned to the RIPE NCC.

(to ripe-389):

1.7 Requesting an AS Number

Before an AS Number can be assigned to an End User, a contractual relationship between this End User and the RIPE NCC must be established. If this contract is terminated, the AS Number assigned must be returned to the RIPE NCC.

Get Involved

The Address Policy Working Group develops policies relating to the allocation and registration of Internet number resources (IPv4 and IPv6 addresses and ASNs) by the RIPE NCC and its members. Anyone with an interest in Internet numbering issues is welcome to observe, participate and contribute to the WG. To post a message to the list, send an email to address-policy-wg@ripe.net. Please note that only subscribers can post messages.

Please contact if you need more information.

Stay up to date!

Follow @PDO_RIPE_NCC on Twitter.