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

Document Actions

Policy Proposals

Publication of Sponsoring LIR for Independent Number Resources

2012-08: This proposal intends to allow the RIPE NCC to identify and make public the sponsoring organisation of each independent number resource.

Revert “Run Out Fairly” after IPv4 depletion

2012-06: This proposal reverts the changes made by 2009-03 "Run Out Fairly" once 2010-02 "Allocations from the last /8" comes into effect.

RIPE NCC Services to Legacy Internet Resource Holders

2012-07: A framework is proposed as the basis for rigorous maintenance of registration data and for delivery of services to legacy Internet resource holders in the RIPE NCC service region.

Abuse Contact Management in the RIPE NCC Database

2011-06: Abuse Contact Management in the RIPE NCC Database. This is a proposal to introduce a new contact attribute named "abuse-c:", which can be included in inetnum, inet6num and aut-num objects.

Transparency in Address Block Transfers

2012-05: Transparency in Address Block Transfers. This proposal intends to increase the transparency of the transfer market for IPv4 addresses. It modifies the current intra-RIR IPv4 allocation transfer policy in order to require the RIPE NCC to publish a record of all transfers conducted under the policy.

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.

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.