Archived Policy Proposals

The policy proposals on this page have been archived. You can see at a glance if they were accepted and adopted by the RIPE community or withdrawn at any stage.

Name Status Proposal Number Working Group Date Archived
Openness about Policy Violations
WITHDRAWN
2013-01 Anti-Abuse Working Group November 2013

Summary: The RIPE NCC is the membership organisation that manages the shared public resources of IP addresses and Autonomous System Numbers in its service region. This proposal makes complaints about delegated resources more visible. It also specifies a separate list that documents all reclaimed resources. The goals are to provide more insight into the good stewardship of the RIPE NCC and to encourage assistance in stopping abuse of these shared public resources. This proposal explicitly does not set or change any policies about assignment, allocation or revocation of these resources.

Reason for withdrawal: After considering the objections raised when 2013-01 was first proposed, combined with the very low level of subsequent feedback, the proposers are of the opinion that consensus on this proposal is not likely to be reached. As a consequence, the proposers decided to withdraw the proposal.

Resource Certification for non-RIPE NCC Members
ACCEPTED
2013-04 RIPE NCC Services Working Group October 2013

Summary: 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, who reside in the the RIPE NCC Service Region.

Removal of requirement for certification of reallocated IPv4 addresses
ACCEPTED
2013-02 Address Policy Working Group June 2013

Summary:  This proposal requests that the text requiring certification of transferred resources is deleted

Extension of IPv6 /32 to /29 on a per-allocation vs per-LIR basis
ACCEPTED
2012-10 Address Policy Working Group May 2013

Summary: 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.

PI Assignments from the last /8
WITHDRAWN
2012-04 Address Policy Working Group May 2013

Summary: 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.

Intra-RIR transfer policy proposal
WITHDRAWN
2012-03 Address Policy Working Group April 2013

Summary: 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
ACCEPTED
2012-09 Address Policy Working Group April 2013

Summary: 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.

Revert “Run Out Fairly” after IPv4 depletion
ACCEPTED
2012-06 Address Policy Working Group February 2013

Summary: This proposal reverts the changes made by 2009-03 "Run Out Fairly".

Transparency in Address Block Transfers
ACCEPTED
2012-05 Address Policy Working Group February 2013

Summary: 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.

Abuse Contact Management in the RIPE NCC Database
ACCEPTED
2011-06 Anti-Abuse Working Group September 2012

Summary: 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.