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 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. ripe-085: Guidelines For The Delegation Of Zones In The 193.in-addr.arpa Domai
delete: <h2> Abstract delete: </h2>

Introduction insert: <br />
insert: <br />
This document provides describes the procedures for the delegation of au- insert: <br />
thority of zones in the 193.in-addr.arpa domain. As of March insert: <br />
16th 1993 the RIPE NCC has been delegated the authority for the insert: <br />
193.in-addr.arpa domain from the root. Due to the fact that in insert: <br />
the 193.x.y address space blocks of 256 class C network numbers insert: <br />
are further delegated to local registries , the possibility ex- insert: <br />
ists to also delegate the zone for these blocks in the 193.in- insert: <br />
addr.arpa domain. This document describes some guidelines to Local Internet Registries (LIRs) and insert: <br />
procedures for this type of delegation and the delegation of re- insert: <br />
verse zones for individual class C networks in 193.x.y. insert: <br />
insert: <br />
insert: <br />
A bit more explained insert: <br />
insert: <br />
With the assignment of class C network numbers following the CIDR insert: <br />
(RFC 1338) model, in which large chunks of the address space are insert: <br />
delegated to one region, and within that region blocks of class C insert: <br />
network numbers are delegated to service providers and non- insert: <br />
provider registries, some hierarchy in the address space is insert: <br />
created, similar to the hierarchy in the domain name space. Due insert: <br />
to this hierarchy the reverse Domain Name System mapping can also insert: <br />
be delegated in a similar model as used for the normal Domain insert: <br />
Name System. For instance, the RIPE NCC has been assigned the insert: <br />
complete class C address space starting with 193. It is there- insert: <br />
fore possible to delegate the 193.in-addr.arpa domain completely insert: <br />
to the RIPE NCC, instead of each and every reverse mapping in the insert: <br />
193.in-addr.arpa domain to be registered with the INTERNIC. This insert: <br />
implies that all 193.in-addr.arpa resistrations will be done by insert: <br />
the RIPE NCC. Even better, since service providers receive com- insert: <br />
plete class C network blocks from the RIPE NCC, the RIPE NCC can insert: <br />
delegate the reverse registrations for such complete blocks to insert: <br />
these local registries. This implies that customers of these insert: <br />
service providers no longer have to register their reverse domain insert: <br />
mapping with the root, but the service provider have authority insert: <br />
over that part of the reverse mapping. This decreases the work- insert: <br />
load on the steps to take when the organisation operating an LIR INTERNIC and the RIPE NCC, and at the same time in- insert: <br />
crease the service a provider can offer its customers by improve insert: <br />
response times for reverse mapping 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 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 . However there are financial, IP insert: <br />
some things that need to be examined a bit more closely to avoid insert: <br />
confusion and inconsistencies. These issues are covered in the insert: <br />
next section. insert: <br />
insert: <br />
insert: <br />
Procedures for the delegation of direct subdomains of 193.in- insert: <br />
addr.arpa insert: <br />
insert: <br />
1. A secondary nameserver at ns.ripe.net is mandatory for all insert: <br />
blocks of class C network numbers delegated in the 193.in- insert: <br />
addr.arpa domain. insert: <br />
insert: <br />
2. Because of the increasing importance of correct reverse ad- insert: <br />
dress mapping, for all delegated blocks a good set of secondaries insert: <br />
must be defined. There should be at least 2 nameservers for all insert: <br />
blocks delegated, excluding the RIPE NCC secondary. insert: <br />
insert: <br />
3. The delegation of a class C block in the 193.in-addr.arpa insert: <br />
domain can be requested by sending in a domain object for the insert: <br />
RIPE database to <hostmaster@ripe.net> with all necessary contact insert: <br />
and nameserver information. The RIPE NCC will then forward all insert: <br />
current reverse zones inside this block to the registry, and insert: <br />
after addition of these by the registry, the NCC will check the insert: <br />
working of the reverse server. Once everything is setup proper- insert: <br />
ly, the NCC will delegate the block, and submit the database ob- insert: <br />
ject for inclusion in the database. An example domain object can insert: <br />
be found at the end of this document. insert: <br />
insert: <br />
4. All reverse servers for blocks must be reachable from the insert: <br />
whole of the Internet. In short, all servers must meet similar insert: <br />
connectivity requirements as top-level domain servers. insert: <br />
insert: <br />
5. Running the reverse server for class C blocks does not imply insert: <br />
that one controls that part of the reverse domain, it only im- insert: <br />
plies that one administers that part of the reverse domain. insert: <br />
insert: <br />
6. Before adding individual nets, the administrator of a reverse insert: <br />
domain must check wether all servers to be added for these nets insert: <br />
are indeed setup properly. insert: <br />
insert: <br />
7. There are some serious implications when a customer of a ser- insert: <br />
vice provider that uses 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 out of the service provider insert: <br />
class C blocks, moves to another service provider. The previous insert: <br />
service provider cannot force its ex-customer to 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 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 RIPE NCC network insert: <br />
addresses, and will review the status of any IP address allocations 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 an organisation operating an LIR changes ownership, a new service agreement may need to be signed. The RIPE NCC will need to request a new service agreement from the new owners if: delete: </p> delete: <ul> delete: <li> The organisation operating the LIR changes name, or delete: </li> delete: <li> The LIR wishes to change 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 have to 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 an organisation operating an LIR takes over one or more LIRs, confirmation of the takeover from all parties involved or their legal successors must be included. delete: </p> delete: <h3> 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 to 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 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 the appropriate insert: <br />
delegation records for reverse mapping of 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 from one LIR to another LIR (or to a non-LIR) require approval by the RIPE NCC. It is expected that all database objects relating to this allocation be correct and up-to-date before the transfer occurs. Transferred allocations containing a large amount of unassigned address space may be set aside and kept by the RIPE NCC until the other allocations held by the LIR are considered fully used (about 80%). Once the LIR has reached full utilisation in its other allocations, the reserved allocations will be made available to the LIR. For further details on allocation policy, please refer to the document "IPv4 Address Allocation and Assignment Policies in the RIPE NCC Service Region" available from the RIPE Document Store at: delete: <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 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 addresses, even insert: <br />
though it they 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 belonging to a customer. insert: <br />
insert: <br />
8. The registration of the reverse zones for individual class C insert: <br />
networks will continue to be billed for services until a formal request to be closed is sent usually be done by a registered contact person(s) of the LIR. delete: <br /> delete: <br /> In cases of mergers, the LIR whose allocation the registry administering the insert: <br />
class C block this network has been transferred to another LIR assigned from. The registry insert: <br />
will continue to be billed until make the necessary changes to the zone, and update the net- insert: <br />
work objects in the RIPE database for these networks, to reflect insert: <br />
the correct "rev-srv" fields. In case the RIPE NCC receives a insert: <br />
request for the reverse zone of an individual class C network out insert: <br />
of a block that has been delegated, the request will be forwarded insert: <br />
to the zone contact for this reverse block. insert: <br />
insert: <br />
9. The NCC advises the following timers and counters for direct insert: <br />
subdomains of 193.in-addr.arpa: 8 hours refresh (28800 seconds), insert: <br />
2 hours retry (7200 seconds), 7 days expire (604800 seconds) and insert: <br />
1 day Time To Live (86400 seconds). The retry counter should be insert: <br />
lowered where connectivity is unstable. insert: <br />
insert: <br />
Above procedures are defined to ensure the necessary high availa- insert: <br />
bility for the 193 reverse domains, and to minimize confusion. insert: <br />
The NCC will ensure fast repsonse times for addition requests, insert: <br />
and will in principle update the 193.in-addr.arpa domain at least insert: <br />
once per working day. insert: <br />
insert: <br />
Example domain object to request a block delegation insert: <br />
insert: <br />
domain: 202.193.in-addr.arpa insert: <br />
descr: Pan European Organisations class C block insert: <br />
admin-c: Daniel Karrenberg insert: <br />
tech-c: Marten Terpstra insert: <br />
zone-c: Marten Terpstra insert: <br />
nserver: ns.eu.net insert: <br />
nserver: sunic.sunet.se insert: <br />
nserver: ns.ripe.net insert: <br />
changed: marten@ripe.net 930319 insert: <br />
source: RIPE insert: <br />
insert: <br />
insert: <br />
insert: <br />
Procedures for the delegation of individual network zones by the insert: <br />
RIPE NCC. insert: <br />
insert: <br />
The registration of the reverse zones for individual class C net- insert: <br />
works will usually be done by the registry administering the insert: <br />
class C block this network has been assigned from. In case the insert: <br />
zone corresponding to the class C block has not been delegated, insert: <br />
the RIPE NCC will automatically add the reverse nameserver as insert: <br />
specified in the "rev-srv" attribute of the RIPE database object insert: <br />
for this network, using the following procedures: insert: <br />
insert: <br />
1. Because of the increasing importance of correct reverse ad- insert: <br />
dress mapping, for all delegated networks a good set of secon- insert: <br />
daries must be defined. There should be at least two nameservers insert: <br />
for all networks delegated. insert: <br />
insert: <br />
2. The "rev-srv" field should ONLY contain one fully qualified insert: <br />
domain name of a nameserver which is authoritative for the re- insert: <br />
verse zone for this network. insert: <br />
insert: <br />
3. If a network has or is going to have any inconsistencies are resolved. delete: </p> delete: <h3> delete: <a id="3.3" name="3.3"> delete: </a> 3.3 Transfers of Address Allocations external connectivi- insert: <br />
ty, it is strongly recommended that it has at least one reverse insert: <br />
nameserver that can be reached 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 of the Internet. insert: <br />
insert: <br />
4. The checking and addition of the reverse zones for single net- insert: <br />
works is completely automated at the RIPE NCC. Although we do insert: <br />
our best to check the setup of the nameservers, these does not insert: <br />
receive the same level of scrutiny 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. nameservers for blocks of insert: <br />
class C network numbers. It is the LIR's responsibility to help its End Users with renumbering. of the network insert: <br />
contacts to ensure proper operation. insert: <br />
insert: <br />
5. Any problems regarding the reverse zones in 193.in-addr.arpa insert: <br />
should be directed to <hostmaster@ripe.net>. insert: <br />
insert: <br />
The NCC also suggests that similar procedures are set up for the insert: <br />
delegation of reverse zones for individual class C networks from insert: <br />
the registries to individual organisations.

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 Guidelines For The Delegation Of Zones In The 193.in-addr.arpa Domain
RIPE Documents Search