Skip to main content
  • Legend
  • Added
  • Deleted

1.0 Definitions

For the purposes of this document, Internet number resources document Internet Number Resource records refer to:

2.0 Introduction

In order for the RIPE NCC to maintain an accurate registry, it must hold accurate data concerning:

  • The natural or legal persons holding the registration of Internet
  • number resourcesThe Internet number resources Number ResourcesThe Internet Number Resource records
    • that are registered to these natural or the natural and legal persons

This means that any transfer of Internet number resources Number Resources from one party to another, or any change to the legal status of a party holding the registration of Internet number resources, Number Resources, must be communicated to the RIPE NCC.

A member The Member must inform the RIPE NCC if one or bothof the following changes occurs:

  1. Internet Number Resource records are transferred. Such transfers may take place:
    1. Because of a change in the member's business structure (for business structure of the Member, for example in the case of a merger or acquisition of the member's organisation, or if the member is undergoing bankruptcy, liquidation, suspension of payments or insolvency proceedings) that can be proved/supported by official documentation from national authorities. Member's organisation; or
    2. In the case of a transfer of Internet number resources from the member to another party pure transfer of an allocation from a Member to another Member according to RIPE
    3. Policy "RIPE Resource Transfer Policies Link: http://www.ripe.net/publications/docs/transfer-policies ".The member Policies (Section 5.5, IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region Link: https://www.ripe.net/publications/docs/ipv4-policies#55 ). Such a transfer may also be facilitated through the RIPE NCC Listing Service. Link: /manage-ips-and-asns/resource-transfers-and-mergers/listing/ The Member
    2. changes its official legal name. Such a change may occur, for example, because of a merger or acquisition of the member's Member's organisation.

This document describes the procedures to be followed for such changes to be properly communicated and registered with to, and registered with, the RIPE NCC.

Additionally, this document describes the procedure for requesting a voluntary transfer lock in accordance with the RIPE Policy “Voluntary Transfer Lock Link: ../../../resolveuid/074e7e56a0c8467db78c9c10b35feee0 ”.

Note:
If a change in a member's the Member's official legal name is accompanied by a transfer of Internet number resources, the member Number Resource records, the Member must first inform the RIPE NCC of the name change and then of the transfer.

If a change in a member's the Member's business structure is notaccompanied by a transfer of Internet number resources Number Resource records or a change in the member's Member's official legal name, then the RIPE NCC does not need to be informed of this change.

This document does not describe the procedure to be followed in the case of changes with regards to independent Internet number resources assigned to End Users or any changes to the End Users business structure. This procedure is described in the RIPE NCC Procedural Document, "Independent Internet Number Resources - Contractual Relationship Changes Between Sponsoring LIR and End User Link: http://www.ripe.net/publications/docs/lir-end-user-contractual-changes ".

This document does not describe the procedure to be followed in case of a transfer of Internet number resources from the RIPE NCC service region to the service region of another RIR and vice versa. This procedure is described in the RIPE NCC procedural document, "Inter-RIR Transfer of Internet Number Resources Link: http://www.ripe.net/publications/docs/inter-rir-transfer-of-inr ".

3.0 Transfer of Internet Number

ResourcesIf a member Resource RecordsIf a Member transfers their Internet number resources Number Resource records to a third party for any reason, this transfer must be declared to the RIPE NCC for approval. to, and approved by, the RIPE NCC.

3.1 Submission of the Request for Transfer

For the transfer to be processed, a

One of the involved parties must submit a request by email to the RIPE NCC for the transfer to be executed:

A registered contact or an authorised person (e.g., senior manager, legal successor) of the involved parties must submit a request to the RIPE NCC. More specifically:

The RIPE NCC will evaluate the request and process the transfer if it is adequately supported by the submitted information (see below under i-v).

must send the request.

The RIPE NCC will ask for the following information:

i. Information regarding the parties involved, including:

  • The full official legal names of all parties involved
  • Which party will transfer the Internet number resources Number Resource records and which party will receive them
  • Recent registration papers issued by the relevant national authorities for all involved parties

If the current official legal names of the involved members Members are different from those the ones in the relevant signed RIPE NCC Standard Service Agreement, then the

procedure described in Section 4.0 Link: #memberchanges must be followed prior to the transfer of the Internet number resources.The

procedure described under Section 4.0 Link: #official-legal-name must be followed prior to the transfer of the Internet Number Resource records. The procedure described under Section 4.0 is not necessary for the transferring member Member if the RIPE NCC Standard Service Agreement for that member of the transferring Member is terminated (see Sections A.1.1 and A.1.2 of the RIPE NCC Procedural Document, "Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources Link: http://www.ripe.net/publications/docs/closure ". Closure of LIR and Deregistration of Internet Number Resources, Section A.1.1. Link: https://www.ripe.net/publications/docs/closure#11 and Section A.1.2. Link: https://www.ripe.net/publications/docs/closure#12 ).

ii. A description of the reason for the transfer (for example, due to merger, acquisition, transfer of Internet number resources allocation according to the RIPE policies)

If the transfer is taking place due to a change in the structure of the organisation(s) involved (e.g., merger, acquisition), involved, a description of the changes among these the organisation(s) is necessary. This The description must be accompanied by the all official legal documents issued by the relevant national authorities proving/supporting the changes the request is based on.

If the change in the structure of the organisation(s) involved cannot be proven/supported by official documentation from national authorities describing this change (e.g., a network acquisition from one member to another), then these cases will fall within the scope of RIPE Policy "RIPE Resource Transfer Policies Link: http://www.ripe.net/publications/docs/transfer-policies ".

iii. A list of the Internet number resources Number Resource records that are requested to be transferred.

If allof the transferring member's Internet number resources Member's Internet Number Resource records registered are being transferred, a confirmation of this is requested.

The member Member must also indicate any End User assignment agreements that are requested to be transferred.

If a member Member transfers all of their Internet number resources, their Number Resource records, the RIPE NCC Standard Service Agreement of the Member may be terminated upon request of the member or following the member's confirmation (see Section A.1.1. of the RIPE NCC Procedural Document, "Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources Link: http://www.ripe.net/publications/docs/closure "). (see Closure of LIR and Deregistration of Internet Number Resources, Section A.1.1. Link: https://www.ripe.net/publications/docs/closure#11 ).

iv. The correct contact details of all parties organisations involved

The RIPE NCC may ask the parties organisations involved to confirm the correctness of their contact details or to update them. The contact details include the billing contact details and the VAT number details.

v. A Transfer Agreement signed by both parties or by their legal successors

The RIPE NCC provides the will make a template of the Transfer Agreement that either available. Either party may submit

to the RIPE NCC.The Transfer Agreement must be

the Transfer Agreement to the RIPE NCC, signed by authorised persons for both parties. For the transferring party, it is required that the Transfer Agreement is signed by an authorised representative having the general capacity to act on behalf of this party. The RIPE NCC reserves the right to request official documentation proving that the person signing on behalf of either party is authorised to do so.

The RIPE NCC may ask the other party/parties to confirm their agreement to the transfer. The confirmation must be authorised (signed or sent) by a registered contact person or authorised person (e.g., senior manager, legal successor).

If the transferring party no longer exists by the time the RIPE NCC is being informed, the receiving party must send:

  • An an official document (issued by a national authority) confirming the closure of the transferring
  • partyA party; anda
    • copy of an older signed agreement between the relevant parties mentioning the transfer of the Internet number resources. Number Resource records. If such an agreement is not available, the RIPE NCC may accept a receiving party must send confirmation of the transfer to the RIPE NCC signed by an authorised person (e.g., senior manager, legal successor) of the receiving party. successor). The RIPE NCC reserves the right to reverse the transfer should another party object to this transfer and provide an agreement that proves that the Internet number resource Number Resource records should have been transferred to them.

