Skip to main content

LACNIC · RIR Watchdog

Delete ROAs for Recovered Resources

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-2023-5
RIR
LACNIC
Official status
Abandoned
Normalized status
Abandoned
Introduced
Sep 20, 2023
Last source update
Oct 14, 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 supplied chronology shows only a procedural status progression: LAC-2023-5 was introduced on 20 September 2023, its sole supplied version record—version 1—was dated the same day and labeled abandoned, and a decision on 9 February 2025 confirmed abandonment. No adopted policy change is established, and no substantive revision can be identified from the supplied evidence.

What the debate was really about

The subject of any substantive debate cannot be determined because the proposal text, participant statements, stance timelines, and arguments are absent. The verified record supports only that a proposal entered the process and ultimately did not advance to adoption; it does not support claims about competing policy principles, interests, incentives, beneficiaries, or opponents.

Decision vs debate

The decision record is clear: LAC-2023-5 was abandoned on 9 February 2025. The discussion record is empty: zero messages, zero discussion participants, zero active days, no stance participants, and no stance transitions. Therefore, the abandonment outcome is established, but no deliberative path connecting introduction to that outcome can be reconstructed.

Participation concentration

Participation concentration cannot be characterized as concentrated or dispersed. The zero HHI and zero top-message shares arise from a base of zero messages and zero discussion participants, so they indicate an absence of measurable discussion rather than evenly distributed participation. One formal actor and one total participant were counted, but that actor's identity, role, and involvement in deliberation are not supplied.

Chokepoint analysis

No substantive or procedural chokepoint can be identified from the supplied facts. The chronology records introduction, an abandoned version, and a later abandonment decision, but provides no proposal text, decision rationale, consensus assessment, vote, sponsor action, or discussion record showing where or by whom progression was blocked.

Uncertainties

  • The proposal text, objectives, and intended policy changes are not supplied.
  • The identity, role, conduct, and objectives of the single counted formal actor are unknown.
  • The relationship between the version-1 abandoned status dated 20 September 2023 and the later abandonment decision dated 9 February 2025 is unexplained.
  • The supplied dataset may not cover every relevant mailing list, meeting, consultation channel, or private exchange.
  • No decision rationale, voting record, consensus assessment, decision-maker identity, or abandonment procedure is supplied.
  • The Doctrine package does not establish a complete substantive official position for this policy 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. Discussion messages0
    First activityUnknown
    Last activityUnknown
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies0
    Freshness: Stale

    Last research attempt: Sep 11, 2026

    Identity verified: Sep 11, 2026

    LACNIC community · Historical
    Authors Santiago Aggio - Version [1] In discussion 20/09/2023 - 15/11/2023 First consensus assessment 15/11/2023 - 29/11/2023 Last call for comments 29/11/2023 - 27/12/2023 Second consensus assessment 27/12/2023 - 03/01/2024 Ratification by the board 03/01/2024 Not ratified 09/02/2024 Abandoned 09/02/2025 Public comments by LACNIC staff for this version LAC-2023-5 v1: Delete ROAs for Recovered Resources LACNIC Staff's Interpretation of the Proposal Authors: Santiago Aggio Applicability: This proposal introduces changes to the Policy Manual.
    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
    0

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

    Viewpoint consistency: No explicit position stated

    1. Sep 9, 2026

      author

      Source facts ↗

    Total policy messages: 0

Sources and coverage

Official policy sources

Public discussion archives

  • lacnic-politicas
    Earliest captured
    Oct 21, 1999
    Latest captured
    Oct 14, 2026
    Last refresh
    Aug 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    5,662
    Known gaps
    26
  • www.lacnic.net
  • lacnic-anuncios
    Earliest captured
    Aug 13, 2026
    Latest captured
    Oct 7, 2026
    Last refresh
    Oct 15, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,207
    Known gaps
    0
  • lacnic-ietf-lac
    Earliest captured
    May 30, 2013
    Latest captured
    Dec 30, 2015
    Last refresh
    Oct 15, 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 15, 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 15, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    373
    Known gaps
    0
  • lacnic-lacnog
    Earliest captured
    Aug 1, 2026
    Latest captured
    Oct 13, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    6,568
    Known gaps
    3
  • lacnic-lactf
    Earliest captured
    Apr 13, 2004
    Latest captured
    Dec 29, 2006
    Last refresh
    Oct 15, 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 15, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    1,356
    Known gaps
    0

Coverage

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