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
RIPE NCC Services to Legacy Internet Resource Holders
ACCEPTED
2012-07 RIPE NCC Services Working Group February 2014

Summary: This proposal created a framework for the rigorous maintenance of registration data and the delivery of services to holders of legacy Internet resource in the RIPE NCC service region. The proposal also amended the policies described in the RIPE Document, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" where this was not consistent with the framework established by the proposal.

Post Depletion Adjustment of Procedures to Match Policy Objectives, and Clean-up of Obsolete Policy Text
ACCEPTED
2013-03 Address Policy Working Group February 2014

Summary: This proposal simplified the stated “Fairness” policy goal and removed the requirement for LIRs to complete a forecast-based documentation of need when requesting IPv4 allocations from the RIPE NCC, when requesting approval for IPv4 transfers, or when End Users request an assignment of address space from an LIR. The proposal also added a “self destruct clause” that removes the “Unforeseen Circumstances” section if the reserved address space returns to the free pool. Finally, the proposal removed text suggesting that the RIPE NCC would assign PI address space to End Users.

Publication of Sponsoring LIR for Independent Number Resources
ACCEPTED
2012-08 RIPE NCC Services Working Group January 2014

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

No Restrictions on End User Assignments in Intra-RIR Transfers
ACCEPTED
2013-05 Address Policy Working Group December 2013

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

PA/PI Unification IPv6 Address Space
WITHDRAWN
2013-06 Address Policy Working Group December 2013

Summary: This policy proposal aims to unify the three RIPE documents ripe-589, ripe-451and ripe-233 and to provide one document for all the IPv6 address space. It also removes the difference between PI and PA; Sub-allocation and Assignment.

Reason for withdrawal: During the Discussion Phase it became clear that the RIPE community did not see the need for such a complex change. As a result, the proposers decided to withdraw the proposal.

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.