IPv6 Mergers, Acquisitions, Reorganizations and Relocations

Original Language Español Date Published 11/03/2019 Last Modified 05/03/2019
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 2.0 (compare)


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-2019-3
Last version: 2


This proposal establishes the mechanism that allows updating IPv6 resource records in case of mergers, acquisitions, reorganizations and relocations.


The merger, acquisition, reorganization or relocation of companies or parts of companies is a common occurrence in the Internet and technology sector, among operators and other businesses.

This is also true for other types of organizations and sectors, all of them end-users of the RIRs.

These cases are not covered by the existing policy, although they are covered in the case of IPv4. It would not make sense to update IPv4 records but not IPv6 records for this type of business operations.

This proposal seeks to simplify the text and clarify that all cases are valid. It also proposes leaving the supporting documentation up to the staff, as such documentation will not necessarily be the same in every case.

Likewise, the proposal clarifies that mergers, acquisitions, reorganizations and relocations may be either within the LACNIC service region or between different service regions (intra- and inter-RIR changes).


Current text


New text:
Mergers, Acquisitions, Reorganizations or Relocations

LACNIC will process and register any transfer of IPv6 resources that occurs as a result of a partial or complete, intra-or inter-RIR merger, acquisition, business reorganization or relocation, regardless of whether the resources are held by ISPs or end-users.

To initiate this change and proceed with the registration, legal documentation supporting the operation shall be provided. Such supporting legal documentation will be decided by LACNIC and/or the other RIRs, if applicable.

Additional Information

The numbering of the proposed text within the corresponding section of the Policy Manual will be decided by LACNIC.


Immediate implementation


Similar policies with varying levels of “openness” exist in other service regions such as ARIN and RIPE.

In addition, an equivalent policy proposal has been submitted in APNIC and another proposal is being prepared for AfriNIC.
• https://www.ripe.net/publications/docs/ripe-682
• https://www.arin.net/policy/nrpm.html#eight2

Public Comments by LACNIC Staff

LACNIC STAFF´S IMPACT ANALYSIS - Proposal LAC-2019-3 - versión 2

LACNIC Staff's Interpretation of the Proposal

This proposal would apply in the case of mergers, acquisitions, reorganizations or relocations of organizations that have received IPv6 address assignments.

Modifications to the current text
A new subsection would be added to Section 4.6. IPv6 Mergers, Acquisitions, Reorganizations and Relocations of the Policy Manual.

Because LACNIC’s policies do not recognize the non-authorized sale or transfer of assigned or allocated resources, such transfers will be considered invalid.

Nevertheless, LACNIC will process and register any IPv6 resource transfer that occurs as a result of a partial or full merger, acquisition, business reorganization or relocation, regardless of whether the resources are held by an ISP or an end-user.

To initiate this change and proceed with the registration, legal documentation at the discretion of LACNIC must be submitted that supports the operation. Examples of such documentation include:
• A copy of the legal document validating the transfer of assets.
• A detailed inventory of all the assets the applicant will employ to continue to use the resources.
• A list of the applicant's clients using the resources.

The need to maintain all resources must also be justified. Otherwise, the holder will be required to return any surplus resources, if applicable, or, alternately, to transfer such surplus resources to third parties under the policies in force (4.5.1., 4.5.2., 4.5.3. y 4.5.4). If resources are to be returned, LACNIC will determine the corresponding terms and deadline.

LACNIC Staff Comments

1. Currently, only Section 2 of the Policy Manual, “IPv4 Addresses,” includes a text that applies to mergers and acquisitions. Although at implementation level a merger or acquisition involves fusing together all the organization's resources, LACNIC understands that this proposal would increase the clarity of the Manual for each type of resource.

2. This proposal is very similar to proposals 2019-2 (for IPv4 resources) and 2019-4 (for ASNs).

3. It eliminates the mention of “inter-RIR” operations previously included in version 1, which LACNIC interprets to mean that mergers, acquisitions, reorganizations or relocations between LACNIC and other regions would not be allowed.

Official Sources:

Situation in other RIRs:
RIPE NCC does not recognize the term “Inter-RIR merger” and would accept all transfers of Internet number resources to its service region, provided they comply with the policies relating to transfers within the corresponding service region. As for Internet number resource transfers from the RIPE NCC to another service region, RIPE NCC would follow the policies in force in the region to which the resources are to be transferred.
A proposal has been under discussion since March 2017: https://www.ripe.net/publications/docs/ripe-682

APNIC does not allow Internet number resource transfers as the result of “Mergers and acquisitions.”
A similar proposal is currently under discussion: https://www.apnic.net/wp-content/uploads/2019/03/prop-130-v001.txt

ARIN policies would currently be incompatible, as the proposals only address mergers, acquisitions, reorganizations and relocations. If LACNIC were to have fully reciprocal inter-RIR transfer policies with a needs-based justification, these would be compatible with the ARIN policies in force. However, the limitations on the types of resources (e.g. legacy resources) or the types of transfers (e.g. mergers and acquisitions) mean that they are not reciprocal.
ARIN processes outgoing inter-RIR transfers according to Section 8.4, Transfers for Specified Recipients.

(To be confirmed)

Privacy Policy