Skip to main content
  • Legend
  • Added
  • Deleted

or their legal successors

The RIPE NCC provides the template of the Transfer Agreement that either party may submit to the RIPE NCC.

The Transfer Agreement must be 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 official document (issued by a national authority) confirming the closure of the transferring party
  • A copy of an older signed agreement between the relevant parties mentioning the transfer of the Internet number resources. If such an agreement is not available, the RIPE NCC may accept a confirmation of the transfer to the RIPE NCC signed by an authorised person (e.g., senior manager, legal successor) of the receiving party. The RIPE NCC reserves the right to reverse the transfer should another party object and provide an agreement that proves that the Internet number resource 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 assignments

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

3.2 If the Receiving Party is not a Member

Members may wish to transfer their Internet number resource to another member or to a third party that is not a member.

If the Internet number resources are transferred to a non-member, the receiving party must apply to be a member by signing a RIPE NCC Standard Service Agreement before the transfer takes place (more information on how to become a member is available Link: ../../../../../../../../../../../../../../../become-a-member ). If the receiving party 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. must be included.

2.4 Contact Person(s)

It is very important to notify the RIPE NCC, if there is a change of contact person(s). This is essential, as only registered contact person(s) can submit Internet resource requests to the RIPE NCC and provide updates to our internal registry files.

If the contact person(s) of the affected LIR has changed, the RIPE NCC may adjust the Assignment Window of the LIR until the contact person(s) is up-to-date with RIPE NCC procedures and RIPE community policies.

If there are no current registered contacts remaining with the LIR, a fax signed by the Managing Director of the LIR on organisation letterhead is required to implement these changes. These changes should include the new registered contact person(s) for the LIR.

2.5 RegID

It is not necessary to obtain a new Registry Identifier (RegID) if the name of the organisation that operates the LIR changes. The RegID is merely an internal identifier used by the RIPE NCC to distinguish the various LIRs. It does not have to correspond to the legal name of the organisation operating the LIR.

If an LIR insists on changing their RegID, a fee corresponding to the sign-up fee for a new LIR will be charged to cover additional administrative work generated. Please see the current version of the RIPE NCC Charging Scheme available from the RIPE Document Store at:

http://www.ripe.net/ripe/docs/charging.html Link: http://www.ripe.net/ripe/docs/charging.html

2.6 Transfers of Address Allocations

All transfers of address allocations from one LIR to another LIR (or to a non-LIR) require approval by the RIPE NCC. It is expected that all database objects relating to this allocation be correct and up-to-date before the transfer occurs. Transferred allocations containing a large amount of unassigned address space may be set aside and kept by the RIPE NCC until the other allocations held by the LIR are considered fully used (about 80%). Once the LIR has reached full utilisation in its other allocations, the reserved allocations will be made available to the LIR. For further details on allocation policy, please refer to the document "IPv4 Address Allocation and Assignment Policies in the RIPE NCC Service Region" available from the RIPE Document Store at:

http://www.ripe.net/ripe/docs/ipv4-policies.html Link: http://www.ripe.net/ripe/docs/ipv4-policies.html

2.7 Takeover Fee

In cases where an organisation operating an LIR takes over one or more LIRs, a takeover fee is due for every LIR taken over (e.g. if three LIRs are taken over, the fee is paid three times). All current outstanding invoices for the LIRs being taken over will also have to be paid in full.

The transfer of address allocations also incurs a takeover fee and does not vary according to the amount of address space being transferred (e.g. if three allocations are being transferred from LIR A to LIR B, the fee is only paid once).

3.0 Closing an LIR

In the case of a closure of an LIR, the RIPE NCC should be contacted at least three months prior to the required closure date at [email protected] Link: mailto:[email protected] .

Only registered LIR contact person(s) can discuss a closure of an LIR with the RIPE NCC. In case of bankruptcy, the court-appointed administrator may take over these responsibilities.

To cease operations, an LIR is required to take the following four steps:

1. Send the RIPE NCC a written request to officially close the LIR. State the reasons for closure of the LIR and state the intention to return the unassigned address space.

2. Provide the RIPE NCC with documentation of all IP assignments made from address space allocated by the RIPE NCC.

