Update to the Policy on IPv4 Assignments to End Users

Original Language Español Date Published 29/03/2018 Last Modified 22/03/2018
Last Call for Comments Period Does not apply Date Ratified Does not apply Implementation Date Does not apply
Status Under discussion Download TXT PDF XML DOCX
See other versions 1.0 (compare)

Authors

Name: Jordi Palet Martinez
Email: jordi.palet@consulintel.es
Organization: The IPv6 Company

Proposal Data

Policy Type: LACNIC
Id: LAC-2018-8
Last version: 1

Summary

Section 2.3.3.4.3 (Applicant Status) of the IPv4 policy on direct assignments by LACNIC to end users assesses different requirements depending on whether an applicant is a multi-homed end user or planning to become one.

There are several reasons why evaluating this requirement does not make sense:

1) In many cases applicants may need stable addressing but may be unable to use NAT and private addresses, regardless of their multihoming status, particularly considering current SLA levels.
2) In some cases, multihoming is not a viable option because of the costs involved, particularly in remote areas where a single provider may be available.
3) The IPv6 policy has long since eliminated the multihoming requirement, so there is no point in including it in the case of IPv4.

This proposal seeks to simplify this evaluation and remove these barriers by unifying the requirements regardless of whether applicants use multihoming.

Rationale

Having different requirements for IPv4 and for IPv6 seems senseless, particularly considering how technologies and SLA levels have improved, meaning that in many cases there may be less need for multihoming.

Text

Current text:

O 2.3.3.4.3. Applicant Status
In addition, the applicant's multihomed or non-multihomed status also affects the evaluation of the application.

If the applicant is a multi-homed end user or can prove interconnection needs with other autonomous systems:

The size of the minimum IPv4 address assignment to a multihomed end user is a /24, while the maximum is a /21. In order to qualify for a block, the applicant must also satisfy the following requirements:

o If the user is not yet multihomed but is planning to become multihomed within a six-month window, or if the user is planning to establish interconnections with other autonomous systems during this window, a detailed justification must be presented.
o Justify the requested block size according to the utilization rate (section 2.3.3.4.2).
o Agree to renumber all blocks assigned by other ISPs within three months and return them to their original ISPs.

Requests for blocks larger than a /21 must also comply with the additional requirements established for non-multihomed end users as described below.

If the applicant is a non-multihomed end user:

The minimum size of IPv4 assignments to a non-multihomed end user is a /20 block. If their IPv4 addressing needs are lower than a /20, non-multihomed end users will need to contact their ISPs in order to obtain addresses.

In order to assign a /20 to an end user, the following requirements must also be met:

Have received a minimum assignment of 8 /24 prefixes from its Internet Service Provider.

Agree to renumber out of the previously assigned space within a period of 12 months and return it to its original provider. This requirement is mandatory for obtaining the requested /20 prefix. The assigned /20 prefix must be used to renumber out of the addressing previously assigned by its provider.

Additional assignments shall follow the policies set forth in Section 2.3.4 applicable to end users.

New text:

o 2.3.3.4.3. Assignment size and procedure
The applicant must justify that the assigned space will be announced from the applicant’s own autonomous system to at least one other autonomous system.

The minimum size of an IPv4 assignment to an end user is a /24 block; the maximum size is a /20, which must be justified according to the utilization rate (section 2.3.3.4.2).

If a block had already been assigned by a provider and the user wishes to keep this block to avoid renumbering, such block may be handed over (making the corresponding changes in the whois database) provided that both parties agree. If additional address space has been justified and its assignment 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. Should they choose to renumber, the block that had been previously assigned must be returned within 6 months.

Additional assignments shall follow the policies set forth in Section 2.3.4 applicable to end users.

Additional Information

-

Timetable

Immediate implementation

References

Other RIRs do not require multihoming, but simply justifying the need for additional address space.