Update the policy on transfers due to mergers/acquisitions

LAC-2018-2-v1 LAC-2018-2-v2 Vs
References:
New
Deleted
Modified
Authors

Name: Ricardo Patara
Email: patara@registro.br
Organization: NIC.BR

Name: Ricardo Patara
Email: patara@registro.br
Organization: NIC.BR

Summary

Proposal to add some items included in transfer policy 2.3.2.18 which, for consistency, should also be included in polic
y 2.3.2.17.

Proposal to add some items included in transfer policy 2.3.2.18 which, for consistency, should also be included in polic
y 2.3.2.17.

Rationale (Describe the problem you intend to solve)

The policy on IPv4 address transfers due to mergers or acquisitions already existed when the policy on transfers for oth
er reasons (2.3.2.18) was implemented. The latter incorporated some important observations that are not included in the
former, even though some of them are present in documents other than the policy documents. For example, the fact that tr
ansferred resources will no longer be considered as legacy resources. This is described in the LACNIC Bylaws.
For reasons of consistency, this should also be reflected in the policy.
The same is true for the restriction of two consecutive IPv4 address transfers, as already specified in policy 2.3.2.18.

The policy on IPv4 address transfers due to mergers or acquisitions already existed when the policy on transfers for oth
er reasons (2.3.2.18) was implemented. The latter incorporated some important observations that are not included in the
former, even though some of them are present in documents other than the policy documents. For example, the fact that tr
ansferred resources will no longer be considered as legacy resources. This is described in the LACNIC Bylaws.
For reasons of consistency, this should also be reflected in the policy.
The same is true for the restriction of two consecutive IPv4 address transfers, as already specified in policy 2.3.2.18.

Current text

Add a paragraph at the end of section 2.3.2.17
It is important to note that:
- Once transferred, resources previously considered to be legacy resources will no longer be considered as such.
- A block that has previously been transferred under sections 2.3.2.17 or 2.3.2.18 may not be transferred again for a pe
riod of one year as of the date on which the previous transfer was concluded. This also applies to sub-blocks, i.e., any
group of addresses contained in the block that is transferred.
- Blocks and sub-blocks from initial or additional allocations or assignments received directly from LACNIC or its NIRs
may not be transferred for a period of three years as of their date of allocation or assignment.

Add a paragraph at the end of section 2.3.2.17
It is important to note that:
- Once transferred, resources previously considered to be legacy resources will no longer be considered as such.
- A block that has previously been transferred under section 2.3.2.17, may not be transferred again under section 2.3.2.
18 for a period of one year as of the date on which the previous transfer was concluded. This also applies to sub-blocks
, i.e., any group of addresses contained in the block that is transferred.
- Blocks and sub-blocks from initial or additional allocations or assignments received directly from LACNIC or its NIRs
may not be transferred under section 2.3.2.17 for a period of one year as of their date of allocation or assignment.

New text

Add a paragraph at the end of section 2.3.2.17
It is important to note that:
- Once transferred, resources previously considered to be legacy resources will no longer be considered as such.
- A block that has previously been transferred under sections 2.3.2.17 or 2.3.2.18 may not be transferred again for a pe
riod of one year as of the date on which the previous transfer was concluded. This also applies to sub-blocks, i.e., any
group of addresses contained in the block that is transferred.
- Blocks and sub-blocks from initial or additional allocations or assignments received directly from LACNIC or its NIRs
may not be transferred for a period of three years as of their date of allocation or assignment.

Add a paragraph at the end of section 2.3.2.17
It is important to note that:
- Once transferred, resources previously considered to be legacy resources will no longer be considered as such.
- A block that has previously been transferred under section 2.3.2.17, may not be transferred again under section 2.3.2.
18 for a period of one year as of the date on which the previous transfer was concluded. This also applies to sub-blocks
, i.e., any group of addresses contained in the block that is transferred.
- Blocks and sub-blocks from initial or additional allocations or assignments received directly from LACNIC or its NIRs
may not be transferred under section 2.3.2.17 for a period of one year as of their date of allocation or assignment.

Additional information

-

According to comments, the proposal was adjusted to remove the restriction to transfer one block again under section 2
2.3.2.17 (Mergers, Acquisitions or Sales of ISPs or End Users)

References

-

-