Archived Policy Proposals
The policy proposals on this page have been archived. You can see at a glance if they were accepted and adopted by the RIPE community or withdrawn at any stage.
| Name | Status | Proposal Number | Working Group | Date Archived |
| Removal of multihomed requirement for IPv6 PI |
ACCEPTED
|
2011-02 | Address Policy Working Group | January 2012 |
| Summary: This proposal intends to remove the multihome requirement necessary to receive PI IPv6 address space in the policy ripe-538, “IPv6 Address Allocation and Assignment Policy”. | ||||
| Global Policy for post exhaustion IPv4 allocation mechanisms by the IANA |
ACCEPTED
|
2011-01 | Address Policy Working Group | October 2011 |
|
Summary: This proposal describes the process that IANA will follow to allocate IPv4 resources to Regional Internet Registries (RIRs) after the central pool of addresses is exhausted. The processes for how IPv4 space may be placed in the IANA Recovered IPv4 Pool is out of the scope of this proposal. |
||||
| Adding Reference to Sponsoring LIR in inetnum, inet6num and aut-num objects |
WITHDRAWN
|
2010-10 | Anti-Abuse Working Group | November 2010 |
|
Summary: This is a proposal to add a reference to sponsoring LIR in inetnum, inet6num and aut-num objects to increase the possibility of abuse tracking and handling. Reason for Withdrawal: The proposer decided to withdraw the proposal based on the feedback received at RIPE 61. A task force will be organised to solve the implementation issues pointed out by the proposal discussion. |
||||
| Frequent Update Request |
WITHDRAWN
|
2010-09 | Anti-Abuse Working Group | November 2010 |
|
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. Reason for Withdrawal: The proposer decided to withdraw the proposal based on the feedback received at RIPE 61. A task force will be organised to solve the implementation issues pointed out by the proposal discussion. |
||||
| Abuse contact information |
WITHDRAWN
|
2010-08 | Anti-Abuse Working Group | May 2011 |
|
Summary: This is a proposal to introduce a mandatory reference to irt objects in the inetnum, inet6num and aut-num objects in the RIPE Database. It provides a more accurate and efficient way for abuse reports to reach the correct network contact and helps reporting institutions to find the correct abuse contact information more easily. Reason for withdrawal: A task force is working to solve the implementation issues pointed out by the proposal discussion. The possible policy consequences will be considered with a new proposal in the future. |
||||
| Ambiguity cleanup on IPv6 Address Space Policy for IXP |
WITHDRAWN
|
2010-07 | Address Policy Working Group | January 2011 |
|
Summary: This proposal aimed to clarify an ambiguous definition in ripe-451 regarding the requirements to join an IXP. Reason for withdrawal: The editorial text change proposed will be discussed in the Cosmetic Surgery Project |
||||
| Registration Requirements for IPv6 End User Assignments |
ACCEPTED
|
2010-06 | IPv6 Working Group | February 2011 |
| Summary: This proposal had two purposes: to create a new policy that defined 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. | ||||
| Global Policy for IPv4 Allocation by the IANA Post Exhaustion |
WITHDRAWN
|
2010-05 | Address Policy Working Group | March 2011 |
|
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. Reason for withdrawal: It was agreed with the proposer that the lack of community feedback and the impossibility of the proposal becoming globally accepted due to recent developments in the global PDP at the time were sufficient reasons to have it withdrawn. |
||||
| 80% Rule Ambiguity Cleanup |
ACCEPTED
|
2010-04 | Address Policy Working Group | October 2010 |
| 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 State in RIPE PDP |
WITHDRAWN
|
2010-03 | Address Policy Working Group | July 2010 |
|
Summary: This proposal would have modified the RIPE Policy Development Process to create a new state that is specific to global policies. This state was "Accepted pending consensus in other RIR communities." This would have allowed a global policy to be further discussed in the event that modifications are made in other RIR communities after acceptance in RIPE Reason for Withdrawal: Proposer decided to withdraw the proposal based on the feedback received at RIPE 60. |
||||