Summary

Section 2.3.3.1 (Initial Allocations to ISPs) of the IPv4 policy establishes requirements that depend on the size of the requested prefix. It also requires renumbering and returning previously received addresses, if applicable (a small ISP receiving addresses from a larger ISP, from which it is now becoming ‘independent’).

In certain cases, the requirement to renumber and return such addresses may not make sense:

(1) Renumbering may not be convenient, and it might be preferable to 'hand over' the resources if both parties agree, with the corresponding changes in the whois database.
2) If the justified need for space is greater than the space currently available and its distribution is possible, the above allows the recipient of such space to decide whether they would like a single contiguous block, or whether they prefer to avoid renumbering and keep the current block plus another block with the additional allocated space.

This proposal seeks to simplify the requirements and allow these options.

Rationale (Describe the problem you intend to solve)

Simplifying is good if both parties agree. Likewise, avoiding renumbering is also good if feasible.

Current text

Current text:
o 2.3.3.1.1. Requirements for a /24 to /22 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.

o 2.3.3.1.2. Requirements for a /21 or shorter prefix (block of 8/24s or more)

Agree to renumber out of the blocks obtained from their providers within a period no longer than 12 months and return the space to its original provider.

New text:
o 2.3.3.1.1. Requirements for a /24 to /22 prefix
3. If a block has already been assigned by a provider and the user wishes to keep this block to avoid renumbering, such block may be handed over (changing the resource holder in Lacnic’s whois database) provided that both parties agree. If additional address space has been justified and its distribution is possible, the recipient may decide whether they prefer to receive the block that is handed over plus an additional block to complete the total required space, or whether they prefer to receive a single block for the total space and proceed to renumber their network. Should they choose to renumber, the block that had previously been assigned must be returned within 12 months. Exceptionally, this period may be extended by an additional 6 months if it can be justified that there was not enough time to obtain the required resources and complete the renumbering process.

o 2.3.3.1.2. Requirements for a /21 or shorter prefix (block of 8/24s or more)

If a block has already been assigned by a provider and the user wishes to keep this block to avoid renumbering, such block may be handed over (changing the resource holder in Lacnic’s whois database) provided that both parties agree. If additional address space has been justified and its distribution is possible, the recipient may decide whether they prefer to receive the block that is handed over plus an additional block to complete the total required space, or whether they prefer to receive a single block for the total space and proceed to renumber their network. Should they choose to renumber, the block that had previously been assigned must be returned within 12 months. Exceptionally, this period may be extended by an additional 6 months if it can be justified that there was not enough time to obtain the required resources and complete the renumbering process.

New text
Analyze diff

Current text:
o 2.3.3.1.1. Requirements for a /24 to /22 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.

o 2.3.3.1.2. Requirements for a /21 or shorter prefix (block of 8/24s or more)

Agree to renumber out of the blocks obtained from their providers within a period no longer than 12 months and return the space to its original provider.

New text:
o 2.3.3.1.1. Requirements for a /24 to /22 prefix
3. If a block has already been assigned by a provider and the user wishes to keep this block to avoid renumbering, such block may be handed over (changing the resource holder in Lacnic’s whois database) provided that both parties agree. If additional address space has been justified and its distribution is possible, the recipient may decide whether they prefer to receive the block that is handed over plus an additional block to complete the total required space, or whether they prefer to receive a single block for the total space and proceed to renumber their network. Should they choose to renumber, the block that had previously been assigned must be returned within 12 months. Exceptionally, this period may be extended by an additional 6 months if it can be justified that there was not enough time to obtain the required resources and complete the renumbering process.

o 2.3.3.1.2. Requirements for a /21 or shorter prefix (block of 8/24s or more)

If a block has already been assigned by a provider and the user wishes to keep this block to avoid renumbering, such block may be handed over (changing the resource holder in Lacnic’s whois database) provided that both parties agree. If additional address space has been justified and its distribution is possible, the recipient may decide whether they prefer to receive the block that is handed over plus an additional block to complete the total required space, or whether they prefer to receive a single block for the total space and proceed to renumber their network. Should they choose to renumber, the block that had previously been assigned must be returned within 12 months. Exceptionally, this period may be extended by an additional 6 months if it can be justified that there was not enough time to obtain the required resources and complete the renumbering process.

Additional information

For the purpose of LACNIC operations, “hand over” (ceder in the Spanish original) is equivalent to a simplification of the transfer process, under which section 2.3.2.18.5 does not apply. In any case, it would not be possible to apply this section as LACNIC has no resources available for organizations other than new-entrants.

Timetable

Immediate implementation

References

-

Presented at:

LACNIC 29 (30/04/2018)