Hello Sander,
Thank you for your question.
That is correct, our primary focus will be on supporting the transfers
of successfully deployed IPv6 networks. At the same time, we will
evaluate requests for allocation transfers without live networks as if
they were new requests submitted directly to the RIPE NCC.
This aligns closely with the intent of policy proposal 2014-12, "Allow
IPv6 Transfers," which aimed to accommodate consolidations between
related companies or the acquisition of active networks from a business
partner without requiring companies to redo their IPv6 implementations. [1]
If the status of existing IPv6 allocation(s) in the receiving LIR's
account would be unclear, we might take the opportunity to clarify this
as well.
I hope this answers your question.
Kind regards,
Marco Schmidt
Manager Registration Services
RIPE NCC
[1] https://www.ripe.net/membership/policies/proposals/2014-12/
On 18/06/2024 14:15, Sander Steffann wrote:
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
