Update the policy on transfers due to mergers/acquisitions

LAC-2018-2-v3 LAC-2018-2-v4 Vs
Referencias:
Nuevo
Eliminado
Modificado
Autores

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

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

Resumen

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.

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.

Justificación

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

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:
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 on
e 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 ma
tch a CIDR bit boundary.

Información Adicional

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

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

Referencias

-

-