LACNIC · RIR Watchdog
IPv4 Mergers, Acquisitions, Reorganizations and Relocations
Start here for the proposal-by-proposal record: what changed, why it mattered, who argued for what, how positions evolved, what was decided, and where the evidence still has gaps.
Source facts
- Policy ID
- LAC-2019-2
- RIR
- LACNIC
- Official status
- Implemented
- Normalized status
- Accepted
- Introduced
- Mar 11, 2019
- Last source update
- Nov 1, 2026
- Coverage
- Partial
Who actually shaped the debate?
Policy evolution
Invalid transfers explicitly excluded · Version 2 restores an express rule that unauthorized sales or transfers are invalid, subject to section 2.3.2.18, before the corporate-change registration provision. Version 1’s proposed replacement began directly with registration of qualifying corporate transfers. This qualifies the proposal’s operation rather than making every transfer registrable.
Source facts −
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.Source facts ↗
Source facts +
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.Source facts ↗
Express intra- and inter-RIR language removed · Version 2 retains partial or complete mergers, acquisitions, reorganizations and relocations but removes the explicit intra- or inter-RIR wording. It also removes the other RIRs from the documentation-discretion clause. The new text no longer expressly promises cross-region processing; that omission alone does not establish a blanket prohibition under other applicable policies.
Source facts −
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.Source facts ↗
Source facts +
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.Source facts ↗
Supporting-document examples restored · Version 2 leaves the sufficiency of legal documentation to LACNIC and restores examples: evidence of asset transfer, an inventory of assets maintaining the resources and a list of clients using them. Version 1 delegated the documentation choice to LACNIC and, where applicable, other RIRs without these examples. The examples are illustrative, not an exhaustive checklist.
Source facts −
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.Source facts ↗
Source facts +
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.Source facts ↗
Need justification and disposition of surplus resources · Version 2 adds a requirement to justify retaining all resources. Surplus resources must be returned or transferred to third parties under the policies cited in the proposal, with LACNIC setting return conditions and timing. Version 1’s proposed rule ended with documentation of the corporate transaction and contained no corresponding surplus-resource requirement.
Source facts −
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.Source facts ↗
Source facts +
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.). When resources are to be returned, LACNIC will determine the corresponding conditions and deadline.Source facts ↗
Stated scope of valid cases · The rationale now expressly states that the cases described as valid include both intra-RIR and inter-RIR cases; the earlier version stated only that all cases are valid.
Source facts −
This proposal seeks to simplify the text and clarify that all cases are valid.Source facts ↗
Source facts +
This proposal seeks to simplify the text and clarify that all cases are valid (both Intra and Inter-RIR).Source facts ↗
Debate timeline
Entities
- Unknown · Public sources found; identity verification pendingDiscussion messages1First activityApr 8, 2019Last activityApr 8, 2019First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies20
- Discussion messages0First activityUnknownLast activityUnknownFirst explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies39
- Discussion messages0First activityUnknownLast activityUnknownFirst explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies5
- Discussion messages0First activityUnknownLast activityUnknownFirst explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies4
Sources and coverage
Official policy sources
Public discussion archives
- lacnic-politicas
- Earliest captured
- Oct 21, 1999
- Latest captured
- Oct 30, 2026
- Last refresh
- Aug 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,636
- Known gaps
- 28
- www.lacnic.net
- lacnic-anuncios
- Earliest captured
- Mar 15, 2002
- Latest captured
- Oct 27, 2026
- Last refresh
- Nov 2, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1,879
- Known gaps
- 0
- lacnic-ietf-lac
- Earliest captured
- May 30, 2013
- Latest captured
- Dec 30, 2015
- Last refresh
- Nov 1, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1,133
- Known gaps
- 0
- lacnic-infofrida
- Earliest captured
- Aug 14, 2006
- Latest captured
- Sep 13, 2011
- Last refresh
- Nov 1, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 292
- Known gaps
- 0
- lacnic-iot
- Earliest captured
- Oct 6, 2015
- Latest captured
- Jul 11, 2017
- Last refresh
- Nov 1, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 373
- Known gaps
- 0
- lacnic-lacnog
- Earliest captured
- Aug 1, 2026
- Latest captured
- Oct 30, 2026
- Last refresh
- Nov 2, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 8,703
- Known gaps
- 4
- lacnic-lactf
- Earliest captured
- Apr 13, 2004
- Latest captured
- Dec 30, 2013
- Last refresh
- Nov 1, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 5,257
- Known gaps
- 0
- lacnic-seguridad
- Earliest captured
- Jan 26, 2006
- Latest captured
- Dec 28, 2007
- Last refresh
- Nov 1, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1,356
- Known gaps
- 0
Coverage
Partial
Earliest captured: Oct 21, 1999
Latest captured: Nov 2, 2026
Freshness
Known gaps
- politicas.lacnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- www.lacnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- lacnic-politicas: Source coverage is incomplete. · The source boundary has not yet been reached.
- www.lacnic.net: Source coverage is incomplete. · The source boundary has not yet been reached.
- lacnic-anuncios: Source coverage is incomplete. · The source boundary has not yet been reached.
- lacnic-ietf-lac: Source coverage is incomplete. · The source boundary has not yet been reached.
- lacnic-infofrida: Source coverage is incomplete. · The source boundary has not yet been reached.
- lacnic-iot: Source coverage is incomplete. · The source boundary has not yet been reached.
- lacnic-lacnog: Source coverage is incomplete. · The source boundary has not yet been reached.
- lacnic-lactf: Source coverage is incomplete. · The source boundary has not yet been reached.
- lacnic-seguridad: Source coverage is incomplete. · The source boundary has not yet been reached.