IPv4 Mergers, Acquisitions, Reorganizations and Relocations

ummary This proposal modifies the mechanism for updating IPv4 resource records in case of mergers, acquisitions, reorganizations and relocations.

ummary This proposal modifies the mechanism for updating IPv4 resource records in case of company mergers, acquisitions, reorganizations and relocations.

Rationale (Describe the problem you intend to solve) 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.

Rationale (Describe the problem you intend to solve) The merger, acquisition, reorganization or relocation of companies or parts of companies is a common occurrence in the Internet and technology sector, among both operators and other businesses.

It also proposes leaving the supporting documentation up to the staff, as such documentation will not necessarily be the same in every case.

It also proposes leaving the supporting documentation up to the staff, as such documentation will not necessarily be the same in every case.

---- New text: 2.3.2.17.

--- New text 2.3.2.17.

Mergers, Acquisitions, Reorganizations or Relocations LACNIC will process and register any transfer of IPv4 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.

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, with the exception of those subject to the provisions of section 2.3.2.18.

Mergers, Acquisitions, Reorganizations or Relocations LACNIC will process and register any transfer of IPv4 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.

Nevertheless, LACNIC will process and register any IPv4 resource transfer that occurs as a result of a partial or complete 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 supporting the operation shall be provided.

To initiate this change and proceed with the registration, legal documentation must be submitted which, at the discretion of LACNIC, supports the operation.

To initiate this change and proceed with the registration, legal documentation supporting the operation shall be provided.

Examples of such documentation include: • A copy of the legal document validating the transfer of assets.

Such supporting legal documentation will be decided by LACNIC and/or the other RIRs, if applicable.

Examples of such documentation include: • A copy of the legal document validating the transfer of assets.

Such supporting legal documentation will be decided by LACNIC and/or the other RIRs, if applicable.

• A detailed inventory of all the assets used by the applicant for maintaining the resources in use.

Such supporting legal documentation will be decided by LACNIC and/or the other RIRs, if applicable.

• A list of the applicant's clients using the resources.

Such supporting legal documentation will be decided by LACNIC and/or the other RIRs, if applicable.

• A list of the applicant's clients using the resources. In addition, 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 (2.3.3 and 2.3.4.).

This proposal seeks to simplify the text and clarify that all cases are valid.

This proposal seeks to simplify the text and clarify that all cases are valid (both Intra and Inter-RIR).