vi. An overview of the utilisation of all allocations and of the status of all independent Internet number resource Number Resource assignments

The RIPE NCC may ask for an overview of the utilisation of all Internet number resources Number Resources registered to the member Member and of all End User assignment agreements signed by the member. Member.

3.2 If the Receiving Party is not Organisation is not yet a Member

Members may wish to transfer their Internet number resource to another member or to a third party Number Resource records to another Member or to an organisation that is not a member. yet a Member.

If the Internet number resources Number Resource records are transferred to a non-member, the receiving party non-Member, the receiving organisation must apply to be a member by signing a Member by signing the RIPE NCC Standard Service Agreement before the transfer takes place (more information on how to become a member is available Link: ../../../../../../../../../../../../../../../become-a-member Member is available Link: https://www.ripe.net/lir-services/member-support/become-a-member ). If the receiving party organisation refuses to do the above, the RIPE NCC will not transfer the Internet number resources to them.

If the Internet number resources to be transferred are Independent Resources (IPv4 PI, IPv6 PI and AS Numbers), the receiving party may either apply to become a member by signing the RIPE NCC Standard Service Agreement, or can enter into a contractual relationship with a sponsoring LIR. For more information, please see the notes on Requesting Independent Resources Link: ../../../../../../../../../../../../../../../participate/resource-management/independent-resources .

Number Resource records to them.

The request for the transfer can be submitted as described above (Section 3.1). 1).

