Scenario 1 — We sponsor before and after
GetIPv6 is the current sponsoring LIR and stays the sponsor after the transfer.
- Order: the recipient (or provider on their behalf) orders RIPE ASN or RIPE ASN + /48 IPv6.
- Open a ticket: the provider tells us which service's ASN to transfer and to which new service.
- Submit application info on the new service page, selecting the "New Application" type. The recipient prepares the same materials as a new application.
- Transfer agreement: we require a transfer agreement signed between provider and recipient (RIPE provides a template).
Scenario 2 — We sponsor now, another LIR after
GetIPv6 is the current sponsor, but a different LIR will sponsor after the transfer. Open a ticket and provide: the service whose ASN is transferred out, the signed provider/recipient transfer agreement, the EUAA signed between the recipient and their new LIR, and contact details for both parties.
Scenario 3 — Another LIR now, we sponsor after
RIPE policy requires resource transfers to be initiated by the resource provider or the provider's sponsoring LIR.
- Order RIPE ASN or RIPE ASN + /48 IPv6 (recipient).
- Open a ticket noting the service is meant to receive an ASN from another org.
- Submit application info with the "New Application" type and complete the EUAA signing with us.
- The current sponsoring LIR submits the resource-transfer request to RIPE NCC.
More on RIPE transfers: Transfers in the RIPE NCC service region.
Questions about a transfer?
Ask on Discord