Skip to main content

LACNIC · RIR Watchdog

Eliminate the requirement for applicants to return the addresses they have been assigned by their providers once they receive a direct assignment

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-10
RIR
LACNIC
Official status
Abandoned
Normalized status
Abandoned
Introduced
Oct 28, 2019
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 verified record shows LAC-2019-10 introduced on 2019-10-28, with version 1 recorded as abandoned on that same date, followed by a decision on 2020-09-21 confirming abandonment. No approval, implementation, replacement text, substantive policy effect, or change in rights or institutional authority is established.

What the debate was really about

The substantive subject of the debate cannot be determined from the supplied evidence. No proposal text, arguments, messages, participant stances, or unresolved or minority positions are provided. The record supports only an interpretation of process outcome: the proposal was introduced and ultimately recorded as abandoned, while the reasons and competing positions remain unknown.

Decision vs debate

The decision outcome is documented, but the discussion is not. LAC-2019-10 has a recorded abandonment decision dated 2020-09-21, 329 days after its introduction on 2019-10-28. The dataset records zero messages, zero discussion participants, zero active days, zero stance participants, and zero stance transitions, so no relationship between deliberation and the decision can be established.

Participation concentration

The captured process contains one formal actor and one total participant but no recorded discussion participation. The zero message shares, HHI, effective-participant count, and core counts represent an empty observed message dataset, not broad, equal, or unconcentrated participation. They also do not prove that no discussion occurred outside the captured source.

Chokepoint analysis

The only observable chokepoint is the formal policy disposition: one formal actor is recorded and the process ended in abandonment. With no actor identities, messages, stance data, rationale, vote, or consensus record, the supplied evidence cannot establish who controlled that chokepoint, how it operated, or whether abandonment resulted from withdrawal, rejection, inactivity, supersession, or another mechanism.

Uncertainties

  • Zero recorded messages may indicate that no discussion occurred in the measured source or that relevant discussion was not captured.
  • The proposal text and the substantive policy change sought are not supplied.
  • The relationship between the version-1 entry marked abandoned on 2019-10-28 and the formal abandonment decision on 2020-09-21 is not procedurally explained.
  • No decision rationale, voting record, consensus assessment, actor identity, or procedural criterion is supplied.
  • The abandonment outcome does not distinguish among rejection, voluntary withdrawal, inactivity, supersession, revision plans, or another cause.
  • The Doctrine package establishes only a partial official position for this subject.

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. Edmundo Cazarez-Lopez · Identity unresolved
    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,372
    Known gaps
    26
  • www.lacnic.net
  • lacnic-anuncios
    Earliest captured
    Aug 13, 2026
    Latest captured
    Oct 7, 2026
    Last refresh
    Oct 10, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,122
    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 10, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    6,122
    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 10, 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.