You are here: Home > Manage IPs and ASNs > Resource Transfers and Mergers > Inter-RIR Transfers

Inter-RIR Transfers

This section has information on the transfer of Internet number resources between RIR service regions.

Organisations in the RIPE NCC service region can transfer Internet number resources with organisations in other RIR service regions. These so-called "inter-RIR" transfers are possible between RIRs with compatible policies. Currently, ARIN and APNIC are the only RIRs that can perform inter-RIR transfers with the RIPE NCC:

  • IPv4 addresses can be transferred to/from the ARIN service region
  • IPv4 addresses and AS Numbers can be transferred to/from the APNIC service region

Inter-RIR transfers must first be approved by both the RIPE NCC and the other RIR before they can be processed.

Internet number resources are always subject to the policies of the RIR they are registered with. For inter-RIR transfers, this means that resources remain under the policies of the RIR they originated with while the transfer is being processed. When the transfer is completed and both RIRs update their registries, the resources fall under the recipient RIR's policies.

The Process

The transfer request is always initiated by the transferring party that holds the resources. They will send a request to the RIR the resources are registered with. All inter-RIR transfer requests are processed by the RIPE NCC in coordination with the relevant RIR, and in compliance with RIPE Policies and the relevant policies of the other RIR.

The RIPE NCC will evaluate all requests in accordance with the procedural document.

For transfers from the RIPE NCC service region, a registered contact or person authorised to represent the party that is requesting the transfer must send the request by email to the RIPE NCC. If this party has a contractual relationship with a sponsoring LIR for the resources being transferred (an End User or legacy holder), then the request must be submitted via the sponsoring LIR.

a. The transferring party needs to complete the inter-RIR transfer template and send an email with the request to .

b. The RIPE NCC will follow a due diligence process and will ask for:

  • Recent registration papers issued by the relevant national authorities for the party within the RIPE NCC service region
  • The confirmation letter of the request for transfer, signed by a company director that is legally authorised to sign/act on behalf of the party within the RIPE NCC service region
  • For legacy resources without a contractual relationship with the RIPE NCC or a sponsoring LIR, the transferring party needs to submit this confirmation letter instead, signed by a company director that is legally authorised to sign/act on behalf of the party within the RIPE NCC service region

c. The RIPE NCC will review the status of all registration data of relevance to the transfer of Internet number resources contained in the RIPE Registry.

d. Once approved, the RIPE NCC will forward the transfer request to the other RIR. The other RIR will process the request in accordance with its own policies. An acknowledgement will be sent to the transferring party.

e. Once the transfer request has been approved by the other RIR, both RIRs will proceed with updating their registries on a specified date. An acknowledgement will be sent to the transferring party.

f. On that date, the RIPE NCC will make any necessary updates in the RIPE Database (e.g., removing the resource objects and their more specifics if necessary). The party within the RIPE NCC service region must assist the RIPE NCC with all appropriate actions needed for this update (e.g., remove or update any resource objects or other related objects). The other RIR will update it's registry accordingly.

g. Once the transfer is completed, the RIPE NCC will notify the transferring party. From this moment, the transferred Internet number resources will fall under the policies of the receiving party's RIR.

The RIPE NCC will only register resources if the network that will be using them has at least one active element located in the RIPE NCC service region. This is in line with the current practice of only allocating or assigning resources for use in our service region.

If the receiving party does not have a contractual relationship with the RIPE NCC, then this party will need to establish a contractual relationship with the RIPE NCC or with a sponsoring LIR prior to the evaluation of the transfer request. This is not required if otherwise stipulated under the relevant RIPE Policies (for example, if legacy resources are transferred to a party that decides not to have a contractual relationship with either the RIPE NCC or a sponsoring LIR for these resources).

a. For transfers to the RIPE NCC service region, the RIPE NCC will be notified by the relevant RIR (once that RIR has approved the transfer) and the RIPE NCC will contact the relevant party within its service region.