3.3 Financial Consequences

All outstanding invoices and all outstanding financial obligations must be paid in full. If the RIPE NCC Standard Service Agreement is terminated in the course of the RIPE NCC financial year, the service fee for this member Member must be paid for the full year. This The payment is the responsibility of the receiving member. Member. If the receiving

party is not a member, then payment is the responsibility of the transferring member.If the receiving party

organisation decides to sign the RIPE NCC Standard Service Agreement, then a sign-up fee must be paid (see RIPE NCC Charging Scheme Link: http://www.ripe.net/publications/docs/charging Link: http://www.ripe.net/ripe/docs/ripe-499 ).

3.4 Internet Number Resource Registration and RIPE Database Issues

The RIPE NCC will review the status of any IP address allocation or independent Internet number resource Number Resource assignment maintained by the party organisations involved, in compliance with the RIPE Policies current at the time of the transfer.

The transferring party or (if the transferring party does not exist anymore) the receiving member receiving Member must deregister from the RIPE Database any invalid or overlapping registrations. registrations or unused assignment approvals.

The RIPE NCC will update the registry, including all RIPE Database objects maintained by the RIPE NCC that are related to this transfer. The transferring member Member must update all RIPE Database objects maintained by them that are related to this transfer.

3.5 Transfers Between LIR Accounts Belonging to the Same Member

Transfers of Internet number resources between LIR accounts belonging to the same member fall within the scope of the RIPE Policy "RIPE Resource Transfer Policies Link: http://www.ripe.net/publications/docs/transfer-policies " and will be evaluated in accordance with them.

Any time restriction that is applied to Internet number resources when they are received must expire before they can be transferred. However, once this restriction has expired, new time restrictions will not be applied to these resources if they are further transferred between LIR accounts held by the same member.

The procedure described above in Section 3.1 is applicable except from paragraphs 3.1.ii and 3.1.v.

If after the transfer the member decides to close an LIR account, all outstanding invoices and all outstanding financial obligations for all LIR accounts must be paid in full.

The RIPE NCC will review the status of any IP address allocation or independent Internet number resource assignment maintained by the member, in compliance with the RIPE Policies current at the time of the transfer.

The member must deregister from the RIPE Database any invalid or overlapping registrations.

The RIPE NCC will update the registry, including all RIPE Database objects maintained by the RIPE NCC that are related to this transfer. The member must update all RIPE Database objects maintained by them that are related to this transfer.

3.6 Transfers of Internet Number Resources under Policy Restrictions Due to a Change in the Member's Business Structure

Internet number resources that are subject to transfer restrictions imposed by the RIPE Policy "RIPE Resource Transfer Policies Link: http://www.ripe.net/publications/docs/transfer-policies ", and that are transferred due to a change in a member's business structure, must either remain registered with the original LIR account or be registered with a new LIR account. The receiving party will be provided with RIPE NCC services for these Internet number resources via either the original LIR account or the new LIR account until the policy restrictions are lifted.

3.7 Transfers due to Seizure

If the RIPE NCC is delivered a court order for the seizure of the right to registration of Internet number resources for the recovery of money, in accordance with Dutch legal procedures, the RIPE NCC will comply with its obligations. This order may create obligations for the RIPE NCC, such as the restriction of the transfer of Internet number resources from the member’s account, the issuance of a statement outlining the Internet number resources registered to a member’s account, and the transfer of the Internet number resources away from the member’s account.

The RIPE NCC will comply on the condition that the court order:

  • Has entered into force and is recognised by the Dutch courts.
  • Is served by a bailiff in advance to the RIPE NCC in the form of an authentic enforceable document (e.g., a court order).
  • Specifically mentions the RIPE NCC and creates an obligation for the RIPE NCC to perform the transfer. (i.e., the enforceable title must apply specifically to the RIPE NCC). This does not mean the RIPE NCC needs to be named as a defendant.
  • States the specific Internet number resources at issue.

Each order will be reviewed on a case-by-case basis. If the RIPE NCC believes that an order or the third party seeking to enforce the order does not comply with RIPE policies or RIPE NCC procedures, the RIPE NCC reserves the right to dispute it.

4.0 Member Changes 4.0 The Member Changes its Official Legal Name

It is the obligation of the member Member to inform the RIPE NCC immediately if any change in the member's Member's official legal name occurs.

The member must send a request for name change via the LIR Portal. The request Member must send an email to ncc [at] ripe [dot] net Link: mailto:ncc@ripe.net informing the RIPE NCC of the name change. This email must include:

  • New registration papers from the national authority; and
  • The official legal documents supporting this change

If the requesting party does not have access to the LIR Portal, the request must be submitted via email to lir-help@ripe.net Link: mailto:lir-help@ripe.net and the above-mentioned documents must be uploaded via a secure link provided by the RIPE NCC.

The RIPE NCC will send a new RIPE NCC Standard Service Agreement Link: http://www.ripe.net/publications/docs/service-agreement for the member Link: http://www.ripe.net/ripe/docs/service-agreement for the Member to sign under the new official legal name. When the RIPE NCC receives the new RIPE NCC Standard Service Agreement properly signed by the member, Member, it will update the registry, including all RIPE Database objects maintained by the RIPE NCC that are related to this change. The member Member must update all RIPE Database objects maintained by them that are related to this change.

If the change in the member's official legal name occurred without a further change in the member's structure (e.g., merger with another legal entity, acquisition by/of another legal entity), the member will not have to sign a new RIPE NCC Standard Service Agreement.

5.0 Voluntary Transfer Lock of Internet Number Resources

5.1 The Scope of The Voluntary Transfer Lock

The RIPE NCC may approve a request for a voluntary transfer lock in accordance with the RIPE Policy “Voluntary Transfer Lock Link: ../../../resolveuid/074e7e56a0c8467db78c9c10b35feee0 ”.

If the RIPE NCC deems that a voluntary transfer lock request is not in line with RIPE policies, RIPE NCC procedural documents, or applicable law, the RIPE NCC reserves the right to reject the request. 

The RIPE NCC reserves the right not to enforce a voluntary transfer lock even if the relevant request has been approved by the RIPE NCC. The RIPE NCC may not enforce a voluntary transfer lock, for example, in case of Transfers of Internet Number Resources Due to a Change in the Member's Business Structure (see above Section 3.6) or Transfers Due to Seizure (see above Section 3.7). 

This document does not describe the procedure to be followed in the case of voluntary transfer locks for independent Internet number resources assigned to End Users. This procedure is described in the RIPE NCC Procedural Document, "Independent Internet Number Resources - Contractual Relationship Changes Between Sponsoring LIR and End User Link: http://www.ripe.net/publications/docs/lir-end-user-contractual-changes ".

5.2 Submission of the Request for Voluntary Transfer Lock

For the voluntary transfer lock to be approved, a registered contact or an authorised person (for e.g., a senior manager, the legal successor) of the requesting party must submit a request to the RIPE NCC.

The RIPE NCC will evaluate the request and approve the voluntary transfer lock if it is adequately supported by the information submitted and documentation as described below.

The RIPE NCC will ask for the following:

The Voluntary Transfer Lock Request Form

The requesting party must complete the Voluntary Transfer Lock Request Form. The template of the Voluntary Transfer Lock Request Form is provided by the RIPE NCC.

The Voluntary Transfer Lock Request Form must be submitted to the RIPE NCC via the LIR Portal by a registered contact or an authorised person of the requesting party.

The Voluntary Transfer Lock Request Form must be signed by the authorised person for the requesting party having the general capacity to act on behalf of this party.  

The RIPE NCC reserves the right to request official documentation proving that the person signing on behalf of the requesting party is authorised to do so.

To complete the Voluntary Transfer Lock Request Form, the requesting party will have to provide:

i. Information regarding the party requesting the voluntary transfer lock, including:

  • The full official legal name
  • Recent registration papers issued by the relevant national authority

If the current official legal name of the requesting party is different from the one in the relevant signed RIPE NCC Standard Service Agreement, then the procedure described in Section 4.0 Link: #memberchanges must be followed prior to requesting voluntary transfer lock.

ii. A list of the Internet number resources for which a voluntary transfer lock is being requested

iii. The correct contact details of the requesting party

The RIPE NCC may ask the requesting party to confirm the correctness of their contact details or to update them. The contact details include the billing contact details and the VAT number details.

iv. The duration of the voluntary transfer lock

In the Voluntary Transfer Lock Request Form the requesting party is required to indicate the duration of the voluntary transfer lock, which can be 6, 12 or 24 months. The voluntary transfer lock will be applied from the date on which the RIPE NCC approves the voluntary transfer lock request. 

The voluntary transfer lock will expire after 6, 12 or 24 months, depending on the duration requested. 

To continue with the voluntary transfer lock after the expiration of the requested lock duration, a member will have to submit a new voluntary transfer lock request to the RIPE NCC for approval.

Members cannot request the cancellation of the voluntary transfer lock once the lock has been applied until the voluntary transfer lock expires. 

5.3 The Publication of Internet Number Resources under the Voluntary Transfer Lock

The RIPE NCC will publish a list of Internet number resources under voluntary transfer lock on its website.