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 ripe-595: Transfer of Internet Number Resource Records and Closures Change of Organisations Operating an LIR a Member’s Official Legal Name
delete: <h2 class="western"> Abstract insert: <h2>

Contents

insert: <p>

insert: <a class="anchor-link" href="#definitions" target="_self" title=""> 1.0 Definitions insert: </a> insert: </p>

insert: <p>

insert: <a class="anchor-link" href="#introduction" target="_self" title=""> 2.0 Introduction insert: </a> insert: </p>

insert: <p>

insert: <a class="anchor-link" href="#transfer" target="_self" title=""> 3.0 Transfer of Internet Number Resource Records insert: </a> insert: </p>

insert: <p style="padding-left: 30px; ">

insert: <a class="anchor-link" href="#submission" target="_self" title=""> 3.1 Submission of the Request for Transfer insert: </a> insert: </p>

insert: <p style="padding-left: 30px; ">

insert: <a class="anchor-link" href="#receiving-organisation" target="_self" title=""> 3.2 If the Receiving Organisation is not yet a Member insert: </a> insert: </p>

insert: <p style="padding-left: 30px; ">

insert: <a class="anchor-link" href="#financial" target="_self" title=""> 3.3 Financial Consequences insert: </a> insert: </p>

insert: <p style="padding-left: 30px; ">

insert: <a class="anchor-link" href="#internet-number-resource-reg" target="_self" title=""> 3.4 Internet Number Resource Registration and RIPE Database Issues insert: </a> insert: </p>

insert: <p>

insert: <a class="anchor-link" href="#official-legal-name" target="_self" title=""> 4.0 The Member Changes its Official Legal Name insert: </a> insert: </p>

insert: <p>

insert: </p>

insert: <h3>

insert: <a name="definitions"> insert: </a> 1.0 Definitions insert: </h3>

insert: <p>

For the purposes of this document Internet Number Resource records refer to: insert: </p>

insert: <ul>
    insert: <li>
  • The registered allocations and assignments of a Member insert: </li>
  • insert: <li>
  • The independent Internet number resources insert: <b> insert: </b> assigned through the Member as a “sponsoring LIR” to an End User insert: </li>
  • insert: </ul>
insert: <h3>

insert: <a name="introduction"> insert: </a> 2.0 Introduction insert: </h3>

insert: <p>

In order for the RIPE NCC to maintain an accurate registry, it must hold accurate data concerning: insert: </p>

insert: <ul>
    insert: <li>
  • The natural or legal persons holding the registration of Internet Number Resources insert: </li>
  • insert: <li>
  • The Internet Number Resource records that are registered to the natural and legal persons insert: </li>
  • insert: </ul>
insert: <p>

This means that any transfer of Internet Number Resources from one party to another, or any change to the legal status of a party holding the registration of Internet Number Resources, must be communicated to the RIPE NCC. insert: </p>

insert: <p>

insert: </p>

insert: <p>

The Member must inform the RIPE NCC if insert: <i> one or both insert: </i> of the following changes occurs: insert: </p>

insert: <ol>
    insert: <li>
  1. Internet Number Resource records are transferred. Such transfers may take place: insert: <ul>
      insert: <li>
    • Because of a change in the business structure of the Member, for example in the case of a merger or acquisition of the Member's organisation; or insert: </li>
    • insert: <li>
    • In the case of a pure transfer of an allocation from a Member to another Member according to RIPE Policies ( insert: <a title="" href="https://www.ripe.net/publications/docs/ipv4-policies#55" class="external-link" target="_self"> Section 5.5, IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region insert: </a> ). Such a transfer may also be facilitated through the insert: <a data-linktype="internal" target="_self" title="" href="resolveuid/8768823a7d79496c8bff938729212474" data-val="8768823a7d79496c8bff938729212474" class="internal-link"> RIPE NCC Listing Service. insert: </a> insert: </li>
    • insert: </ul>
    insert: </li>
  2. insert: <li>
  3. The Member changes its official legal name insert: <b> . insert: </b> Such a change may occur, for example, because of a merger or acquisition of the Member's organisation. insert: </li>
  4. insert: </ol>
