Skip to main content

LACNIC · RIR Watchdog

Adapting the allocation / assignment policy for IPv4 exhaustion.

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-2013-3
RIR
LACNIC
Official status
Implemented
Normalized status
Accepted
Introduced
Nov 25, 2013
Last source update
Oct 9, 2026
Coverage
Partial

Who actually shaped the debate?

10Total participants
8Discussion contributors
2Formal actors
10Discussion messages
7.1Effective participants
70%Top-five discussion share
3People covering 50%
6People covering 80%

BTW Analysis

BTW Analysis

What changed

LAC-2013-3 moved from introduction on 25 November 2013 through two recorded versions, both dated 25 November 2013 and marked "Implemented" with normalized status "accepted," to an accepted decision on 15 August 2014. The supplied evidence does not reveal any substantive difference between versions 1 and 2.

What the debate was really about

The subject of the debate cannot be determined from the supplied record because the proposal text, policy objective, discussion messages, stakeholder interests, and stated arguments are absent. The record establishes procedural progression and acceptance, not the substantive issue contested or resolved.

Decision vs debate

The decision outcome is clear: the proposal was accepted on 15 August 2014 and its recorded versions carry implemented status. The discussion record is absent: there are zero messages, zero discussion participants, zero active days, zero stance-bearing participants, and zero stance transitions. Consequently, the evidence cannot connect deliberation, persuasion, consensus, voting, or particular arguments to the outcome.

Participation concentration

The dataset contains two formal actors and no discussion participants. All message-share measures, HHI, effective participant count, and core-participant counts are zero because there were zero captured messages. These values are structurally uninformative and do not establish either broad participation, equal participation, or actual concentration of influence.

Chokepoint analysis

The observable process chokepoint is the formal decision stage, because the supplied chronology records an accepted decision while providing no observable discussion pathway into that decision. However, the decision-maker, consensus test, voting procedure, actor identities, and respective authority of the two formal actors are not supplied, so no person or institution can be identified as the effective chokepoint and no substantive power shift can be established.

Uncertainties

  • The proposal text, policy objective, expected benefits, costs, and affected stakeholder rights are not supplied.
  • The substantive differences, if any, between versions 1 and 2 are unknown.
  • The common date for introduction and both versions may reflect same-day processing or a source-metadata convention.
  • No discussion messages, participant identities, stance timelines, unresolved arguments, or minority arguments are supplied.
  • The identities and institutional roles of the two formal actors are unknown.
  • The decision procedure, decision authority, consensus test, voting record, rationale, and implementation details are absent.
  • Zero concentration metrics result from a zero-message dataset and cannot be used to infer evenly distributed participation.
  • The participation metrics were computed on 27 August 2026 from the identified source revision, but the completeness of the underlying historical record cannot be assessed.
  • The supplied Doctrine establishes no complete official position on this policy and does not fill the missing historical or substantive facts.

Policy evolution

2
Accepted · Implemented
Nov 25, 2013
Source facts ↗

Section 11.1 critical-infrastructure eligibility and repeat requests · The supplied new text expressly allows a critical-infrastructure request even when the requester has already received IPv4 resources, and exempts critical-infrastructure requests from the restriction on receiving additional resources from the reserve. It removes the supplied old text's separate six-month restriction and its requirements to follow item 2.3.3.2, submit an IPv6 implementation plan, and demonstrate at least 80% utilization.

Section 11.1 reserve activation and treatment of pending requests · The reserve-activation trigger changes from inability to satisfy a request using the section 11.2 reserve to inability to satisfy a request in full because of insufficient IPv4 resources in the LACNIC region. The pending-request rule also changes from requests larger than a /22 receiving only a /22 to applications smaller than a /22 receiving only a /22.

Section 11.1 independence cross-reference · The supplied old text states that this policy does not replace section 11.2 and that the section 11.2 reserve is independent; the supplied new text instead states that it does not replace section 11.1 while continuing to describe the section 11.2 reserve as independent.

Section 11.2 repeat allocations and qualification requirements · The supplied new text removes the separate prohibition on future allocations or assignments during a six-month period, retaining a single rule permitting additional resources after six months and critical-infrastructure requests up to a /22 at any time. It also removes the supplied old text's requirements for recurring critical-infrastructure requests to follow item 2.3.3.2, include an IPv6 implementation plan, and demonstrate at least 80% utilization.

Terminology across language versions · The supplied new version adds an explicit terminology-harmonization proposal: Spanish "suave" is to be replaced by "gradual," and Portuguese "tranquilo" by "gradativo." The supplied old version contains no corresponding terminology proposal.

Debate timeline

  1. Introduced

    Introduced

    Source facts ↗
  2. Official version

    1

    Accepted · Implemented

    Source facts ↗
  3. Official version

    2

    Accepted · Implemented

    Source facts ↗
  4. Public discussion

    [LACNIC/Politicas] LAC-2013-03v2 - Call for consensus // llamado a consenso // convocatória ao consenso

    7 Discussion messages · 7 Entities

    Source facts ↗
  5. Official decision

    accepted

    accepted

    Source facts ↗

Entities

Freshness: Stale
  1. Discussion messages2
    First activityJan 27, 2014
    Last activityFeb 14, 2014
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies24
  2. Max Larson Henry · Identity unresolved
    Discussion messages2
    First activityNov 22, 2013
    Last activityNov 25, 2013
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies4
  3. Juan Alejo Peirano · Identity unresolved
    Discussion messages1
    First activityFeb 26, 2014
    Last activityFeb 26, 2014
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies4
  4. Christian O'Flaherty · Identity unresolved
    Discussion messages1
    First activityFeb 26, 2014
    Last activityFeb 26, 2014
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies4
  5. Luis Balbinot · Identity unresolved
    Discussion messages1
    First activityFeb 26, 2014
    Last activityFeb 26, 2014
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies2
  6. Pedro Torres · Identity unresolved
    Discussion messages1
    First activityFeb 28, 2014
    Last activityFeb 28, 2014
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies1
  7. Discussion messages1
    First activityFeb 28, 2014
    Last activityFeb 28, 2014
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies3
  8. Edna Samudio de Jaen · Identity unresolved
    Discussion messages1
    First activityFeb 28, 2014
    Last activityFeb 28, 2014
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies0
  9. Discussion messages0
    First activityUnknown
    Last activityUnknown
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies17
  10. Discussion messages0
    First activityUnknown
    Last activityUnknown
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies1

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,296
    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,103
    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 8, 2026
    Last refresh
    Oct 10, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    6,010
    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.