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.
Draft Policy Text
Any LIR is allowed to re-allocate complete or partial blocks of IPv4 address space that have been previously allocated to them either by the RIPE NCC or by IANA but which are currently not assigned. Re-allocation may only be to another LIR within the RIPE NCC Service Region. The block that is to be re-allocated must not be smaller than the minimum allocation block size at the time of re-allocation.
Enabling Methods for Reallocation of IPv4 Resources Re-allocation is to be reflected in the RIPE Database. This re-allocation may be on either a permanent or non-permanent basis. The re-allocation will be notified to the RIPE NCC who will record the change of allocation. Re-allocated blocks will be signed to establish current allocation owner.
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 usageof 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.
Arguments Opposing the Proposal
This policy proposal allows LIRs to move around allocations without prior approval by RIPE NCC. This is a big departure from currently set policy. It also leans heavily on the quality of (execution of) current allocation policy to prevent potential abuse or an increased speed of depletion.