Skip to main content

LACNIC · RIR Watchdog

Modification of the Time Required for a Proposal to be Presented at the Public Policy Forum

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-8
RIR
LACNIC
Official status
Implemented
Normalized status
Accepted
Introduced
Aug 4, 2020
Last source update
Oct 10, 2026
Coverage
Partial

Who actually shaped the debate?

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

BTW Analysis

BTW Analysis

What changed

The verified record shows an administrative progression from introduction on 4 August 2020 through four recorded versions, each marked implemented and normalized as accepted, to a final accepted decision on 3 December 2020. What changed substantively between versions cannot be determined because version texts and change summaries are absent.

What the debate was really about

The supplied evidence does not reveal the substantive issue under debate. It establishes only that LAC-2019-8 moved through four recorded versions and reached acceptance; it does not identify the competing policy positions, affected interests, obligations, benefits, costs, enforcement arrangements, or points of disagreement.

Arguments that prevailed

  • No substantive argument can be identified as having prevailed because no proposal text, discussion messages, stance records, decision rationale, or argument summaries are supplied; only the policy's accepted and implemented disposition is established.

Decision vs debate

The decision outcome is clear: LAC-2019-8 was accepted on 3 December 2020, and versions 1 through 4 are recorded as implemented and normalized as accepted. The discussion pathway is not observable because the dataset contains zero captured messages, zero discussion participants, zero active discussion days, no stance timelines, and no unresolved or minority arguments. This establishes an accepted administrative outcome, not the presence or absence of actual debate.

Participation concentration

The concentration metrics describe an empty captured message distribution rather than broad, equal, or concentrated participation. With zero messages and zero discussion participants, the zero top-message shares, zero HHI, zero effective-participant count, and zero core counts have no meaningful deliberative concentration interpretation. The two formal actors must not be treated as two discussion participants or as the complete affected stakeholder set.

Chokepoint analysis

The observable institutional chokepoint was the final decision recorded on 3 December 2020, which converted the introduced and versioned proposal into an accepted outcome. The supplied evidence does not identify the deciding body, decision rule, consensus test, vote, quorum, or actors controlling that chokepoint.

Uncertainties

  • The substantive content of the proposal and versions 1 through 4 is not supplied, so amendments, compromises, narrowing, or expansion cannot be reconstructed.
  • All four versions share the recorded date of 4 August 2020; the evidence does not explain whether this reflects publication timing, archival migration, or another recording convention.
  • Zero captured messages does not establish that no debate occurred in meetings, consultations, private exchanges, or sources outside the dataset.
  • The identities and functions of the two formal actors are unknown.
  • No decision rationale, consensus assessment, vote, quorum, objection record, or governing decision rule is supplied.
  • No complete official Doctrine position on LAC-2019-8 is established by the supplied package.

Policy evolution

2
Accepted · Implemented
Aug 4, 2020
Source facts ↗

Minimum discussion period before a Public Policy Forum · The proposed minimum prior-discussion period was changed from 45 calendar days to three weeks.

3
Accepted · Implemented
Aug 4, 2020
Source facts ↗

Discussion-period requirement for new versions of proposals · The new version adds a provision allowing the PDP chairs to decide whether the three-week pre-Forum discussion requirement applies to new versions of proposals already under discussion.

Presented at · The “Presented at” entry changed from “LACNIC 32 (06/10/2019)” to a dash.

4
Accepted · Implemented
Aug 4, 2020
Source facts ↗

Proposal summary and objectives · The stated objective changed from applying a three-week pre-Forum discussion period to extending lead time by two weeks, prioritizing new proposals at the Forum, and giving the Chairs authority over presentation of previously presented proposals' new versions.

Rationale · The rationale changed from insufficient time for Staff impact analysis and mailing-list discussion to avoiding unnecessary Forum presentation of revisions that lack significant changes, allowing list consensus and more time for new proposals.

Eligibility and lead time for Forum presentation · The proposed rule changed from requiring all topics and items to have been discussed on the list at least three weeks before the Forum to requiring only new proposals to have been published at least two weeks before the Forum; the new wording also expressly requires qualifying new proposals to be presented and discussed.

Chair discretion for revised proposals · Chair discretion changed from deciding whether the three-week discussion requirement applies to new versions already under discussion to deciding whether each new version of a previously presented proposal needs Forum presentation, based on significant textual modifications and subsequent list discussions.

Presented-at information · The presented-at field changed from a dash to “LACNIC 33 (online) (05/05/2020).”

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 version

    3

    Accepted · Implemented

    Source facts ↗
  5. Official version

    4

    Accepted · Implemented

    Source facts ↗
  6. Official decision

    accepted

    accepted

    Source facts ↗

Entities

Freshness: Stale
  1. Discussion messages1
    First activityApr 2, 2013
    Last activityApr 2, 2013
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies24
  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 policies2

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,297
    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,099
    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,011
    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.