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
PI Assignment Size	2006-05	29 August 2006	Review	14 March 2007	Awaiting Decision from WG Chair	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.
Ensuring Efficient Use of Historical IPv4 Resources	2008-07	15 October 2008	Discussion	24 August 2009	Awaiting Decision from Proposer	Address Policy
Summary: This is a proposal to require documentation of all address resources held when assessing a RIPE NCC member's eligibility for further IPv4 address space.
Initial Certification Policy for Provider Aggregatable Address Space Holders	2008-08	16 October 2008	Discussion	13 November 2008	Awaiting Decision from Proposer	Address Policy
Summary: The RIPE NCC plans to deploy a certification service that can be used to secure uniqueness of resources. This proposal lays out guidelines for how LIRs can receive certificates over their Provider Aggregatable (PA) address space holdings and how these certificates should be maintained.
Temporary Internet Number Assignment Policies	2010-01	18 March 2010	Review	7 September 2010	Further Community Discussion	Address Policy
Summary: This proposal expands the RIPE NCC's ability to assign number resources for temporary purposes and allows the RIPE NCC to reserve pools of IP addresses and Autonomous System (AS) Numbers, which can be used by the RIPE NCC to make temporary direct assignments to End Users.
Allocations from the last /8	2010-02	13 April 2010	Review	4 August 2010	Awaiting Decision from Proposer	Address Policy
Summary: This proposal describes how the RIPE NCC should distribute address space from its last /8 worth of IPv4 address space.
80% Rule Ambiguity Cleanup	2010-04	17 June 2010	Review	6 September 2010	Further Community Discussion	Address Policy
Summary: This proposal is to solve the ambiguity in the current wording of the IPv4 Allocation Policy (ripe-492) regarding the "80% utilisation" rule.
Global Policy for IPv4 Allocation by the IANA post exhaustion	2010-05	23 August 2010	Discussion	20 September 2010	Initial Discussion	Address Policy
Summary: This is a proposal to create a policy allowing for the allocation of IPv4 address space after the depletion of the IANA IPv4 address pool.
Registration Requirements for IPv6 End User Assignments	2010-06	1 September 2010	Discussion	29 September 2010	Initial Discussion	IPv6
Summary: This proposal has two purposes: to create a new policy that defines the use of new attributes in the RIPE Database and to change the policy text of ripe-481 to require the use of these new database attributes.