One-way interregional transfers to LACNIC

LACNIC's transfer policies allow only intra-regional transfers. Thus, transfers depend on the willingness of LACNIC members to offer their excess resources. Given the current demand, this explains the limited amount of resources offered for transfer.

Current text Because the LACNIC region has received less IPv4 assignments, there is little in terms of excess resource invent

Current text Because the LACNIC region has received less IPv4 assignments, there is little in terms of excess resource invent

Proposed text: 2.3.2.18.4 (v.1).- LACNIC shall maintain a publicly accessible transfer log of all IPv4 address block transfers registered before LACNIC. This log shall specify the date on which each transaction took place, the transferring organization, the origin RIR, the receiving organization and the block that w

Current text Because the LACNIC region has received less IPv4 assignments, there is little in terms of excess resource invent

. Proposed text: 2.3.2.18.6.(v.1)- A block previously transferred under this policy may not subsequently be transferred for a period of one year as of the date on which the operation is recorded in

ch RIR. Recent studies conducted by RIPE and ARIN demonstrate that operators that acquire IPv4 resources exhibit greater growth in terms of IPv6 utilization, which indicates that the more an operator grows its IPv4 network, the more it us

One of the key tasks of Regional Registries is maintain up-to-date and valid information, so that it will be useful for the purposes for which it is required. The existence of a policy that allows transferring address blocks from other regions to the LAC region will make it easier to maintain the Registry information, while temporarily alleviating some of the problems faced by operators transferring addresses into the region.

ration. Current text Current text: 2.3.

Current text: 2.3.2.18. Transfer of IPv4 Blocks within the LACNIC Region Proposed Text: 2.3.2.18. Transfer of IPv4 Blocks within and towards the LACNIC

ferred. Proposed text: 2.3.2.18.4 (v.1).- LACNIC shall maintain a publicly accessible transfer log of all IPv4 address block transfers registered before LACNIC. This log shall specify the date on which each transaction took place, the transferring organization, the origin RIR, the receiving organization and the block that was tran

erred. Proposed Text: 2.3.2.18.4. LACNIC shall maintain a publicly accessible transfer log of all IPv4 address block transfers registered before the organization. This log shall specify the date on which each operation took place, the transferring organization, the origin RIR, the receiving organization, and the block that was t