Increase the minimum period of time required before a block can be transferred under section 2.3.2.18 - N/D

General information

Português
04/09/2015
Implemented
100 %.

Ricardo Patara - Version [1, 2]
In discussion
01/10/2015
Last call for comments
30/09/2015 - 14/11/2015
Ratification by the board
15/11/2015
Implemented
14/12/2015

Summary

Once in force, the provisions of section 2.3.2.18 will allow blocks that have been assigned for at least one year to be transferred, even in cases not involving the merger, acquisition or sale of any organizations.

This proposal seeks to modify this term, extending it to at least five years.

This will also affect paragraph 8 of section 11.1.

Rationale (Describe the problem you intend to solve)

An allocation made just one year ago and once again available for transfer may possibly be a sign of a poorly drafted utilization plan, and therefore a sign of poor distribution or incorrect or even false information.

The goal of increasing to 5 years the minimum period of time before an allocated block can be transferred is to avoid cases where, acting in bad faith, allocations are received under sections 11.2 or 11.2 and then transferred after a minimum amount of time (one year), for example, for profit.

Current text

Change 2.3.2.18.9. to:

"2.3.2.18.9.- Blocks and their sub-blocks from allocations or assignments from LACNIC, being initial or additional, can not be transferred for a period of FIVE years as of the allocation or assignment date.”

Change paragraph 8 of section 11.1 to:

"8. Blocks received under this policy may not be transferred as specified in paragraph 2.3.2.18 of the policy manual for a period of FIVE years. The same applies to its sub-blocks, i.e., blocks consisting of a subset of the IPv4 addresses contained in the block.”

New text
Analyze diff

Change 2.3.2.18.9. to:

"2.3.2.18.9.- Blocks and their sub-blocks from allocations or assignments from LACNIC, being initial or additional, can not be transferred for a period of FIVE years as of the allocation or assignment date.”

Change paragraph 8 of section 11.1 to:

"8. Blocks received under this policy may not be transferred as specified in paragraph 2.3.2.18 of the policy manual for a period of FIVE years. The same applies to its sub-blocks, i.e., blocks consisting of a subset of the IPv4 addresses contained in the block.”

Additional information

None

Timetable

Immediate implementation

References

2.3.2.18. Transfer of IPv4 Blocks within the LACNIC Region
11.1. Special IPv4 Allocations/Assignments Reserved for New Members

Presented at:

-


Summary

Once in force, the provisions of section 2.3.2.18 will allow blocks that have been assigned for at least one year to be transferred, even in cases not involving the merger, acquisition or sale of any organizations.

This proposal seeks to modify this term, extending it to at least three years.

This will also affect paragraph 8 of section 11.1 and paragraph 6 of section 11.2

Rationale (Describe the problem you intend to solve)

An allocation made just one year ago and once again available for transfer may possibly be a sign of a poorly drafted utilization plan, and therefore a sign of poor distribution or incorrect or even false information.

The goal of increasing to 3 years the minimum period of time before an allocated block can be transferred is to avoid cases where, acting in bad faith, allocations are received under sections 11.1 or 11.2 and then transferred after a minimum amount of time (one year), for example, for profit.

Current text

Change 2.3.2.18.9. to:

"2.3.2.18.9.- Blocks and their sub-blocks from allocations or assignments from LACNIC, being initial or additional, can not be transferred for a period of THREE years as of the allocation or assignment date.”

Change paragraph 8 of section 11.1 to:

"8. Blocks received under this policy may not be transferred as specified in paragraph 2.3.2.18 of the policy manual for a period of THREE years. The same applies to its sub-blocks, i.e., blocks consisting of a subset of the IPv4 addresses contained in the block.”

Change paragraph 6 of section 11.2 to:

"6. Blocks received under this policy may not be transferred as specified in paragraph 2.3.2.18 of the policy manual for a period of THREE years. The same applies to its sub-blocks, i.e., blocks consisting of a subset of the IPv4 addresses contained in the block.”

New text
Analyze diff

Change 2.3.2.18.9. to:

"2.3.2.18.9.- Blocks and their sub-blocks from allocations or assignments from LACNIC, being initial or additional, can not be transferred for a period of THREE years as of the allocation or assignment date.”

Change paragraph 8 of section 11.1 to:

"8. Blocks received under this policy may not be transferred as specified in paragraph 2.3.2.18 of the policy manual for a period of THREE years. The same applies to its sub-blocks, i.e., blocks consisting of a subset of the IPv4 addresses contained in the block.”

Change paragraph 6 of section 11.2 to:

"6. Blocks received under this policy may not be transferred as specified in paragraph 2.3.2.18 of the policy manual for a period of THREE years. The same applies to its sub-blocks, i.e., blocks consisting of a subset of the IPv4 addresses contained in the block.”

Additional information

None

Timetable

Immediate implementation

References

2.3.2.18. Transfer of IPv4 Blocks within the LACNIC Region
11.1. Special IPv4 Allocations/Assignments Reserved for New Members
11.2. Allocations/Assignments for Gradual IPv4 Resource Exhaustion

Presented at:

LACNIC 24 (28/09/2015)