- 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.
- 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.
- 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.
- 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.
- 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.
- Removal of requirement for certification of reallocated IPv4 addresses
2013-02: Removal of requirement for certification of reallocated IPv4 addresses. This proposal requests that the text requiring certification of transferred resources is deleted
- Resource Certification for non-RIPE NCC Members
2013-04: Currently, the RIPE NCC Resource Certification (RPKI) service is only available for RIPE NCC members. This proposal intends to allow the RIPE NCC to issue resource certificates for non-members, such as Provider Independent End Users and Legacy address space holders, which reside in the RIPE NCC Service region.
- 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.