11. POLICIES RELATING TO THE EXHAUSTION OF IPv4 ADDRESS SPACE

Important notes:

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.

The following policies relate to the IPv4 address space exhaustion process

11.1.Special IPv4 Allocations/Assignments Reserved for New Members

  1. LACNIC will create an IPv4 reserve using the space allocated by the IANA to LACNIC post-IPv4 exhaustion, also considering the recovered and returned space mentioned in Section 7 of the Policy Manual.
  2. No IPv4 allocations or assignments will be made to organizations that have already been assigned or allocated IPv4 resources by LACNIC or by the organizations that preceded LACNIC in the region currently serviced by LACNIC.
  3. Under this policy, IPv4 address requests classified as critical infrastructure according to the LACNIC policies in force may receive addresses, even if they have already been assigned IPv4 resources by LACNIC.
  4. LACNIC may only make IPv4 allocations or assignments greater than or equal to a /24 and smaller than or equal to a /22 from this reserve pool.
  5. LACNIC will only allocate or assign resources from this reserve after approval of the first IPv4 address request that cannot be satisfied in full due to lack of IPv4 resources in the LACNIC region.
  6. Once this policy comes into force, IPv4 resource applications smaller than a /22 that are pending approval may only receive a /22
  7. Those organizations that receive IPv4 resources under the terms set forth in the following policy may not receive from LACNIC additional IPv4 resources that are part of this reserve, with the exception of requests for critical infrastructure.
  8. Blocks received under this policy may not be transferred as specified in paragraph 2.3.2.18 of the policy manual for a period of three years. The same applies to its sub-blocks, i.e., blocks consisting of a subset of the IPv4 addresses contained in the block.
  9. This policy does not replace section 11.1 of the Policy Manual. The reserve created under section 11.2 is independent from the reserve created under the following policy.
  10. If the applicant has not already been assigned an IPv6 address block by LACNIC, it must also request an IPv6 address block in accordance with the applicable policy.


11.2.Allocations/Assignments for Gradual IPv4 Resource Exhaustion

  1. LACNIC will create a reserve of IPv4 addresses equivalent to a /10 block for the purpose of achieving gradual exhaustion of IPv4 resources within the LACNIC region.
  2. LACNIC may only make IPv4 allocations or assignments greater than or equal to a /24 and smaller than or equal to a /22 from this reserve pool.
  3. LACNIC will only allocate or assign resources from this reserve after approval of the first IPv4 address request that cannot be satisfied in full due to lack of IPv4 resources in the LACNIC region.
  4. Once this policy comes into force, IPv4 resource applications smaller than a /22 that are pending approval may only receive a /22.
  5. Organizations receiving IPv4 resources under the terms set forth in the following policy may receive additional IPv4 resources from LACNIC after a period of six months, provided that they generate a new request that justifies the need for additional IPv4 resources according to the IPv4 address allocation or assignment policies in force. Organizations requesting address blocks for critical infrastructure may request up to a /22 at any time.
  6. Blocks received under this policy may not be transferred as specified in paragraph 2.3.2.18 of the policy manual for a period of three years. The same applies to its sub-blocks, i.e., blocks consisting of a subset of the IPv4 addresses contained in the block.
  7. This proposal does not replace section 11.1 of the Policy Manual. The reserve created under section 11.1 is independent from the reserve created under this proposal.

11.3.Post-Exhaustion IPv4 IANA-distributed Allocations/Assignments

Resources allocated by IANA to LACNIC once item 11.2 of the Policy Manual becomes effective will only be allocated / assigned under the guidelines set forth on item 11.1 of the Policy Manual.

CHK_LACNIC