You are here: Home > Participate > Policy Development > Policy Proposals

Document Actions

Policy Proposals

Intra-RIR transfer policy proposal

2012-03: Presently the allocation period for all allocations and transfers from within the RIPE NCC service region is 3 month. While this makes sense for new RIPE allocations, where there is a shortage of supply, in the case of transfers often the source is from a larger dormant block held by an LIR. It makes sense to increase the period of use for transfers to better match the quantity that is available and needed from this larger supply pool.

PI Assignments from the last /8

2012-04: PI Assignments from the last /8. The final /8 of address space to be administered by the RIPE NCC is subject to a restrictive delegation policy. In its current form, it can only be used to provide allocations of IPv4 address space to LIRs. This is inherently biased against the large number of organisations which require Provider Independent (PI) assignments of IPv4 address space. This policy seeks to redress this bias by allowing End Users to receive PI assignments from the last /8.

Policy for Inter-RIR transfers of IPv4 address space

2012-02: This policy proposal describes how transfers of IPv4 address space between LIRs of different Regional Internet Registries will occur.

Inter-RIR IPv4 Address Transfers

2012-01: Inter-RIR IPv4 Address Transfers. This proposal is intended to allow IPv4 address space transfers between the RIPE NCC and other RIRs in order to supplement the pool of available IPv4 addresses.

Extension of the Minimum Size for IPv6 Initial Allocation

2011-04: This proposal modifies the eligibility for an organisation to receive an initial IPv6 allocation up to a /29. This is in order to enable small LIRs to deploy IPv6 using “IPv6 Rapid Deployment”, also known as “6rd”, as defined in RFC 5969 in a manner that does not encourage issuing a single /64 to end customers when an LIR has a minimum allocation of /32.

Safeguarding future IXPs with IPv4 space

2011-05: Safeguarding future IXPs with IPv4 space. This policy proposal will permit the operators in the RIPE NCC service region to continue building successful Internet Exchange Point communities after IPv4 depletion.

Allocating/Assigning Resources to the RIPE NCC

2009-02: This proposal sets out how the RIPE NCC can allocate/assign resources to itself.

Removal of multihomed requirement for IPv6 PI

2011-02: This proposal intends to remove the multihome requirement necessary to receive PI IPv6 address space in the policy ripe-538, “IPv6 Address Allocation and Assignment Policy”. There are enough End Users (businesses) that have a valid reason for their own address space, without the desire to become a LIR or multihoming.

Global Policy for post exhaustion IPv4 allocation mechanisms by the IANA

2011-01: This proposal describes the process that IANA will follow to allocate IPv4 resources to Regional Internet Registries (RIRs) after the central pool of addresses is exhausted. The processes for how IPv4 space may be placed in the IANA Recovered IPv4 Pool is out of the scope of this proposal

Post-depletion IPv4 address recycling

2011-03: This proposal intends to define better how the address management of returned IPv4 address space will be performed when the final /8 policy comes into effect.

RIPE Forum

The RIPE Forum is an additional way to participate in RIPE community mailing list discussions using a web-based interface rather than an email client.

Check out the forum

Please contact if you need more information.

Stay up to date!

Follow @PDO_RIPE_NCC on Twitter.