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-628: Transfer of Internet Registries (LIRs) on the steps to take when the organisation operating an LIR changes ownership (due to Number Resource Records and Change of a merger, sale or takeover) or stops serving entirely as an LIR. Member’s Official Legal Name
delete: <h2> Abstract insert: <h2 class="western">

Contents

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: <hr noshade="noshade" size="1" /> delete: <p> delete: <a href="#1.0"> insert: <span> 1.0 insert: <a href="#1"> Definitions insert: </a> insert: </span> insert: </p>

insert: <p>

insert: <span> 2.0 insert: <a href="#2"> Introduction 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"> insert: </span> insert: </p>

insert: <p>

insert: <span> 3.0 Closing an LIR delete: </a> delete: </p> delete: <div class="indent"> delete: <a href="#3.1"> insert: <a href="#3"> Transfer of Internet Number Resource Records insert: </a> insert: </span> insert: </p>

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

insert: <span> 3.1 Further Assignments delete: </a> delete: <br /> delete: <a href="#3.2"> insert: <a href="#31"> Submission of the Request for Transfer insert: </a> insert: </span> insert: </p>

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

insert: <span> 3.2 Finance delete: </a> delete: <br /> delete: <a href="#3.3"> insert: <a href="#32"> If the Receiving insert: </a> insert: <a href="#32"> Party insert: </a> insert: <a href="#32"> insert: </a> insert: <a href="#32"> is insert: </a> insert: <a href="#32"> not insert: </a> insert: <a href="#32"> a insert: </a> insert: <span> insert: <a href="#32"> Member insert: </a> insert: </span> insert: </span> insert: </p>

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

insert: <span> 3.3 Transfers of Address Allocations from a Closing LIR delete: </a> delete: <br /> delete: <a href="#3.4"> insert: <a href="#33"> Financial Consequences insert: </a> insert: </span> insert: </p>

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

insert: <span> 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 insert: <a href="#34"> Internet Number Resource Registration and RIPE 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"> Issues insert: </a> insert: </span> insert: </p>

insert: <p>

insert: <span> 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> insert: <a href="#4"> The insert: <span> Member insert: </span> Changes its Official Legal Name insert: </a> insert: </span> insert: </p>

insert: <h3 class="western">

insert: <a name="1"> insert: </a> insert: <span> insert: <span> 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> 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: Definitions insert: </span> insert: </span> insert: </h3>

insert: <p>

insert: <span> For the purposes of this document: insert: </span> insert: </p>

insert: <p>

insert: <span> Internet number resource records refer to insert: </span>

  • A takeover of one LIR by another LIR, closing one of the LIRs. insert: <p>

    insert: <span> The registered insert: <span> allocations and assignments of a Member insert: </span> insert: </span> insert: </p>

  • A takeover of one LIR by another LIR, both remain open. insert: <p>

    insert: <span> The independent Internet number resources assigned through the Member as a “sponsoring LIR” to an End User insert: </span> insert: </p>

    insert: </li>
  • insert: </ul>
insert: <h3 class="western">

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

insert: <p>

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

insert: <ul>
    insert: <li>
  • insert: <p>

    insert: <span> The natural or legal persons holding the registration of Internet number resources insert: </span> insert: </p>

  • A takeover of an LIR by a non-LIR. insert: <p>

    insert: <span> The Internet number resource records that are registered to the natural and legal persons insert: </span> insert: </p>

2. Outline the details of the change, stating: insert: <span> 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: </span> insert: </p>

insert: <p>

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

insert: <ol>
    insert: <li>
  1. insert: <p>

    insert: <span> Internet Number Resource records are transferred. Such transfers may take place: insert: </span>

    insert: </li>
  2. insert: <li>
  3. insert: <p>

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

    insert: </li>
  4. insert: </ol>
insert: <p>

insert: <span> This document describes the procedures to be followed for such changes to be properly communicated to, and registered with, the RIPE NCC. insert: </span> insert: </p>

insert: <p>

insert: </p>

insert: <p>

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

insert: <p>

insert: <span> If a change 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> delete: </p> delete: <h3> delete: <a id="2.7" name="2.7"> delete: </a> 2.7 Takeover Fee 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: </span> insert: </p>

insert: <p>

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

insert: <p>

insert: <span> This document does not describe the procedure to be followed in the case of changes with regards to independent Internet number resources assigned to End Users or any changes to the End User's business structure. This procedure is described in the RIPE NCC Procedural Document, “ insert: <a href="https://www.ripe.net/publications/docs/lir-end-user-contractual-changes"> Independent Internet Number Resources – Contractual Relationship Changes Between Sponsoring LIR and End User insert: </a> ”. insert: </span> insert: </p>

