Eliminate the ASN Requirement for End Users

Original Language Español Date Published 29/10/2019 Last Modified 28/10/2019
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: Edmundo Cazarez-Lopez
Email: edmundo.cazarez@nic.mx
Organization: NIC México

Proposal Data

Policy Type: LACNIC
Id: LAC-2019-11
Last version: 1

Summary

This proposal seeks to eliminate the requirement according to which end users must have an AS to make use of the addresses they are assigned.

Rationale

The current text of the policy implies that end users must have an AS in order to make use of the addresses they are assigned. In fact, many end users find themselves in scenarios where they have no need for an AS and can make an informed decision to not have an AS or use one. Likewise, we have also encountered cases where the AS assigned to an end user are not in use.
Some end users see the requirement for an ASN simply as an additional charge for address assignments.

Text

The proposal modifies the text of subsection 2.3.3.4.3.:

It eliminates the first paragraph of the current text and the heading of the subsection.

---- Current text: -----

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).

...

---- Proposed text: ----

2.3.3.4.3 - Assignment size

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).

...

Additional Information

`-

Timetable

Immediate implementation once the proposal reaches consensus and is ratified by the Board.

References

-

Public Comments by LACNIC Staff

LACNIC STAFF´S IMPACT ANALYSIS - Proposal LAC-2019-11 - versión 1

LACNIC Staff's Interpretation of the Proposal
---------------------------------------------

Applicability
------------
This proposal would apply in the case of initial IPv4 assignments to end users.

Modifications to the current text
--------------------------------
The proposal eliminates the following text in section 2.3.3.4.3 of the Policy Manual:
“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.”

LACNIC Staff's Comments
--------------------------
(Comments are observations intended to help distinguish the changes presented in the proposal from the current text of the Policy Manual)

1. The proposal eliminates the text that requires justifying that the assigned space will be announced from an autonomous system held by the applicant.

Impact of the policy on the registry system
--------------------------------------------
This proposal would require minor changes to LACNIC's registry system.

Official Sources
----------------
Other RIRs

- AFRINIC, APNIC, ARIN and RIPE
The other RIRs do not require end users to announce the requested IPv4 block from their own ASN.

- APNIC
The policies in force in the APNIC region require justifying the need at the time of requesting the resources. However, once the space has been delegated, there are no policies to specify how their resources must be used in their own networks.

- RIPE
The general position of the RIPE Community is that the registry should not be involved in decisions on how to operate a network.

Privacy Policy