insert: <p>

insert: </p>

This document provides guidelines to Local Internet Registries (LIRs) on the steps to take when the organisation operating describes the procedures to be followed for such changes to be properly communicated to, and registered with, the RIPE NCC. insert: </p>

insert: <p>

insert: </p>

insert: <p>

insert: <b> Note: insert: </b> insert: </p>

insert: <p>

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. insert: </p>

insert: <p>

If a change in the Member's business structure is insert: <i> not insert: </i> 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. insert: </p>

insert: <h3>

insert: <a name="transfer"> insert: </a> 3.0 Transfer of Internet Number Resource Records insert: </h3>

insert: <p>

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. insert: </p>

insert: <p>

insert: </p>

insert: <p>

insert: <b> insert: <a name="submission"> insert: </a> 3.1 Submission of the Request for Transfer insert: </b> insert: </p>

insert: <p>

One of the involved parties must submit a request by email to the RIPE NCC for the transfer to be executed: insert: </p>

insert: <ul> insert: <p>

A registered contact or 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 authorised person (e.g., senior manager, legal successor) must send the request. insert: </p>

insert: <p>

insert: </p>

insert: <p>

The RIPE NCC will ask for the following information: insert: </p>

insert: <p>

insert: <b> i. Information regarding the parties involved, including: insert: </b> insert: </p>

insert: <ul>
    insert: <li>
  • The full official legal names of all parties involved insert: </li>
  • insert: <li>
  • Which party will transfer the Internet Number Resource records and which party will receive them insert: </li>
  • insert: <li>
  • Recent registration papers issued by the relevant national authorities for all involved parties insert: </li>
  • insert: </ul>
insert: <p>

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 insert: <a class="anchor-link" href="#official-legal-name" target="_self" title=""> Section 4.0 insert: </a> 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 delete: </a> delete: </p> delete: <p style="padding-left: 30px; "> delete: <a class="anchor-link" href="#2.3"> 2.3 Change of the transferring Member is terminated (see Closure of LIR and Deregistration of Internet Number Resources, insert: <a href="https://www.ripe.net/publications/docs/closure#11"> Section A.1.1. insert: </a> and insert: <a href="https://www.ripe.net/publications/docs/closure#12"> Section A.1.2. insert: </a> ). insert: </p>

insert: <p>

insert: </p>

insert: <p>

insert: <b> ii. A description of the reason for the transfer (for example, due to merger, acquisition, transfer of allocation according to the RIPE policies) insert: </b> insert: </p>

insert: <p>

If the transfer is taking place due to a change in Operating 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. insert: </p>

insert: <p>

insert: </p>

insert: <p>

insert: <b> iii. A list of the Internet Number Resource records that are requested to be transferred. If insert: <i> all insert: </i> of the transferring Member's Internet Number Resource records registered are being transferred, a confirmation of this is requested. insert: </b> insert: </p>

insert: <p>

The Member must also indicate any End User assignment agreements that are requested to be transferred. insert: </p>

insert: <p>

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, insert: <a href="https://www.ripe.net/publications/docs/closure#11"> Section A.1.1. insert: </a> ). insert: </p>

insert: <p>

insert: </p>

insert: <p>

insert: <b> iv. The correct contact details of all organisations involved insert: </b> insert: </p>

insert: <p>

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. insert: </p>

insert: <p>

insert: </p>

insert: <p>

insert: <b> v. A Transfer Agreement signed by both parties or by their legal successors insert: </b> insert: </p>

insert: <p>

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). insert: </p>

insert: <p>

insert: </p>

insert: <p>

If the transferring party no longer exists by the time the RIPE NCC is being informed, the receiving party must send: insert: </p>

