Skip to main content

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?

11Total participants
10Discussion contributors
1Formal actors
25Discussion messages
6.1Effective participants
80%Top-five discussion share
3People covering 50%
5People covering 80%

Policy evolution

2
Accepted · Implemented
Feb 11, 2016
Source facts ↗

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.

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.

Timing of critical-infrastructure requests · A new rule expressly allows address requests for critical infrastructure to be submitted at any time.

Review of assignment size · A new rule makes allocation size subject to verification of use and analysis by LACNIC or the corresponding NIR.

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.

3
Accepted · Implemented
Feb 11, 2016
Source facts ↗

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.

4
Accepted · Implemented
Feb 11, 2016
Source facts ↗

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.

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.

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. 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 ↗
  7. Public discussion

    [LACNIC/Politicas] Host Sailor, Ltd.

    3 Discussion messages · 3 Entities

    Source facts ↗
  8. Public discussion

    [LACNIC/Politicas] Propuesta de política LAC-2016-2 - Ultimos Comentarios

    2 Discussion messages · 2 Entities

    Source facts ↗
  9. 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 ↗
  10. Official decision

    accepted

    accepted

    Source facts ↗

Entities

Freshness: Stale
  1. Alex Ojeda · Identity unresolved
    Discussion messages7
    First activityFeb 12, 2016
    Last activityDec 1, 2016
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies11
  2. Gianina Pensky · Identity unresolved
    Discussion messages5
    First activityMar 3, 2016
    Last activityMar 15, 2016
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies23
  3. Juan Alejo Peirano · Identity unresolved
    Discussion messages4
    First activitySep 9, 2016
    Last activityNov 10, 2016
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies23
  4. Discussion messages2
    First activityFeb 12, 2016
    Last activityFeb 23, 2016
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies27
    Freshness: Stale

    Last research attempt: Sep 17, 2026

    Identity verified: Oct 14, 2026

    LACNIC · Historical
    Ricardo Patara (*) - Registration Service Manager.
    www.lacnic.net
    NIC.BR · Current
    Actualmente se desempeña como gerente de Recursos de Numeración de Internet en NIC.BR
    blog.lacnic.net

    Verified 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

    1. 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 ↗
    2. Feb 23, 2016 · Question or clarify

      [LACNIC/Politicas] Nueva porpuesta de politica 2016-2

      ajustes al 2.3.3.2

      Source facts ↗

    Total policy messages: 69

  5. Unknown · Public sources found; identity verification pending
    Discussion messages2
    First activitySep 28, 2016
    Last activityNov 12, 2016
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies20
  6. Discussion messages1
    First activityApr 18, 2016
    Last activityApr 18, 2016
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies17
  7. Arturo Servin · Identity unresolved
    Discussion messages1
    First activityAug 14, 2016
    Last activityAug 14, 2016
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies10
  8. Sergio Rojas. . . · Identity unresolved
    Discussion messages1
    First activityAug 15, 2016
    Last activityAug 15, 2016
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies11
  9. Alejandro Guzman · Identity unresolved
    Discussion messages1
    First activitySep 28, 2016
    Last activitySep 28, 2016
    First explicit stanceOppose
    Latest explicit stanceOppose
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies9
  10. Ronald F. Guilmette · Identity unresolved
    Discussion messages1
    First activityAug 13, 2016
    Last activityAug 13, 2016
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies1
  11. Edmundo Cazarez-Lopez · Identity unresolved
    Discussion messages0
    First activityUnknown
    Last activityUnknown
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other 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

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.