Inter-RIR IPv4 Address Transfers

Original Language Español Date Published 15/08/2014 Last Modified 22/04/2014
Last Call for Comments Period Does not apply Date Ratified Does not apply Implementation Date Does not apply
Status Abandoned Download TXT PDF XML DOCX
See other versions 1.0 2.0 3.0 (compare)

Authors

Name: Gustavo Lozano
Email: glozano.gli@gmail.com
Organization: Persona

Name: Edmundo Cazarez
Email: ecazarez@nic.mx
Organization: Personal

General opinion

Proposal Data

Policy Type: LACNIC
Id: LAC-2012-8
Last version: 3
Presented at: LACNIC 18, LACNIC 19, LACNIC 20, LACNIC 21, LACNIC 22

Summary

This proposal allows transferring IPv4 addresses between different regions.

Rationale

This proposal allows transferring IPv4 addresses between different regions.

The authors believe that disallowing inter-RIR IPv4 address transfers creates a differential status for its members, as most RIRs already have or are in the process of implementing policies that support these transfers.

The arguments that justify allowing IPv4 address transfers between different regions and Lacnic include:

IPv4 address markets are already a reality: IPv4 address transfers may already be happening in the region without generating any records in Lacnci's database. The authors believe that Lacnic’s Registry function in maintaining an updated record of the holders of IPv4 resources is essential to the proper functioning of the Internet.

APNIC, RIPE and ARIN already have inter-RIR IPv4 address transfer policies in force or policy proposals seeking to allow such transfers. APNIC currently has an inter-RIR IPv4 address transfer policy. Lacnic needs to adapt its processes and tools to consider a future in which IPv4 address transfers, including inter-RIR transfers, will be frequent.

This proposal contains enough provisions to allow an orderly inter-RIR IPv4 address market when transfers originate or terminate in the LACNIC region.

Text

NOTE: This section will come into force when Lacnic or any of its NIRs becomes unable, for the first time, to cover an IPv4 block allocation or assignment for lack of resources.

AfriNIC, APNIC, ARIN and RIPE are considered foreign RIRs as long as they have a policy in place that allows transferring IPv4 resources between different regions.

A foreign entity is an entity that is part of a foreign RIR and is not part of Lacnic.

A local entity is an entity that is part of Lacnic.

IPv4 resources transferred from Lacnic to a foreign RIR:

• The minimum block size that may be transferred is a /24.
• In order for a foreign entity to qualify for receiving a transfer, it must first go through the process of justifying its IPv4 address needs before the RIR receiving the address space. In other words, the foreign entity must justify the initial/additional allocation/assignment before its RIR. If the receiving RIR approves the transfer, Lacnic shall proceed to transfer custody of the address space to said RIR.
• Upon receiving an IPv4 address block transfer request, Lacnic shall verify that the local entity transferring the block is in fact the holder of said block according to Lacnic's records. The foreign entity and the local entity must present before Lacnic a copy of the legal document supporting the transfer.
• The local entity shall automatically be ineligible to receive IPv4 resource allocations and/or assignments from Lacnic for a period of one year as of the transaction date registered in the transfer log.
• IPv4 resources assigned/allocated by Lacnic during the past year may not be transferred to a foreign RIR.
• Once the transfer is complete, Lacnic shall modify the information on the transferred resource to reflect the change of holder.
• Before completing the transfer, transferred legacy resources shall no longer be considered as such; therefore, the foreign RIR shall receive the block as a non-legacy block.

IPv4 resources transferred from a foreign RIR to Lacnic:

• The minimum block size that may be transferred is a /24.
• In order for a local entity to qualify for receiving a transfer, it must first go through the process of justifying its IPv4 address needs before Lacnic. That is to say, the local entity must justify the initial/additional allocation/assignment, as applicable, before Lacnic according to the policies in force.
• The local entity must comply with all Lacnic policies in force.
• The foreign entity and the local entity must present before Lacnic a copy of the legal document supporting the transfer.
• Once the transfer is complete, Lacnic shall modify the information on the transferred resource to reflect the change of holder.
• Transferred legacy resources shall no longer be considered as such; therefore, Lacnic shall receive the block as non-legacy block.
• Transferred blocks may not subsequently be transferred for a period of one year as of the transaction date registered in the transfer log. The same applies to its sub-blocks, i.e. blocks consisting of a subset of the IPv4 addresses contained in the block.

Additional Information

NO

Timetable

Esta sección entrará en vigor cuando LACNIC o alguno de sus NIRs sea incapaz, por primera vez, de cubrir una distribución o asignación de un bloque IPv4 por falta de recursos

References

NO