Inter-RIR Transfer Policy

Original Language Español Date Published 31/10/2018 Last Modified 24/10/2018
Last Call for Comments Period Does not apply Date Ratified Does not apply Implementation Date Does not apply
Status Under discussion Download TXT PDF XML DOCX
See other versions 1.0 (compare)

Authors

Name: Jordi Palet Martinez
Email: jordi.palet@theipv6company.com
Organization: The IPv6 Company

Name: Edwin Salazar
Email: edwin.salazar@wifitelecom.ec
Organization: Wifitelecom

Name: Edmundo Cázarez
Email: edmundo.cazarez@nic.mx
Organization: NIC.MX

Proposal Data

Policy Type: LACNIC
Id: LAC-2018-14
Last version: 1

Summary

This proposal seeks to establish the mechanism to allow the transfer of resources (IPv4, IPv6, ASNs) between different regions and to align LACNIC with an existing market in which the region is not currently participating, something we consider to be negative for the region.

Rationale

In recent years and with the exhaustion of IPv4, several regions have solved this problem by allowing not only intra-regional transfers but also transfers between different regions. This allows for market dynamics, as an increased offer reduces prices.

However, an inter-RIR mechanism has not been established for LACNIC, and this is leading the region to a situation of discrimination and address scarcity, not only within the RIR itself, but also in the regional market. This the lack of addresses can even make it difficult to establish new businesses in the region.

Likewise, the lack of an inter-RIR transfer policy does not prevent “under-the-table” transfers and, therefore, involves the loss of certain resources’ registration history, the main function of an RIR.

As a protection measure, in the case of IPv4 and ASN, we believe such transfers should only be allowed from LACNIC to other regions if the resources to be transferred are legacy resources, while inbound transfers should be allowed regardless of their status. This has the additional advantage of allowing these resources to surface and incorporating them into the RIR system.

In addition, it is important to highlight that, in certain cases, IPv6 deployment may require small blocks of IPv4 addresses for use by the transition mechanisms or significantly increase

their cost if such blocks are not available, so many organizations in the LACNIC region might be at a serious disadvantage if they do not have access to the global market, as is currently the case.

Accepting this type of transfers is certainly not without risks. It is possible that an initial price increase might occur, but this would quickly align with the global market, as is usually the case with equivalent markets.

Text

Current text: –
New text:
(Note: The following text would be added as a new, separate section at the end of the current Policy Manual, with the numbering that LACNIC sees fit and before the Appendixes.)

1. Inter-RIR Transfer Policy
1.1. In the case of IPv4, the minimum size that can be transferred is a /24.
1.2. In the case of IPv6, the minimum size that can be transferred is a /48.
1.3. IPv4 or ASN resources can only be transferred from LACNIC to another RIR if they are legacy resources.
1.4. Resources associated with IPv6 allocations or assignments made by LACNIC may not be transferred until two (2) years after their distribution or assignment, as appropriate.
1.5. In order for an entity to receive a transfer, it must first complete the process of justifying the need for the resources, either before LACNIC or before the corresponding RIR (depending on whether the transfer is inbound or outbound), as appropriate, according to the policies in force.
1.6. LACNIC or the corresponding RIR (depending on whether the transfer is inbound or outbound) will verify the holder of the resources to be transferred and that they are not involved in any dispute.
1.7. Both the transferring and the receiving entities must submit to LACNIC a copy of the legal document supporting the operation.
1.8. Both the transferring and the receiving entities will be subject to the policies and membership terms and conditions of the corresponding RIR.
1.9. In its existing transfer log, LACNIC will record the date on which the operation took place, the transferring entity, the receiving entity, the corresponding RIR in each case, and other relevant data of the transferred resource.
1.10. Once the transfer is complete, LACNIC will modify the information on the transferred resource to reflect the change of holder.
1.11. Transferred blocks (as well as their sub-blocks) may not be subsequently transferred for a period of one year as of the date on which the transaction is registered in the transfer log.
1.12. Legacy resources transferred into the LACNIC region will no longer be considered legacy resources.

Additional Information

Although it is still pending verification, it appears that this proposal would be compatible with the Inter-RIR transfer policies of APNIC, ARIN and RIPE, as they are all bidirectional.

Timetable

Immediate implementation

References

There are Inter-RIR policies in place in APNIC, ARIN and RIPE. These have widely proven their efficiency and have not created any issues for their respective communities, quite the contrary.

ARIN appears to be the region where the transfer of the largest number of addresses to the other regions that have resource transfer policies have originated.
• http://www.lacnic.net/innovaportal/file/3277/1/2-john-sweeting-arin.pdf
• https://ripe77.ripe.net/presentations/145-18-0903-NRO-Statistics-2018.pdf

Privacy Policy