LACNIC · RIR Watchdog
IPv4 reserve pool for critical Internet infrastructure in the region.
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-2016-2
- RIR
- LACNIC
- Official status
- Implemented
- Normalized status
- Accepted
- Introduced
- Feb 11, 2016
- Last source update
- Oct 15, 2026
- Coverage
- Partial
Who actually shaped the debate?
Policy evolution
Reserve relationship to IPv4 exhaustion phases · The newer text expressly describes the /15 reserve as independent from IPv4-exhaustion reserves. It also removes the earlier rationale that focused on difficulty assigning critical-infrastructure addresses after Phase 3 is triggered, while retaining the broader statement that the reserve is not subject to depletion phases.
Source facts −
Validated evidence is unavailable.Source facts +
Validated evidence is unavailable.Definition of critical infrastructure · The reserve-creation rule now expressly incorporates the meaning of critical infrastructure defined in paragraph 2.3.3.2 of the Policy Manual; the earlier rule did not include this cross-reference.
Source facts −
1. LACNIC will create an IPv4 reserve equivalent to a /15 to facilitate the deployment of infrastructure considered to be critical or essential for the operation of the Internet in the region.Source facts ↗
Source facts +
. Special IPv4 reserve pool for critical Internet infrastructure in the region. 1. LACNIC will create an IPv4 reserve equivalent to a /15 to facilitate the deployment of infrastructure considered to be critical or essential for the operation of the Internet in the region, where critical iSource facts ↗
Timing of critical-infrastructure requests · A new rule expressly allows address requests for critical infrastructure to be submitted at any time.
Source facts −
1. LACNIC will create an IPv4 reserve equivalent to a /15 to facilitate the deployment of infrastructure considered to be critical or essential for the operation of the Internet in the region. 2. Assignments from this reserve will be limited to the following sizes: minimum assignment size: /24 maximum assignment size: /22Source facts ↗
Source facts +
frastructure has the meaning defined in paragraph 2.3.3.2 of the Policy ManuaSource facts ↗
Review of assignment size · A new rule makes allocation size subject to verification of use and analysis by LACNIC or the corresponding NIR.
Source facts −
2. Assignments from this reserve will be limited to the following sizes: minimum assignment size: /24 maximum assignment size: /22 3. Once the resources are no longer needed for the purpose they were originally requested, the addresses assigned under this section must be returned to LACNIC or to the corresponding NIR.Source facts ↗
Source facts +
the following sizes: minimum assignment size: /24 maximum assignment size: /22 4. Allocation size will be suSource facts ↗
Conforming changes to IPv4 depletion provisions in section 11 · The newer text adds three conforming amendments: it removes the critical-infrastructure exception from paragraph 7 of item 11.1, directs elimination of paragraph 3 under section 11 with renumbering, and removes the sentence in item 11.2 allowing critical-infrastructure applicants to request up to a /22 at any time. The earlier supplied text proposed only the standalone section 2.3.5 rules and did not contain these section 11 amendments.
Source facts −
Validated evidence is unavailable.Source facts +
Validated evidence is unavailable.IPv4 micro-assignment prefix range in Policy Manual section 2.3.3.2 · The new version adds, in both mirrored proposal-text blocks, an instruction to amend the definition of an IPv4 micro-assignment from prefixes longer than /20 and up to /24 to prefixes longer than or equal to /22 and up to /24. The old version proceeds directly from the proposed critical-infrastructure reserve section to the section 11.1 amendment and contains no corresponding section 2.3.3.2 amendment.
Source facts −
Validated evidence is unavailable.Source facts +
Validated evidence is unavailable.Reserve activation relative to IPv4 exhaustion phases · The old text described the /15 reserve as independent from IPv4-exhaustion reserves. The new text expressly provides that the reserve will be used only after the Phase 3 address space runs out.
Source facts +
the region. 1. This reserve will be used once the address space for Phase 3 of the regional IPv4 Exhaustion PSource facts ↗
Micro-assignment prefix boundary · The proposed definition changes from prefixes longer than or equal to /22 to prefixes strictly longer than /22, thereby excluding /22 itself from the stated micro-assignment range.
Proposed amendments to Policy Manual section 11 · The old text included a section 11 amendment package that removed the critical-infrastructure exception from item 11.1, eliminated paragraph 3 under section 11, and removed the item 11.2 sentence allowing critical-infrastructure requests up to /22 at any time. That package is absent from the bounded operative proposal in the new text, which contains only the section 2.3.3.2 amendment and new section 2.3.5.
Source facts −
Validated evidence is unavailable.Source facts +
Validated evidence is unavailable.Debate timeline
Public discussion
[LACNIC/Politicas] Nueva porpuesta de politica 2016-2 // New policy proposal 2016-2 //Nova proposta de política 2016-2
3 Discussion messages · 2 Entities
Source facts ↗Public discussion
[LACNIC/Politicas] Host Sailor, Ltd.
3 Discussion messages · 3 Entities
Source facts ↗Public discussion
[LACNIC/Politicas] Propuesta de política LAC-2016-2 - Ultimos Comentarios
2 Discussion messages · 2 Entities
Source facts ↗Public discussion
[LACNIC/Politicas] Llamado Ultimos Comentarios // Chamado ultimos comentarios // Last Call for Comments
3 Discussion messages · 1 Entities
Source facts 1 ↗Source facts 2 ↗
Entities
- Alex Ojeda · Identity unresolvedDiscussion messages7First activityFeb 12, 2016Last activityDec 1, 2016First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies11
- Gianina Pensky · Identity unresolvedDiscussion messages5First activityMar 3, 2016Last activityMar 15, 2016First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies23
- Juan Alejo Peirano · Identity unresolvedDiscussion messages4First activitySep 9, 2016Last activityNov 10, 2016First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies23
- Discussion messages2First activityFeb 12, 2016Last activityFeb 23, 2016First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies27Freshness: Stale
Last research attempt: Sep 17, 2026
Identity verified: Oct 14, 2026
LACNIC · Historical Ricardo Patara (*) - Registration Service Manager.
www.lacnic.netNIC.BR · Current Actualmente se desempeña como gerente de Recursos de Numeración de Internet en NIC.BR
blog.lacnic.netVerified public profiles
- Discussion messages
- 2
- First activity
- Feb 12, 2016
- Last activity
- Feb 23, 2016
- First explicit stance
- Unknown
- Latest explicit stance
- Unknown
- Stance changes
- 0
- Viewpoint consistency
- No explicit position stated
- Other policies
- 27
First explicit stance: Unknown → Latest explicit stance: Unknown · Stance changes: 0
Viewpoint consistency: No explicit position stated
- Feb 12, 2016 · Question or clarify
[LACNIC/Politicas] Nueva porpuesta de politica 2016-2
para que no parezca estar creando una reserva para algun otro tipo especial de infra.
Source facts ↗ - Feb 23, 2016 · Question or clarify
[LACNIC/Politicas] Nueva porpuesta de politica 2016-2
ajustes al 2.3.3.2
Source facts ↗
Per-policy stance timelines:LAC-2012-8 · Unknown · No explicit position statedLAC-2013-1 · Unknown · No explicit position statedLAC-2013-2 · Unknown · No explicit position statedLAC-2013-4 · Unknown · No explicit position statedLAC-2014-2 · Unknown · No explicit position statedLAC-2014-3 · Unknown · No explicit position statedLAC-2015-2 · Unknown · No explicit position statedLAC-2015-4 · Unknown · No explicit position statedLAC-2016-2 · Unknown · No explicit position statedLAC-2016-5 · Oppose · No validated consistency assessmentLAC-2017-2 · Oppose · No validated consistency assessmentLAC-2017-5 · Oppose · No validated consistency assessmentLAC-2017-6 · Support · No validated consistency assessmentLAC-2017-8 · Propose alternative · No validated consistency assessmentLAC-2018-1 · Oppose · No validated consistency assessmentLAC-2018-12 · Support with changes · No validated consistency assessmentLAC-2018-2 · Support · No validated consistency assessmentLAC-2018-5 · Support with changes · No validated consistency assessmentLAC-2018-6 · Oppose · No validated consistency assessmentLAC-2018-7 · Unknown · No explicit position statedLAC-2018-8 · Oppose · No validated consistency assessmentLAC-2018-9 · Oppose · No validated consistency assessmentLAC-2019-12 · Unknown · No explicit position statedLAC-2020-9 · Unknown · No explicit position statedLAC-2024-4 · Unknown · No explicit position statedLAC-2026-3 · Unknown · No explicit position statedIPv4 address block allocation policies — Working Group 3 (2002) · Unknown · No explicit position statedMultihomed End User Microallocation (2003) · Unknown · No explicit position statedTotal policy messages: 69
- Unknown · Public sources found; identity verification pendingDiscussion messages2First activitySep 28, 2016Last activityNov 12, 2016First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies20
- Discussion messages1First activityApr 18, 2016Last activityApr 18, 2016First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies17
- Arturo Servin · Identity unresolvedDiscussion messages1First activityAug 14, 2016Last activityAug 14, 2016First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies10
- Sergio Rojas. . . · Identity unresolvedDiscussion messages1First activityAug 15, 2016Last activityAug 15, 2016First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies11
- Alejandro Guzman · Identity unresolvedDiscussion messages1First activitySep 28, 2016Last activitySep 28, 2016First explicit stanceOpposeLatest explicit stanceOpposeStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies9
- Ronald F. Guilmette · Identity unresolvedDiscussion messages1First activityAug 13, 2016Last activityAug 13, 2016First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies1
- Edmundo Cazarez-Lopez · Identity unresolvedDiscussion messages0First activityUnknownLast activityUnknownFirst explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies0
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,629
- 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.
