You are here: Home > Publications > RIPE Document Store > Transfer of Internet Number Resources and Change of a Member’s Official Legal Name

Changes to Transfer of Internet Number Resources and Change of a Member’s Official Legal Name

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-689: Transfer of ripe-301: This document provides guidelines to Local Internet Number Resources and Change of Registries (LIRs) on the steps to take when the organisation operating an LIR changes ownership (due to a Member’s Official Legal Name merger, sale or takeover) or stops serving entirely as an LIR.

Contents Abstract

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

insert: <hr noshade="noshade" size="1" />
insert: <p>

insert: <a href="#1.0"> 1.0 delete: <a href="#definitions"> Definitions delete: </a> delete: </p> delete: <p> Introduction insert: </a> insert: <br />
insert: <a href="#2.0"> 2.0 delete: <a href="#introduction"> LIR Ownership Change insert: </a> insert: </p>

insert: <div class="indent">
insert: <p>

insert: <a href="#2.1"> 2.1 IP Address Space insert: </a> insert: <br />
insert: <a href="#2.2"> 2.2 Service Agreement insert: </a> insert: <br />
insert: <a href="#2.3"> 2.3 Change in Operating Organisation insert: </a> insert: <br />
insert: <a href="#2.4"> 2.4 Contact Person(s) insert: </a> insert: <br />
insert: <a href="#2.5"> 2.5 RegID insert: </a> insert: <br />
insert: <a href="#2.6"> 2.6 Transfers of Address Allocations insert: </a> insert: <br />
insert: <a href="#2.7"> 2.7 Takeover Fee insert: </a> insert: </p>

insert: </div>
insert: <p>

insert: <a href="#3.0"> 3.0 Closing an LIR insert: </a> insert: </p>

insert: <div class="indent">
insert: <a href="#3.1"> 3.1 Further Assignments insert: </a> insert: <br />
insert: <a href="#3.2"> 3.2 Finance insert: </a> insert: <br />
insert: <a href="#3.3"> 3.3 Transfers of Address Allocations from a Closing LIR insert: </a> insert: <br />
insert: <a href="#3.4"> 3.4 Open Address Space Requests insert: </a> insert: <br />
insert: <a href="#3.5"> 3.5 End Users Keeping Address Assignments insert: </a> insert: <br />
insert: <a href="#3.6"> 3.6 Continued Internet Connectivity to End Users insert: </a> insert: <br />
insert: <a href="#3.7"> 3.7 Discontinued Internet Connectivity to End Users insert: </a> insert: <br />
insert: <a href="#3.8"> 3.8 Database Responsibilities insert: </a> insert: <br />
insert: <a href="#3.9"> 3.9 Unassigned Address Space insert: </a> insert: </div>
insert: <p>

insert: <a href="#4.0"> 4.0 When an LIR is Closed by the RIPE NCC insert: </a> insert: </p>

insert: <p>

insert: </p>

insert: <hr noshade="noshade" size="1" />
insert: <h2>

insert: <a name="1.0"> insert: </a> 1.0 Introduction delete: </a> delete: </p> delete: <p> 3.0 delete: <a href="#transfer"> Transfer of Internet Number Resources delete: </a> delete: </p> delete: <p style="padding-left: 30px;"> 3.1 delete: <a href="#transfer31"> Submission of the Request for Transfer delete: </a> delete: </p> delete: <p style="padding-left: 30px;"> 3.2 delete: <a href="#transfer32"> If the Receiving Party is not a Member delete: </a> delete: </p> delete: <p style="padding-left: 30px;"> 3.3 delete: <a href="#transfer33"> Financial Consequences delete: </a> delete: </p> delete: <p style="padding-left: 30px;"> 3.4 delete: <a href="#transfer34"> Internet Number Resource Registration insert: </h2>

insert: <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 delete: </a> delete: </p> delete: <p style="padding-left: 30px;"> 3.5 delete: <a href="#transfer35"> Transfers Between LIR Accounts Belonging to the Same Member delete: </a> delete: </p> delete: <p> 4.0 delete: <a href="#memberchanges"> Member Changes Official Legal Name delete: </a> delete: </p> delete: <p>   delete: </p> delete: <h3> delete: <a name="definitions"> delete: </a> 1.0 Definitions delete: </h3> delete: <p> For the purposes of this document, Internet number resources refer to: issues that need resolving. Therefore, the RIPE NCC must always be contacted when an LIR changes ownership or closes. insert: </p>

insert: <h2>

