IPv6 Mergers, Acquisitions, Reorganizations and Relocations

LAC-2019-3-v1 LAC-2019-3-v2 Vs
References:
New
Deleted
Modified
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

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

Summary

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

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

Rationale

The merger, acquisition, reorganization or relocation of companies or parts of companies is a common occurrence in the I
nternet 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 sen
se 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 d
ocumentation 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 LA
CNIC service region or between different service regions (intra- and inter-RIR changes).

The merger, acquisition, reorganization or relocation of companies or parts of companies is a common occurrence in the I
nternet and technology sector, among both 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 sen
se 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 d
ocumentation up to the staff, as such documentation will not necessarily be the same in every case.

Text

Current text
None
---
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 provide
d. Such supporting legal documentation will be decided by LACNIC and/or the other RIRs, if applicable.

Current text: No such text exists.
----
New text
Mergers, Acquisitions, Reorganizations or Relocations
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 comple
te 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 must be submitted which, at the discretio
n of LACNIC, 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 used by the applicant for maintaining the resources in use.
• A list of the applicant's clients using the resources.
The need to maintain all the resources must also be justified, forcing the return of the surplus resources if applicable
or, alternatively, the transfer of such surplus resources to third parties under the policies in force (4.5.1., 4.5.2.,
4.5.3. y 4.5.4). When resources are to be returned, LACNIC will determine the corresponding conditions and deadline.

Additional Information

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

The numbering of the proposed text within the corresponding section of the Policy Manual will be decided by LACNIC.
In extreme cases, the non-existence of this policy might result in this issue being taken to the courts if LACNIC refuse
s to update the registry for any type of resources, and, based on the legislation currently in force in Uruguay, the cou
rts might force LACNIC to modify the registry. We believe that having this policy would avoid this situation and allows
maintaining control according to the wishes of the community. It would also avoid legal costs to both parties involved.

References

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 AfriNI
C.
• https://www.ripe.net/publications/docs/ripe-682
• https://www.arin.net/policy/nrpm.html#eight2

Similar policies with varying levels of “openness” exist in other service regions such as ARIN and RIPE.
ARIN is discussing a proposal to allow inter-RIR transfers (even if they are not due to mergers, acquisitions, reorganiz
ations or relocations):
• https://www.arin.net/participate/policy/drafts/2019_4/
In addition, an equivalent policy proposal has been submitted in APNIC and another proposal is being prepared for AfriNI
C.
• https://www.ripe.net/publications/docs/ripe-682
• https://www.arin.net/policy/nrpm.html#eight2