11. Policies Relating to the Exhaustion of IPv4 Address Space

The following policies relate to the IPv4 address space exhaustion process.

11.1. Special IPv4 Allocations/Assignments Reserved for New Members

When IANA’s pool of IPv4 addresses is exhausted or when the remaining available space cannot be allocated to the RIRs and LACNIC has in its custody the equivalent of a /12, LACNIC will begin to apply exclusively the following criteria for allocating and assigning IPv4 addresses:

1. Only allocations larger than or equal to a /24 and smaller than or equal to a /22 will be made.
2. No allocations will be made to organizations that already have IPv4 addresses allocated by LACNIC or by the organizations that preceded LACNIC in the region currently serviced by LACNIC.
3. /22 blocks will only be allocated to new ISPs that have not been allocated IPv4 addresses by LACNIC or by their upstream providers, and that can prove the need for at least a /24 during the following 12 months.
4. /24 blocks will be assigned to critical infrastructure with no other requirement than that of being critical infrastructure in accordance with the definitions contained in LACNIC’s policies. These organizations may receive up to a /22 if they can prove their need during the following 12 months.
5. Those organizations that receive IPv4 addresses from LACNIC under the conditions established in items 3 and 4 of the present policy will not be able to receive future IPv4 allocations or assignments from LACNIC.
6. If the applicant does not already have an IPv6 address block assigned by LACNIC, it must also request an IPv6 address block in accordance with the corresponding applicable policy.

1.1.2 Allocations/Assignments for Gradual IPv4 Resource Exhaustion

1. LACNIC will create a reserve equivalent to a /12 block of IPv4 addresses 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 /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 that receive IPv4 resources under the terms set forth in the following policy may receive additional IPv4 resources from LACNIC six months later, 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.
6. Those organizations that receive IPv4 resources from LACNIC under the terms set forth in the following policy may not receive future IPv4 resource allocations or assignments from LACNIC for a period of 6 months.
7. 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 one year. The same applies to its sub-blocks, i.e. blocks consisting of a subset of the IPv4 addresses contained in the block.
8. 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.