insert: <a id="2.0" name="2.0"> insert: </a> 2.0 LIR Ownership Change insert: </h2>

insert: <p>

In the case of an LIR ownership change, the LIR should contact the RIPE NCC at insert: <a href="mailto:lir-help@ripe.net"> lir-help@ripe.net insert: </a> . insert: </p>

insert: <p>

Only registered LIR contact person(s) can discuss the change of an LIR ownership with the RIPE NCC. insert: </p>

insert: <p>

The following steps are required to change the organisation operating an LIR: insert: </p>

insert: <p>

1. Clarify the type of change: insert: </p>

insert: <ul>
    insert: <li>
  • A takeover of one LIR by another LIR, closing one of the LIRs. insert: </li>
  • insert: <li>
  • A takeover of one LIR by another LIR, both remain open. insert: </li>
  • insert: <li>
  • A takeover of an LIR by a non-LIR. insert: </li>
  • insert: </ul>
insert: <p>

2. Outline the details of the change, stating:

  • The registered allocation and assignment records of a member reason for the change of organisation.
  • In the case of a transfer of Internet The name of the company/companies involved. insert: </li>
  • insert: <li>
  • The number resources from the member to another party according to RIPE Policy “ delete: <a href="http://www.ripe.net/publications/docs/transfer-policies" data-linktype="external" data-val="http://www.ripe.net/publications/docs/transfer-policies"> RIPE Resource Transfer Policies delete: </a> ”. Such a transfer may also be facilitated through the RIPE NCC Listing Service. of LIRs affected by the change. insert: </li>
  • insert: <li>
  • The RegID(s) of the LIR(s) affected by the change.

  delete: </p> 3. Present the following documents to the RIPE NCC: insert: </p>

insert: <ul>
    insert: <li>
  • Confirmation from all parties agreeing to the change (See section insert: <a href="#2.3"> 2.3 insert: </a> ). insert: </li>
  • insert: <li>
  • Updated list of contact person(s) (See section insert: <a href="#2.4"> 2.4 insert: </a> ). insert: </li>
  • insert: <li>
  • Updated billing e-mail contact details, including any changes to VAT number. insert: </li>
  • insert: <li>
  • A new service agreement, if applicable (See section insert: <a href="#2.2"> 2.2 insert: </a> ). insert: </li>
  • insert: <li>
  • Legal documentation supporting the name change, if applicable (See section insert: <a href="#2.2"> 2.2 insert: </a> ). insert: </li>
  • insert: <li>
  • Overview of utilisation in all allocations (See section insert: <a href="#2.6"> 2.6 insert: </a> ). insert: </li>
  • insert: </ul>

delete: <a name="introduction"> delete: </a> 2.0 Introduction insert: <a id="2.1" name="2.1"> insert: </a> 2.1 IP Address Space

In order for the RIPE NCC to maintain an accurate registry, it must hold accurate data concerning: 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. insert: </p>

insert: <h3>

