Policy Proposals
-
Community / Policy DevelopmentLanguage Clarification in “IPv6 Address Space Policy For Internet Exchange Points”
2014-09: Language Clarification in “IPv6 Address Space Policy For Internet Exchange Points”
PolicyProposal • address policy ipv6 -
Community / Policy DevelopmentPublication of Sponsoring LIR for Legacy Internet Resource Holders
2014-06: Publication of Sponsoring LIR for Legacy Internet Resource Holders
PolicyProposal • ncc services -
Community / Policy DevelopmentPolicy for Inter-RIR Transfers of Internet Resources
2014-05: Policy for Inter-RIR Transfers of Internet Resources
PolicyProposal • ipv4 address policy -
Community / Policy DevelopmentRemoving IPv6 Requirement for Receiving Space from the Final /8
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).
PolicyProposal • ipv4 address policy ipv6 -
Community / Policy DevelopmentRemove 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.
PolicyProposal • as numbers address policy -
Community / Policy DevelopmentAllow 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.
PolicyProposal • ipv4 address policy -
Community / Policy DevelopmentAbandoning 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.
PolicyProposal • ipv4 address policy -
Community / Policy DevelopmentPA/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.
PolicyProposal -
Community / Policy DevelopmentNo 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.
PolicyProposal -
Community / Policy DevelopmentResource 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.
PolicyProposal