[Name of the receiving party (natural or legal person)]
[Registration No, Registration Authority]
(Hereafter referred to as Receiving Party)
The Receiving Party
2.1 The Receiving 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”). In case there is no contractual relationship yet established between the Receiving Party with the RIPE NCC or a sponsoring LIR, and unless otherwise stipulated under the relevant RIPE Policies, this transfer shall not be completed until the contractual relationship is established and the RIPE NCC receives evidence of this.
2.2 Provided that the Internet Number Resources are requested to be registered with the RIPE Registry from an RIR with policies that require the receiving RIR to adhere to a needs-based policy, the Receiving Party must provide a plan for the use of at least 50% of the Internet Number Resources within five years, which will be evaluated by the RIPE NCC. The RIPE NCC will further evaluate this request as it would evaluate a transfer within its own service region.
2.3 From the moment the transfer is completed, the registration and maintenance of the Internet Number Resources shall be subject to the terms and conditions of the Basic Agreement and RIPE Policies and, as such, compliance with them is mandatory.
2.4 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.5 The terms and conditions of this transfer shall 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.6 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 request the reverse of all changes made to the other RIR registry accordingly. In any case, the Receiving 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.7 The RIPE NCC shall not be responsible and cannot be held liable for any direct and/or indirect damages, including damages to the Receiving 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.8 The Receiving 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.9 In the 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 other party on the last date the Internet Number Resources are agreed to be registered with the Receiving party.
Thus agreed by person authorised to represent and act on behalf of the Receiving Party:
Name of authorised person