How to Transfer IP Addresses and ASNs

From RIPE NCC Translated
Revision as of 06:56, 9 May 2022 by Karla (talk | contribs) (Marked this version for translation)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Other languages:
English • ‎Türkçe • ‎español • ‎italiano • ‎русский • ‎العربية • ‎فارسی

Background

We authorise and process transfers of Internet number resources between networks.A resource transfer changes the holdership of these resources from offering party A to receiving party B. LIRs and End Users can transfer IP addresses and ASNs within our service region. All transfers are free of charge.

The following transfer scenarios are possible:

  • From LIR to LIR
  • From End User to End User
  • From LIR to End User and vice versa


Types of Resources That can be Transferred

IPv4 Allocation IPv4 PI IPv6 Allocation IPv6 PI 16-bit ASN 32-bit ASN
RIPE NCC membership required yes no yes no no no
Can be sponsored no yes no yes yes yes
Transfer restriction yes yes no no yes no
Minimum transfer size - - /32 /48 - -

24 Month Restriction

IPv4 addresses and 16-bit ASNs can only be transferred 24 months after they have been received by the resource holder.  


Submit a Transfer Request

The LIR offering their resources needs to request a transfer via their LIR Portal (under ‘Resources’ -> ‘Request Transfer’) by clicking the button below.

You will need to fill in the required information and select the resources you wish to transfer.

Information you will need:

  • The recent company registration document from both parties
  • A Transfer Agreement signed by both parties. This agreement must be signed by representatives that are legally authorised to sign/act on behalf of their respective organisations organisations
  • Documentation that prove the signees are legally authorised to sign on behalf of their organisation (this is usually visible on the company registration document)
  • If the receiving party is an End User, we will also need the End User Assignment and Maintenance Agreement signed by the receiving End User and the sponsoring LIR

Request Transfer


What happens After I Request a Transfer?

Both the Offering and Receiving party will get automatic confirmation of the request.

It’s important that Receiving party replies to this email to confirm that agree  and want to proceed with the transfer.

If some details or documents are missing, the RIPE NCC will follow up with the  relevant party..

In most cases, a transfer is completed within one or two business days. Both parties are notified once the transfer has been registered. Internet number resources are updated in the RIPE Database and details of the transfer are published on our website.


Transfers Between Regions - Inter-RIR Transfers

You can also transfer Internet number resources to companies or individuals outside of the RIPE NCC service region. These are called inter-RIR transfers. It is important to note that each RIR has its own unique policy framework, which means that different requirements can apply. The relevant policies of each RIR will apply until the inter-RIR transfer is completed.

Here are the RIRs that allow inter-RIR transfers and their policies:

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


Which Resources can be Transferred?

Because each RIR has its own policy framework, there are some differences in terms of what kinds of resources can be transferred between RIRs. The table below shows this in more detail.

AFRINIC does not currently have an inter-RIR policy. This means that no resources of any kind can be transferred to/from this region.

RIPE NCC IPv4, ASNs (including legacy) ARIN
RIPE NCC IPv4, ASNs (including legacy) APNIC
RIPE NCC IPv4 (including legacy) LACNIC

When resources are transferred from an RIR to the RIPE NCC, we will determine the status of these together with the receiving party. Resources with the [Legacy] status can keep this status.


Who Can Request an Inter-RIR Transfer?

From the RIPE NCC to another RIR

RIPE NCC members (LIRs), [End Users] through their sponsoring LIR, and [Legacy holders can request a transfer by sending an email to inter-rir@ripe.net.


From another RIR to the RIPE NCC

Any resource holder with an RIR.


Request an Inter-RIR Transfer

Transfers from the RIPE NCC to Another RIR

The transferring party needs to complete the inter-RIR transfer template and send an email with their request to inter-rir@ripe.net

What you will need:

  • 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

You will also need to help us with any actions required to complete the update - such as updating or removing RIPE Database objects.

What Happens After I Request a Transfer?

We will start evaluating your request as soon as we receive an email with the supporting documents. Once your request has been approved, we will notify the receiving RIR, who will start their evaluation and contact the receiving party in order to complete the transfer.

Once the transfer request has been approved by the other RIR, both RIRs will proceed with updating their registries on a specified date. On that date, we will make the updates in the RIPE Database.


Transfers from another RIR to the RIPE NCC

The RIPE NCC will only register resources if the network using them has at least one active element located in the RIPE NCC service region. This is consistent 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, it will need to establish one prior to our evaluation of the transfer request. In the case of independent resources or [Legacy resources], a sponsoring LIR may be used instead. Please note that a contractual agreement is not required for legacy resources.

An Inter-RIR transfer must start in the originating service region. A request should be submitted through the relevant RIR’s communication channel. The originating RIR will evaluate the request and contact the RIPE NCC once approved.

We will then contact the receiving party and perform due diligence checks.

What you will need:

  • 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 IPv4: the desired status of the IPv4 addresses
  • For legacy resources where the receiving party decides not to have a contractual relationship with either the RIPE NCC or a sponsoring LIR, then this confirmation letter needs to be submitted instead, signed by a company director that is legally authorised to sign/act on behalf of the party within the RIPE NCC service region
  • (If necessary) End User Assignment Agreement
  • (If necessary) Legacy Agreement
  • For transfers from ARIN, the recipient must provide us with a plan to use at least 50% of the transferred resources within five years


What Happens After I Request a Transfer?

Once the transfer request is approved, we will notify the other RIR. Together with the other RIR, we will then update our registries on a specified date. An acknowledgement will be sent to the receiving party.

On that date, we will make updates in the RIPE Database (e.g. create the resource objects) and notify the receiving party or their sponsoring LIR.

Inter-RIR transfers require more work than regular transfers. Coordination with RIRs in different time zones is needed to ensure compliance with the relevant policies in both regions. Updates to RIR registries must also be synchronised to ensure correct registration. Because of this, processing transfers between RIRs will take longer than transfers within the RIPE NCC service region.

If you have any questions related to inter-RIR transfers that are not answered here, you can contact us at inter-rir@ripe.net.