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

Document Actions

Policy Proposals

Post Depletion Adjustment of Procedures to Match Policy Objectives, and Clean-up of Obsolete Policy Text

2013-03: This proposal removes the need-based requirement for IPv4 delegations in the RIPE NCC service area. It also incorporates section 5.6 "Use of last /8 for PA Allocations" into the main policy text, removing all references to the "last /8" itself, and to the reaching of it as a future event.

Openness about Policy Violations

2013-01: This proposal intends to provide more insight into the good stewardship of the RIPE NCC and to encourage assistance in stopping abuse of these shared public resources.

Extension of IPv6 /32 to /29 on a per-allocation vs per-LIR basis

2012-10: This proposal aims to clarify the approved text of proposal 2011-04 on the extensions of IPv6 allocations to ensure that any /32 may be extended to /29, without having to restrict to one extension on a per-LIR-total-summary basis.

Modification of The Time Limits For Temporary Internet Assignments

2012-09: Practical experience has indicated that the time limits used in ripe-526 are too short for certain types of events. This policy proposal recommends changing these time limits to allow more flexibility for End Users of temporary Internet number assignments. The excess time limits for the various assignment purposes are also aligned to be the same.

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.

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.