Name: Jordi Palet Martínez
Email: jordi.palet@theipv6company.com
Organization: The IPv6 Company

Name: Jordi Palet Martínez
Email: jordi.palet@theipv6company.com
Organization: The IPv6 Company

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

This proposal solves cases where a text appears in the sections on IPv4 or IPv6 sections, yet clearly applyies 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 apply equally to IPv4, IPv6, and even ASN resources, so the reasonable thing to do would be to move these texts to Section 1, Definitions. The same can be said about the section on IPv6.

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 thingese texts to doa new Section 1 (General Ruldes) bwhich includes tohe movgeneral rules thesat are in thexts currento Section 1, (Definitions), renumbering the rest of the definitions as Section 0.

The se are minor editorial chan bges saind abnout inthended secto modiofy any operational IPv6aspects.

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.

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

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.

4.4.2 Non-Guaranteed Routability

There is no guarantee that any address allocation or assignment will be globally routable.
However, RIRs must apply procedures that reduce the possibility of fragmented address space which may lead to a loss of routability.

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.

2.3.21.134.2 Geolocation

In addition to the infoPrmation avacilabple in the WHOIS database, the assignmentsfor madPrope byr LACNIC and the sub-assignments made by its members will be published in a file along wisth information on the country in which the prefix was assigned. This file will be available for Sthe community to download freely. Among other udses, this file may be used to geolocate an IP address. p

The1.15. filRe fsourmat and the place where it will be pqublished will be defined by the LACNIC staff s

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.

41.413.2 RPKI ROAs with Origin ASN 0

2.3.2.13.2 Geolocation-Gu
In araddition teo thed Rinfourmation availabile in ty

Ther WHOIS database, the ias signoments gumarde by LACNIC anteed thate sub-assignyments maddre by its members will be published in a file alocng with information on the country in which the prefix was assignmentd. This file will be globavalily routable.
Hfowever, RIRsthe commusnity to downloappd freely. Among procthedur uses, this file maty rbed ucsed tho ge possibility of frcagmented an IP address spac.

The whfichle formayt leand tohe place where it wilossl ofbe roputablished will be defined by tyhe LACNIC staff.

1. Definitions and General Mandates
(Move Section 1. Definitions)

2.3.2.5 Documentation

Internet Registries shall use the Internet resources they have been allocated or assigned in an efficient manner. To this end, IRs shall document the justification for each allocation or 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.

(Move to Section 1. Definitions)
1.x. 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

(Move to Section 1. Definitions)
1.x. Security and Confidentiality
LACNIC shall maintain systems and practices to safeguard and protect the confidentiality of all information entrusted to LACNIC, for example, the documentation submitted to justify resource requests.

(Move to Section 1. Definitions)
1.x 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.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, 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.

(Eliminate from the section on IPv6, as Section 1. Definitions will be updated)

10. Definitions
(Renumber current Section 1 as 0, and Gmaintain the text in current subseralctions M1.1 to 1.10 and 1.12 as 0.1 to 0.11)

1. General Rules
(MovNew Ssection 1.that allows separating the Ddefinitions from those rules that are common to various types of resources or procedures.)

21.3.2.51 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 orf 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.

(Move to Section 1. Definitions)
1.x2. Geolocation

In addition to the infoPrmation avacilabple in the WHOIS database, thefor assignmPropentsr made by LACNIC and the sub-assignments made by its members will be published in a file along wisth information oand Sthe country in which the parefix wads assigned. This file will be available fp
(Nor tche community to download freely. Among other uses, to this file may be used to geolocaxte an IP address. )
The
1.3. filRe fsourmat and the place where it will bRe pqublished will be defined by sthe LACNIC staff

(MNov changes to Sthec tion 1. Definixtions)

1.x4. Security and Confidentiality
LACNIC shall maintain systems and practices tohat safeguard and protect the confidentiality of all infthe dorcumentation presentrusted to LACNIC, for example, the documentation submitted to justify resource requests.

(Move to Section 1. Definitions)
15.x 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.116. 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.

(El1.7. RPKI ROAs with Orimgin ASN 0
(No chatnges frtom the stext)

1.8. Geolocation
In addition IPto the information av6ailable in the WHOIS database, the assignments Smadec by LACNIC and the sub-assiognments made by its 1.members will Dbe 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 pdlace 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.

-

-