We propose modifying the text describing the requirements for ASN distribution with a view to making it more simple and clear. We also propose modifying the time during which an ASN may be requested before the applicable requirements are met.

The current ASN assignment policy includes two requirements that must be met simultaneously in order to be granted an ASN, as they consider different needs. As it is written, however, the policy seems to imply that both requirements must be met simultaneously, and this can lead to confusion at the time of interpreting this policy.
To solve this problem, we propose replacing the term "multi-homed" in the first requirement and, instead, using "the need to interconnect," as this is a broader requirement and includes unique routing policy cases set forth in the second requirement. This change also involves modifying the second requirement so that it is consistent with the first.
Due to legal or operational issues, months can often go by from the moment the intent to establish a private interconnection is agreed until the interconnection is actually in place. It is for this reason that we propose modifying the time before the need for an ASN from 2 weeks to six month.

We propose modifying the ASN distribution requirements, which are currently as follows:

LACNIC shall allocate Autonomous System Numbers to those organizations that meet the following requirements:

1. The organization must be multi-homed and each provider must have two or more independent Autonomous Systems at the time of the application, or planning to become multi-homed within a period of no more than two weeks as of the moment of the application.

2. The organization must submit detailed documentation describing the applicant's routing policy, which must be unique and different to that applied by the ASN to which it is connected. This documentation must include the exterior routing protocol to be used, IP addresses that will conform the AS, and a detailed explanation of the reasons why its routing policy differs from that of its providers.

The proposed text is as follows:

LACNIC shall allocate Autonomous System Numbers to those organizations that meet the following requirements:

1. The organization must have the need to interconnect with other independent Autonomous Systems at the time of the application, or be planning to interconnect within a period of no more than six (6) month as of the moment of the application. After this period, LACNIC may revoke the assigned ASN if it has not been used.

2. Detail the applicant's routing policy, specifying the ASNs with which the organization will interconnect and the IP addresses that will be announced through the requested ASN.

We propose modifying the ASN distribution requirements, which are currently as follows:

LACNIC shall allocate Autonomous System Numbers to those organizations that meet the following requirements:

1. The organization must be multi-homed and each provider must have two or more independent Autonomous Systems at the time of the application, or planning to become multi-homed within a period of no more than two weeks as of the moment of the application.

2. The organization must submit detailed documentation describing the applicant's routing policy, which must be unique and different to that applied by the ASN to which it is connected. This documentation must include the exterior routing protocol to be used, IP addresses that will conform the AS, and a detailed explanation of the reasons why its routing policy differs from that of its providers.

The proposed text is as follows:

LACNIC shall allocate Autonomous System Numbers to those organizations that meet the following requirements:

1. The organization must have the need to interconnect with other independent Autonomous Systems at the time of the application, or be planning to interconnect within a period of no more than six (6) month as of the moment of the application. After this period, LACNIC may revoke the assigned ASN if it has not been used.

2. Detail the applicant's routing policy, specifying the ASNs with which the organization will interconnect and the IP addresses that will be announced through the requested ASN.

NA

Inmediatly

NA

LACNIC 22 (27/10/2014)