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 certain items included in transfer policy 2.3.2.18 which, for consistency, should also be included in po
licy 2.3.2.17.

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 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 policy documents. For example, the fact that transf
erred 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 document.

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.

Add a paragraph at the end of section 2.3.2.17:

2.3.2.17.1.- Transferred legacy resources will no longer be considered as such.

2.3.2.17.2 - A block that has previously been transferred under this policy may not be transferred again in full for a p
eriod of one year.

2.3.2.17.2.1 – During this one-year period, only transfers of up to 20% of the addresses of a transferred block will be
allowed.

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.

Add a paragraph at the end of section 2.3.2.17:

2.3.2.17.1.- Transferred legacy resources will no longer be considered as such.

2.3.2.17.2 - A block that has previously been transferred under this policy may not be transferred again in full for a p
eriod of one year.

2.3.2.17.2.1 – During this one-year period, only transfers of up to 20% of the addresses of a transferred block will be
allowed.

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)

Changes were made regarding the possibility of subsequent transfers based on the comments received through the mailing l
ist and at the public forum.