< This document provides guidelines to Local Internet Registries (LIRs) on the steps to take when the organisation operating an LIR changes ownership (due to a merger, sale or takeover) or stops serving entirely as an LIR. _________________________________________________________________ 2.0 LIR Ownership Change Link: #2.0 2.1 IP Address Space Link: #2.1 2.2 Service Agreement Link: #2.2 2.3 Change in Operating Organisation Link: #2.3 2.4 Contact Person(s) Link: #2.4 Link: closure ". When an organisation or company operating an LIR changes ownership status or stops serving as an LIR there are financial, IP address space and RIPE Database issues that need resolving. Therefore, the RIPE NCC must always be contacted when an LIR changes ownership or closes. In the case of an LIR ownership change, the LIR should contact the RIPE NCC at [email protected] Link: mailto:[email protected] . Only registered LIR contact person(s) can discuss the change of an LIR ownership with the RIPE NCC. The following steps are required to change the organisation operating an LIR: 1. Clarify the type of change: A takeover of one LIR by another LIR, closing one of the LIRs. A takeover of one LIR by another LIR, both remain open. A takeover of an LIR by a non-LIR. 2. Outline the details of the change, stating: The reason for the change of organisation. The name of the company/companies involved. The number of LIRs affected by the change. The RegID(s) of the LIR(s) affected by the change. 3. Present the following documents to the RIPE NCC: Confirmation from all parties agreeing to the change (See section 2.3). Updated list of contact person(s) (See section 2.4). Updated billing e-mail contact details, including any changes to VAT number. A new service agreement, if applicable (See section 2.2). Legal documentation supporting the name change, if applicable (See section 2.2). Overview of utilisation in all allocations (See section 2.6). Following any type of change (such as mergers, acquisitions or takeovers) of an organisation operating an LIR, the RIPE NCC will review the status of any IP address allocations that are held by the new organisation. When an organisation operating an LIR changes ownership, a new service agreement may need to be signed. The RIPE NCC will need to request a new service agreement from the new owners if: The organisation operating the LIR changes name, or The LIR wishes to change their RegID. The registration documentation from the relevant Chamber of Commerce, or its country equivalent, supporting the name change must be submitted to the RIPE NCC. The Standard RIPE NCC Service Agreement is available from the RIPE Document Store at: http://www.ripe.net/ripe/docs/service-agreement Link: http://www.ripe.net/ripe/docs/service-agreement If the organisation operating the LIR does not change its name and keeps the original RegID, the LIR can continue operating under the same service agreement. In cases where an organisation operating an LIR takes over one or more LIRs, confirmation of the takeover from all parties involved or their legal successors must be included. 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. 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 Link: http://www.ripe.net/ripe/docs/charging Abstract
Table of Contents
Contents 1.0 Definitions Link: #definitions 2.0 Introduction Link: #introduction 3.0 Transfer of Internet Number Resource Records Link: #transfer 3.1 Submission of the Request for Transfer Link: #submission 3.2 If the Receiving Organisation is not yet a Member Link: #receiving-organisation 3.3 Financial Consequences Link: #financial 4.0 The Member Changes its Official Legal Name Link: #official-legal-name 1.0 Definitions For the purposes of this document Internet Number Resource records refer to: The registered allocations and assignments of a Member The independent Internet number resourcesassigned through the Member as a “sponsoring LIR” to an End User 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 Resources The Internet Number Resource records that are registered to the natural and legal persons This means that any transfer of Internet Number Resources1.0 Introduction
2.0 LIR Ownership Change
2.1 IP Address Space
2.2 Service Agreement
2.3 Change in Operating Organisation
2.4 Contact Person(s)
2.5 RegID
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
The Member must inform the RIPE NCC if one or both of the following changes occurs:
in the RIPE NCC Service Region" available from the RIPE Document Store at:
http://www.ripe.net/ripe/docs/ipv4-policies Link: http://www.ripe.net/ripe/docs/ipv4-policies
This document describes the procedures to be followed for such changes to be properly communicated to, and registered with, the RIPE NCC.
Note:
If a change in the Member's official legal name is accompanied by a transfer of Internet Number Resource records, the Member must first inform the RIPE NCC of the name change and then of the transfer.
If a change in the Member's business structure is not accompanied by a transfer of Internet Number Resource records or a change in the Member's official legal name, then the RIPE NCC does not need to be informed of this change.
If a Member transfers their Internet Number Resource records to a third party for any reason, this transfer must be declared to, and approved by, the RIPE NCC.
3.1 Submission of the Request for Transfer
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) must send the request.
The RIPE NCC will ask for the following information:
i. Information regarding the parties involved, including:
If the current official legal names of the involved Members are different from the ones in the relevant signed RIPE NCC Standard Service Agreement, then 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 if the RIPE NCC Standard Service Agreement of the transferring Member is terminated (see 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 allocation according to the RIPE policies)
If the transfer is taking place due to a change in the structure of the organisation(s) involved, a description of the changes among the organisation(s) is necessary. The description must be accompanied by all official legal documents proving/supporting the changes the request is based on.
iii. A list of the Internet Number Resource records that are requested to be transferred. If all of the transferring Member's Internet Number Resource records registered are being transferred, a confirmation of this is requested.
The Member must also indicate any End User assignment agreements that are requested to be transferred.
If a Member transfers all of their Internet Number Resource records, the RIPE NCC Standard Service Agreement of the Member may be terminated (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 organisations involved
The RIPE NCC may ask the 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 will make a template of the Transfer Agreement available. Either party may submit the Transfer Agreement to the RIPE NCC, signed by authorised persons for both parties. 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 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:
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 Organisation is not yet a Member
Members may wish to transfer their Internet Number Resource records to another Member or to an organisation that is not yet a Member.
If the Internet Number Resource records are transferred to a non-Member, the receiving organisation must apply to be 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: https://www.ripe.net/lir-services/member-support/become-a-member ).
If the receiving organisation refuses to do the above, the RIPE NCC will not transfer the Internet Number Resource records to them.
The request for the transfer can be submitted as described above (Section 1).
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).
This section is replaced by the RIPE NCC organisational document "Closure of LIR and Deregistration of Internet Number Resources" available from the RIPE Document Store at: http://www.ripe.net/ripe/docs/closure Link: http://www.ripe.net/ripe/docs/closure .
If the receiving 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/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 assignment maintained by the organisations involved, in compliance with the RIPE Policies current at the time of the transfer.
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.
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 an email to ncc [at] ripe [dot] net Link: mailto:[email protected] informing the RIPE NCC of the name change. This email must include:
The RIPE NCC will send a new RIPE NCC Standard Service Agreement 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, 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.