Skip to main content

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.

Archived Date:
June 2009
Working Group:
Address Policy Working Group
Archived Date:
May 2009
Working Group:
Address Policy Working Group
Summary: This was a proposal to allow an LIR operating separate networks in unconnected geographical areas to receive multiple /32 IPv6 allocations.

Reason for Withdrawal:
The proposer, together with the Working Group Chairs, decided to withdraw this proposal due to insufficient support for it as it is written.
Archived Date:
April 2009
Working Group:
Address Policy Working Group
Summary: This proposal introduced a solution for organisations that needed IPv6 Provider Independent (PI) address space.
Archived Date:
February 2009
Working Group:
Address Policy Working Group
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.

Reason for Withdrawal: The proposer decided to withdraw this proposal upon publication of RFC 5396.
Archived Date:
December 2008
Working Group:
Address Policy Working Group

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.

2007-05: IPv6 ULA-Central
State:
Withdrawn
Archived Date:
November 2008
Working Group:
Address Policy Working Group
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. 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).

Reason for Withdrawal: The proposer decided to withdraw this proposal and wait for the IETF process on the subject to conclude.
Archived Date:
October 2008
Working Group:
Address Policy Working Group

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. The proposal also reaffirms and clarifies the existing RIPE policy that IPv4 provider independent address assignments of any type cannot be sub-assigned.

Archived Date:
September 2008
Working Group:
Address Policy Working Group

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.

Reason for Withdrawal: The proposer decided to withdraw this proposal due to insufficient support for it.

Archived Date:
September 2008
Working Group:
Address Policy Working Group

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.

Archived Date:
May 2008
Working Group:
Address Policy Working Group

Summary: With the acceptance of this policy RIPE NCC will run a one-time operation to allocate an IPv6 block to every LIR that does not have any existing IPv6 holdings.

Reason for Withdrawal: The proposer decided to withdraw this proposal due to insufficient support for it.