You are here: Home > Publications > RIPE Document Store > Mergers, Acquisitions, Takeovers and Closures of Organisations Operating an LIR

Changes to Mergers, Acquisitions, Takeovers and Closures of Organisations Operating an LIR

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-515: Mergers, Acquisitions, Takeovers and Closures of Organisations Operating an LIR ripe-185: European Internet Registry Policies And Procedures
delete: <h2 class="western"> Abstract delete: </h2>

insert: <br />
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. delete: </p> delete: <p> _________________________________________________________________ delete: </p> delete: <h2 class="western"> Table of Contents delete: </h2> delete: <p> delete: </p> delete: <p> delete: <a class="anchor-link" href="#1.0"> 1.0 Introduction delete: </a> delete: </p> delete: <p> delete: <a class="anchor-link" href="#2.0"> 2.0 LIR Ownership Change delete: </a> delete: </p> delete: <p style="padding-left: 30px; "> delete: <a class="anchor-link" href="#2.1"> 2.1 IP Address Space delete: </a> delete: </p> delete: <p style="padding-left: 30px; "> delete: <a class="anchor-link" href="#2.2"> 2.2 Service Agreement delete: </a> delete: </p> delete: <p style="padding-left: 30px; "> delete: <a class="anchor-link" href="#2.3"> 2.3 Change in Operating Organisation delete: </a> delete: </p> delete: <p style="padding-left: 30px; "> delete: <a class="anchor-link" href="#2.4"> 2.4 Contact Person(s) delete: </a> delete: </p> delete: <p style="padding-left: 30px; "> delete: <a class="anchor-link" href="#2.5"> 2.5 RegID delete: </a> delete: </p> delete: <p style="padding-left: 30px; "> delete: <a class="anchor-link" href="#2.6"> 2.6 Transfers of Address Allocations delete: </a> delete: </p> delete: <p style="padding-left: 30px; "> delete: <a class="anchor-link" href="#2.7"> 2.7 Takeover fee delete: </a> delete: </p> delete: <p> delete: <a class="anchor-link" href="#3.0"> 3.0 Closing an LIR delete: </a> delete: </p> delete: <p> This section is replaced by the RIPE NCC organisational document " delete: <a href="https://www.ripe.net/publications/docs/closure"> Closure of LIR and Deregistration of Internet Number Resources delete: </a> ". delete: </p> delete: <p> delete: <a class="anchor-link" href="#4.0"> 4.0 When an LIR is Closed by the RIPE NCC delete: </a> delete: </p> delete: <p> This section is replaced by the RIPE NCC organisational document " delete: <a href="https://www.ripe.net/publications/docs/closure"> Closure of LIR and Deregistration of Internet Number Resources delete: </a> ". delete: </p> delete: <h2 class="western"> delete: <a name="1.0"> delete: </a> 1.0 Introduction delete: </h2> delete: <p> 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. delete: </p> delete: <h2 class="western"> delete: <a name="2.0"> delete: </a> 2.0 LIR Ownership Change delete: </h2> delete: <p> In the case of an LIR ownership change, the LIR should contact the RIPE NCC at delete: <a href="mailto:[email protected]"> [email protected] delete: </a> . delete: </p> delete: <p> Only registered LIR contact person(s) can discuss the change of an LIR ownership with the RIPE NCC. delete: </p> delete: <p> The following steps are required to change the organisation operating an LIR: delete: </p> delete: <p> delete: </p> delete: <p> 1. Clarify the type of change: delete: </p> delete: <ul> delete: <li> delete: <p> A takeover of one LIR by another LIR, closing one of the LIRs. delete: </p> delete: </li> delete: <li> delete: <p> A takeover of one LIR by another LIR, both remain open. delete: </p> delete: </li> delete: <li> delete: <p> A takeover of an LIR by a non-LIR. delete: </p> delete: </li> delete: </ul> delete: <p> delete: </p> delete: <p> 2. Outline the details of the change, stating: delete: </p> delete: <ul> delete: <li> delete: <p> The reason for the change of organisation. delete: </p> delete: </li> delete: <li> delete: <p> The name of the company/companies involved. delete: </p> delete: </li> delete: <li> delete: <p> The number of LIRs affected by the change. delete: </p> delete: </li> delete: <li> delete: <p> The RegID(s) of the LIR(s) affected by the change. delete: </p> delete: </li> delete: </ul> delete: <p> delete: </p> delete: <p> 3. Present the following documents to the RIPE NCC: delete: </p> delete: <ul> delete: <li> delete: <p> Confirmation from all parties agreeing to the change (See section 2.3). delete: </p> delete: </li> delete: <li> delete: <p> Updated list of contact person(s) (See section 2.4). delete: </p> delete: </li> delete: <li> delete: <p> Updated billing e-mail contact details, including any changes to VAT number. delete: </p> delete: </li> delete: <li> delete: <p> A new service agreement, if applicable (See section 2.2). delete: </p> delete: </li> delete: <li> delete: <p> Legal documentation supporting the name change, if applicable (See section 2.2). delete: </p> delete: </li> delete: <li> delete: <p> Overview of utilisation in all allocations (See section 2.6). delete: </p> delete: </li> delete: </ul> delete: <h3 class="western"> delete: <a name="2.1"> delete: </a> 2.1 IP Address Space delete: </h3> delete: <p> 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. delete: </p> delete: <h3 class="western"> delete: <a name="2.2"> delete: </a> 2.2 Service Agreement delete: </h3> delete: <p> 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: delete: </p> delete: <ul> delete: <li> delete: <p> The organisation operating the LIR changes name, or delete: </p> delete: </li> delete: <li> delete: <p> The LIR wishes to change their RegID. delete: </p> delete: </li> delete: </ul> delete: <p> The registration documentation from the relevant Chamber of Commerce, or its country equivalent, supporting the name change must be submitted to the RIPE NCC. delete: </p> delete: <p> The Standard RIPE NCC Service Agreement Document is available from the RIPE Document Store at: delete: <a href="http://www.ripe.net/ripe/docs/service-agreement"> http://www.ripe.net/ripe/docs/service-agreement delete: </a> in a ASCII and PDF

