Archived RIPE Policy Proposals

— pdp

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
Safeguarding future IXPs with IPv4 space		2011-05	Address Policy	June 2012
Summary: This policy proposal will permit the operators in the RIPE NCC service region to continue building successful Internet Exchange Point communities after IPv4 depletion.
Extension of the Minimum Size for IPv6 Initial Allocation		2011-04	Address Policy	May 2012
Summary: This proposal modifies the eligibility for an organisation to receive an initial IPv6 allocation up to a /29. This is in order to enable small LIRs to deploy IPv6 using “IPv6 Rapid Deployment”, also known as “6rd”, as defined in RFC 5969 in a manner that does not encourage issuing a single /64 to end customers when an LIR has a minimum allocation of /32.
Inter-RIR Address Transfers		2012-01	Address Policy	May 2012
Summary: This proposal is intended to allow IPv4 address space transfers between the RIPE NCC and other RIRs in order to supplement the pool of available IPv4 addresses. Reason for withdrawal: With respect to 2012-01, after the feedback and discussion at the RIPE 64 Meeting, the proposer decided to collaborate with other community members in submitting another policy proposal related to IPv4 transfers. Therefore the proposer decided to withdraw this proposal.
Removal of multihomed requirement for IPv6 PI		2011-02	Address Policy	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”.
Post-depletion IPv4 address recycling		2011-03	Address Policy	October 2011
Summary: This proposal intends to define better how the address management of returned IPv4 address space will be performed when the final /8 policy comes into effect.
Global Policy for post exhaustion IPv4 allocation mechanisms by the IANA		2011-01	Address Policy	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.
PI Assignment Size		2006-05	Address Policy	October 2011
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.
Temporary Internet Number Assignment Policies		2010-01	Address Policy	August 2011
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.
Initial Certification policy in the RIPE NCC Service Region		2008-08	Address Policy	July 2011
Summary: This proposal lays out guidelines for how LIRs can receive Resource Public Key Infrastructure (RPKI) certificates over their IP Resources and how these certificates should be maintained. Reason for withdrawal: After carefully following the discussion in the Concluding Phase of the Policy Development Process, the proposer is of the opinion that consensus on this proposal is not possible within the RIPE community. As a consequence, the proposer has decided to withdraw the proposal.
Abuse contact information		2010-08	Anti-Abuse	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.
Global Policy for IPv4 Allocation by the IANA post exhaustion		2010-05	Address Policy	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.
Registration Requirements for IPv6 End User Assignments		2010-06	IPv6	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.
Ambiguity cleanup on IPv6 Address Space Policy for IXP		2010-07	Address Policy	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
Allocations from the last /8		2010-02	Address Policy	January 2011
Summary: This proposal described how the RIPE NCC should distribute address space from its last /8 worth of IPv4 address space.
Frequent Update Request		2010-09	Anti-Abuse	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.
Adding Reference to Sponsoring LIR in inetnum, inet6num and aut-num objects		2010-10	Anti-Abuse	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.
Ensuring Efficient Use of Historical IPv4 Resources		2008-07	Address Policy	November 2010
Summary: This was a proposal to require documentation of all address resources held when assessing a RIPE NCC member's eligibility for further IPv4 address space. Reason for Withdrawal: Proposer decided to withdraw the proposal.
80% Rule Ambiguity Cleanup		2010-04	Address Policy	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 for the Allocation of IPv4 blocks to Regional Internet Registries		2009-01	Address Policy	August 2010
Summary: With the depletion of the IANA free pool of IPv4 address space, the current policy regarding the allocation of IPv4 address space to the RIRs will become moot. The RIRs may, according to their individual policies and procedures, recover IPv4 address space. This policy provides a mechanism for the RIRs to retro allocate the recovered IPv4 address space to the IANA and provides the IANA the policy by which it can allocate it back to the RIRs on a needs basis. This policy creates a new global pool of IPv4 address space that can be allocated where it is needed on a global basis without a transfer of address space between the RIRs. NOTE: In October 2010, ICANN announced that the NRO deemed the global policy proposal abandoned due to differences in the global proposal texts among the RIRs. Hence this proposal, although regionally accepted, will never be globally implemented. The ICANN announcement is available online at: http://www.icann.org/en/announcements/announcement-12may09-en.htm
Global Policy State in RIPE PDP		2010-03	Address Policy	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.
Using the Resource Public Key Infrastructure to Construct Validated IRR Data		2008-04	Routing	July 2010
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. Reason for Withdrawal: Proposers decided to withdraw the proposal.
IPv4 Allocation and Assignments to Facilitate IPv6 Deployment		2009-04	Address Policy	April 2010
Summary: The last IPv4 /8 that the RIPE NCC will hold is proposed to be dedicated to facilitate deployment of IPv6. Allocations and assignments from this block will be made based on demonstrated need, but the size will be downscaled taking into account existing transition technologies (for example dual-stack lite, NAT464, successors of NAT-PT). The proposed minimum allocation size is to be a /27 for such allocations and assignments. Allocations and assignments from this block will also be justified by demonstrating that the requirements of the transition plan as specified in RFC 5211 are met. Reason for Withdrawal: Authors decided that they want to make a new proposal (see 2010-02).
Use of final /8		2008-06	Address Policy	April 2010
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. Reason for Withdrawal: Authors decided that they want to make a new proposal (see 2010-02).
Run Out Fairly		2009-03	Address Policy	December 2009
Summary: This is a proposal to gradually reduce the allocation and assignment periods in step with the expected life time of the IPv4 unallocated pool in order to address the perception of unfairness once the pool has run out. The proposal is not intended to stretch the lifetime of the unallocated pool. The proposal is independent of other proposals to reserve address space for transition purposes and/or new entrants. It can be implemented independently of these.
IPv6 Provider Independent (PI) Assignments for LIRs		2009-08	Address Policy	September 2009
Summary:This proposal is to allow LIRs to receive IPv6 PI assignments in addition to an IPv6 allocation.
Internet Assigned Numbers Authority (IANA) Policy for Allocation of ASN Blocks (ASNs) to Regional Internet Registries		2009-07	Address Policy	September 2009
Summary: According to the current global policy (ripe-416), IANA will cease to make any distinction between 16 bit and 32-bit only ASN blocks by 31 December 2009, when making allocations to RIRs. This proposal is to extend this date by one year, to 31 December 2010.
Removing Routing Requirements from the IPv6 Address Allocation Policy		2009-06	Address Policy	September 2009
Summary:The IPv6 address allocation policy currently contains mandates about how an allocated address range should be announced into the routing table. Following discussion at RIPE 58, it is proposed that this is removed from the address policy as it does not relate to address allocation.
Allocating/Assigning Resources to the RIPE NCC		2009-02	Address Policy	July 2009
Summary: This proposal sets out how the RIPE NCC can allocate/assign resources to itself.
Multiple IPv6 /32 Allocations for LIRs		2009-05	Address Policy	May 2009
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.
Provider Independent (PI) IPv6 Assignments for End User Organisations		2006-01	Address Policy	April 2009
Summary: This proposal introduced a solution for organisations that needed IPv6 Provider Independent (PI) address space.
ASPLAIN Format for the Registration of 4-byte ASNs		2008-09	Address Policy	February 2009
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.
Enabling Methods for Reallocation of IPv4 Resources		2007-08	Address Policy	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.
IPv6 ULA-Central		2007-05	Address Policy	November 2008
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.
Direct Internet Resource Assignments to End Users from the RIPE NCC		2007-01	Address Policy	October 2008
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.
Global Policy for the Allocation of the Remaining IPv4 Address Space		2008-03	Address Policy	September 2008
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.
Cooperative Distribution of the End of the IPv4 Free Pool		2007-09	Address Policy	September 2008
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.
Assigning IPv6 PA to Every LIR		2008-02	Address Policy	May 2008
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.
Assigning IPv6 PI to Every INETNUM Holder		2008-01	Address Policy	May 2008
Summary: With the acceptance of this policy, the RIPE NCC will conduct a one-time operation to assign a /56 IPv6 PI prefix to all End Users with an IPv4 assignment registered in the RIPE Database. Reason for Withdrawal: The proposer decided to withdraw this proposal due to insufficient support for it.
End Policy for IANA IPv4 Allocations to RIRs		2007-07	Address Policy	March 2008
Summary: This proposal seeks to provide the solutions to the problems in terms of address management which may arise if no measures are taken for IPv4 address exhaustion. Reason for Withdrawal: Authors decided that they want to make a new proposal (see 2008-03).
Global Policy for the Allocation of the Remaining IPv4 Address Space		2007-06	Address Policy	March 2008
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, an identical number of IPv4 allocation units (/8s) will be allocated from IANA to each RIR, replacing the current IPv4 allocation policy. Reason for Withdrawal: Authors decided that they want to make a new proposal (see 2008-03).
Proposal to Amend the IPv6 Assignment and Utilisation Requirement Policy		2005-08	Address Policy	November 2007
Summary: To amend the RIPE IPv6 address allocation policies regarding the definition of the default size of End Site allocations, the threshold value for End Site allocation efficiency, and the method of calculation of the End Site allocation efficiency metric.
IPv4 Countdown Policy		2007-03	Address Policy	October 2007
Summary: This policy proposal proposes four general principles, which will be needed to accomplish the smooth termination of IPv4 address allocation. Reason for Withdrawal: Authors decided that they want to make a new proposal (see 2007-07).
IANA Policy for Allocation of ASN Blocks to RIRs		2007-04	Address Policy	September 2007
Summary: This This proposal is to have a global policy for the Regional Internet Registries (RIRs) to receive blocks of Autonomous System Numbers (ASNs) from the Internet Assigned Numbers Authority (IANA).
Change in IP Assignments for Anycasting DNS Policy		2007-02	Address Policy	August 2007
Summary: This proposal suggested that there should no longer be a requirement to be a ccTLD or a gTLD to receive IPv4 and IPv6 assignments for anycasting DNS. Reason for Withdrawal: The proposer decided to withdraw this proposal due to insufficient support for it.
IPv6 Address Allocation and Assignment Policy		2006-02	Address Policy	July 2007
Summary: This proposal is to change the IPv6 Initial Allocation criteria and the End Site definition in the "IPv6 Address Allocation and Assignment Policy".
First Raise in IPv4 Assignment Window Size		2006-07	Address Policy	April 2007
Summary: This proposal suggests the Assignment Window (AW) available to new LIRs should automatically be raised from zero (0) to /21 (2,048 IPv4 addresses) six months after they receive their first allocation. Because the sub-allocation policy references the AW policy, the sub-allocation policy also needs to be updated. This proposal suggests that the maximum sub-allocation should be kept at /20 (4,096 IPv4 addresses).
IPv4 Maximum Allocation Period		2006-06	Address Policy	March 2007
Summary: This proposal is to have the RIPE NCC allocate address space to Local Internet Registries (LIRs) based on their one-year needs. In other words, it suggests setting a maximum allocation period of 12 months.
Contact E-Mail Address Requirements		2006-04	Address Policy	February 2007
Summary: This proposal suggested that working and up-to-date contact e-mail addresses should be maintained at all times for address space that is registered in the RIPE Database. Reason for Withdrawal: Withdrawn by the proposer and the Address Policy Working Group chair as not enough consensus was reached.
4-Byte AS Number Policy		2005-12	Address Policy	September 2006
Summary: This policy proposal details a set of actions and associated dates for RIR AS Number allocation policies to assist in an orderly transition to use of the 4-byte AS Number space.
IP Assignments for Anycasting DNS		2005-02	Address Policy	September 2006
Summary: To enable country code Top Level Domain (ccTLD) and global Top Level Domain (gTLD) name server operators to provide their DNS service using shared unicast technology, RIPE NCC may assign one IPv4 and/or one IPv6 prefix to each TLD operator.
LIR-PARTITIONED Status for IPv6		2006-03	Database	July 2006
Summary: This proposal is to have a new status for IPv6 address space as "LIR-PARTITIONED". Reason for Withdrawal: The proposer decided that the proposal was no longer necessary.
IPv6 Initial Allocation		2005-03	Address Policy	June 2006
Summary: The proposal is to change the IPv6 Initial Allocation criteria outlined in the "IPv6 Address Allocation and Assignment Policy". The proposed change is to remove "have a plan for making at least 200 /48 assignments to other organisations within two years" and to remove the reference to "/48s" as the assignment size. Reason for Withdrawal: Withdrawn by proposer who thought this proposal is superceded by 2006-02, IPv6 Address Allocation and Assignment Policy.
Multicast Monitoring on RIPE NCC Test Traffic Boxes		2005-11	Test Traffic	May 2006
Summary: A proposal to add testing of multicast connectivity between the RIPE NCC Test Traffic boxes that are connected to multicast-capable networks. Reason for Withdrawal: During the discussion phase, the working group decided that the RIPE NCC should do the work and that there was no need to complete the full PDP cycle for this proposal.
Consumer Broadband Monitoring Feasibility		2005-10	Test Traffic	May 2006
Summary: This is a proposal to have the RIPE NCC, as a neutral body, develop a way of measuring performance for consumer broadband networks. The proposal requests funding for a limited deployment prototype with the purpose of assessing industry and consumer acceptance, functional requirements and technical issues. Reason for Withdrawal: During the discussion phase, the working group decided that the RIPE NCC should do the work and that there was no need to complete the full PDP cycle for this proposal.
HD-ratio Proposal		2005-01	Address Policy	May 2006
Summary: The proposal is to change the further allocation criteria for IPv4 as described in ripe-324: "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region". Reason for Withdrawal: Withdrawn by proposer who felt that as there had been a number of objections, consensus had not been reached.
Internet Assigned Numbers Authority (IANA) Policy for Allocation of IPv6 Blocks to Regional Internet Registries		2005-09	Address Policy	April 2006
Summary: The proposal was to have a policy governing the allocation of IPv6 address space from the IANA to the Regional Internet Registries (RIRs).
IPv6 Address Allocation and Assignment Policy - definition for "End-Site"		2005-04	Address Policy	January 2006
Summary: There are various terms for "end-site" in the IPv6 allocation and assignment policy (ripe-267) and the RFC3177. We need to have a final definition for "End-Site" to establish clear internal assignment policies. Reason for Withdrawal: During discussions the proposer decided that the proposal was no longer necessary.
Introducing DNSSEC Service to Reverse DNS Trees		2005-07	DNS	October 2005
Summary: To implement DNSSEC, we propose extending the policy for Reverse Address Delegation of IPv4 and IPv6 Address Space in the RIPE NCC Service Region.
Proposal to Add Regional Boundaries to Policy Documents		2005-06	Address Policy	July 2005
Summary: Our AS assignment policy has the following statement in it - "The RIPE NCC assigns AS Numbers for Autonomous Systems located in the RIPE NCC service region". Neither the IPv4 nor the IPv6 policy documents have such a clear statement in them. It might be a good idea to add a similar statement to those documents when they are updated. Reason for Withdrawal: The proposer decided to withdraw this proposal.
Proposal to Remove Special African Policies From RIPE Policy Documents		2005-05	Address Policy	July 2005
Summary: To modify the policy document text to reflect full recognition of AfriNIC as a functioning RIR.

Sections

Archived RIPE Policy Proposals