insert: <ul>
    insert: <li>
  • an official document (issued by a national authority) confirming the closure of the transferring party; and insert: </li>
  • insert: <li>
  • a copy of an older signed agreement between the relevant parties mentioning the transfer of the Internet Number Resource records. If such an agreement is not available, the receiving party must send confirmation of the transfer to the RIPE NCC signed by an authorised person (e.g., senior manager, legal 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 records should have been transferred to them. insert: </li>
  • insert: </ul>
insert: <p>

insert: </p>

insert: <p>

insert: <b> vi. An overview of the utilisation of all allocations and of the status of all independent Internet Number Resource assignments insert: </b> insert: </p>

insert: <p>

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. insert: </p>

insert: <p>

insert: </p>

insert: <p>

insert: <b> insert: <a name="receiving-organisation"> insert: </a> 3.2 If the Receiving 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 not yet a Member insert: </b> insert: </p>

insert: <p>

Members may wish to transfer their Internet Number Resource records to another Member or to an organisation or company operating an LIR changes ownership status or stops serving that is not yet a Member. insert: </p>

insert: <p>

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 ( insert: <a href="https://www.ripe.net/lir-services/member-support/become-a-member"> more information on how to become a Member is available insert: </a> ). insert: </p>

insert: <p>

If the receiving organisation refuses to do the above, the RIPE NCC will not transfer the Internet Number Resource records to them. insert: </p>

insert: <p>

The request for the transfer can be submitted as an LIR there are financial, IP address space described above (Section 1). insert: </p>

insert: <p>

insert: </p>

insert: <p>

insert: <b> insert: <a name="financial"> insert: </a> 3.3 Financial Consequences insert: </b> insert: </p>

insert: <p>

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. The payment is the responsibility of the receiving Member. insert: </p>

insert: <p>

If the receiving organisation decides to sign the RIPE NCC Standard Service Agreement, then a sign-up fee must be paid (see insert: <a href="http://www.ripe.net/ripe/docs/ripe-499"> RIPE NCC Charging Scheme insert: </a> ). insert: </p>

insert: <p>

insert: </p>

insert: <p>

insert: <b> insert: <a name="db-issues"> insert: </a> insert: <a name="internet-number-resource-reg"> insert: </a> 3.4 Internet Number Resource Registration 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 Issues insert: </b> insert: </p>

insert: <p>

The RIPE NCC will review the status of any IP address allocations 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. insert: </p>

insert: <p>

The receiving Member must deregister from the RIPE Database any invalid or overlapping registrations or unused assignment approvals. insert: </p>

insert: <p>

The RIPE NCC will update the registry, including all RIPE Database objects maintained by the RIPE NCC that are held by the related to this transfer. The transferring Member must update all RIPE Database objects maintained by them that are related to this transfer. insert: </p>

insert: <h3>

insert: <a name="official-legal-name"> insert: </a> 4.0 The Member Changes its Official Legal Name insert: <b> insert: </b> insert: </h3>

insert: <p>

It is the obligation of the Member to inform the RIPE NCC immediately if any change in the Member's official legal name occurs. insert: </p>

insert: <p>

The Member must send an email to insert: <a class="email-link" href="mailto:[email protected]" target="_self" title=""> informing the RIPE NCC of the name change. This email must include: insert: </p>

insert: <ul>
    insert: <li>
  • New registration papers from the national authority; and insert: </li>
  • insert: <li>
  • The official legal documents supporting this change insert: </li>
  • insert: </ul>
insert: <p>

insert: </p>

insert: <p>

The RIPE NCC will send a new organisation. delete: </p> delete: <h3 class="western"> delete: <a name="2.2"> delete: </a> 2.2 insert: <a class="external-link" href="http://www.ripe.net/ripe/docs/service-agreement" target="_self" title=""> RIPE NCC Standard Service Agreement delete: </h3> delete: <p> insert: </a> for the Member to sign under the new official legal name. When an organisation operating an LIR changes ownership, a the RIPE NCC receives the 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 RIPE NCC Standard RIPE NCC Service Agreement 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> delete: </p> 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 properly signed by the Member, it will update the registry, including 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 RIPE Database objects maintained by the RIPE NCC that 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 related to this change. The Member must update all RIPE Database objects maintained by them 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 are related 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> change. insert: </p>

Mergers, Acquisitions, Takeovers Transfer of Internet Number Resource Records and Closures Change of Organisations Operating an LIR a Member’s Official Legal Name