Archived Policy Proposals

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

Summary: This policy proposal aims to unify the three RIPE documents ripe-589, ripe-451 and 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.t set or change any policies about assignment, allocation or revocation of these resources.

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.

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.

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.

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

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.

Summary: This policy proposal seeks to redress the bias against the large number of organisations which require Provider Independent (PI) assignments of IPv4 address space by allowing End Users to receive PI assignments from the last /8.

Reason for withdrawal: Since the introduction of 2013-03, "No Need - Post Depletion Reality Adjustment and Cleanup", it has become clear that the RIPE Community is heading towards full deregulation of the IPv4 assignment model. The proposer has decided that it is unlikely that the RIPE Community would achieve consensus on PI assignments from the last /8 without a requirements-based assignment mechanism.

Consequently the proposer decided to withdraw this proposal.

Summary: This proposal aims at changing the evaluation of the receiving LIR's addressing needs to a period of up to 24 months for transferred allocations

Reason for withdrawal: The proposer had initially proposed a 24-month justification to align with policies from other RIRs.
The proposer found the ongoing policy proposal 2013-03 "No Need - Post-Depletion Reality Adjustment and Cleanup" as being more in line with her views.

As a consequence, the proposer has withdrawn the proposal.

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.

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