Skip to main content

LACNIC · RIR Watchdog

ASN 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-4
RIR
LACNIC
Official status
Implemented
Normalized status
Accepted
Introduced
Mar 11, 2019
Last source update
Oct 14, 2026
Coverage
Partial

Who actually shaped the debate?

3Total participants
UnknownDiscussion contributors
3Formal actors
UnknownDiscussion messages
UnknownEffective participants
UnknownTop-five discussion share
UnknownPeople covering 50%
UnknownPeople covering 80%

BTW Analysis

BTW Analysis

What changed

The verified record shows LAC-2019-4 introduced on 11 March 2019, with three labeled versions recorded on that same date and each marked “Implemented” or normalized as accepted, followed by a formal acceptance decision on 22 January 2020. Because no version texts or change summaries are supplied, no substantive change among versions 1, 2, and 3 can be identified.

What the debate was really about

The subject of any debate cannot be determined from the supplied evidence. There are no captured messages, participant stance timelines, minority arguments, or descriptions of proponents’ and opponents’ concerns. The evidence supports only a procedural account of versioning and acceptance, not a substantive characterization of the debate.

Arguments that prevailed

  • No specific substantive argument can be identified as having prevailed. Only the policy itself is recorded as formally accepted.

Arguments that did not prevail

  • No rejected, unresolved, or minority argument is supplied, so none can be identified as not prevailing.

Decision vs debate

The formal decision is clear: the policy was accepted on 22 January 2020. The discussion record is absent from the supplied dataset: it contains zero messages, zero discussion participants, zero active days, zero recorded stances, and zero stance transitions. Acceptance therefore cannot be interpreted as evidence of broad deliberative agreement, a particular consensus level, or support for any identified rationale.

Participation concentration

Meaningful participation concentration cannot be evaluated. Although the dataset counts three formal actors and three total participants, it records no discussion participants or messages. Consequently, the zero message shares, zero HHI, zero effective participant count, and zero core-participant counts are degenerate no-activity results, not evidence that participation was broad, equal, or unconcentrated. The identities, roles, stances, and influence of the three formal actors are unknown.

Chokepoint analysis

The observable chokepoint was the formal decision stage culminating in acceptance on 22 January 2020, but the supplied facts do not identify who controlled that stage or what standard was applied. With no discussion record, rationale, vote, consensus determination, or actor identities, it is not possible to establish whether agenda control, drafting authority, community deliberation, or administrative review determined the outcome.

Uncertainties

  • The identical recorded date for introduction and all three versions leaves their actual sequence and timing uncertain.
  • The absence of version texts and change summaries prevents reconstruction of substantive amendments, compromises, or administrative relabeling.
  • Zero captured messages and discussion participants do not prove that no debate occurred in uncaptured venues or records.
  • The identities, functions, positions, and relative influence of the three formal actors are not supplied.
  • No decision rationale, vote count, consensus determination, appeal record, or implementation evidence is supplied.
  • The Doctrine package establishes no complete official company position on LAC-2019-4.
  • The chronology reflects a supplied verified record attributed to a LACNIC institutional page; under the Doctrine package, that page is not controlling Doctrine authority.

Policy evolution

2
Accepted · Implemented
Mar 11, 2019
Source facts ↗

Summary · The summary changes from a title-like description of ASN mergers, acquisitions, reorganizations, and relocations to a statement that the proposal establishes a mechanism for updating ASN resource records in those cases.

Validity of non-authorized resource transfers · The proposed policy adds an explicit rule that non-authorized sales or transfers of assigned or allocated resources are invalid before describing the transfers LACNIC will process.

Intra-RIR and inter-RIR scope · The explicit qualification that covered mergers, acquisitions, reorganizations, or relocations may be intra-RIR or inter-RIR is removed; the replacement provision describes those transactions without the qualification.

Supporting legal documentation · The documentation provision changes from documentation decided by LACNIC and/or another applicable RIR to documentation that, at LACNIC's discretion, supports the operation. It also adds examples: a legal asset-transfer document, an inventory of assets used to maintain the resources, and a client list.

Resource-retention justification and surplus resources · The proposed policy adds requirements to justify retaining all resources, return or transfer surplus resources under applicable policies, and allow LACNIC to determine the conditions and deadline when resources must be returned.

Additional information concerning legal proceedings and costs · The additional-information section adds an explanation that absence of the policy might lead to court proceedings over registry updates and states that the policy could avoid that situation and related legal costs while preserving community-directed control.

3
Accepted · Implemented
Mar 11, 2019
Source facts ↗

Intended transfer scope · The rationale changes from stating that all cases are valid to stating that the proposal is only for the Intra-RIR case.

Debate timeline

  1. Introduced

    Introduced

    Source facts ↗
  2. Official version

    1

    Accepted · Implemented

    Source facts ↗
  3. Official version

    2

    Accepted · Implemented

    Source facts ↗
  4. Official version

    3

    Accepted · Implemented

    Source facts ↗
  5. Official decision

    accepted

    accepted

    Source facts ↗

Entities

Freshness: Stale
  1. Discussion messages0
    First activityUnknown
    Last activityUnknown
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies39
  2. Discussion messages0
    First activityUnknown
    Last activityUnknown
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies5
    Freshness: Stale

    Last research attempt: Sep 19, 2026

    Identity verified: Sep 20, 2026

    LACNIC · Historical
    /D General information Download TXT PDF DOCX Original language Español Last modified 14/04/2014 Status Implemented 100 %. Authors Edmundo Cázarez - Version [1] In discussion 15/08/2014 Ratification by the board 15/08/2014 Implemented 03/10/2014 Version 1 Summary This document proposes giving equal treatment to returned and recovered resources, expanding the scope
    politicas.lacnic.net

    Verified 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
    5

    First explicit stance: Unknown → Latest explicit stance: Unknown · Stance changes: 0

    Viewpoint consistency: No explicit position stated

    1. Sep 12, 2026

      author

      Source facts ↗

    Total policy messages: 0

  3. Discussion messages0
    First activityUnknown
    Last activityUnknown
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies4

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,637
    Known gaps
    26
  • www.lacnic.net
  • lacnic-anuncios
    Earliest captured
    Aug 13, 2026
    Latest captured
    Oct 7, 2026
    Last refresh
    Oct 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,176
    Known gaps
    0
  • lacnic-ietf-lac
    Earliest captured
    May 30, 2013
    Latest captured
    Dec 30, 2015
    Last refresh
    Oct 14, 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 14, 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 14, 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,518
    Known gaps
    3
  • lacnic-lactf
    Earliest captured
    Apr 13, 2004
    Latest captured
    Dec 29, 2006
    Last refresh
    Oct 14, 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 14, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    1,356
    Known gaps
    0

Coverage

Partial
Earliest captured: Oct 21, 1999
Latest captured: Oct 14, 2026

Freshness

Freshness: Stale · Last refresh:

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.