You are here: Home > Participate > Policy Development > Policy Proposals

Document Actions

Policy Proposals

Proposal to Amend the IPv6 Assignment and Utilisation Requirement Policy

2005-08: 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: This policy proposal proposes four general principles, which will be needed to accomplish the smooth termination of IPv4 address allocation.

IANA Policy for Allocation of ASN Blocks to RIRs

2007-04: IANA Policy for Allocation of ASN Blocks to RIRs. 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: Change in IP Assignments for Anycasting DNS Policy. 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.

IPv6 Address Allocation and Assignment Policy

2006-02: IPv6 Address Allocation and Assignment Policy. 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: First Raise in IPv4 Assignment Window Size. 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: IPv4 Maximum Allocation Period. 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: Contact E-Mail Address Requirements. 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.

Registration Requirements for IPv6 End User Assignments

2010-06: Registration Requirements for IPv6 End User Assignments. 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

Allocations from the last /8

2010-02: This proposal describes how the RIPE NCC should distribute IPv4 address space from the final /8 address block it receives from the IANA. The proposal only discusses PA allocations; any other type of allocation or assignment is out of scope for this proposal.

RIPE Forum

The RIPE Forum is an additional way to participate in RIPE community mailing list discussions using a web-based interface rather than an email client.

Check out the forum

Please contact if you need more information.

Stay up to date!

Follow @PDO_RIPE_NCC on Twitter.