Archived Policy Proposals

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".

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.

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.

Summary: This proposal modifies the eligibility for an organisation to receive an initial IPv6 allocation up to a /29. This is in order to enable small LIRs to deploy IPv6 using “IPv6 Rapid Deployment”, also known as “6rd”, as defined in RFC 5969 in a manner that does not encourage issuing a single /64 to end customers when an LIR has a minimum allocation of /32.

Summary: This policy proposal will permit the operators in the RIPE NCC service region to continue building successful Internet Exchange Point communities after IPv4 depletion.

Summary: The goal of this proposal is to allow IPv4 address space transfers between the RIPE NCC and other RIRs in order to supplement the pool of available IPv4 addresses.

Summary: This proposal intends to remove the multihome requirement necessary to receive PI IPv6 address space in the policy ripe-538, “IPv6 Address Allocation and Assignment Policy”.