Skip to main content

LACNIC · RIR Watchdog

Resources Are Assigned in a Unique and Exclusive Capacity

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-6
RIR
LACNIC
Official status
Implemented
Normalized status
Accepted
Introduced
Apr 23, 2019
Last source update
Oct 9, 2026
Coverage
Partial

Who actually shaped the debate?

4Total participants
1Discussion contributors
3Formal actors
1Discussion messages
1Effective participants
100%Top-five discussion share
1People covering 50%
1People covering 80%

BTW Analysis

BTW Analysis

What changed

LAC-2019-6 was introduced on 23 April 2019, and the record lists versions 1 and 2 on that same date, each with raw status "Implemented" and normalized status "accepted." An accepted decision followed on 22 January 2020. Because neither version text nor a change log is supplied, no substantive difference between the versions can be identified.

What the debate was really about

The subject of any substantive debate cannot be determined from the supplied record. There are no captured messages, participant stances, unresolved or minority arguments, policy provisions, or decision rationale. The evidence establishes a formal policy progression and accepted outcome, not the issues, incentives, or competing positions underlying it.

Arguments that prevailed

  • The proposal itself prevailed in the narrow procedural sense that the final recorded decision was accepted; no substantive supporting argument or rationale is available in the supplied evidence.

Decision vs debate

The decision record is clear but the discussion record is empty: the proposal reached an accepted decision on 22 January 2020, while the metrics contain zero messages, zero discussion participants, zero active days, zero stance participants, and zero stance transitions. Acceptance therefore cannot be linked to observable advocacy, opposition, compromise, consensus formation, or changes of position.

Participation concentration

Message-based participation concentration is not measurable because the captured distribution contains no messages. The zero top-one, top-five, and top-ten shares, zero HHI, zero effective participant count, and zero core-participant counts describe an empty dataset rather than broad or evenly distributed participation. Three formal actors account for all three counted participants, but their identities, roles, activity, and relative influence are unspecified.

Chokepoint analysis

The only visible procedural chokepoint is the formal path from the recorded versions to the accepted decision. The evidence does not identify the decision rule, consensus assessment, vote, reviewer, gatekeeping institution, or role of the three formal actors, so it cannot establish who controlled that chokepoint or whether influence was concentrated. Any stronger attribution would exceed the supplied facts.

Uncertainties

  • It is unclear whether zero captured messages means that no public discussion occurred or that discussion records were unavailable to the metrics process.
  • The substantive contents of versions 1 and 2 and the differences between them are unknown.
  • Both versions carry the introduction date of 23 April 2019, so their actual drafting or publication sequence is uncertain.
  • The identities, functions, and relative influence of the three formal actors are not defined.
  • The decision rule, consensus assessment, vote record, objections, rationale, implementation scope, and affected parties are not supplied.
  • No participant stances or unresolved or minority arguments were captured, so no position can be classified as defeated or withdrawn.
  • The Doctrine package establishes no complete policy-specific official position for this subject.

Policy evolution

2
Accepted · Implemented
Apr 23, 2019
Source facts ↗

Stated problem and rationale · The old version frames the problem as exclusive rights and control by original recipients of assigned or allocated resources. The new version instead frames it as clarifying that IPv4 and IPv6 resources are assigned under the same conditions and that the rule applies to all resources.

Current-text baseline · The old version identifies a proposed general section titled “Resources Are Assigned in a Unique and Exclusive Capacity” as the current text. The new version instead identifies section 2.2.2, an IPv4-specific description of the Internet Registry System, as the current text.

Form and scope of the proposed policy text · The old proposed text is a standalone rule stating that LACNIC assigns Internet resources uniquely and exclusively. The new proposed text recasts the change as a generic definition of the Internet Registry System and expressly refers to Internet number resources including addresses and ASNs.

Authorized third-party use and verification · The old text allows the original recipient to place resources in other networks or under another entity’s administrative control subject to policy and registry consistency. The new text states that resources are for exclusive use by the recipient or recipient-authorized third parties where policy permits, and adds a recommendation that authorizations be verifiable using RPKI.

Suggested placement and treatment of section 2.2.2 · The old version suggests creating a new Policy Manual section, possibly before the appendixes. The new version says section 2.2.2 would be eliminated and renumbered because it applies exclusively to IPv4, with replacement text placed in the generic Definitions section.

Timetable · The timetable changes from a dash with no stated implementation timing to “Immediate implementation.”

Presentation information · The presentation entry changes from “LACNIC 31 (06/05/2019)” to “LACNIC 32 (06/10/2019).”

Debate timeline

  1. Introduced

    Introduced

    Source facts ↗
  2. Official version

    1

    Accepted · Implemented

    Source facts ↗
  3. Official version

    2

    Accepted · Implemented

    Source facts ↗
  4. Official decision

    accepted

    accepted

    Source facts ↗

Entities

Freshness: Stale
  1. Discussion messages1
    First activityNov 25, 2019
    Last activityNov 25, 2019
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies1
  2. Fernando Frediani · Identity unresolved
    Discussion messages0
    First activityUnknown
    Last activityUnknown
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies0
  3. Discussion messages0
    First activityUnknown
    Last activityUnknown
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies1
  4. Discussion messages0
    First activityUnknown
    Last activityUnknown
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies33

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,300
    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,102
    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,014
    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.