3. Provide a list of any End Users that have expressed a need to keep their assigned IP address space and/or Autonomous System Number (ASN). Contact information such as e-mail addresses of these End Users should be included. (See section 3.7 Link: #3.7 )

4. Verify that the contents of the RIPE Database are up-to-date. A closing LIR is responsible for removing any objects entered by them in the RIPE Database that are no longer valid. Please send a confirmation to the RIPE NCC that all obsolete and invalid objects have been removed. (See section 3.8 Link: #3.8 )

3.1 Further Assignments

A closing LIR is not allowed to make any further assignments from its address space allocations.

3.2 Finance

An LIR will continue to be billed for services until a formal request to be closed is sent by a registered contact person(s) of the LIR.

In cases of mergers, the LIR whose allocation has been transferred to another LIR will continue to be billed until any inconsistencies are resolved.

3.3 Transfers of Address Allocations from a Closing LIR

If an LIR wishes to transfer its allocations to another existing LIR, it must provide the documentation about all assignments to the LIR receiving the transferred allocation. As outlined above, all transfers require approval by the RIPE NCC and all database objects must be valid and up-to-date.

3.4 Open Address Space Requests

As soon as the LIR decides to close, it should halt any open requests for IP address space and refer the End Users to the list of LIRs. This will prevent the customer from having to renumber at a later date. This list is available at:

http://www.ripe.net/lir/registries/indices/index.html Link: /membership/member-support/list-of-members/

3.5 End Users Keeping Address Assignments

A closing LIR should always encourage its End Users to renumber into an address allocation held by another LIR. This way, customer assignments can then be routed as part of the other LIR's allocation. Organisations in receipt of a Provider Aggregatable (PA) assignment should note that a new provider will not be able to announce an aggregate block. They may, therefore, have problems getting their addresses routed.

For more information, please see the

notes on Requesting Independent Resources Link: ../../../../../../../../../../../../../../../participate/resource-management/independent-resources .

The request for the transfer can be submitted as described above (Section 3.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 must be paid for the full year. This payment is the responsibility of the receiving member. If the receiving party is not a member, then payment is the responsibility of the transferring member.

If the receiving party 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 ).

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 assignment maintained by the party 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 must deregister

RIPE documents "Smallest RIPE NCC Allocation / Assignment Sizes" and "Provider Independent versus Provider Aggregatable Address Space" available 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 transferring 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 Document Store at:

http://www.ripe.net/ripe/docs/smallest-alloc-sizes.html

http://www.ripe.net/ripe/docs/pi-pa.html

The LIR should also supply the RIPE NCC with a list of Assignments kept by End Users in the following format:

Inetnum Range            Size  Date      Netname
 
 193.0.0.0 - 193.0.1.255  512   19950101  RIPE-NCC

3.6 Continued Internet Connectivity to End Users

The End Users can continue to use the address space already assigned to them by the closing LIR. The LIR will continue to provide Internet connectivity to its End Users as an Internet Service Provider (ISP). Assignments made by an LIR that has closed are valid for as long as the original criteria under which they were assigned remain valid. (See section 3.8 Link: #3.8 )

3.7 Discontinued Internet Connectivity to End Users

If the LIR will no longer provide Internet connectivity to End Users with assigned address space, this address space should be retrieved from the End Users by the LIR as they renumber. It is the LIR's responsibility to help its End Users with renumbering.

3.8 Database Responsibilities

LIRs are responsible for the accuracy of the data they enter into the RIPE Database. In the case of a closure of an LIR, the LIR should remove any objects in the RIPE Database that are no longer valid. This includes inetnum, aut-num and domain objects with obsolete information.

In cases where End Users of an LIR keep the address space assigned to them after the LIR closes, the LIR maintainer in the database objects representing these assignments needs to be removed and replaced by the RIPE NCC maintainer. The LIR should provide the RIPE NCC with a list of relevant database objects agreeing to the RIPE NCC overwriting the current LIR maintainer.

3.9 Unassigned Address Space

Unassigned address space will be returned to the RIPE NCC and will revert back to the public pool of IP address space. It can be assigned by the RIPE NCC as necessary. Should an LIR decide to close and reopen at a later date, it must repeat all formal steps required to establish a new LIR.

4.0 When an LIR is Closed by the RIPE NCC

The RIPE NCC may decide

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 Official Legal Name

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

The member must send a request for name change via the LIR Portal. The request 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 [email protected] Link: mailto:[email protected] and the above-mentioned documents must be uploaded via a secure link provided by the RIPE NCC.

that stops paying its bills to the RIPE NCC and/or cannot be contacted by the RIPE NCC for a significant period of time. Moreover, if an LIR consistently violates the policies established by the Internet Assigned Numbers Authority (IANA) or the RIPE community, in spite of multiple warnings, it may be closed.

The RIPE NCC will send a new RIPE NCC Standard Service Agreement Link: http://www.ripe.net/publications/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, it will update the registry, including all RIPE Database objects maintained by the RIPE NCC that are related to this change. The 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.

the LIR a message to notify it of its closure. The LIR must then provide documentation to the RIPE NCC regarding its allocated address space and follow the other procedures for closing an LIR as stated in section 3.0 Link: #3.0 .

If the LIR does not provide the RIPE NCC with the proper Documentation, the RIPE NCC will determine which address space should be returned to the public pool of IP address space.