LACNIC · RIR Watchdog
Adapting the allocation / assignment policy for IPv4 exhaustion.
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-2013-3
- RIR
- LACNIC
- Official status
- Implemented
- Normalized status
- Accepted
- Introduced
- Nov 25, 2013
- Last source update
- Oct 15, 2026
- Coverage
- Partial
Who actually shaped the debate?
Policy evolution
Section 11.1 critical-infrastructure eligibility and repeat requests · The supplied new text expressly allows a critical-infrastructure request even when the requester has already received IPv4 resources, and exempts critical-infrastructure requests from the restriction on receiving additional resources from the reserve. It removes the supplied old text's separate six-month restriction and its requirements to follow item 2.3.3.2, submit an IPv6 implementation plan, and demonstrate at least 80% utilization.
Source facts −
Validated evidence is unavailable.Source facts +
Validated evidence is unavailable.Section 11.1 reserve activation and treatment of pending requests · The reserve-activation trigger changes from inability to satisfy a request using the section 11.2 reserve to inability to satisfy a request in full because of insufficient IPv4 resources in the LACNIC region. The pending-request rule also changes from requests larger than a /22 receiving only a /22 to applications smaller than a /22 receiving only a /22.
Source facts −
Validated evidence is unavailable.Source facts +
Validated evidence is unavailable.Section 11.1 independence cross-reference · The supplied old text states that this policy does not replace section 11.2 and that the section 11.2 reserve is independent; the supplied new text instead states that it does not replace section 11.1 while continuing to describe the section 11.2 reserve as independent.
Source facts −
Validated evidence is unavailable.Source facts +
Validated evidence is unavailable.Section 11.2 repeat allocations and qualification requirements · The supplied new text removes the separate prohibition on future allocations or assignments during a six-month period, retaining a single rule permitting additional resources after six months and critical-infrastructure requests up to a /22 at any time. It also removes the supplied old text's requirements for recurring critical-infrastructure requests to follow item 2.3.3.2, include an IPv6 implementation plan, and demonstrate at least 80% utilization.
Source facts −
Validated evidence is unavailable.Source facts +
Validated evidence is unavailable.Terminology across language versions · The supplied new version adds an explicit terminology-harmonization proposal: Spanish "suave" is to be replaced by "gradual," and Portuguese "tranquilo" by "gradativo." The supplied old version contains no corresponding terminology proposal.
Source facts −
Validated evidence is unavailable.Source facts +
Validated evidence is unavailable.Debate timeline
Public discussion
[LACNIC/Politicas] LAC-2013-03v2 - Call for consensus // llamado a consenso // convocatória ao consenso
7 Discussion messages · 7 Entities
Source facts ↗
Entities
- Discussion messages2First activityJan 27, 2014Last activityFeb 14, 2014First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies25
- Max Larson Henry · Identity unresolvedDiscussion messages2First activityNov 22, 2013Last activityNov 25, 2013First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies4
- Juan Alejo Peirano · Identity unresolvedDiscussion messages1First activityFeb 26, 2014Last activityFeb 26, 2014First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies4
- Christian O'Flaherty · Identity unresolvedDiscussion messages1First activityFeb 26, 2014Last activityFeb 26, 2014First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies4
- Luis Balbinot · Identity unresolvedDiscussion messages1First activityFeb 26, 2014Last activityFeb 26, 2014First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies2
- Pedro Torres · Identity unresolvedDiscussion messages1First activityFeb 28, 2014Last activityFeb 28, 2014First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies1
- Discussion messages1First activityFeb 28, 2014Last activityFeb 28, 2014First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies3
- Edna Samudio de Jaen · Identity unresolvedDiscussion messages1First activityFeb 28, 2014Last activityFeb 28, 2014First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies0
- Discussion messages0First activityUnknownLast activityUnknownFirst explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies17Freshness: Stale
Last research attempt: Sep 20, 2026
Identity verified: Sep 20, 2026
LACNIC · Historical wnload TXT PDF DOCX Original language Español Last modified 14/04/2014 Status Implemented 100 %. Authors Juan Alejo - Version [1] Carlos Plasencia - Version [2] In discussion 25/11/2013 Last call for comments 24/01/2014 - 14/02/2014 Ratification by the board 04/03/2014 Ratified 25/03/2014 Implemented 15/08/2014 Compare versions Version 1 Version 2 Summary This pol
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
- 17
First explicit stance: Unknown → Latest explicit stance: Unknown · Stance changes: 0
Viewpoint consistency: No explicit position stated
- Oct 15, 2026
author
Source facts ↗
Per-policy stance timelines:LAC-2013-3 · Unknown · No explicit position statedLAC-2013-4 · Unknown · Insufficient evidence to assess consistencyLAC-2014-1 · Unknown · Insufficient evidence to assess consistencyLAC-2014-2 · Unknown · Insufficient evidence to assess consistencyLAC-2014-3 · Unknown · Insufficient evidence to assess consistencyLAC-2015-1 · Unknown · Insufficient evidence to assess consistencyLAC-2015-2 · Unknown · Insufficient evidence to assess consistencyLAC-2015-3 · Unknown · Insufficient evidence to assess consistencyLAC-2015-4 · Unknown · Insufficient evidence to assess consistencyLAC-2015-5 · Unknown · Insufficient evidence to assess consistencyLAC-2015-6 · Unknown · Insufficient evidence to assess consistencyLAC-2016-1 · Unknown · Insufficient evidence to assess consistencyLAC-2016-2 · Unknown · Insufficient evidence to assess consistencyLAC-2016-3 · Unknown · Insufficient evidence to assess consistencyLAC-2016-4 · Unknown · Insufficient evidence to assess consistencyLAC-2016-5 · Unknown · Insufficient evidence to assess consistencyLAC-2016-6 · Unknown · Insufficient evidence to assess consistencyLAC-2016-7 · Unknown · Insufficient evidence to assess consistencyTotal policy messages: 35
- Discussion messages0First activityUnknownLast activityUnknownFirst explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies1
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,715
- Known gaps
- 26
- www.lacnic.net
- lacnic-anuncios
- Earliest captured
- Sep 1, 2026
- Latest captured
- Sep 1, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,177
- Known gaps
- 0
- lacnic-ietf-lac
- Earliest captured
- May 30, 2013
- Latest captured
- Dec 30, 2015
- Last refresh
- Oct 15, 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 15, 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 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 373
- Known gaps
- 0
- lacnic-lacnog
- Earliest captured
- Aug 1, 2026
- Latest captured
- Oct 14, 2026
- Last refresh
- Oct 11, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 6,650
- Known gaps
- 3
- lacnic-lactf
- Earliest captured
- Apr 13, 2004
- Latest captured
- Dec 29, 2006
- Last refresh
- Oct 15, 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 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1,356
- Known gaps
- 0
Coverage
Partial
Earliest captured: Oct 21, 1999
Latest captured: Oct 15, 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.