insert: <a id="2.2" name="2.2"> insert: </a> 2.2 Service Agreement insert: </h3>

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

  • The natural organisation operating the LIR changes name, or legal persons holding the registration of Internet number resources
  • The Internet number resources that are registered to these natural or legal persons LIR wishes to change their RegID.

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 The registration of Internet number resources, must be communicated to the RIPE NCC. delete: </p> delete: <p> A member must inform the RIPE NCC if delete: <em> one or both delete: </em> of the following changes occurs: delete: </p> delete: <ol> delete: <li> Internet Number Resource are transferred. Such transfers may take place: delete: </li> delete: <ul> delete: <li> Because of a change in the member's business structure (for example in the case of a merger or acquisition of the member's organisation, or if the member is undergoing bankruptcy, liquidation, suspension of payments or insolvency proceedings) that can be proved/supported by official documentation from national authorities. delete: </li> delete: <li> In the case of a transfer of Internet number resources from the member to another party according to RIPE Policy “ delete: <a href="http://www.ripe.net/publications/docs/transfer-policies" data-linktype="external" data-val="http://www.ripe.net/publications/docs/transfer-policies"> RIPE Resource Transfer Policies delete: </a> ”. Such a transfer may also be facilitated through the delete: <a data-val="e222449049284bb1af45883cccde2da1" href="../../../resolveuid/e222449049284bb1af45883cccde2da1" data-linktype="internal"> RIPE NCC Listing Service delete: </a> . delete: <br /> delete: <br /> delete: </li> delete: </ul> delete: <li> The member changes the relevant Chamber of Commerce, or its official legal name delete: <strong> . delete: </strong> Such a change may occur, for example, because of a merger or acquisition of the member's organisation. delete: </li> delete: </ol> delete: <p> This document describes the procedures for such changes to be properly communicated and registered with the RIPE NCC. delete: </p> delete: <p> delete: <strong> Note: delete: </strong> delete: </p> delete: <p> If a change in a member's official legal name is accompanied by a transfer of Internet number resources, the member must first inform the RIPE NCC of country equivalent, supporting the name change and then of the transfer. delete: </p> delete: <p> If a change in a member's business structure is delete: <em> not delete: </em> accompanied by a transfer of Internet number resources or a change in the member's official legal name, then the RIPE NCC does not need to be informed of this change. delete: </p> delete: <p> 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 Users business structure. This procedure is described in the RIPE NCC Procedural Document, “ delete: <a href="http://www.ripe.net/publications/docs/lir-end-user-contractual-changes" data-val="http://www.ripe.net/publications/docs/lir-end-user-contractual-changes" data-linktype="external"> Independent Internet Number Resources – Contractual Relationship Changes Between Sponsoring LIR and End User delete: </a> ”. delete: </p> delete: <p> This document does not describe the procedure to be followed in case of a transfer of Internet number resources from the RIPE NCC service region to the service region of another RIR and vice versa. This procedure is described in the RIPE NCC procedural document, “ delete: <a class="external-link" href="http://www.ripe.net/publications/docs/inter-rir-transfer-of-inr" data-linktype="external" data-val="http://www.ripe.net/publications/docs/inter-rir-transfer-of-inr"> Inter-RIR Transfer of Internet Number Resources delete: </a> ”. delete: </p> delete: <p>   delete: </p> delete: <h3> delete: <a name="transfer"> delete: </a> 3.0 Transfer of Internet Number Resources delete: </h3> delete: <p> If a member transfers their Internet number resources to a third party for any reason, this transfer must be declared to the RIPE NCC for approval. delete: </p> delete: <h4> delete: <a name="transfer31"> delete: </a> 3.1 Submission of the Request for Transfer delete: </h4> delete: <p> For the transfer to be processed, one of the involved parties must submit a request to the RIPE NCC: delete: </p> delete: <ul> delete: <li> If the transfer is due to a change in the member's business structure that can be proved/supported by official documentation by national authorities (e.g., merger, acquisition, bankruptcy, liquidation), the request must be submitted via the LIR Portal. to the RIPE NCC. insert: </p>

insert: <p>

The Standard RIPE NCC Service Agreement is available from the RIPE Document Store at: insert: <br />
insert: <br />
insert: <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 insert: </a> insert: </p>

insert: <p>

If the requesting party organisation operating the LIR does not change its name and keeps the original RegID, the LIR can continue operating under the same service agreement. insert: </p>

insert: <h3>

insert: <a id="2.3" name="2.3"> insert: </a> 2.3 Change in Operating Organisation insert: </h3>

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

insert: <h3>

insert: <a id="2.4" name="2.4"> insert: </a> 2.4 Contact Person(s) insert: </h3>

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

insert: <h3>

insert: <a id="2.5" name="2.5"> insert: </a> 2.5 RegID insert: </h3>

insert: <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 access rights to the LIR portal, the to correspond to the legal name of the organisation operating the LIR. insert: </p>

insert: <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: insert: <br />
insert: <br />
insert: <a class="external-link" href="http://www.ripe.net/ripe/docs/charging.html" target="_self" title=""> http://www.ripe.net/ripe/docs/charging.html insert: </a> insert: </p>

insert: <h3>

insert: <a id="2.6" name="2.6"> insert: </a> 2.6 Transfers of Address Allocations insert: </h3>

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

insert: <h3>

insert: <a id="2.7" name="2.7"> insert: </a> 2.7 Takeover Fee insert: </h3>

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

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

insert: <h2>

insert: <a id="3.0" name="3.0"> insert: </a> 3.0 Closing an LIR insert: </h2>

insert: <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 insert: <a href="mailto:lir-help@ripe.net"> lir-help@ripe.net insert: </a> . insert: <br />
insert: <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. insert: <br />
insert: <br />
To cease operations, an LIR is required to take the following four steps: insert: <br />
insert: <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. insert: <br />
insert: <br />
2. Provide the RIPE NCC with documentation of all IP assignments made from address space allocated by the RIPE NCC. insert: </p>

