Updated Approach to IPv6 Transfer Requests

During the Address Policy Working Group session at RIPE 88, we presented on the topic of IPv6 stockpiling by several members. The session highlighted widespread support for evolving our application of IPv6, emphasising the importance of enforcing policy requirements for transfers of IPv6 allocations.

In response to this feedback, the RIPE NCC is now prioritising the enforcement of policy requirements when evaluating IPv6 allocation transfer requests. Since transferred resources are no different than allocations made by the RIPE NCC, if the receiving party of a transfer request already holds an IPv6 allocation, they must document the need for another allocation according to the policy requirements for subsequent allocations.

This means the receiving party must demonstrate how they have utilised their existing allocation or justify the need for a new one. In the case of an IPv6 allocation transfer, a successfully deployed network on that range would be considered a valid new need.

This updated approach is applied to any new transfer request submitted from 17 June 2024.

Please be advised that this updated approach only applies to transfer requests under RIPE policies. If the change of holdership of an IPv6 allocation is due to a company merger or acquisition, the RIPE NCC will process this change in accordance with relevant RIPE NCC procedures.