Policy Proposals

2014-12: Allow IPv6 Transfers

2014-10: Language Clarification in “IPv6 Addresses for Internet Root Servers In The RIPE Region”

2014-08: Language Clarification in “Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region”

2014-11: Language Clarification for “Allocating/Assigning Resources to the RIPE NCC”

2014-09: Language Clarification in “IPv6 Address Space Policy For Internet Exchange Points”

2014-06: Publication of Sponsoring LIR for Legacy Internet Resource Holders

2014-05: Policy for Inter-RIR Transfers of Internet Resources

2014-04: In order to receive an allocation from the final /8, LIRs are currently required to have received an IPv6 allocation. LIRs that have an existing IPv6 PI assignment but no PA allocation do not meet this criterion. In order to qualify, they need to request an IPv6 allocation and subsequently return their existing PI assignment (per ripe-589 section 7.1).

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.

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.