Hi Marco, > 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.
Just to be clear: "a successfully deployed network on *the range that is being transferred* would be considered a valid need” or are you talking about the recipient’s original range? Or both/either? :) > 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. Thank you! Sander -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/address-policy-wg
