Skip to main content

Confirmation of Transfer from the RIPE NCC Service Region (Legacy Resources Without Contract)

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

Whereas:

  1. The Offering Party confirms to be the legitimate holder of legacy Internet resources, including of those listed below (hereafter referred to as “Legacy Internet Resources”).

    [Insert the relevant Legacy Internet Resources to be transferred to the other RIR]

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

  3. The Party confirms that all information provided in connection with this request is true, accurate and up-to-date.

The Offering Party

  1. Requests the RIPE NCC to undertake the appropriate actions so that the registration of the Legacy Internet 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 Offering Party is responsible for the maintenance of the Legacy Internet Resources.

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, or 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, and from the moment this is completed, the registration of the Legacy Internet Resources will be subject to the applicable terms and policies of the other RIR.

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

2.7 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, or if it is sufficiently proven that the Offering Party is not the legitimate holder of the Legacy Internet Resources at the time of the request, 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.8 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.9 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.

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