delete: <p> delete: </p> delete: <p> 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. delete: </p> delete: <h3 class="western"> delete: <a name="2.3"> delete: </a> 2.3 Change in Operating Organisation delete: </h3> delete: <p> 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. delete: </p> delete: <h3 class="western"> delete: <a name="2.4"> delete: </a> 2.4 Contact Person(s) delete: </h3> delete: <p> 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. delete: </p> delete: <p> delete: </p> delete: <p> 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. delete: </p> delete: <p> delete: </p> delete: <p> 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 delete: </p> delete: <p> changes. These changes should include the new registered contact person(s) for the LIR. delete: </p> delete: <h3 class="western"> delete: <a name="2.5"> delete: </a> 2.5 RegID delete: </h3> delete: <p> 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. delete: </p> delete: <p> delete: </p> delete: <p> 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: delete: <a href="http://www.ripe.net/ripe/docs/charging"> http://www.ripe.net/ripe/docs/charging delete: </a> delete: </p> delete: <h3 class="western"> delete: <a name="2.6"> delete: </a> 2.6 Transfers of Address Allocations delete: </h3> delete: <p> 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: delete: </p> delete: <p> delete: <a href="http://www.ripe.net/ripe/docs/ipv4-policies"> http://www.ripe.net/ripe/docs/ipv4-policies delete: </a> delete: </p> delete: <h3 class="western"> delete: <a name="2.7"> delete: </a> 2.7 Takeover Fee delete: </h3> delete: <p> 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. delete: </p> delete: <p> delete: </p> delete: <p> 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). delete: </p> delete: <h2 class="western"> delete: <a name="3.0"> delete: </a> 3.0 Closing an LIR delete: </h2> delete: <p> 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: delete: <a href="http://www.ripe.net/ripe/docs/closure"> http://www.ripe.net/ripe/docs/closure delete: </a> . delete: </p> delete: <h2 class="western"> delete: <a name="4.0"> delete: </a> 4.0 When an LIR is Closed by the RIPE NCC delete: </h2> delete: <p> 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: delete: <a href="http://www.ripe.net/ripe/docs/closure"> http://www.ripe.net/ripe/docs/closure delete: </a> . delete: </p>
Mergers, Acquisitions, Takeovers and Closures of Organisations Operating an LIR European Internet Registry Policies And Procedures