Skip to main content

LACNIC · RIR Watchdog

Impact Analysis Is Mandatory

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-3
RIR
LACNIC
Official status
Abandoned
Normalized status
Abandoned
Introduced
Apr 12, 2023
Last source update
Oct 13, 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 a procedural evolution rather than an identifiable substantive policy change: LAC-2020-3 was introduced on 2023-04-12, had five numbered versions each recorded as abandoned, and received a final abandoned decision on 2024-07-11. Because the proposal texts, version differences, and baseline policy are not supplied, no change in rights, duties, eligibility, or resource policy can be established.

What the debate was really about

The subject of any substantive debate cannot be determined from the supplied evidence. No messages, stance timelines, argument summaries, proposal text, or version differences are present. The record therefore supports only the conclusion that repeated versions did not produce an adopted proposal, not an account of the interests or policy questions contested.

Arguments that prevailed

  • No substantive argument can be identified as having prevailed. Procedurally, abandonment prevailed and the proposal did not displace the pre-proposal position within the supplied chronology.

Arguments that did not prevail

  • The proposal's case for adoption did not prevail procedurally, but its substance and supporting arguments are not supplied and therefore cannot be characterized.
  • No minority or unresolved argument can be identified because none is included in the supplied stance timelines or argument records.

Decision vs debate

A formal outcome is observable, but a discussion path is not. The chronology records abandonment on 2024-07-11, while the measured dataset contains zero messages, zero discussion participants, zero active days, zero stance participants, and zero stance transitions. This means the decision cannot be causally linked to any captured argument, participant stance, consensus finding, or vote. It does not establish that no discussion occurred outside the captured dataset.

Participation concentration

Participation concentration cannot be meaningfully assessed. The dataset counts one formal actor and one total participant but no discussion participants or messages. Consequently, the reported zero message shares, zero HHI, zero effective participant count, and zero core counts are non-informative rather than evidence of broad, balanced, or unconcentrated participation.

Chokepoint analysis

The observable chokepoint was failure to advance beyond repeated abandoned versions to adoption. The supplied record does not identify whether this resulted from lack of support, withdrawal, procedural expiry, supersession, unresolved objections, or another mechanism. The absence of proposal texts, discussion records, stance data, and decision rationale prevents attribution of the outcome to a particular actor or institutional stage.

Uncertainties

  • It is unknown what versions 1 through 5 proposed or how they differed.
  • It is unknown why each version and the final proposal were abandoned.
  • It is unknown whether zero captured discussion reflects an absence of public debate or incomplete capture scope.
  • The actual chronology and duration of substantive revisions cannot be reconstructed because all five version records carry the same date.
  • No decision rationale, consensus determination, vote, or responsible decision-maker is supplied.
  • The identity and procedural role of the single formal actor are not supplied.
  • The Doctrine package establishes only a partial position for this subject and cannot fill the factual gaps.

Policy evolution

2
Abandoned · Abandoned
Apr 12, 2023
Source facts ↗

PDP chair functions concerning staff comments and impact analyses · The old version eliminated the PDP-chair function in section 3.2.1; the new version instead retains a function requiring the chairs to receive staff comments on proposal aspects in addition to the corresponding Impact Analysis.

Extension of the four-week Impact Analysis publication deadline · The old version allowed an extension of no more than two weeks and required presentation of a draft. The new version removes the fixed two-week cap, requires that an extension be reasonable, and makes presentation of a draft conditional on possibility.

Public Policy Forum workload exception to deadline calculation · The new version adds that the four weeks preceding the Public Policy Forum are not counted as working days for new proposals or versions with significant modifications, while stating that LACNIC will nevertheless attempt to publish the documents; the old version proceeds directly from the Impact Analysis contents to Additional information without this exception.

3
Abandoned · Abandoned
Apr 12, 2023
Source facts ↗

Impact Analysis publication deadline · The maximum period for LACNIC to publish an Impact Analysis for each proposal version changed from four weeks to six weeks; the provision allowing reasonable extensions in special cases remains.

4
Abandoned · Abandoned
Apr 12, 2023
Source facts ↗

PDP chair responsibility for staff input · The chair function changes from merely receiving staff comments to requesting and receiving those comments, in addition to the corresponding Impact Analysis.

Impact Analysis publication scope · The requirement changes from publishing an Impact Analysis for each version of a proposal to publishing one for the latest version; the new version also expressly states that an analysis is unnecessary for a version superseded by a newer version.

Impact Analysis deadline and delay accountability · The fixed maximum six-week deadline, subject to a reasonably justified special-case extension and possible draft presentation, is replaced by publication as soon as possible within a reasonable period. A delay exceeding four weeks, after excluding the four weeks before each Public Policy Forum, must be justified both at the Public Forum and on the Policy List.

Treatment of the pre-forum period · The old version excluded the four-week pre-forum period as working days only for new proposals or versions with significant modifications and retained a best-efforts publication commitment. The new version instead excludes that period when determining whether an Impact Analysis delay exceeds four weeks, without retaining the old best-efforts sentence.

5
Abandoned · Abandoned
Apr 12, 2023
Source facts ↗

Impact Analysis publication triggers · The requirement to publish an Impact Analysis for the latest version of each proposal was replaced with requirements covering the first version of each proposal and versions containing substantial changes relative to prior analyses, even without community discussion.

Impact Analyses for subsequent proposal versions · The new version adds a conditional process for subsequent versions: LACNIC prepares an Impact Analysis when community discussion occurs and comments are received, with the chairs consulted if the level of discussion is uncertain.

Moderator authority to require an Impact Analysis · The new version adds an overriding requirement that LACNIC prepare an Impact Analysis whenever the moderators identify the need for one.

Superseded proposal versions · The prior express exception stating that Impact Analyses need not be published for proposal versions superseded by newer versions was removed and replaced by the new version-based preparation and publication rules.

Debate timeline

  1. Introduced

    Introduced

    Source facts ↗
  2. Official version

    1

    Abandoned · Abandoned

    Source facts ↗
  3. Official version

    2

    Abandoned · Abandoned

    Source facts ↗
  4. Official version

    3

    Abandoned · Abandoned

    Source facts ↗
  5. Official version

    4

    Abandoned · Abandoned

    Source facts ↗
  6. Official version

    5

    Abandoned · Abandoned

    Source facts ↗
  7. 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 policies39
    Freshness: Stale

    Last research attempt: Sep 19, 2026

    Identity verified: Oct 11, 2026

    The IPv6 Company · Historical
    Name: Jordi Palet Martínez Email: [email protected] Organization: The IPv6 Company
    politicas.lacnic.net
    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
    39

    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: 141

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

Coverage

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