This proposal solves cases where a text appears in the IPv4 or IPv6 sections, yet clearly applies to all resources.

It separates the definitions from the general rules that apply to various resources or procedures.

The section on IPv4 includes several subsections that clearly apply equally to IPv4, IPv6, and even ASN resources. The same can be said about the section on IPv6. It is therefore reasonable to move these texts to a new Section 1 (General Rules) which includes the general rules that are in the current Section 1 (Definitions), renumbering the rest of the definitions as Section 0.

These are minor editorial changes and not intended to modify any operational aspects.

1. Definitions

2.3.2.5 Documentation
Internet Registries shall use the IPv4 addresses they have been allocated in an efficient manner. To this end, the IRs shall document the justification for each IPv4 address assignment. At the request of LACNIC, the corresponding IR shall make this information available. LACNIC shall not make complementary allocations to those Internet Registries that have not properly documented the use of the blocks they have already been allocated. In these cases, existing allocations may also be reviewed.

The documentation LACNIC may request includes:
• Engineering plans.
• Subnetting and aggregation plan.
• Description of network topology.
• Description of network routing plans.
• Receipts documenting investments (equipment).
• Other relevant documents.

1.14. Principles for Proper Administration and Stewardship

1.15. Resource requests

2.3.2.14. Security and Confidentiality
LACNIC shall maintain systems and practices that safeguard and protect the confidentiality of all the information entrusted to LACNIC in the documentation submitted to justify the allocation or assignment of IPv4 addresses.

2.3.2.15. Equal Processing of All Applications
LACNIC shall process every application strictly in the order in which they are received, regardless of geographical factors, demographic factors, language, etc. Under no circumstance shall LACNIC grant special treatment or make exceptions to the norm established for the processing of applications. For this purpose, LACNIC shall use an application numbering system that will allow their proper administration.

1.11 Non-Guaranteed Routability
Neither LACNIC nor the NIRs will guarantee the routability of allocated or assigned addresses.

Resource recipients are responsible for negotiating such routability with their connectivity providers. LACNIC shall provide the corresponding guidance when necessary.
However, allocated or assigned resources must be announced within a maximum of 90 days, except in those cases where the need not to announce the resources is justified.

RIRs must apply operational procedures that reduce the possibility of fragmentation of the address space to minimize the risk of loss of routability.

1.13. RPKI ROAs with Origin ASN 0

2.3.2.13.2 Geolocation
In addition to the information available in the WHOIS database, the assignments made by LACNIC and the sub-assignments made by its members will be published in a file along with information on the country in which the prefix was assigned. This file will be available for the community to download freely. Among other uses, this file may be used to geolocate an IP address.

The file format and the place where it will be published will be defined by the LACNIC staff.

0. Definitions
(Renumber current Section 1 as 0, and maintain the text in current subsections 1.1 to 1.10 and 1.12 as 0.1 to 0.11)

1. General Rules
(New section that allows separating the definitions from those rules that are common to various types of resources or procedures.)

1.1 Documentation

Internet Registries shall use the Internet resources they have been allocated or assigned in an efficient manner. To this end, the IRs shall document the justification for each allocation of assignment.

At the request of LACNIC, the corresponding IR shall make this information available. LACNIC shall not make complementary allocations or assignments to those Internet Registries that have not properly documented the use of the blocks they have already been allocated or assigned. In these cases, existing allocations or assignments may also be reviewed.

The documentation LACNIC may request includes:
• Engineering plans.
• Subnetting and aggregation plan.
• Description of network topology.
• Description of network routing plans.
• Receipts documenting investments (equipment).
• Other relevant documents.

1.2. Principles for Proper Administration and Stewardship
(No changes to the text)

1.3. Resource Requests
(No changes to the text)

1.4. Security and Confidentiality
LACNIC shall maintain systems and practices that safeguard and protect the confidentiality of all the documentation presented to LACNIC to justify resource requests.

1.5. Equal Processing of All Applications
LACNIC shall process each application strictly in the order in which they are received, regardless of geographical factors, demographic factors, language, etc.

Under no circumstance shall LACNIC grant special treatment or make exceptions to the norm established for application processing. For this purpose, LACNIC shall use an application numbering system that will allow their proper administration.

1.6. Non-Guaranteed Routability
Neither LACNIC nor the NIRs will guarantee the routability of allocated or assigned addresses.

Resource recipients are responsible for negotiating such routability with their connectivity providers. LACNIC shall provide the corresponding guidance when necessary.

However, the allocated or assigned resources must be announced (within a maximum of 3, 12, and 6 months in the case of IPv4, IPv6, and ASN resources, respectively), except in those cases where the need not to announce the resources is justified.

RIRs must apply operational procedures that reduce the possibility of fragmentation of the address space to minimize the risk of loss of routability.

1.7. RPKI ROAs with Origin ASN 0
(No changes to the text)

1.8. Geolocation
In addition to the information available in the WHOIS database, the assignments made by LACNIC and the sub-assignments made by its members will be published in a file along with information on the country in which the prefix was assigned. This file will be available for the community to download freely. Among other uses, this file may be used to geolocate an IP address.

The file format and the place where it will be published will be defined by the LACNIC staff.

The proposed numbering is not set in stone, and the staff may renumber or rearrange some of the sections if it believes that it would make more sense from an editorial point of view.

-

-

LACNIC 38 (04/10/2022)