LAC-2016-4: Modify direct IPv6 address assignments to end users

General Information

Español
07/03/2016
Implemented
100 %.

Jordi Palet Martinez - Version [1, 2]
Initial discussion
10/03/2016
Last call for comments
05/05/2016 - 19/06/2016
Ratification by the Board
20/06/2016
Implemented
01/08/2016

Summary

This policy was designed based on its IPv4 equivalent. Some of its considerations make no sense in IPv6 and are not covered by other RIRs.

This proposal seeks to modify the text so that these considerations will be consistent with the reality of IPv6

Rationale

Some of the information which is currently required makes no sense and actually does not affect LACNIC's decision on whether to assign the requested resources.

Since there is no obligation to announce these resources, it makes no sense to talk about routing plans or protocols.

In IPv6, address shortage is not even remotely a consideration. Indeed, this protocol was designed to allow subnets with very few nodes, which implies that what matters is not the number of nodes but the number of subnets, depending on the organization's needs.

Current Text

The requirements under section 4.5.4.2 would be as follows:

1. Not be an LIR or an ISP.
2. In case of announcing the assignment on the Internet inter-domain routing system, the receiving organization shall announce the block maintaining de-aggregation to a minimum in accordance with the announcing organization's needs.
3. Provide detailed information showing how the requested block will be used within the following three, six and twelve months.
4. Submit addressing plans for at least one year.

New Text
Analyze Diff

The requirements under section 4.5.4.2 would be as follows:

1. Not be an LIR or an ISP.
2. In case of announcing the assignment on the Internet inter-domain routing system, the receiving organization shall announce the block maintaining de-aggregation to a minimum in accordance with the announcing organization's needs.
3. Provide detailed information showing how the requested block will be used within the following three, six and twelve months.
4. Submit addressing plans for at least one year.

Additional Information

None

Timetable

Immediate implementation.

References

-


Summary

This policy was designed based on its IPv4 equivalent. Some of its considerations make no sense in IPv6.

This proposal seeks to modify the text so that these considerations will be consistent with the reality of IPv6

Rationale

Some of the information which is currently required makes no sense and actually does not affect LACNIC's decision on whether to assign the requested resources.

Since there is no obligation to announce these resources, it makes no sense to talk about routing plans or protocols.

In IPv6, address shortage is not even remotely a consideration. Indeed, this protocol was designed to allow subnets with very few nodes, which implies that what matters is not the number of nodes but the number of subnets, depending on the organization's needs.

Current Text

The current text of the policy, section 4.5.4.2, is:

1. Not be an LIR or ISP.
2. In case of announcing the assignment on the Internet inter-domain routing system, the receiving organization shall announce the block maintaining de-aggregation to a minimum in accordance with the announcing organization's needs.
3. Provide detailed information showing how the requested block will be used within the following three, six and twelve months.
4. Submit addressing plans for at least a year, and host numbers on each subnet.
5. Submit a detailed description of the network topology.
6. Prepare a detailed description of the network routing plans, including the routing protocols to be used as well as any existing limitations.

The proposal modification would leave the text at this section:
1. Not be an LIR or ISP.
2. In case of announcing the assignment on the Internet inter-domain routing system, the receiving organization shall announce the block maintaining de-aggregation to a minimum in accordance with the announcing organization's needs.
3. Provide detailed information showing how the requested block will be used within the following three, six and twelve months.
4. Submit addressing plans for at least a year.

This proposal does NOT modify the rest of the text.

New Text
Analyze Diff

The current text of the policy, section 4.5.4.2, is:

1. Not be an LIR or ISP.
2. In case of announcing the assignment on the Internet inter-domain routing system, the receiving organization shall announce the block maintaining de-aggregation to a minimum in accordance with the announcing organization's needs.
3. Provide detailed information showing how the requested block will be used within the following three, six and twelve months.
4. Submit addressing plans for at least a year, and host numbers on each subnet.
5. Submit a detailed description of the network topology.
6. Prepare a detailed description of the network routing plans, including the routing protocols to be used as well as any existing limitations.

The proposal modification would leave the text at this section:
1. Not be an LIR or ISP.
2. In case of announcing the assignment on the Internet inter-domain routing system, the receiving organization shall announce the block maintaining de-aggregation to a minimum in accordance with the announcing organization's needs.
3. Provide detailed information showing how the requested block will be used within the following three, six and twelve months.
4. Submit addressing plans for at least a year.

This proposal does NOT modify the rest of the text.

Additional Information

The items that would be eliminated are not contemplated by other RIRs

Timetable

Immediate implementation.

References

-