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

Document Actions

Policy Proposals

Remove Multihoming Requirement for AS Number Assignments

2014-03: This policy proposal would remove the requirement that a network be multihomed in order to receive an AS Number assignment from the RIPE NCC.

Allow IPv4 PI transfer

2014-02: According to “IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region”, it is not possible to transfer Provider Independent (PI) IP space. There is, however, a lot of IPv4 PI space that was assigned over the past years and there is currently a market for this space as well. Although it isn’t possible to actually hand-over the IP space in the RIPE Registry, some people are actually “selling ownership via side-letters” or other means. This poses a risk for the buyer (new users) and as the registry isn’t correctly maintained, the world is looking at incorrect/stale/false data in the registry.

Abandoning the Minimum Allocation Size for IPv4

2014-01: Abandonment of the Minimum Allocation Size concept in the "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" document, currently ripe-606.

PA/PI Unification IPv6 Address Space

2013-06: This policy proposal aims to unify the three RIPE documents ripe-589, ripe-451 and ripe-233 and to provide one document for all the IPv6 space. It also removes the difference between PI and PA.

No Restrictions on End User Assignments in Intra-RIR Transfers

2013-05: This policy proposal intends to update the intra-RIR IPv4 transfer policy with the removal of the restriction on End User assignments.

Resource Certification for non-RIPE NCC Members

2013-04: Currently, the RIPE NCC Resource Certification (RPKI) service is only available for RIPE NCC members. This proposal intends to allow the RIPE NCC to issue resource certificates for non-members, such as Provider Independent End Users and Legacy address space holders, which reside in the RIPE NCC Service region.

Removal of requirement for certification of reallocated IPv4 addresses

2013-02: Removal of requirement for certification of reallocated IPv4 addresses. This proposal requests that the text requiring certification of transferred resources is deleted

Post Depletion Adjustment of Procedures to Match Policy Objectives, and Clean-up of Obsolete Policy Text

2013-03: This proposal removes the need-based requirement for IPv4 delegations in the RIPE NCC service area. It also incorporates section 5.6 "Use of last /8 for PA Allocations" into the main policy text, removing all references to the "last /8" itself, and to the reaching of it as a future event.

Openness about Policy Violations

2013-01: This proposal intends to provide more insight into the good stewardship of the RIPE NCC and to encourage assistance in stopping abuse of these shared public resources.

Extension of IPv6 /32 to /29 on a per-allocation vs per-LIR basis

2012-10: This proposal aims to clarify the approved text of proposal 2011-04 on the extensions of IPv6 allocations to ensure that any /32 may be extended to /29, without having to restrict to one extension on a per-LIR-total-summary basis.

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.