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 14, 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 · Last refresh: · The latest refresh failed. The last successful result is shown.
  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 policies2
    Freshness: Stale

    Last research attempt: Oct 9, 2026

    Identity verified: Oct 9, 2026

    · Historical
    Authors Tomas Lynch - Version [1, 2]
    politicas.lacnic.net
    LACNIC · Historical
    También ha sido moderador del Foro Público de Políticas de LACNIC entre 2019 y 2023.
    blog.lacnic.net
    LACNOG · Unknown
    Miembro fundador de LACNOG, participa asiduamente de LACNIC y LACNOG desde 2010 habiendo sido miembro del comité de programa de ambos eventos.
    blog.lacnic.net
    Vultr · Unknown
    Actualmente es Senior Network Architect en Vultr, Cloud Service Provider, a cargo de la estrategia, diseño, y operación de la red global de la empresa.
    blog.lacnic.net
    Discussion messages
    1
    First activity
    Nov 25, 2019
    Last activity
    Nov 25, 2019
    First explicit stance
    Unknown
    Latest explicit stance
    Unknown
    Stance changes
    0
    Viewpoint consistency
    Insufficient evidence to assess consistency
    Other policies
    2

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

    Viewpoint consistency: Insufficient evidence to assess consistency

    These two jointly signed notices record procedural steps for different proposals. They do not establish Tomas Lynch's personal substantive positions or a reversal of those positions. The conflicting dates within the multilingual LAC-2018-13 notice are a source discrepancy, not evidence of personal inconsistency. This assessment covers only these two validated notices.

    Acceptable Use Policy (AUP) for the Policy List

    Assessment: Insufficient evidence to assess consistency · The LAC-2018-13 notice invites community comments on unresolved staff observations. It expresses no personal support or opposition by Tomas Lynch, so it cannot establish consistency or inconsistency in his substantive position.

    Conditions: The notice is jointly signed by Tomas Lynch and Ariel Weher in their policy-process role. · The Spanish and Portuguese versions state 25 July 2019, whereas the English version states 25 June 2019. The conflicting dates do not establish a single deadline or a change of personal position.

    We would like to receive community feedback and comments on the impact analysis of LAC-2018-13 ?Acceptable Use Policy (AUP) for the Policy List, version 3,? as some of the staff?s comments remain unresolved.

    el 25 de Julio de 2019.

    until 25 June 2019.

    Tom?s Lynch Ariel Weher Chairs of the Public Development Process LACNIC

    Resources Are Assigned in a Unique and Exclusive Capacity

    Assessment: Insufficient evidence to assess consistency · The LAC-2019-6 notice announces the end of initial discussion and a forthcoming consensus assessment. It neither endorses or opposes the proposal nor announces that consensus has already been reached.

    Conditions: The notice is jointly signed by the policy chairs; it does not distinguish either signatory's personal position. · Only this procedural notice is present for this policy in the assessed corpus.

    We inform you that today is the culmination of initial discussion period for the following proposals: - LAC-2019-6 v2: Resources Are Assigned in a Unique and Exclusive Capacity The next step will be the assessment of the consensus by the co-chairs within two weeks from today.

    Tom?s Lynch Ariel Weher Chairs of the Public Development Process LACNIC

    Acceptable Use Policy (AUP) for the Policy List · Resources Are Assigned in a Unique and Exclusive Capacity

    Assessment: Insufficient evidence to assess consistency · Inviting comments on LAC-2018-13 and announcing a later procedural step for LAC-2019-6 concern different proposals and stages. These actions do not demonstrate contradictory personal policy positions.

    Conditions: The assessment is limited to two validated notices from July and November 2019. · A conclusion about consistency across substantive positions would require statements attributable to Tomas Lynch that express those positions and their conditions.

    We would like to receive community feedback and comments on the impact analysis of LAC-2018-13 ?Acceptable Use Policy (AUP) for the Policy List, version 3,? as some of the staff?s comments remain unresolved.

    Tom?s Lynch Ariel Weher Chairs of the Public Development Process LACNIC

    We inform you that today is the culmination of initial discussion period for the following proposals: - LAC-2019-6 v2: Resources Are Assigned in a Unique and Exclusive Capacity The next step will be the assessment of the consensus by the co-chairs within two weeks from today.

    Tom?s Lynch Ariel Weher Chairs of the Public Development Process LACNIC

    1. Nov 25, 2019 · Procedural or neutral

      [LACNIC/Politicas] LAC-2019-6 - Fin discusión inicial / Fin discussão inicial / End initial discussion

      Conditions:

      The policy chairs announce the end of initial discussion and a forthcoming consensus assessment; this notice states neither personal support or opposition nor an already reached consensus.

      LAC-2019-6 v2: Resources Are Assigned in a Unique and Exclusive Capacity … The next step will be the assessment of the consensus by the co-chairs within two weeks from today.

      Source facts ↗

    Total policy messages: 2

  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 policies39

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

Coverage

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