insert: <h3 class="western">

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

In cases where an organisation operating an LIR takes over one or more LIRs, a takeover fee insert: <span> 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: </span> insert: </p>

insert: <h4>

insert: <a name="31"> insert: </a> 3.1 Submission of the Request for Transfer insert: </h4>

insert: <p>

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

insert: <ul>
    insert: <li>
  • insert: <p>

    insert: <span> If the transfer is due to a change in the business structure of the Member (e.g., merger or acquisition), the request must be submitted to insert: <a href="mailto:ncc@ripe.net"> ncc@ripe.net insert: </a> insert: </span> insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    insert: <span> insert: <span> If the transfer is a transfer of IPv4 address records from one Member to another insert: </span> insert: </span> insert: <span> insert: <span> party ac insert: </span> insert: </span> insert: <span> insert: <span> cording to RIPE Policies ( insert: <a title="" href="https://www.ripe.net/publications/docs/ipv4-policies#55" class="external-link" target="_self"> Sections 5.5 and 6.4, "IPv4 Address Allocation and Assignment Policies for every the RIPE NCC Service Region insert: </a> ”), the request must be submitted to insert: <a href="mailto:lir-help@ripe.net"> lir-help@ripe.net insert: </a> insert: </span> insert: </span> insert: </p>

    insert: </li>
  • insert: </ul>
insert: <p>

insert: <span> A registered contact or an authorised person (e.g., senior manager, legal successor) must send the request. insert: </span> insert: </p>

insert: <p>

insert: </p>

insert: <p>

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

insert: <p>

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

insert: <ul>
    insert: <li>
  • insert: <p>

    insert: <span> The full official legal names of all parties involved insert: </span> insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    insert: <span> Which party will transfer the Internet number resource records and which party will receive them insert: </span> insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    insert: <span> Recent registration papers issued by the relevant national authorities for all involved parties insert: </span> insert: </p>

    insert: </li>
  • insert: </ul>
insert: <p>

insert: <span> I insert: </span> insert: <span> insert: <span> f 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 href="#4"> Section insert: </a> insert: <a href="#4"> 4.0 insert: </a> must be followed prior to the transfer of the Internet number resource records. insert: </span> insert: </span> insert: </p>

insert: <p>

insert: <span> insert: <span> 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 taken over (e.g. if three LIRs and Deregistration of Internet number resources, insert: <a title="" href="https://www.ripe.net/publications/docs/closure#11" class="external-link" target="_self"> Section A.1.1. insert: </a> and insert: <a title="" href="https://www.ripe.net/publications/docs/closure#12" class="external-link" target="_self"> Section A.1.2. insert: </a> ). insert: </span> insert: <b> insert: <span> insert: </span> insert: </b> insert: </span> insert: </p>

insert: <p>

insert: <span> insert: <b> insert: <span> insert: <br />
insert: </span>
insert: </b>
insert: </span>
insert: </p>

insert: <p>

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

insert: <p>

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

insert: <p>

insert: <span> insert: <b> insert: <br />
insert: </b>
insert: </span>
insert: </p>

insert: <p>

insert: <span> insert: <b> iii. A list of the Internet number resource records that are taken over, the fee requested to be transferred. If insert: </b> insert: <i> insert: <b> all insert: </b> insert: </i> insert: <b> of the transferring Member's Internet number resource records registered are being transferred, a confirmation of this is paid three times). requested. insert: </b> insert: </span> insert: </p>

insert: <p>

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

insert: <p>

insert: <span> 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 title="" href="https://www.ripe.net/publications/docs/closure#11" class="external-link" target="_self"> Section A.1.1. insert: </a> ). insert: </span> insert: </p>

insert: <p>

insert: <span> insert: <b> insert: <br />
insert: </b>
insert: </span>
insert: </p>

insert: <p>

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

insert: <p>

insert: <span> The RIPE NCC may ask the parties 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: </span> insert: </p>

insert: <p>

insert: <span> insert: <b> insert: <br />
insert: </b>
insert: </span>
insert: </p>

insert: <p>

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

insert: <p>

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

insert: <p>

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

insert: <ul>
    insert: <li>
  • insert: <p>

    insert: <span> an official document (issued by a national authority) confirming the closure of the transferring party; and insert: </span> insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

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

    insert: </li>
  • insert: </ul>
