LACNIC · RIR Watchdog
RPKI ASN 0 ROA
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-12
- RIR
- LACNIC
- Official status
- Implemented
- Normalized status
- Accepted
- Introduced
- Nov 12, 2019
- Last source update
- Oct 14, 2026
- Coverage
- Partial
Who actually shaped the debate?
Policy evolution
Creation and technical configuration of AS 0 ROAs · The old text permitted LACNIC to create an ASN 0 ROA. The new text requires LACNIC to create AS 0 ROAs and expressly places the number of ROAs and other technical parameters under LACNIC's discretion.
Source facts −
Validated evidence is unavailable.Source facts +
text: LACNIC will create specific Routing Origin Authorizations (ROAs) in the RPKI infrastructure with AS 0 in the Origin ASN field and the list of unallocated or unassigned Internet Number Resources exclusively under LACNIC administration in the Prefixes list such ROAs. The number of the before mentioned ROAs and any other technical parameter of it will be under LACNIC discSource facts ↗
Invalidation and replacement when resources are allocated or assigned · The old text required an ASN 0 ROA containing a resource scheduled for allocation or assignment to be invalidated and replaced without that resource before allocation. The new text instead states that once a resource is allocated or assigned, LACNIC will invalidate ROAs containing it and issue replacement ROAs as necessary.
Source facts −
the case an specific Internet Number Resource, present in a ASN0 ROA, is to be allocated or assigned, that ROA must be invalidated and new one would be issued without the soon to be allocated Internet Number Resource. ASource facts ↗
Source facts +
todian. Once an Internet Number Resource is allocated or assigned, LACNIC will invalidate ROAs that contain such resources and will issue new ROAs that do not include them, as neSource facts ↗
Debate timeline
Entities
- Discussion messages0First activityUnknownLast activityUnknownFirst explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies27
- Discussion messages0First activityUnknownLast activityUnknownFirst explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies0Freshness: Stale
Last research attempt: Sep 19, 2026
Identity verified: Sep 19, 2026
· Historical Authors Ricardo Patara - Version [1, 2] Aftab Sidiqui - Version [1, 2]
politicas.lacnic.netVerified public profiles
- Discussion messages
- 0
- First activity
- Unknown
- Last activity
- Unknown
- First explicit stance
- Unknown
- Latest explicit stance
- Unknown
- Stance changes
- 0
- Viewpoint consistency
- No explicit position stated
- Other policies
- 0
First explicit stance: Unknown → Latest explicit stance: Unknown · Stance changes: 0
Viewpoint consistency: No explicit position stated
- Oct 12, 2026
author
Source facts ↗
Per-policy stance timelines:LAC-2019-12 · Unknown · No explicit position statedTotal policy messages: 0
Sources and coverage
Official policy sources
Public discussion archives
- lacnic-politicas
- Earliest captured
- Oct 21, 1999
- Latest captured
- Oct 14, 2026
- Last refresh
- Aug 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 5,680
- 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,191
- 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 13, 2026
- Last refresh
- Oct 11, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 6,548
- 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
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.
