Skip to main content

LACNIC · RIR Watchdog

Add a short descriptor to policy proposal identification codes

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-2020-8
RIR
LACNIC
Official status
Abandoned
Normalized status
Abandoned
Introduced
Sep 23, 2020
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

LAC-2020-8 was introduced on 23 September 2020, recorded as version 1, and reached a recorded decision status of abandoned on 3 December 2020. The supplied facts show no adoption, implementation, later version, or replacement policy consequence.

What the debate was really about

The substance of the debate cannot be determined from the supplied record because it contains no proposal text, messages, argument summaries, participant stances, or minority positions. The record establishes only the proposal's lifecycle and abandoned outcome, not the policy issue contested or the reasons for abandonment.

Arguments that prevailed

  • No substantive argument can be identified as prevailing. The only established result is the formal outcome of abandonment, without a supplied rationale or causal account.

Decision vs debate

The decision record and discussion record are materially different: abandonment is recorded as the formal outcome, while the measured discussion dataset contains zero messages, zero discussion participants, zero active days, zero stance participants, and zero stance transitions. This supports saying that no discussion was observed in the measured dataset, but not that no discussion occurred through meetings, mailing lists, or other uncaptured channels. The 71-day interval between introduction and decision does not reveal what activity occurred during that period.

Participation concentration

Participation concentration is not meaningfully measurable because there were no recorded messages or discussion participants. The zero top-message shares, HHI, effective-participant count, and core counts are empty-discussion results, not evidence of broad, equal, or decentralized participation. One formal actor and one total participant were counted, but that actor's identity, role, authority, and causal relationship to abandonment are not supplied.

Chokepoint analysis

The only observable process chokepoint is the formal layer: one formal actor is counted while no message-based participation is recorded, and the proposal ultimately has an abandoned decision status. This does not establish that the formal actor controlled, initiated, or caused the outcome. The decisive procedural mechanism, decision-maker, withdrawal action, consensus assessment, or other basis for abandonment remains unidentified.

Uncertainties

  • Zero recorded messages may mean that no discussion occurred or that relevant discussion was not captured in the verified dataset.
  • The proposal text, objective, and changes sought by version 1 are not supplied.
  • The identity, role, authority, action, and causal significance of the single formal actor are unknown.
  • No reason, procedural basis, decision-maker, consensus assessment, vote, or withdrawal notice is supplied for the abandoned outcome.
  • The version-1 entry is dated the same day as introduction while carrying an abandoned status; the record does not establish whether that status applied on that date or was attached later.
  • The supplied chronology may be incomplete if additional versions, meetings, discussion channels, or related proposals existed outside the verified evidence.
  • The Doctrine package establishes no complete official position specifically explaining LAC-2020-8 and therefore supplies no basis for inventing an endorsement, opposition, preferred outcome, or causal narrative.

Policy evolution

Debate timeline

  1. Introduced

    Introduced

    Source facts ↗
  2. Official version

    1

    Abandoned · Abandoned

    Source facts ↗
  3. Official decision

    abandoned

    abandoned

    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 policies0

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,388
    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.