insert: <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 insert: <a href="#3.7"> 3.7 insert: </a> ) insert: <br />
insert: <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 insert: <a href="#3.8"> 3.8 insert: </a> ) insert: </p>

insert: <h3>

insert: <a id="3.1" name="3.1"> insert: </a> 3.1 Further Assignments insert: </h3>

insert: <p>

A closing LIR is not allowed to make any further assignments from its address space allocations. insert: </p>

insert: <h3>

insert: <a id="3.2" name="3.2"> insert: </a> 3.2 Finance insert: </h3>

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

insert: <h3>

insert: <a id="3.3" name="3.3"> insert: </a> 3.3 Transfers of Address Allocations from a Closing LIR insert: </h3>

insert: <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 submitted via email to delete: <a href="mailto:ncc@ripe.net"> ncc@ripe.net delete: </a> delete: </li> delete: <li> If this is a transfer of Internet number resource valid and up-to-date. insert: </p>

insert: <h3>

insert: <a id="3.4" name="3.4"> insert: </a> 3.4 Open Address Space Requests insert: </h3>

insert: <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 one member to another party according to RIPE Policy “ delete: <a href="http://www.ripe.net/publications/docs/transfer-policies" data-linktype="external" data-val="http://www.ripe.net/publications/docs/transfer-policies"> RIPE Resource Transfer Policies delete: </a> ”, the request must be submitted via the delete: <a href="https://my.ripe.net" data-linktype="external" data-val="https://my.ripe.net"> LIR Portal delete: </a> . delete: </li> delete: </ul> delete: <p> A registered contact or an authorised person (e.g., senior manager, legal successor) must send the request. delete: </p> delete: <p> The RIPE NCC will ask for the following information: delete: </p> delete: <p> delete: <strong> i. Information regarding the parties involved, including: delete: </strong> delete: </p> delete: <ul> delete: <li> The full official legal names of all parties involved delete: </li> delete: <li> Which party will transfer the Internet number resources and which party will receive them delete: </li> delete: <li> Recent registration papers issued by the relevant national authorities for all involved parties delete: </li> delete: </ul> delete: <p> If the current official legal names of the involved members are different from those in the relevant signed RIPE NCC Standard Service Agreement, then the procedure described in delete: <a href="#memberchanges"> Section 4.0 delete: </a> must be followed prior to the transfer of the Internet number resources. delete: </p> delete: <p> The procedure described under Section 4.0 is not necessary for the transferring member if the RIPE NCC Standard Service Agreement for that member is terminated (see Sections A.1.1 and A.1.2 of the RIPE NCC Procedural Document, “ delete: <a href="http://www.ripe.net/publications/docs/closure" data-linktype="external" data-val="http://www.ripe.net/publications/docs/closure"> Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources delete: </a> ”. delete: </p> delete: <p> delete: <strong> ii. A description of the reason for the transfer (for example, due to merger, acquisition, transfer of Internet number resources according to the RIPE policies) delete: </strong> delete: </p> delete: <p> If the transfer is taking place due to a change in the structure of the organisation(s) involved (e.g., merger, acquisition), a description of the changes among these organisation(s) is necessary. having to renumber at a later date. This description must be accompanied by the official legal documents issued by the relevant national authorities proving/supporting the changes the request is based on. delete: </p> delete: <p> If the change in the structure of the organisation(s) involved cannot be proven/supported by official documentation from national authorities describing this change (e.g., a network acquisition from one member to another), then these cases will fall within the scope of RIPE Policy “ delete: <a href="http://www.ripe.net/publications/docs/transfer-policies" data-linktype="external" data-val="http://www.ripe.net/publications/docs/transfer-policies"> RIPE Resource Transfer Policies delete: </a> ”. delete: </p> delete: <p> delete: <strong> iii. A list of the Internet number resources that are requested to be transferred. If delete: <em> all delete: </em> of the transferring member's Internet number resources registered are being transferred, a confirmation of this is requested. delete: </strong> delete: </p> delete: <p> The member must also indicate any End User assignment agreements that are requested to be transferred. delete: </p> delete: <p> If a member transfers all of their Internet number resources, their RIPE NCC Standard Service Agreement may be terminated (see Section A.1.1. of the RIPE NCC Procedural Document, “ delete: <a href="http://www.ripe.net/publications/docs/closure"> Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources delete: </a> ”). delete: </p> delete: <p> delete: <strong> iv. The correct contact details of all parties involved delete: </strong> delete: </p> delete: <p> 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. delete: </p> delete: <p> delete: <strong> v. A Transfer Agreement signed by both parties or by their legal successors delete: </strong> delete: </p> delete: <p> The RIPE NCC provides the template of the Transfer Agreement that either party may submit to the RIPE NCC. delete: </p> delete: <p> The Transfer Agreement must be signed by authorised persons for both parties. For the transferring party, it is required that the Transfer Agreement is signed by an authorised representative having the general capacity to act on behalf of this party. The RIPE NCC reserves the right to request official documentation proving that the person signing on behalf of either party is authorised to do so. delete: </p> delete: <p> 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). delete: </p> delete: <p> If the transferring party no longer exists by the time the RIPE NCC is being informed, the receiving party must send: delete: </p> delete: <ul> delete: <li> An official document (issued by a national authority) confirming the closure of the transferring party delete: </li> delete: <li> A copy of an older signed agreement between the relevant parties mentioning the transfer of the Internet number resources. If such an agreement is not available, the RIPE NCC may accept a confirmation of the transfer to the RIPE NCC signed by an authorised person (e.g., senior manager, legal successor) of the receiving party. The RIPE NCC reserves the right to reverse the transfer should another party object and provide an agreement that proves that the Internet number resource should have been transferred to them. delete: </li> delete: </ul> delete: <p> delete: <strong> vi. An overview of the utilisation of all allocations and of the status of all independent Internet number resource assignments delete: </strong> delete: </p> delete: <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. delete: </p> delete: <h4> delete: <a name="transfer32"> delete: </a> 3.2 If the Receiving Party is not a Member delete: </h4> delete: <p> Members may wish to transfer their Internet number resource to another member or to a third party that is not a member. delete: </p> delete: <p> If the Internet number resources are transferred to a non-member, the receiving party must apply to be a member by signing a RIPE NCC Standard Service Agreement before the transfer takes place ( delete: <a data-val="e292d712e8380f2d2507f0a15e4b66a4" href="../../../resolveuid/e292d712e8380f2d2507f0a15e4b66a4" data-linktype="internal"> more information on how to become a member is available delete: </a> ). If the receiving party refuses to do the above, the RIPE NCC at: insert: </p>

insert: <p>

insert: <a data-val="3628263b9a882491a5225984f80cc634" href="resolveuid/3628263b9a882491a5225984f80cc634" data-linktype="internal" class="internal-link"> http://www.ripe.net/lir/registries/indices/index.html insert: </a> insert: </p>

insert: <h3>

insert: <a id="3.5" name="3.5"> insert: </a> 3.5 End Users Keeping Address Assignments insert: </h3>

insert: <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 transfer the Internet number resources to them. delete: </p> delete: <p> If the Internet number resources to be transferred are Provider Independent (PI) addresses, the receiving party may either apply to become a member by signing the RIPE NCC Standard Service Agreement, or can enter into a contractual relationship with a sponsoring LIR. able to announce an aggregate block. They may, therefore, have problems getting their addresses routed. insert: </p>

insert: <p>

For more information, please see the notes on delete: <a data-val="9aaab7c7511208c0395fcc9d76608352" href="../../../resolveuid/9aaab7c7511208c0395fcc9d76608352" data-linktype="internal"> Requesting RIPE documents "Smallest RIPE NCC Allocation / Assignment Sizes" and "Provider Independent Resources delete: </a> . versus Provider Aggregatable Address Space" available from the RIPE Document Store at: insert: </p>

insert: <p>

http://www.ripe.net/ripe/docs/smallest-alloc-sizes.html insert: </p>

insert: <p>

http://www.ripe.net/ripe/docs/pi-pa.html

The request LIR should also supply the RIPE NCC with a list of Assignments kept by End Users in the following format: insert: </p>

insert: <pre>
 Inetnum Range Size Date Netname  insert: <br /> 
insert: <br />
193.0.0.0 - 193.0.1.255 512 19950101 RIPE-NCC insert: </pre>
insert: <h3>

insert: <a id="3.6" name="3.6"> insert: </a> 3.6 Continued Internet Connectivity to End Users insert: </h3>

insert: <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 the transfer as long as the original criteria under which they were assigned remain valid. (See section insert: <a href="#3.8"> 3.8 insert: </a> ) insert: </p>

insert: <h3>

insert: <a id="3.7" name="3.7"> insert: </a> 3.7 Discontinued Internet Connectivity to End Users insert: </h3>

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

insert: <h3>

insert: <a id="3.8" name="3.8"> insert: </a> 3.8 Database Responsibilities insert: </h3>

insert: <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 insert: <b> inetnum insert: </b> , insert: <b> aut-num insert: </b> and insert: <b> domain insert: </b> objects with obsolete information. insert: </p>

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

insert: <h3>

insert: <a id="3.9" name="3.9"> insert: </a> 3.9 Unassigned Address Space insert: </h3>

insert: <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 submitted assigned by the RIPE NCC as described above (Section 3.1). delete: </p> delete: <h4> delete: <a name="transfer33"> delete: </a> 3.3 Financial Consequences delete: </h4> delete: <p> All outstanding invoices necessary. Should an LIR decide to close and reopen at a later date, it must repeat all outstanding financial obligations formal steps required to establish a new LIR. insert: </p>

insert: <h3>

insert: <a id="4.0" name="4.0"> insert: </a> 4.0 When an LIR is Closed by the RIPE NCC insert: </h3>

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

insert: <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 insert: <a href="#3.0"> 3.0 insert: </a> . insert: </p>

insert: <p>

If the LIR does not provide the RIPE NCC with the proper Documentation, the RIPE NCC will determine which address space should 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. This payment is the responsibility of the receiving member. If the receiving party is not a member, then payment is the responsibility of the transferring member. delete: </p> delete: <p> If the receiving party decides to sign the RIPE NCC Standard Service Agreement, then a sign-up fee must be paid (see delete: <a href="http://www.ripe.net/publications/docs/charging"> RIPE NCC Charging Scheme delete: </a> ). delete: </p> delete: <h4> delete: <a name="transfer34"> delete: </a> 3.4 Internet Number Resource Registration and RIPE Database Issues delete: </h4> delete: <p> delete: <strong> The RIPE NCC will review the status of any returned to the public pool of IP address 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. delete: </strong> delete: </p> delete: <p> The receiving member must deregister from the RIPE Database any invalid or overlapping registrations or unused assignment approvals. delete: </p> delete: <p> 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. delete: </p> delete: <h4> delete: <a name="transfer35"> delete: </a> 3.5 Transfers Between LIR Accounts Belonging to the Same Member delete: </h4> delete: <p> Transfers of Internet number resources between LIR accounts belonging to the same member fall within the scope of the RIPE Policy “ delete: <a href="http://www.ripe.net/publications/docs/transfer-policies" data-linktype="external" data-val="http://www.ripe.net/publications/docs/transfer-policies"> RIPE Resource Transfer Policies delete: </a> ” and will be evaluated in accordance with them. delete: </p> delete: <p> The procedure described above in Section 3.1 is applicable except from paragraphs 3.1.ii and 3.1.v. delete: </p> delete: <p> If after the transfer the member decides to close an LIR account, all outstanding invoices and all outstanding financial obligations for this LIR account must be paid in full. delete: </p> delete: <p> The RIPE NCC will review the status of any IP address allocation or independent Internet number resource assignment maintained by the member, in compliance with the RIPE Policies current at the time of the transfer. delete: </p> delete: <p> The member must deregister from the RIPE Database any invalid or overlapping registrations. delete: </p> delete: <p> The RIPE NCC will update the registry, including all RIPE Database objects maintained by the RIPE NCC that are related to this transfer. The member must update all RIPE Database objects maintained by them that are related to this transfer. delete: </p> delete: <p>   delete: </p> delete: <h3> delete: <a name="memberchanges"> delete: </a> 4.0 Member Changes Official Legal Name delete: </h3> delete: <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. delete: </p> delete: <p> The member must send an email to delete: <a href="mailto:ncc@ripe.net"> ncc@ripe.net delete: </a> informing the RIPE NCC of the name change. This email must include: delete: </p> delete: <ul> delete: <li> New registration papers from the national authority; and delete: </li> delete: <li> The official legal documents supporting this change delete: </li> delete: </ul> delete: <p> The RIPE NCC will send a new delete: <a href="http://www.ripe.net/publications/docs/service-agreement"> RIPE NCC Standard Service Agreement delete: </a> for the member to sign under the new official legal name. When the RIPE NCC receives the new RIPE NCC Standard Service Agreement properly signed by the member, it will update the registry, including all RIPE Database objects maintained by the RIPE NCC that are related to this change. The member must update all RIPE Database objects maintained by them that are related to this change. delete: </p> delete: <p> If the change in the member's official legal name occurred without a further change in the member's structure (e.g., merger with another legal entity, acquisition by/of another legal entity), the member will not have to sign a new RIPE NCC Standard Service Agreement. delete: </p> space. insert: </p>

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