Policy Proposals

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.

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.

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.

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

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

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

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

2008-09: This proposal seeks to modify the current policy document 'Autonomous System (AS) Number Assignment Policies and Procedures' to adopt the use of ASPLAIN for recording and representation of 4-byte AS Numbers.

2007-05: This policy is intended to allow the assignment of IPv6 blocks within the so-called 'Centrally Assigned Unique Local IPv6 Unicast Addresses' to organisations or individuals requiring it. These addresses are globally unique and intended for local communications, usually within a site or set of them and are not expected to be routable on the global Internet. Prefix FC00::/7 is already reserved by IANA for ULA (bit 8 determines if locally or centrally assigned, so ULA or ULA-Central).

2007-01: This proposal states that a contractual relationship between an End User and a sponsoring LIR or the RIPE NCC must be established before the End User receives Internet number resources (Autonomous System (AS) Number, Provider Independent (PI) IPv4 and IPv6, Internet Exchange Point (IXP) and anycasting assignments) directly from the RIPE NCC. The proposal also reaffirms and clarifies the existing RIPE policy that IPv4 provider independent address assignments of any type cannot be sub-assigned.