You're looking at an older or unpublished version: 3

Enabling Methods for Reallocation of IPv4 Resources

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.

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.

Rationale:

Arguments Supporting the Proposal

  • Once the IANA resources and subsequently the ability of the RIRs to supply LIRs with fresh IPv4 allocations run out, a new mechanism needs to be in place to cope with that situation. With this new policy, a framework is created to enable usage of the probably significant pool of 'allocated but unused' IPv4 resources. By implementing both a permanent and a non-permanent transfer, most mechanisms that will evolve for moving such space can probably be accommodated.
  • Transferring resources between non-LIRs and between LIRs of different RIRs is outside the scope of this policy. Not implementing this or similar policies will not stop such new mechanisms from evolving.
  • In this 3rd version of the proposal, following the feedback received from the community on the previous versions, an additional criteria is proposed for the receiving LIR so that they will need to demonstrate their need for address space in order to receive a re-allocation. The proposed demonstration of need for a transfer from one LIR to another is to keep it consistent with the criteria to receive further address space from the RIPE NCC directly. As of today’s current policy, this means the receiving LIRs will have to have an eighty percent (80%) usage within all the address space that they already hold before they can receive a re-allocation. If the further allocation criteria changes in the future, same change will apply for transfers.

Arguments Opposing the Proposal

  • None