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.
Name
 |
Number
|
Submission
Date |
Current
Phase |
Phase
Ends/Ended |
Latest Status |
Working Group |
|
|
|
| Provider
Independent (PI) IPv6 Assignments for End User Organisations |
2006-01 |
20 April 2006 |
Discussion |
23 December 2008 |
Initial Community Discussion
|
|
| Summary:
This proposal introduces a solution for organisations that need IPv6 Provider Independent (PI) address space.
|
|
| PI Assignment Size |
2006-05 |
29 August 2006 |
Review |
14 March 2007 |
Awaiting Decision from WG Chairs
|
|
| 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. |
| Enabling Methods for Reallocation of IPv4 Resources |
2007-08 |
23 October 2007 |
Concluding |
8 December 2008 |
|
|
| 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. |
| Using the Resource Public Key Infrastructure to Construct Validated IRR Data |
2008-04 |
29 April 2008 |
Discussion |
27 May 2008 |
Awaiting Decision from Proposers
|
|
| 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. |
| Anycasting Tier 0/1 ENUM |
2008-05 |
4 September 2008 |
Discussion |
12 November 2008 |
Awaiting Decision from Proposer |
|
| Summary: The proposal is to allow Tier 0/1 ENUM operators to receive IPv4 and IPv6 anycasting assignments. |
| Use of Final /8 |
2008-06 |
15 October 2008 |
Discussion |
12 November 2008 |
Awaiting Decision from Proposer |
|
| Summary: 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. |
| Ensuring Efficient Use of Historical IPv4 Resources |
2008-07 |
15 October 2008 |
Discussion |
12 November 2008 |
Awaiting Decision from Proposer |
|
| Summary: This is a proposal to require documentation of all historical 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 |
|
| 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. |
| ASPLAIN Format for the Registration of 4-byte ASNs |
2008-09 |
20 October 2008 |
Discussion |
17 November 2008 |
Awaiting Decision from Proposer |
|
| Summary: 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.. |
| |
|
|
|
|