7. RESOURCE REVOCATION AND RETURN
The PDF document hosted on this page is the authoritative version of the Policy Manual. The web version is provided to make it easier for readers to quickly browse the different sections of the Manual.
In the event of a conflict between the web version and the pdf version of the Manual, the pdf version shall control.
This document and/or information was originally written in Spanish, the official language of Uruguay, the country where LACNIC is legally incorporated and whose laws and regulations LACNIC must meet. Likewise, unofficial information and/or documents are also written in Spanish, as this is the language in which most of LACNIC's collaborators and officers work and communicate. We do our best to ensure that our translations are reliable and serve as a guide for our non-Spanish-speaking members. However, discrepancies may exist between the translations and the original document and/or information written in Spanish. In this case, the original text written in Spanish will always prevail.
Resource allocations and assignments will remain valid as long as the objectives of exclusivity, preservation, routability, information, and the rest of the policies in general continue to be met.
Therefore, LACNIC may invalidate any allocation or assignment if it is determined that the requirements no longer exist or that the criteria set forth in the Policy Manual are no longer satisfied.
The following may be considered grounds for resource revocation:
o Unused or unannounced resources (where mandatory).
o Failure to maintain reverse resolution records for the assigned resources.
o Failure to update the allocation and assignment information on the whois database managed by LACNIC or the NIRs, as applicable.
o Unauthorized transfers.
o Repeated and/or continued policy violations.
o Failure to comply with contractual obligations towards LACNIC or its NIRs, including non-payment and document fraud.
o Organizations that have disappeared or fail to respond.
When the violation has been caused by a third party, without the knowledge of the organization receiving the resources, and if it is evident that there is no collusion or negligence on the part of said organization, the revocation process will not be initiated.
To ensure the efficient utilization of regional resources, LACNIC will verify that the organizations receiving resources are using such resources correctly. This will be done automatically whenever possible and more exhaustively when there is evidence to suggest that certain resources are not being used properly.
Once the evidence has been detected and confirmed, the resource recovery process will include the following steps:
- a) LACNIC shall attempt to contact the organization and rectify the situation.
- b) If the situation cannot be rectified, LACNIC shall publish the resources that are to be recovered for a maximum of three months.
During this period, the organization may rectify the situation with LACNIC.
- c) In all other cases, two months after the resources are published, LACNIC shall proceed to delete the NS records pointing to the authoritative nameservers of the resources involved This information may be recovered once the organization reestablishes contact with LACNIC or with the corresponding NIR.
- d) If three months after the resources are published the organization has not rectified the situation, the resources shall be recovered and the records of the holders of these resources shall be removed from LACNIC’s database.
- e) All other provisions specified in the Registration Services Agreement and Bylaws shall apply.
When the revocation of resources involves essential strategic infrastructure that is necessary for the operation of the Internet in the region, or in exceptional situations such as natural disasters or political instability, the LACNIC Board of Directors may extend the resource revocation period, with prior assessment by the LACNIC Staff once such an exceptional situation is detected.
Resource recipients may return the resources to LACNIC, in full or in part, at any time.
If all the resources are returned, all the other provisions specified in the Registration Services Agreement and Bylaws shall apply.
LACNIC shall publish the resources that have been recovered or returned so that the corresponding routing filters may be updated.
IPv4 resources will be added at the “end” of the pool in use at the moment of their recovery or return, and will be used in the order in which they have been added to the pool.
IPv6 and ASN resources will be added to their respective pools in force two years after their recovery or return.
However, LACNIC may use these resources differently, applying best best practices to optimize compliance with the provisions of section 2 of RFC7020. For example, if 16-bit ASNs are recovered or returned.”