Nombre: Ricardo Patara
Email: patara@registro.br
Organización: NIC.BR

Nombre: Ricardo Patara
Email: patara@registro.br
Organización: NIC.BR

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.

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.

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.

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., Twhisch 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, awhich is already specified in policy 2.3.2.18.

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.-Note that:

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

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.-Note that:

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

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

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

-

-