b. The RIPE NCC will follow a due diligence process and will ask for:

  • Recent registration papers issued by the relevant national authorities for the party within the RIPE NCC service region
  • The confirmation letter for the request for transfer, signed by a company director that is legally authorised to sign/act on behalf of the party within the RIPE NCC service region
  • For legacy resources where the receiving party decides not to have a contractual relationship with either the RIPE NCC or a sponsoring LIR, the receiving party needs to submit this confirmation letter instead, signed by a company director that is legally authorised to sign/act on behalf of the party within the RIPE NCC service region
  • For transfers from an RIR with policies that require the receiving RIR to adhere to a needs-based policy, the recipient must provide the RIPE NCC with a plan for the use of at least 50% of the transferred resources within five years

c. The RIPE NCC, in cooperation with the receiving party, and in compliance with RIPE Policies, will determine the status that the resources to be transferred will receive once they are registered in the RIPE Registry.

Note: Legacy resources transferred to the RIPE Registry that have not had their legacy status revoked by the transferring RIR will retain their legacy status, unless otherwise requested by the receiving party. If the resources have lost their legacy status, they will be handled in accordance with their new status.

d. Once the transfer request is approved, the RIPE NCC will notify the other RIR and both RIRs will proceed with updating their registries on a specified date. An acknowledgement will be sent to the receiving party.

e. On that date, the RIPE NCC will make any necessary updates in the RIPE Database (e.g., create the resource objects). It is the responsibility of the party within the RIPE NCC service region to create any further necessary objects in the RIPE Database.

f. Once the transfer is completed, the RIPE NCC will notify the receiving party. From this moment, the transferred Internet number resources will fall under RIPE Policies.

 

Please note: Inter-RIR transfers require considerably more work than regular transfers. Coordination between the RIRs (in different time zones) is required to ensure compliance with relevant policies in both regions, and updates to the RIR registries must be synchronised to ensure correct registration. Because of this, processing transfers between RIRs will take longer than transfers within the RIPE NCC service region.

Affected Services

Because inter-RIR transfers involve moving resources from one RIR registry to another, the following services may be affected and likely won’t be available immediately.

When resources are transferred into the RIPE NCC service region, it is the responsibility of the receiving party to create domain objects in the RIPE Database to request reverse DNS delegation for the associated address space. It may take up to 24 hours for the reverse delegation to appear in the DNS.

When resources are transferred out of the RIPE NCC service region, all associated objects in the RIPE Database, including domain objects, will be deleted. Any reverse delegation for the resources will be removed from the DNS immediately, and it is the responsibility of the receiving party to immediately request reverse DNS delegation in the registry of the other RIR.

When resources are transferred into the RIPE NCC service region, the resource certificate issued to you in the region of origin (if any) will be shrunk or revoked dependent on that region's policy when the transfer is completed. However, it can take up to two months before a resource certificate can be issued for these resources in the RIPE NCC service region. During this time you will not be able to issue ROAs for your resources. Please note that any announcements for these resources would appear as "RPKI Unknown", rather than “Invalid", because there will be no other ROAs for these resources. More information on BGP origin validation is available here.

When resources are transferred out of the RIPE NCC service region, the RIPE NCC will shrink or revoke your resource certificate for these resources as soon as the transfer is complete. Any ROAs issued for these resources will become invalid and will be removed. When and if these resources are eligible for certification in the target region depends on that region's local policy. Similar to above however, announcements for these resources will appear with "RPKI Unknown", until ROAs are issued in the target region.


Further Details

This template is to be submitted to the RIPE NCC when requesting a resource transfer from the RIPE NCC to another RIR:
Inter-RIR Transfer template

Confirmation letters:
For all Internet number resources (except legacy resources not covered by a contractual relationship):
1. Template confirmation letter for transfers to the RIPE NCC service region
2. Template confirmation letter for transfers from the RIPE NCC service region

For legacy resources without a contractual relationship:
3. Template confirmation letter for transfers to the RIPE NCC service region
4. Template confirmation letter for transfers from the RIPE NCC service region

All confirmation letters must be signed by a company director that is legally authorised to sign/act on behalf of the party within the RIPE NCC service region

If you have any questions related to inter-RIR transfers that are not answered through these pages you can contact us at