insert: <p>

insert: <span> insert: <b> insert: <span> insert: <span> insert: <br />
insert: </span>
insert: </span>
insert: </b>
insert: </span>
insert: </p>

insert: <p>

insert: <span> insert: <b> insert: <span> insert: <span> v insert: </span> insert: <span> insert: <span> i. insert: </span> insert: </span> insert: <span> insert: <span> An overview of the utilisation of all allocations and of the status of all independent Internet number resource assignments insert: </span> insert: </span> insert: </span> insert: </b> insert: </span> insert: </p>

insert: <p>

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

insert: <h4>

insert: <a name="32"> insert: </a> 3.2 If the Receiving Party is not a Member insert: </h4>

insert: <p>

insert: <span> insert: <span> Members may wish to transfer their Internet number resource records to another Member or to a third party that is not a Member. insert: </span> insert: </span> insert: </p>

insert: <p>

insert: <span> insert: <span> If the Internet number resource records are transferred to a non-Member, the receiving party 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> ) If the receiving party refuses to do the above, the RIPE NCC will not transfer the Internet number resource records to them. insert: </span> insert: </span> insert: </p>

insert: <p>

insert: <span> insert: <span> If the Internet number resource records to be transferred are Provider Independent (PI) addresses , the receiving party may either apply to be a Member by signing the RIPE NCC Standard Service Agreement or enter into a contractual relationship with a sponsoring LIR. insert: </span> insert: <span> insert: <span> For more information, please see: insert: </span> insert: </span> insert: </span> insert: </p>

insert: <p>

insert: <a href="https://www.ripe.net/lir-services/resource-management/independent-resources/"> insert: <span> insert: <span> insert: <span> insert: <span> https://www.ripe.net/lir-services/resource-management/independent-resources/ insert: </span> insert: </span> insert: </span> insert: </span> insert: </a> insert: </p>

insert: <p>

insert: <span> insert: <span> The request for the transfer can be submitted as described above (Section 1). insert: </span> insert: </span> insert: </p>

insert: <h4>

insert: <a name="33"> insert: </a> 3.3 Financial Consequences insert: </h4>

insert: <p>

insert: <span> insert: <span> All current outstanding invoices for the LIRs being taken over will also have to and all outstanding financial obligations must be paid in full. delete: </p> delete: <p> The transfer of 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.If the receiving party is not a Member, then the payment is the responsibility of the transferring Member. insert: </span> insert: </span> insert: </p>

insert: <p>

insert: <span> insert: <span> If the receiving party 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/charging"> RIPE NCC Charging Scheme insert: </a> ). insert: </span> insert: </span> insert: </p>

insert: <h4>

insert: <a name="34"> insert: </a> 3.4 Internet Number Resource Registration and RIPE Database Issues insert: </h4>

insert: <p>

insert: <span> insert: <b> insert: <span> The RIPE NCC will review the status of any IP address allocations also incurs a takeover fee 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. insert: </span> insert: </b> insert: </span> insert: </p>

insert: <p>

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

insert: <p>

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

insert: <h3 class="western">

insert: <a name="4"> insert: </a> insert: <span> insert: <span> 4.0 The Member Changes its Official Legal Name insert: </span> insert: </span> insert: </h3>

insert: <p>

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

insert: <p>

insert: <span> The Member must send an email to insert: <a href="mailto:ncc@ripe.net"> ncc@ripe.net insert: </a> informing the RIPE NCC of the name change. This email must include: insert: </span> insert: </p>

insert: <ul>
    insert: <li>
  • insert: <p>

    insert: <span> New registration papers from the national authority; 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> . insert: </span> insert: </p>

    insert: </li>
  • insert: <li>
  • insert: <p>

    insert: <span> The official legal documents supporting this change insert: </span>

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

    insert: </li>
  • insert: </ul>
insert: <p>

insert: <span> insert: <span> T insert: </span> insert: </span> insert: <span> insert: <span> insert: <span> he RIPE NCC will send a new insert: <a title="" href="https://www.ripe.net/publications/docs/service-agreement" class="external-link" target="_self"> RIPE NCC Standard Service Agreement insert: </a> 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 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 IP assignments made from address space allocated RIPE Database objects maintained by the RIPE NCC. delete: </p> delete: <p> 3. Provide a list of any End Users NCC 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 are related to this change. The Member must update all RIPE Database are up-to-date. A closing LIR is responsible for removing any objects entered maintained 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, related to 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> change. insert: </span> insert: </span> insert: </span> 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
RIPE Documents Search