Inter-RIR IPv4 Address Transfers

LAC-2012-8-v2 LAC-2012-8-v3 Vs
References:
New
Deleted
Modified
Authors

Name: Juan Alejo
Email: jpeirano@lacnic.net
Organization: LACNIC
Name: Juan Alejo 2
Email: jpeirano@lacnic.net
Organization: LACNIC

Name: Gustavo Lozano
Email: glozano.gli@gmail.com
Organization: Persona
Name: Edmundo Cazarez
Email: ecazarez@nic.mx
Organization: Personal

Summary

This proposal allows transferring IPv4 addresses between different regions.

This proposal allows transferring IPv4 addresses between different regions.

Rationale (Describe the problem you intend to solve)

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 when
most RIRs already have or are in the process of implementing policies that support them.
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 genera
ting any records in LACNIC's database. The authors believe that LACNIC’s Registration 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 safeguards to allow an orderly inter-RIR IPv4 address market where transfers originate or
terminate in the LACNIC region.

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 genera
ting any records in Lacnci's database. The authors believe that Lacnic’s Registry function in maintaining an updated rec
ord 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 t
erminate in the LACNIC region.

Current text

AfriNIC, APNIC, ARIN and RIPE are considered foreign RIRs as long as they have a policy in place that allows transferrin
g 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 that may be 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 justifyi
ng its IPv4 address needs before the RIR receiving the address space. In other words, the foreign entity must justify be
fore its RIR the initial/additional allocation/assignment. If the receiving RIR approves the transfer, LACNIC shall proc
eed to transfer custody of the address space to that RIR.
• Upon receiving an IPv4 address block transfer request, LACNIC shall verify that the local entity transferring the b
lock is in fact the holder of said block according to LACNIC's records. The foreign entity and the local entity must pre
sent 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 LAC
NIC 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 can not be transferred to a foreign RIR.
• Once the transfer is complete, LACNIC shall modify the information on the transferred resource in order to reflect
the change of holder.
• Transferred legacy resources shall no longer be considered as such before completing the transfer; therefore, the f
oreign RIR shall receive the block as a non-legacy block.
IPv4 resources that may be 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. In other words, the local entity must justify before LACNIC the initial/additiona
l allocation/assignment, as applicable, 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 tran
sfer.
• Once the transfer is complete, LACNIC shall modify the information on the transferred resource in order to reflect
the change of holder.
• Transferred legacy resources shall no longer be considered as such; therefore, LACNIC shall receive the block as a
non-legacy block.
• Transferred resources may not subsequently be transferred for a period of one year as of the transaction date regis
tered 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.

NOTE: This section will come into force when Lacnic or any of its NIRs becomes unable, for the first time, to cover an I
Pv4 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 transferrin
g 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 justifyi
ng its IPv4 address needs before the RIR receiving the address space. In other words, the foreign entity must justify th
e initial/additional allocation/assignment before its RIR. If the receiving RIR approves the transfer, Lacnic shall proc
eed 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 b
lock is in fact the holder of said block according to Lacnic's records. The foreign entity and the local entity must pre
sent 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 Lac
nic 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 chang
e 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/a
ssignment, 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 tran
sfer.
• Once the transfer is complete, Lacnic shall modify the information on the transferred resource to reflect the chang
e of holder.
• Transferred legacy resources shall no longer be considered as such; therefore, Lacnic shall receive the block as no
n-legacy block.
• Transferred blocks may not subsequently be transferred for a period of one year as of the transaction date register
ed in the transfer log. The same applies to its sub-blocks, i.e. blocks consisting of a subset of the IPv4 addresses con
tained in the block.

New text

AfriNIC, APNIC, ARIN and RIPE are considered foreign RIRs as long as they have a policy in place that allows transferrin
g 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 that may be 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 justifyi
ng its IPv4 address needs before the RIR receiving the address space. In other words, the foreign entity must justify be
fore its RIR the initial/additional allocation/assignment. If the receiving RIR approves the transfer, LACNIC shall proc
eed to transfer custody of the address space to that RIR.
• Upon receiving an IPv4 address block transfer request, LACNIC shall verify that the local entity transferring the b
lock is in fact the holder of said block according to LACNIC's records. The foreign entity and the local entity must pre
sent 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 LAC
NIC 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 can not be transferred to a foreign RIR.
• Once the transfer is complete, LACNIC shall modify the information on the transferred resource in order to reflect
the change of holder.
• Transferred legacy resources shall no longer be considered as such before completing the transfer; therefore, the f
oreign RIR shall receive the block as a non-legacy block.
IPv4 resources that may be 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. In other words, the local entity must justify before LACNIC the initial/additiona
l allocation/assignment, as applicable, 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 tran
sfer.
• Once the transfer is complete, LACNIC shall modify the information on the transferred resource in order to reflect
the change of holder.
• Transferred legacy resources shall no longer be considered as such; therefore, LACNIC shall receive the block as a
non-legacy block.
• Transferred resources may not subsequently be transferred for a period of one year as of the transaction date regis
tered 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.

NOTE: This section will come into force when Lacnic or any of its NIRs becomes unable, for the first time, to cover an I
Pv4 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 transferrin
g 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 justifyi
ng its IPv4 address needs before the RIR receiving the address space. In other words, the foreign entity must justify th
e initial/additional allocation/assignment before its RIR. If the receiving RIR approves the transfer, Lacnic shall proc
eed 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 b
lock is in fact the holder of said block according to Lacnic's records. The foreign entity and the local entity must pre
sent 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 Lac
nic 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 chang
e 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/a
ssignment, 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 tran
sfer.
• Once the transfer is complete, Lacnic shall modify the information on the transferred resource to reflect the chang
e of holder.
• Transferred legacy resources shall no longer be considered as such; therefore, Lacnic shall receive the block as no
n-legacy block.
• Transferred blocks may not subsequently be transferred for a period of one year as of the transaction date register
ed in the transfer log. The same applies to its sub-blocks, i.e. blocks consisting of a subset of the IPv4 addresses con
tained in the block.

Additional information

NO

NO

References

NO

NO