LACNIC · RIR Watchdog
IPv6 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-3
- RIR
- LACNIC
- Official status
- Implemented
- Normalized status
- Accepted
- Introduced
- Mar 11, 2019
- Last source update
- Oct 12, 2026
- Coverage
- Partial
Who actually shaped the debate?
Policy evolution
New Text Content · The new text expands the scope of valid transfers to explicitly include partial or complete mergers, acquisitions, business reorganizations, or relocations regardless of ISP/end-user status, and adds a prohibition on unauthorized sales/transfers. It introduces specific examples of required legal documentation (asset transfer documents, inventory, client list) and mandates justification for maintaining resources with requirements to return or transfer surplus resources under specific policy sections. The new text also specifies that LACNIC determines conditions/deadlines for resource returns.
Source facts −
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 documentatioSource facts ↗
Source facts +
Validated evidence is unavailable.Rationale - Scope Clarification · The new rationale removes the clarification that mergers/acquisitions/etc. may be intra- or inter-RIR changes, which was present in the old version.
Source facts −
ectors, all of them end-users of the RIRs. These cases are not covered by the existing policy, although they are covered in the casSource facts ↗
Source facts +
and sectors, all of them end-users of the RIRs. These cases are not covered by the existing policy, although they are covered in thSource facts ↗
Additional Information - Legal Context · The new text adds information regarding potential legal consequences in Uruguay if LACNIC refuses to update the registry, and states that having this policy avoids such situations and legal costs.
Source facts −
e decided by LACNIC and/or the other RIRs, if applicable. New text Analyze diff Current textSource facts ↗
Source facts +
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 resSource facts ↗
References - ARIN Draft · The new text adds a reference to an ARIN draft proposal discussing inter-RIR transfers.
Source facts −
are held by ISPs or end-users. To initiate this change and proceed with the registration, legal doSource facts ↗
Source facts +
urces 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. New text Analyze diff Current text: No such text exists. ---- New text Mergers, Acquisitions, Reorganizations or RSource facts ↗
Presentation Venue · The presentation venue is updated from '-' to 'LACNIC 31 (06/05/2019)'.
Stated transfer scope in the rationale · The rationale changes the stated scope from clarifying that “all cases are valid” to clarifying that the proposal is “only for the Intra-RIR case.”
Source facts −
his proposal seeks to simplify the text and clarify that all cases are valid.Source facts ↗
Source facts +
his proposal seeks to simplify the text and clarify that it is only for the Intra-RIR case.Source facts ↗
Debate timeline
Entities
- 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 policies4Freshness: Stale · Last refresh: · The latest refresh failed. The last successful result is shown.
Last research attempt: Sep 18, 2026
Identity verified: Sep 19, 2026
· Historical Authors Jordi Palet Martinez - Version [1, 2, 3] Edwin Salazar - Version [1, 2, 3] Edmundo Cázarez - Version [1, 2]
politicas.lacnic.netVerified public profiles
- Discussion messages
- 0
- First activity
- Unknown
- Last activity
- Unknown
- First explicit stance
- Unknown
- Latest explicit stance
- Unknown
- Stance changes
- 0
- Viewpoint consistency
- No explicit position stated
- Other policies
- 4
First explicit stance: Unknown → Latest explicit stance: Unknown · Stance changes: 0
Viewpoint consistency: No explicit position stated
- Sep 12, 2026
author
Source facts ↗
Per-policy stance timelines:LAC-2018-14 · Unknown · No explicit position statedLAC-2019-1 · Unknown · No explicit position statedLAC-2019-2 · Unknown · No explicit position statedLAC-2019-3 · Unknown · No explicit position statedLAC-2019-4 · Unknown · No explicit position statedTotal policy messages: 0
Sources and coverage
Official policy sources
Public discussion archives
- lacnic-politicas
- Earliest captured
- Oct 21, 1999
- Latest captured
- Oct 12, 2026
- Last refresh
- Aug 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 5,553
- Known gaps
- 26
- www.lacnic.net
- lacnic-anuncios
- Earliest captured
- Aug 13, 2026
- Latest captured
- Oct 7, 2026
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,135
- Known gaps
- 0
- lacnic-ietf-lac
- Earliest captured
- May 30, 2013
- Latest captured
- Dec 30, 2015
- Last refresh
- Oct 12, 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
- Oct 12, 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
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 373
- Known gaps
- 0
- lacnic-lacnog
- Earliest captured
- Aug 1, 2026
- Latest captured
- Oct 9, 2026
- Last refresh
- Oct 11, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 6,416
- Known gaps
- 2
- lacnic-lactf
- Earliest captured
- Apr 13, 2004
- Latest captured
- Dec 29, 2006
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,267
- Known gaps
- 0
- lacnic-seguridad
- Earliest captured
- Jan 26, 2006
- Latest captured
- Dec 28, 2007
- Last refresh
- Oct 12, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1,356
- Known gaps
- 0
Coverage
Partial
Earliest captured: Oct 21, 1999
Latest captured: Oct 12, 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.
