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-301: This document provides guidelines to Local ripe-065: RIPE NCC 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. Numbers Registration Procedures
delete: <h2> Abstract delete: </h2> insert: <p>

insert: <b> This document is obsoleted by ripe-72, version 0.7 of this documen insert: </b> t insert: </p>

This document provides guidelines to Local Internet Registries (LIRs) describes the procedures for the reassignment of IP insert: <br />
network numbers from blocks obtained from the RIPE Network Coordination insert: <br />
Centre. It deals with items as providing information for the RIPE and insert: <br />
US NIC databases, as well as reassignment of IP addresses in light of insert: <br />
the "Supernetting" proposal, as documented in RFC 1338, by Vince Fuller insert: <br />
et al. insert: <br />
insert: <br />
insert: <br />
Introduction insert: <br />
insert: <br />
Since May 1st 1992, the RIPE Network Coordination Centre (NCC) is insert: <br />
acting as a delegated registry for IP networks numbers to NICs and NOCs insert: <br />
in Europe. It is RIPE NCC policy not to give out network numbers to insert: <br />
individual organisations, who should refer in turn, to their IP network insert: <br />
service provider. insert: <br />
insert: <br />
The mission of the RIPE NCC is to give network numbers to the various insert: <br />
service providers and NICs. The NICs and NOCs can then reassign the insert: <br />
actual IP network numbers to organisations requesting IP network insert: <br />
numbers. insert: <br />
insert: <br />
insert: <br />
Class B Network Number Allocation Procedure insert: <br />
insert: <br />
Service providers can request Class B network numbers 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: <hr noshade="noshade" size="1" /> delete: <p> delete: <a href="#1.0"> 1.0 Introduction delete: </a> delete: <br /> delete: <a href="#2.0"> 2.0 LIR Ownership Change delete: </a> delete: </p> delete: <div class="indent"> delete: <p> delete: <a href="#2.1"> 2.1 IP Address Space delete: </a> delete: <br /> delete: <a href="#2.2"> 2.2 Service Agreement delete: </a> delete: <br /> delete: <a href="#2.3"> 2.3 Change in Operating Organisation delete: </a> delete: <br /> delete: <a href="#2.4"> 2.4 Contact Person(s) delete: </a> delete: <br /> delete: <a href="#2.5"> 2.5 RegID delete: </a> delete: <br /> delete: <a href="#2.6"> 2.6 Transfers of Address Allocations delete: </a> delete: <br /> delete: <a href="#2.7"> 2.7 Takeover Fee delete: </a> delete: </p> delete: </div> delete: <p> delete: <a href="#3.0"> 3.0 Closing an LIR delete: </a> delete: </p> delete: <div class="indent"> delete: <a href="#3.1"> 3.1 Further Assignments delete: </a> delete: <br /> delete: <a href="#3.2"> 3.2 Finance delete: </a> delete: <br /> delete: <a href="#3.3"> 3.3 Transfers of Address Allocations a one-by-one insert: <br />
basis from a Closing LIR delete: </a> delete: <br /> delete: <a href="#3.4"> 3.4 Open Address Space Requests delete: </a> delete: <br /> delete: <a href="#3.5"> 3.5 End Users Keeping Address Assignments delete: </a> delete: <br /> delete: <a href="#3.6"> 3.6 Continued Internet Connectivity to End Users delete: </a> delete: <br /> delete: <a href="#3.7"> 3.7 Discontinued Internet Connectivity to End Users delete: </a> delete: <br /> delete: <a href="#3.8"> 3.8 Database Responsibilities delete: </a> delete: <br /> delete: <a href="#3.9"> 3.9 Unassigned Address Space delete: </a> delete: </div> delete: <p> delete: <a href="#4.0"> 4.0 When an LIR is Closed by the RIPE NCC delete: </a> delete: </p> delete: <p> delete: </p> delete: <hr noshade="noshade" size="1" /> delete: <h2> 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 the RIPE NCC. Because class B address space and RIPE Database issues that need resolving. Therefore, the RIPE NCC is a critical insert: <br />
resource, a request for a class B network number must always be contacted when an LIR changes ownership or closes. delete: </p> delete: <h2> delete: <a id="2.0" 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:lir-help@ripe.net"> lir-help@ripe.net 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> 1. Clarify the type of change: delete: </p> delete: <ul> delete: <li> A takeover of one LIR be accompanied by another LIR, closing one of the LIRs. delete: </li> delete: <li> A takeover of one LIR by another LIR, both remain open. delete: </li> delete: <li> A takeover of an LIR by a non-LIR. delete: </li> delete: </ul> delete: <p> 2. Outline the details of the change, stating: delete: </p> delete: <ul> delete: <li> The reason for the change of organisation. delete: </li> delete: <li> The name of the company/companies involved. delete: </li> delete: <li> The number of LIRs affected by the change. delete: </li> delete: <li> The RegID(s) of the LIR(s) affected by the change. delete: </li> delete: </ul> delete: <p> 3. Present the following documents to the RIPE NCC: delete: </p> delete: <ul> delete: <li> Confirmation from all parties agreeing to the change (See section delete: <a href="#2.3"> 2.3 delete: </a> ). delete: </li> delete: <li> Updated list of contact person(s) (See section delete: <a href="#2.4"> 2.4 delete: </a> ). delete: </li> delete: <li> Updated billing e-mail contact details, including any changes to VAT number. delete: </li> delete: <li> A new service agreement, if applicable (See section delete: <a href="#2.2"> 2.2 delete: </a> ). delete: </li> delete: <li> Legal documentation supporting the name change, if applicable (See section delete: <a href="#2.2"> 2.2 delete: </a> ). delete: </li> delete: <li> Overview of utilisation in all allocations (See section delete: <a href="#2.6"> 2.6 delete: </a> ). delete: </li> delete: </ul> delete: <h3> delete: <a id="2.1" 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 insert: <br />
a justification in terms of the requesting organisation's size, current insert: <br />
network and expected network growth. The requestor should also make insert: <br />
clear why they cannot use a block of class C network numbers to achieve insert: <br />
their goals. The RIPE NCC will review the status of requests using the same standards insert: <br />
as any other Internet Registry, particularly the US NIC. insert: <br />
insert: <br />
insert: <br />
Class C Allocation Procedures insert: <br />
insert: <br />
insert: <br />
NICs and NOCs accepting a block of class C numbers agree to adhere to insert: <br />
the following procedures: insert: <br />
insert: <br />
A) The RIPE NCC will assign complete class C blocks to individual NICs insert: <br />
and NOCs. They can be requested from <hostmaster@ripe.net>. insert: <br />
insert: <br />
B) In order to prevent implementation problems, network numbers ending insert: <br />
with 0 or 255 should NOT be reassigned. insert: <br />
insert: <br />
C) Full information about reassigned network numbers must be reported insert: <br />
back to the RIPE NCC and the US NIC in full RIPE database format (ref insert: <br />
ripe-13). The complete entries should be sent immediately after insert: <br />
reassignment to <ripe-dbm@ripe.net> and <hostmaster@nic.ddn.mil> insert: <br />
Unfortunately, the RIPE NCC is not yet ready to accept block entries for insert: <br />
the RIPE database, so you must send in each individual entry. insert: <br />
insert: <br />
D) Reassignment of class C network numbers should be done in a manner insert: <br />
that facilitates Supernetting (see next section). insert: <br />
insert: <br />
E) Requests for network numbers should be reasonable. All NICs and NOCs insert: <br />
should prevent stockpiling of network numbers. insert: <br />
insert: <br />
F) On first request from the RIPE NCC, the class C network numbers not insert: <br />
yet reassigned, must be returned to the RIPE NCC. insert: <br />
insert: <br />
insert: <br />
Supernetting insert: <br />
insert: <br />
NICs and NOCs reassigning IP address allocations network numbers are urgently requested to insert: <br />
read the Supernetting proposal by Vince Fuller et al. This document can insert: <br />
be obtained from the rfc section of the RIPE document store or other RFC insert: <br />
servers. It is called rfc1338.txt. insert: <br />
The Supernetting proposal was made to reduce the increase of routing insert: <br />
table size in the current Internet. It proposes to create a hierarchy insert: <br />
of IP network numbers, which can then be aggregated resulting in less insert: <br />
routing table entries in routing equipment. While this proposal has not insert: <br />
been formally adopted we expect that are held by the new organisation. delete: </p> delete: <h3> delete: <a id="2.2" name="2.2"> delete: </a> 2.2 Service Agreement delete: </h3> delete: <p> When something at least along the same insert: <br />
principle will be implemented in the near future. insert: <br />
insert: <br />
Here is how it works: insert: <br />
insert: <br />
If 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 A needs 8 class C network numbers, the numbers should insert: <br />
be given out in such a way that the routing information for each of insert: <br />
these 8 networks could appear as one entry with the correct mask in insert: <br />
routers. insert: <br />
insert: <br />
More concretely: insert: <br />
insert: <br />
Service provider S hands out networks 192.24.8 through 192.24.15 to insert: <br />
organisation A. These networks can then appear in routing equipment as a insert: <br />
supernet route to 192.24.8 with mask 255.255.248.0. This way 8 class C insert: <br />
network numbers appear as one routing table entry. insert: <br />
insert: <br />
The guidelines that can be derived from the new owners if: delete: </p> delete: <ul> delete: <li> The organisation operating the LIR changes name, or delete: </li> delete: <li> The LIR wishes to change Supernetting proposal are: insert: <br />
insert: <br />
A) Service providers should reserve blocks of class C network numbers from insert: <br />
their RegID. 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 is available from the RIPE Document Store at: delete: <br /> delete: <br /> delete: <a title="" href="https://www.ripe.net/ripe/docs/service-agreement.html" class="external-link" target="_self"> http://www.ripe.net/ripe/docs/service-agreement.html delete: </a> 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> delete: <a id="2.3" name="2.3"> delete: </a> 2.3 Change in Operating Organisation delete: </h3> delete: <p> In cases where allocation for each organisations requesting class C network numbers. insert: <br />
insert: <br />
B) The size of these blocks should always be a power of 2. insert: <br />
insert: <br />
C) The numbers in these blocks should be contiguous. insert: <br />
insert: <br />
D) The blocks should start on bit boundaries. insert: <br />
(ie powers of 2, AND multiples of the block size) insert: <br />
insert: <br />
E) The blocks reserved for an organisation operating an LIR takes should be sufficient for a insert: <br />
reasonable expected growth over one or more LIRs, confirmation of the takeover from all parties involved or their legal successors must be included. delete: </p> delete: <h3> delete: <a id="2.4" 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: <br /> delete: <br /> If the contact person(s) of the affected LIR has changed, the RIPE NCC the next few years. insert: <br />
insert: <br />
F) Multi-homed organizations 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: <br /> delete: <br /> 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. delete: </p> delete: <h3> delete: <a id="2.5" 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> 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: <br /> delete: <br /> delete: <a class="external-link" href="http://www.ripe.net/ripe/docs/charging.html" target="_self" title=""> http://www.ripe.net/ripe/docs/charging.html delete: </a> delete: </p> delete: <h3> delete: <a id="2.6" name="2.6"> delete: </a> 2.6 Transfers of Address Allocations delete: </h3> delete: <p> All transfers of address allocations space from one LIR to another LIR (or to a non-LIR) require approval by the RIPE NCC. It of their insert: <br />
providers, the RIPE NCC, or the global NIC, as 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 appropriate to their insert: <br />
network configuration. These organisations are strongly encouraged to insert: <br />
contact 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, for guidance. insert: <br />
insert: <br />
If you have any questions concerning this, 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: <br /> delete: <br /> delete: <a class="external-link" href="http://www.ripe.net/ripe/docs/ipv4-policies.html" target="_self" title=""> http://www.ripe.net/ripe/docs/ipv4-policies.html delete: </a> do not hesitate to insert: <br />
call or mail us at ncc@ripe.net.

