LAC-2018-2: Update the policy on transfers due to mergers/acquisitions

Información General

Português
03/09/2018
Abandonada
0 %.

Ricardo Patara - Versión [1, 2, 3, 4]
Discussão inicial
07/02/2018
Abandonada
18/10/2018

Resumen

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

Justificación

The policy on IPv4 address transfers due to mergers or acquisitions already existed when the policy on transfers for other 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 transferred 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.

Texto Actual

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 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 for a period of three years as of their date of allocation or assignment.

Texto Nuevo
Oprima aquí para ver/ocultar las diferencias entre el texto actual y el nuevo

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 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 for a period of three years as of their date of allocation or assignment.

Información Adicional

-

Tiempo de Implementacion

Immediate implementation

Referencias

-


Resumen

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

Justificación

The policy on IPv4 address transfers due to mergers or acquisitions already existed when the policy on transfers for other 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 transferred 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.

Texto Actual

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.

Texto Nuevo
Oprima aquí para ver/ocultar las diferencias entre el texto actual y el nuevo

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.

Información Adicional

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)

Tiempo de Implementacion

Immediate implementation

Referencias

-


Resumen

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

Justificación

The policy on IPv4 address transfers due to mergers or acquisitions already existed when the policy on transfers for other 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 transferred 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.

The same is true for the restriction of two consecutive IPv4 address transfers, as already specified in policy 2.3.2.18.

Texto Actual

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.

Texto Nuevo
Oprima aquí para ver/ocultar las diferencias entre el texto actual y el nuevo

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.

Información Adicional

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

Tiempo de Implementacion

Immediate implementation

Referencias

-


Resumen

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

Justificación

The policy on IPv4 address transfers due to mergers or acquisitions already existed when the policy on transfers for other 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 transferred resources will no longer be considered as legacy resources, which is described in the LACNIC Bylaws.

For reasons of consistency, this should also be reflected in the policy document.

The same is true for the restriction of two consecutive IPv4 address transfers, which is already specified in policy 2.3.2.18.

Texto Actual

Add a paragraph at the end of section 2.3.2.17:

Note that:

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

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

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

Texto Nuevo
Oprima aquí para ver/ocultar las diferencias entre el texto actual y el nuevo

Add a paragraph at the end of section 2.3.2.17:

Note that:

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

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

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

Información Adicional

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

Tiempo de Implementacion

Immediate implementation

Referencias

-