Policy Proposals

2013-05: This policy proposal intends to update the intra-RIR IPv4 transfer policy with the removal of the restriction on End User assignments.

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.

2013-02: Removal of requirement for certification of reallocated IPv4 addresses. This proposal requests that the text requiring certification of transferred resources is deleted

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.

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.

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.

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.

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

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.

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.