delete: <h3> delete: <a id="2.7" 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> 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> delete: <a id="3.0" name="3.0"> delete: </a> 3.0 Closing an LIR delete: </h2> delete: <p> 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 delete: <a href="mailto:lir-help@ripe.net"> lir-help@ripe.net delete: </a> . delete: <br /> delete: <br /> 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. delete: <br /> delete: <br /> To cease operations, an LIR is required to take the following four steps: delete: <br /> delete: <br /> 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. delete: <br /> delete: <br /> 2. Provide the RIPE NCC with documentation of all IP assignments made from address space allocated by the RIPE NCC. delete: </p> delete: <p> 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 delete: <a href="#3.7"> 3.7 delete: </a> ) delete: <br /> delete: <br /> 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 delete: <a href="#3.8"> 3.8 delete: </a> ) delete: </p> delete: <h3> delete: <a id="3.1" name="3.1"> delete: </a> 3.1 Further Assignments delete: </h3> delete: <p> A closing LIR is not allowed to make any further assignments from its address space allocations. delete: </p> delete: <h3> delete: <a id="3.2" name="3.2"> delete: </a> 3.2 Finance delete: </h3> delete: <p> 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. delete: <br /> delete: <br /> In cases of mergers, the LIR whose allocation has been transferred to another LIR will continue to be billed until any inconsistencies are resolved. delete: </p> delete: <h3> delete: <a id="3.3" name="3.3"> delete: </a> 3.3 Transfers of Address Allocations from a Closing LIR delete: </h3> delete: <p> 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. delete: </p> delete: <h3> delete: <a id="3.4" name="3.4"> delete: </a> 3.4 Open Address Space Requests delete: </h3> delete: <p> 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: delete: </p> delete: <p> delete: <a data-val="3628263b9a882491a5225984f80cc634" href="resolveuid/3628263b9a882491a5225984f80cc634" data-linktype="internal" class="internal-link"> http://www.ripe.net/lir/registries/indices/index.html delete: </a> delete: </p> delete: <h3> delete: <a id="3.5" name="3.5"> delete: </a> 3.5 End Users Keeping Address Assignments delete: </h3> delete: <p> 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. delete: </p> delete: <p> For more information, please see the RIPE documents "Smallest RIPE NCC Allocation / Assignment Sizes" and "Provider Independent versus Provider Aggregatable Address Space" available from the RIPE Document Store at: delete: </p> delete: <p> http://www.ripe.net/ripe/docs/smallest-alloc-sizes.html delete: </p> delete: <p> http://www.ripe.net/ripe/docs/pi-pa.html delete: </p> delete: <p> The LIR should also supply the RIPE NCC with a list of Assignments kept by End Users in the following format: delete: </p> delete: <pre> Inetnum Range Size Date Netname delete: <br /> delete: <br /> 193.0.0.0 - 193.0.1.255 512 19950101 RIPE-NCC delete: </pre> delete: <h3> delete: <a id="3.6" name="3.6"> delete: </a> 3.6 Continued Internet Connectivity to End Users delete: </h3> delete: <p> 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 delete: <a href="#3.8"> 3.8 delete: </a> ) delete: </p> delete: <h3> delete: <a id="3.7" name="3.7"> delete: </a> 3.7 Discontinued Internet Connectivity to End Users delete: </h3> delete: <p> 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. delete: </p> delete: <h3> delete: <a id="3.8" name="3.8"> delete: </a> 3.8 Database Responsibilities delete: </h3> delete: <p> 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 delete: <b> inetnum delete: </b> , delete: <b> aut-num delete: </b> and delete: <b> domain delete: </b> objects with obsolete information. delete: </p> delete: <p> 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. delete: </p> delete: <h3> delete: <a id="3.9" name="3.9"> delete: </a> 3.9 Unassigned Address Space delete: </h3> delete: <p> 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. delete: </p> delete: <h3> delete: <a id="4.0" name="4.0"> delete: </a> 4.0 When an LIR is Closed by the RIPE NCC delete: </h3> delete: <p> The RIPE NCC may decide to close an LIR 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. delete: </p> delete: <p> The RIPE NCC will send 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 delete: <a href="#3.0"> 3.0 delete: </a> . delete: </p> delete: <p> 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. delete: </p>
Mergers, Acquisitions, Takeovers and Closures of Organisations Operating an LIR RIPE NCC Internet Numbers Registration Procedures
RIPE Documents Search