Dear colleagues, During the Address Policy WG session at RIPE 88, I presented on the topic of IPv6 stockpiling by several members [1]. There was widespread support from the working group that our application of IPv6 needs to evolve, emphasising the importance of enforcing policy requirements for transfers of IPv6 allocations. In light of this, the RIPE NCC will now prioritise enforcing 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 [2][3]. 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 will be applied to any new transfer request submitted from today. Please note, 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. Kind regards, Marco Schmidt Manager Registration Services RIPE NCC [1] https://ripe88.ripe.net/wp-content/uploads/presentations/73-RIPE88-Feeback-f... [2] https://www.ripe.net/publications/docs/ripe-807/#2-1-transfer-requirements [3] https://www.ripe.net/publications/docs/ripe-738/#52-subsequent-allocation