Dear all, I would like to provide an update on our approach to IPv6 Allocation Transfers. Around 18 months ago, following guidance from the WG during RIPE 88, we updated our approach to IPv6 allocation transfer requests. When the receiving member already holds an IPv6 allocation, they must now demonstrate how they utilise their existing allocation or justify the need for another one, in line with policy requirements. [1] Since then, around 1,100 IPv6 allocations have been returned to the RIPE NCC instead of being transferred, since they were no longer needed or justified. This is an increase of nearly 300% compared to the previous period. At the same time, around 650 allocations were transferred where operational need was demonstrated, reflecting an overall reduction of about 75% in IPv6 allocation transfers. Now, we are still seeing organisations holding multiple IPv6 allocations accumulated over time and have therefore started a second phase of this approach. We are conducting IPv6-focused audits with selected members with 10 or more IPv6 allocations to better understand deployment plans and assess compliance with the current RIPE IPv6 policies. This may lead to further discussion in the WG, including a possible policy review. If your organisation holds multiple IPv6 allocations that are no longer needed, or if you are unsure about policy compliance, please contact Registration Services via the LIR Portal to return unused resources or request a compliance review. Kind regards, Marco Schmidt Manager Registration Services RIPE NCC [1] https://mailman.ripe.net/archives/list/address-policy-wg@ripe.net/thread/SR5...