LACNIC · RIR Watchdog
Considerations for Declaring a Proposal Abandoned
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-2023-3
- RIR
- LACNIC
- Official status
- Implemented
- Normalized status
- Accepted
- Introduced
- Feb 7, 2024
- Last source update
- Oct 10, 2026
- Coverage
- Partial
Who actually shaped the debate?
Policy evolution
Status classification terminology · The old version classified “Abandoned” as semi-permanent and classified “Did not reach consensus” and “Not ratified” separately as semi-transitory. The new version removes the semi-transitory category and instead describes “Did not reach consensus” and “Not ratified” as semi-permanent.
Source facts −
Validated evidence is unavailable.Source facts +
Validated evidence is unavailable.Time before abandonment · The prescribed period changes from 10 months to 12 calendar months.
Source facts −
unctions of the PDP chairs include “to decide whether a policy is abandoned,” this text is very simple and refers to policies, not proposals. Likewise, it does not provide any guidance on when the chairs should decide that a proposal has been abandoned. In fact, the chairs might even abuse this function by deciding that a proposal has been abandoned even when its discussion continues. In view of the above, this proposal defines when a proposal should be considered abandoned, defining a 10-monthSource facts ↗
Source facts +
prior discussion. Version 2 of this proposal takes this responsibility away from the moderators and makes it part of LACNIC's responsibilities. The new version specifies that LACNIC will automatically consider a proposal abandoned after 12 calendar months. To achieve this, the item “To decide whether to abandon a policy” is deleted from section 3.2.1 of the PDP and the corresponding text is added in Chapter 4, Responsibilities and Obligations ofSource facts ↗
Abandonment trigger and author-action conditions · Under the old text, abandonment depended on the author neither submitting a new proposal nor communicating a decision to withdraw within the specified period after failure to reach consensus or ratification. Under the new text, the trigger is instead that the proposal remains in either listed status for 12 months; no separate author-action or communication condition is stated, and the last version is automatically moved to “Abandoned.”
Source facts −
Validated evidence is unavailable.Source facts +
Validated evidence is unavailable.Responsibility and abandonment workflow · The old version assigned the chairs an operative role: they were to request that LACNIC change the proposal’s status. The new version removes the chairs’ abandonment function and assigns LACNIC an automatic status-change responsibility, eliminating the chair-request step.
Source facts −
Validated evidence is unavailable.Source facts +
Validated evidence is unavailable.Placement of the new rule · The old version placed the abandonment rule at the end of section 3.2.4, “Responsibilities and obligations of PDP Chairs.” The new version places it as a new item in Chapter 4, “Responsibilities and Obligations of LACNIC.”
Source facts −
Validated evidence is unavailable.Source facts +
makes it part of LACNIC's responsibilities. The new version specifies that LACNIC will automatically consider a proposal abandoned after 12 calendar months. To achieve this, the item “To decide whether to abandon a policy” is deleted from section 3.2.1 of the PDP and the corresponding text is added in Chapter 4, Responsibilities and Obligations ofSource facts ↗
Debate timeline
Entities
Source coverage is incomplete.
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,317
- 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,101
- 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,052
- 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
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.
