Skip to main content

LACNIC · RIR Watchdog

Managing Recovered Resources that were originally part of the Reserve for Critical Infrastructure

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-2022-3
RIR
LACNIC
Official status
Implemented
Normalized status
Accepted
Introduced
Apr 25, 2023
Last source update
Oct 10, 2026
Coverage
Partial

Who actually shaped the debate?

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

BTW Analysis

BTW Analysis

What changed

The recorded process moved from introduction on 2023-04-25 through two versions, both recorded on that date as implemented and normalized as accepted, to a final accepted decision on 2023-08-22. The supplied evidence does not include the version texts or a change record, so no substantive difference between versions 1 and 2 can be established.

What the debate was really about

The subject of any substantive debate cannot be reconstructed from the supplied record. It contains no discussion messages, discussion participants, stance timelines, or unresolved or minority arguments. The evidence establishes procedural progression and acceptance, not the policy issues, competing interests, incentives, or rationale involved.

Arguments that prevailed

  • No substantive argument can be identified as prevailing. What prevailed procedurally was the proposal, as shown by the accepted decision on 2023-08-22.

Decision vs debate

The decision is clear: the policy was accepted on 2023-08-22. Discussion is not evidenced in the measured dataset, which records zero messages, zero discussion participants, zero active days, zero stance participants, and zero stance transitions. Acceptance therefore must not be interpreted as proof of documented unanimity, broad deliberation, or persuasion within this dataset.

Participation concentration

The record contains one formal actor and one total participant but no discussion participants and no messages. The zero HHI, zero message-share values, zero core-participant counts, and zero effective participant count are degenerate no-message outputs; they do not show either broad distribution or speaker concentration. The record is formally minimal rather than a measurable multi-person debate.

Chokepoint analysis

The only identifiable procedural chokepoint is the accepted decision recorded on 2023-08-22, which converted the proposal's recorded progression into an accepted outcome. The supplied facts do not identify the formal actor, decision rationale, voting or consensus mechanism, or any participant influence, so no actor-specific control or institutional power shift can be attributed.

Uncertainties

  • Zero recorded messages and discussion participants may indicate either that no discussion occurred or that relevant discussion was not captured in the measured dataset.
  • The texts and substantive differences of versions 1 and 2 are not supplied, so the extent and direction of policy evolution cannot be determined.
  • The decision rationale, consensus quality, vote distribution, and identity or role of the single formal actor are not supplied.
  • The zero concentration metrics cannot be interpreted as evidence of evenly distributed participation because they arise from a dataset containing no messages.
  • The supplied Doctrine package provides only a partial official position for this subject and does not support a substantive company judgment about the policy's merits, legitimacy, incentives, or power effects.

Policy evolution

2
Accepted · Implemented
Apr 25, 2023
Source facts ↗

Current-text scope · The current-text description changes from unchanged text in sections 2.3.3.2, 2.3.5, and 7.1 to unchanged text only in section 2.3.5.

Reincorporation requirement in proposed section 2.3.5 item 8 · The proposed requirement changes from reincorporation into “the reserve” accompanied by the purpose clause “so that this reserve will be preserved as much as possible” to direct reincorporation into “this reserve”; the quarantine requirement remains present.

Presented-at information · The presented-at entry changes from “LACNIC 38 (04/10/2022)” to “LACNIC 39 (10/05/2023).”

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 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 policies3

Sources and coverage

Official policy sources

Public discussion archives

  • lacnic-politicas
    Earliest captured
    Oct 21, 1999
    Latest captured
    Oct 8, 2026
    Last refresh
    Aug 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    5,368
    Known gaps
    26
  • www.lacnic.net
  • lacnic-anuncios
    Earliest captured
    Aug 13, 2026
    Latest captured
    Oct 7, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,118
    Known gaps
    0
  • lacnic-ietf-lac
    Earliest captured
    May 30, 2013
    Latest captured
    Dec 30, 2015
    Last refresh
    Oct 10, 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 10, 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 10, 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,123
    Known gaps
    0
  • lacnic-lactf
    Earliest captured
    Apr 13, 2004
    Latest captured
    Dec 29, 2006
    Last refresh
    Oct 10, 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 10, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    1,356
    Known gaps
    0

Coverage

Partial
Earliest captured: Oct 21, 1999
Latest captured: Oct 11, 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.