RIPE Policy Proposals

Anyone in the RIPE (Réseaux IP Européens) community can suggest a new policy or a change to an existing policy. You do not have to be a member of the RIPE NCC.

RIPE is a collaborative forum open to anyone who is interested in wide area IP networks. There are no membership requirements for participation in RIPE. Its activities are performed on a voluntary basis and decisions are made by consensus.

The RIPE NCC provides administrative support for RIPE. One of the jobs that the RIPE NCC does is to look after the Policy Development Process. The RIPE NCC manages the process, but all input comes from the RIPE community. The RIPE NCC does not make policies, however it is responsible for making sure that they are applied in its service region.

A glossary of terms explains the phrases used in the table below.

Name	Number	Submission Date	Current Phase	Phase Ends/Ended	Latest Status	Working Group
Provider Independent (PI) IPv6 Assignments for End User Organisations	2006-01	22 May 2007	Discussion	19 June 2007	Awaiting Decision from Proposer	Address Policy
Summary: This proposal is intended to provide a solution for organisations that need IPv6 Provider Independent (PI) assignments.
PI Assignment Size	2006-05	29 August 2006	Review	14 March 2007	Awaiting Decision from WG Chairs	Address Policy
Summary: This proposal suggests to have the minimum assignment size for PI assignments to be a /24 when routing is a major issue for a multihoming End User.
Direct Internet Resource Assignments to End Users from the RIPE NCC	2007-01	26 June 2008	Review	24 July 2008	Further Community Discussion	Address Policy
Summary: 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. It also states that the text in the policy should mention more explicitly that PI assignments can not be sub-assigned.
IPv6 ULA-Central	2007-05	2 May 2007	Discussion	13 August 2007	Awaiting Decision from Proposer	Address Policy
Summary: 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.
Enabling Methods for Reallocation of IPv4 Resources	2007-08	23 October 2007	Review	9 July 2008	Further Community Discussion	Address Policy
Summary: This proposal outlines a framework to migrate previously allocated IPv4 resources from one Local Internet Registry (LIR) to another LIR within the RIPE NCC Service Region.
Cooperative Distribution of the End of the IPv4 Free Pool	2007-09	26 November 2007	Discussion	24 December 2007	Awaiting Decision from Proposer	Address Policy
Summary: This policy will establish a process for RIR-to-RIR redistribution of the tail-end of the IPv4 pool, taking effect after the IANA Reserve is exhausted. Each redistribution Allocation will be triggered by the recipient RIR depleting its reserve to a 30 day supply, and will result in up to a 3 month supply being transferred from the RIR with the longest remaining time before it exhausts its own pool.
Global Policy for the Allocation of the Remaining IPv4 Address Space	2008-03	3 March 2008	Review	26 June 2008	Further Community Discussion	Address Policy
Summary: This policy describes the process for the allocation of the remaining IPv4 space from IANA to the RIRs. When a minimum amount of available space is reached, one /8 will be allocated from IANA to each RIR, replacing the current IPv4 allocation policy.
Using the Resource Public Key Infrastructure to Construct Validated IRR Data	2008-04	29 April 2008	Discussion	27 May 2008	Awaiting Decision from Proposers	Routing
Summary: 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.