You are here: Home > Participate > Policy Development > Policy Proposals

Policy Proposals

Provider Independent (PI) IPv6 Assignments for End User Organisations

2006-01: This proposal introduced a solution for organisations that needed IPv6 Provider Independent (PI) address space.

Multiple IPv6 /32 Allocations for LIRs

2009-05: This is a proposal to allow an LIR operating separate networks in unconnected geographical areas to receive multiple /32 IPv6 allocations.

Allocating/Assigning Resources to the RIPE NCC

2009-02: This proposal sets out how the RIPE NCC can allocate/assign resources to itself.

Removing Routing Requirements from the IPv6 Address Allocation Policy

2009-06: The IPv6 address allocation policy currently contains mandates about how an allocated address range should be announced into the routing table. Following discussion at RIPE 58, it is proposed that this is removed from the address policy as it does not relate to address allocation.

Internet Assigned Numbers Authority (IANA) Policy for Allocation of ASN Blocks (ASNs) to Regional Internet Registries

2009-07: According to the current global policy (ripe-416), IANA will cease to make any distinction between 16 bit and 32-bit only ASN blocks by 31 December 2009, when making allocations to RIRs. This proposal is to extend this date by one year, to 31 December 2010

IPv6 Provider Independent (PI) Assignments for LIRs

2009-08: This proposal is to allow LIRs to receive IPv6 PI assignments in addition to an IPv6 allocation.

Run Out Fairly

2009-03: This is a proposal to gradually reduce the allocation and assignment periods in step with the expected life time of the IPv4 unallocated pool in order to address the perception of unfairness once the pool has run out. The proposal is not intended to stretch the lifetime of the unallocated pool. The proposal is independent of other proposals to reserve address space for transition purposes and/or new entrants. It can be implemented independently of these.

Use of final /8

2008-06: This proposal describes how RIPE NCC should make allocations from its last /8 worth of address space at the time of total depletion of the IANA free pool.

IPv4 Allocation and Assignments to Facilitate IPv6 Deployment

2009-04: The last IPv4 /8 that the RIPE NCC will hold is proposed to be dedicated to facilitate deployment of IPv6. Allocations and assignments from this block will be made based on demonstrated need, but the size will be downscaled taking into account existing transition technologies (for example dual-stack lite, NAT464, successors of NAT-PT). The proposed minimum allocation size is to be a /27 for such allocations and assignments.

Using the Resource Public Key Infrastructure to Construct Validated IRR Data

2008-04: This is a proposal to introduce a new registry that augments IRR data with the formally verifiable trust model of the Resource Public Key Infrastructure (RPKI) and provide ISPs with the tools to generate an overlay to the IRR which is much more strongly trustable.

RIPE Forum

The RIPE Forum is an additional way to participate in RIPE community mailing list discussions using a web-based interface rather than an email client.

Check out the forum

Please contact if you need more information.

Stay up to date!

Follow @PDO_RIPE_NCC on Twitter.