Skip to main content

LACNIC · RIR Watchdog

Update to “Resource Recovery and Return” and consistency with the rest of the Manual

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

Who actually shaped the debate?

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

BTW Analysis

BTW Analysis

What changed

LAC-2019-9 was introduced on 2019-07-12. Versions 1 and 2 are both recorded on that date with raw status "Implemented" and normalized status "accepted." The chronology then records an accepted decision on 2021-11-22. The supplied record does not include policy text, version diffs, or distinct revision timestamps, so the substantive change between versions cannot be determined.

What the debate was really about

The subject of any debate cannot be determined from the supplied facts. No policy provisions, discussion messages, participant stances, supporting arguments, objections, or amendment requests are provided.

Decision vs debate

The decision outcome is established in the supplied chronology: accepted on 2021-11-22. The deliberative path is not established. The participation dataset records zero messages, zero discussion participants, zero active days, zero stance participants, and zero stance transitions. This means no discussion is captured in the dataset, not necessarily that no discussion occurred elsewhere.

Participation concentration

No substantive concentration finding is possible. The dataset records one formal actor and one total participant but no discussion participants or messages. Consequently, the zero message shares, zero HHI, zero effective-participant count, and zero core-participant counts describe an empty captured discussion set and do not show either concentrated or dispersed influence. The single formal actor is not evidence of debate dominance.

Chokepoint analysis

The principal analytical chokepoint is the absence of the policy text, version diffs, discussion records, stance evidence, actor roles, and decision rationale. The recorded formal process reached acceptance, but the supplied facts do not identify who controlled a procedural chokepoint, how consensus was assessed, or which actor influenced the result. The shared timestamp for versions 1 and 2 also prevents reconstruction of the revision sequence.

Uncertainties

  • The substantive provisions of LAC-2019-9 and the practical effects of acceptance are not supplied.
  • Versions 1 and 2 share the introduction timestamp, leaving their ordering and the nature of any revision unresolved.
  • Zero discussion metrics may reflect absent or uncaptured records and do not prove that no public or private debate occurred.
  • The identity, role, and procedural significance of the one formal actor are not supplied.
  • No decision rationale, consensus assessment, voting record, deciding-body identity, or implementation evidence is provided.
  • The supplied Doctrine package establishes only a partial official position and does not establish a company position on the policy's merits.
  • The recorded chronology relies on a LACNIC page that the supplied Doctrine treats as an opposing-party institutional source rather than controlling authority evidence; the chronology remains supplied verified fact for this interpretation.

Policy evolution

2
Accepted · Implemented
Jul 12, 2019
Source facts ↗

Proposal scope and identified policy-improvement items · The new version expressly links the proposal to items 1, 8, and 10 on the cited list of potential improvements; the old version referred to potential improvements without identifying numbered items or providing that link.

Whois information as a ground for resource revocation · The revocation ground for failing to update allocation and assignment information is expanded from LACNIC's Whois database alone to the Whois database managed by LACNIC or the NIRs, as applicable.

Third-party-caused violations · Where a violation was caused by a third party without the recipient's knowledge and there is no collusion or negligence, the old text said the revocation process would not be completed; the new text says the process will not be initiated.

Use of recovered or returned IPv6 and ASN resources · The old text placed IPv6 and ASN resources into their respective pools two years after recovery or return. The new text retains the two-year rule but additionally authorizes LACNIC to use the resources differently according to best practices to optimize compliance with RFC 7020, including treatment of recovered or returned 16-bit ASNs.

Non-guaranteed routability policy · The old draft's consolidated routability provision was limited to allocated or assigned IPv4 addresses. The new draft applies non-guaranteed routability to allocated or assigned addresses generally and incorporates the requirement that RIRs use operational procedures reducing address-space fragmentation and routability-loss risk.

Proper administration and stewardship requirements · The old draft stated that resources must be distributed among qualifying regional organizations and added a requirement to become a LACNIC or corresponding RIR member and sign the Registration Services Agreement. The new draft instead says resources must be allocated to qualifying organizations, removes that membership-and-signature sentence, and adds that obtaining any resources from LACNIC or the corresponding NIR causes the recipient's legacy resources to cease being considered legacy resources.

Resource-request procedures · The old draft eliminated the IPv4 application-template section as an operational mechanism common to all resources without supplying replacement policy text. The new draft adds a general Resource Requests section stating that requests to LACNIC or the corresponding NIR will use systems in force and that incomplete requests will be returned with completion instructions.

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 activityJul 12, 2019
    Last activityJul 12, 2019
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies39

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

Coverage

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