You are here: Home > Manage IPs and ASNs > Resource Transfers and Mergers > Inter-RIR Transfers > Documentation > Confirmation of Transfer from the RIPE NCC Service Region

Confirmation of Transfer from the RIPE NCC Service Region

[Name of the offering party (natural or legal person)]
[(Legal) address]
[City/country]
[Registration No, Registration Authority]
[Email]
[orgID]
(Hereafter referred to as Offering Party)

Whereas:

  1. The Offering Party has entered into an agreement with the RIPE NCC (Standard Service Agreement or Legacy Agreement) or with a sponsoring LIR (any of the above agreements hereafter referred to as “Basic Agreement”).

  2. The Offering Party has requested the registration of Internet number resources, or legacy Internet resources that were obtained outside the RIR system, and the RIPE NCC has registered Internet number resources or legacy Internet resources as per above to the Offering Party, including the resources listed here below (hereafter referred to as “Internet Number Resources”)

    [Insert the Internet Number Resources to be transferred to the other RIR]

  3. The Party wishes to transfer the Internet Number Resources to another party with name [insert the name of the receiving party,] established in [city/country, legal address] that intends to register the Internet Number Resources within the registry of [insert the name of the receiving RIR]

The Offering Party:

1. Requests the RIPE NCC to undertake the appropriate actions so that the registration of the Internet Number Resources will be transferred from the RIPE Registry to the registry of [insert RIR] and make any further related updates in the RIPE Database such as removing and/or updating the relevant resource objects and, if necessary, their more specifics (including route and domain objects).

2. Acknowledges, confirms and agrees the following:

2.1 Until the moment the transfer is completed, the Internet Number Resources fall within the RIPE Policies and as such the Offering Party is responsible for complying with them.

2.2 The RIPE NCC may disclose to the other RIR any information related to the Offering Party that may be necessary for the compliance of this request.

2.3 The RIPE NCC shall not be responsible and cannot be held liable for this transfer, nor for the non-fulfillment of this transfer due to restrictions from RIPE Policies and/or the relevant applicable policies of the other RIR.

2.4 The terms and conditions of this transfer may be the subject of a separate agreement of which the RIPE NCC is not a party. The RIPE NCC shall not be responsible and cannot be liable for this transfer, or for its non-fulfillment due to any reason derived from a dispute or a disagreement between the parties involved in this transfer agreement.

2.5 Due to this transfer all rights and obligations with regards to the registration of the Internet Number Resources that arise from the Basic Agreement of the Offering Party will be terminated. The Internet Number Resources will be subject to the applicable terms and policies of the other RIR.

2.6 Any other rights and obligations that arise from the Basic Agreement of the Offering Party, including any other right to any other Internet number resources registered to the Offering Party by the RIPE NCC, shall not be affected by this transfer.

2.7 Any operational damage and/or impact that may be caused due to this transfer and the requested changes in the RIPE Registry and the relevant RIPE Database objects shall be the Offering Party’s sole responsibility.

2.8 If it subsequently comes to the RIPE NCC’s attention that any of the information and/or documentation provided in connection with this request is substantially incorrect, falsified or misleading, the RIPE NCC reserves the right to revert all changes made to the RIPE Registry in compliance with this request and to request the reverse of all changes made to the other RIR registry accordingly. In any case, the Offering Party will be liable for any damages caused to any third party, including the parties of this transfer, due to RIPE NCC’s compliance with this request.

2.9 The RIPE NCC shall not be responsible and cannot be held liable for any direct and/or indirect damages, including damages to the Offering Party’s business, loss of profit, damages to third parties caused due to compliance with this request or the ongoing maintenance of the relevant RIPE Registry records in accordance with this request.

2.10 The Offering Party shall indemnify the RIPE NCC against any and all third party claims filed against the RIPE NCC in relation to compliance with this request.

2.11 In case of a transfer on a non-permanent basis, the RIPE NCC will commence all necessary actions for the return of the Internet Number Resources to the Offering Party on the last date the Internet Number Resources are agreed to be registered with the other party.

Thus agreed by person authorised to represent and act on behalf of the Offering Party:

Offering Party
Place
Date
Name of authorised person
Function
Signature