Skip to main content

LACNIC · RIR Watchdog

Priority on the IPv4 Waiting List for Those Who Have Already Deployed IPv6

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-2025-4
RIR
LACNIC
Official status
Did not reach consensus
Normalized status
Rejected
Introduced
Sep 2, 2025
Last source update
Oct 15, 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-2025-4 entered the recorded process as version 1 on 2025-09-02 and was ultimately rejected on 2025-11-12 after being recorded as having not reached consensus. No later version, implementation, or substantive policy change is established by the supplied facts.

What the debate was really about

The substantive subject of the debate cannot be determined from the supplied record because it contains neither the proposal text nor discussion messages, positions, or arguments. The only established issue at the outcome level was whether version 1 had achieved consensus; the recorded answer was that it had not.

Arguments that prevailed

  • No substantive argument can be identified as prevailing. The only supported prevailing procedural determination was that version 1 had not reached consensus, resulting in rejection.

Arguments that did not prevail

  • The proposal embodied in version 1 did not prevail because it was rejected after failing to reach consensus; the record does not disclose the proposal's substantive claims or supporting arguments.

Decision vs debate

The decision is documented, but the discussion is not. The chronology establishes a rejected outcome on 2025-11-12, while the participation data records zero messages, zero discussion participants, zero active days, no stance timelines, and no stance transitions. It is therefore possible to report the disposition but not to reconstruct the deliberation or attribute the result to particular participants or objections.

Participation concentration

Participation concentration cannot be meaningfully assessed from an empty message sample. Top-message shares and HHI of 0.0, an effective participant count of 0.0, and zero core participants indicate no captured discussion rather than broad, equal, or decentralized participation. One formal actor is counted, but that actor's identity, authority, and influence are not supplied.

Chokepoint analysis

The observable chokepoint was the consensus threshold: version 1 did not reach consensus and consequently ended in rejection. The evidence does not reveal the substantive objections, procedural assessment, actor, or institutional mechanism responsible for that blockage, so control of the chokepoint cannot be attributed to the single counted formal actor or to any stakeholder coalition.

Uncertainties

  • Zero captured messages may indicate that no public discussion occurred or that the evidence collection is incomplete.
  • The substantive policy change sought by LAC-2025-4 is not supplied.
  • The objections or disagreements that prevented consensus are not identified.
  • The identity, authority, conduct, and influence of the single formal actor are unknown.
  • The record does not establish whether the proposal was withdrawn, revised elsewhere, procedurally closed, appealed, or eligible for resubmission.
  • No complete Doctrine position for or against LAC-2025-4 is supplied, so the rejection cannot be characterized as a Doctrine endorsement.

Policy evolution

Debate timeline

  1. Introduced

    Introduced

    Source facts ↗
  2. Official version

    1

    Rejected · Did not reach consensus

    Source facts ↗
  3. Official decision

    rejected

    rejected

    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 9, 2026

      author

      Source facts ↗

    Total policy messages: 156

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,693
    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,206
    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,567
    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.