Modify the minimum size of initial allocations to ISPs

LAC-2017-4-v1 LAC-2017-4-v2 Vs
Referencias:
Nuevo
Eliminado
Modificado
Autores

Name: Evandro Antonio Ramos Terra Varonil de Sousa
Email: evandro@varonil.com.br
Organization: ABRANET, ABRINT, FASTERNET

Name: Evandro Antonio Ramos Terra Varonil de Sousa.
Email: evandro@varonil.com.br
Organization: ABRANET, ABRINT, ISOC.BR, SEINESP, FASTERNET

Resumen

This policy proposal seeks to modify the minimum size of initial IPv4 address allocations to Internet Service Providers
established in the LACNIC region, changing it from the current /22 to a /24.

This policy proposal seeks to modify the minimum size of initial IPv4 address allocations to Internet Service Providers
established in the LACNIC region, changing it from the current /22 to a /24.

Justificación

Considering that the LACNIC region has entered the final phase of IPv4 Exhaustion (Phase 3), I believe it no longer make
s sense for the minimum size of an allocation to be a /22 prefix. By reducing this minimum allocation to a /24 we will a
llow the entrance of new ISPs.
We should bear in mind that, according to section 2.3.3.4.3 of the Policy Manual, the minimum size of IPv4 assignments t
o end users is already a /24.
When a company is created, in addition to complying with the requirements of its national government, fiscal and regulat
ory systems, the Internet Service Provider may begin planning and operating its ISP as an Autonomous System (AS) with IP
v4 and IPv6 address blocks that will allow them to start a small yet sustainable operation.
This allocation of a /24 prefix is also the minimum IPv4 size commonly accepted by Internet edge routers, so this smalle
r size will also allow new entrants to operate on the Internet using IPv4 prefixes.
This change is also justified because it will allow new ISPs to obtain a minimum IPv4 block, possibly for the purpose of
applying IPv4 translation techniques and transitioning to IPv6 as its network grows.

Considering that the LACNIC region has entered the final phase of IPv4 Exhaustion (Phase 3), I believe it no longer make
s sense for the minimum size of an allocation to be a /22 prefix. By reducing this minimum allocation to a /24 we will a
llow the entrance of new ISPs.
We should bear in mind that, according to section 2.3.3.4.3 of the Policy Manual, the minimum size of IPv4 assignments t
o end users is already a /24.
When a company is created, in addition to complying with the requirements of its national government, fiscal and regulat
ory systems, the Internet Service Provider may begin planning and operating its ISP as an Autonomous System (AS) with IP
v4 and IPv6 address blocks that will allow them to start a small yet sustainable operation.
This allocation of a /24 prefix is also the minimum IPv4 size commonly accepted by Internet edge routers, so this smalle
r size will also allow new entrants to operate on the Internet using IPv4 prefixes.
This change is also justified because it will allow new ISPs to obtain a minimum IPv4 block, possibly for the purpose of
applying IPv4 translation techniques and transitioning to IPv6 as its network grows.

Texto

Current text:
2.3.3.1- Initial Allocations to ISPs
The minimum initial allocation size applicable to Internet Service Providers established within LACNIC's service region
is a /22.
2.3.3.1.1 Requirements for a /22 prefix (block of 4/24s)
In order to qualify for the allocation of a /22 prefix, the requesting ISP must satisfy the following requirements:
1. Prove utilization or immediate necessity of a /24.
2. Submit a detailed one-year utilization plan for a /23.
3. Agree to renumber out of the previously assigned block and return those IPv4 addresses to their ISPs no later than 12
months after the allocation of the /22.
4. If the applicant does not already have an IPv6 block assigned by LACNIC, simultaneously request an IPv6 block in acco
rdance with the applicable policy.
Proposed text:
2.3.3.1- Initial Allocations to ISPs
The minimum initial allocation size applicable to Internet Service Providers established within LACNIC's service region
is a /24.
2.3.3.1.1- Requirements for a /24 prefix
In order to qualify for the allocation of a /24 prefix, the requesting ISP must satisfy the following requirements:
1. Prove utilization or immediate necessity of at least 25% of the requested prefix.
2. Submit a detailed one-year utilization plan for the requested prefix.
3. Agree to renumber out of the previously assigned block and return those IPv4 addresses no later than 12 months after
the date on which the requested block was allocated.
4. If the applicant does not already have an IPv6 block assigned by LACNIC, simultaneously request an IPv6 block in acco
rdance with the applicable policy.

Current text:
2.3.3.1- Initial Allocations to ISPs
The minimum initial allocation size applicable to Internet Service Providers established within LACNIC's service region
is a /22.
2.3.3.1.1 Requirements for a /22 prefix (block of 4/24s)
In order to qualify for the allocation of a /22 prefix, the requesting ISP must satisfy the following requirements:
1. Prove utilization or immediate necessity of a /24.
2. Submit a detailed one-year utilization plan for a /23.
3. Agree to renumber out of the previously assigned block and return those IPv4 addresses to their ISPs no later than 12
months after the allocation of the /22.
4. If the applicant does not already have an IPv6 block assigned by LACNIC, simultaneously request an IPv6 block in acco
rdance with the applicable policy.
Proposed text:
2.3.3.1- Initial Allocations to ISPs
The minimum initial allocation size applicable to Internet Service Providers established within LACNIC's service region
is a /24.
2.3.3.1.1- Requirements for a /24 to /22 prefix
In order to qualify for the allocation of a /24 to /22 prefix, the requesting ISP must satisfy the following requirement
s:
1. Prove utilization or immediate necessity of at least 25% of the requested prefix.
2. Submit a detailed one-year utilization plan for at least 50% of the requested prefix.
3. Agree to renumber out of the previously assigned block and return those IPv4 addresses no later than 12 months after
the date on which the requested block was allocated.
4. If the applicant does not already have an IPv6 block assigned by LACNIC, simultaneously request an IPv6 block in acco
rdance with the applicable policy.

Información Adicional

Based on information obtained from the NIRs, I believe this change in policy will benefit small ISPs throughout Latin Am
erica and the Caribbean.

Based on information obtained from the NIRs, I believe this change in policy will benefit small ISPs throughout Latin Am
erica and the Caribbean.

Referencias

ARIN NUMBER RESOURCE POLICY MANUAL
4.2.1.5. Minimum allocation
In general, ARIN allocates /24 and larger IP address prefixes to ISPs. If allocations smaller than /24 are needed, ISPs
should request address space from their upstream provider.

ARIN NUMBER RESOURCE POLICY MANUAL
4.2.1.5. Minimum allocation
In general, ARIN allocates /24 and larger IP address prefixes to ISPs. If allocations smaller than /24 are needed, ISPs
should request address space from their upstream provider.