Update the policy on transfers due to mergers/acquisitions

. - 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 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 transferr

. - 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 transferr

d. - 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 assignme

d. - 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 assignme

t. Additional informatio

t. 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 Use

- 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.

2.3.2.17.2 - A block that has previously been transferred under this policy may not be transferred again in full for a period 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.

- 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 period 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: 2.3.2.17.1.- Transferred legacy resources will no longer be considered as such.

Add a paragraph at the end of section 2.3.2.17: Note that: - Transferred legacy resources will no longer be considered as such

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.

- During this one-year period, only transfers of up to 20% of the addresses of a transferred block will be allowed. Such transfers must have a prefix length equal or shorter than the minimum allowed by the policies currently in force and match a CIDR bit boundary

- Presented at: LACNIC 29 (30/04/2018)

- Presented at: LACNIC 30 (24/09/2018