BTW.Media
Daily editionStrategic Internet Intelligence
Sign InRegister

LACNIC · RIR Watchdog

Unify Texts That Apply to Both IPv4 and IPv6

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-2022-1
RIR
LACNIC
Official status
Implemented
Normalized status
Accepted
Introduced
Sep 14, 2022
Last source update
Oct 10, 2026
Coverage
Partial

Who actually shaped the debate?

1Total participants
UnknownDiscussion contributors
1Formal actors
UnknownDiscussion messages
UnknownEffective participants
UnknownTop-five discussion share
UnknownPeople covering 50%
UnknownPeople covering 80%

Policy evolution

2
Accepted · Implemented
Sep 14, 2022
Source facts ↗

Proposed policy structure and section numbering · The old version proposed combining definitions and general mandates in Section 1 and moving material into that section. The new version instead proposes renumbering Definitions as Section 0 and creating a separate Section 1 titled General Rules.

Source facts −
diff 1. Definitions and General Mandates (Move Section 1. Definit
Source facts ↗
Source facts +
mat and the place where it will be published will be defined by the LACNIC staff. New text Analyze diff 0. Definitions (Renumber current Section 1 as 0, and maintain the text in current subsections 1.1 to 1.10 and 1.12 as 0.1 to 0.11) 1. General Rules (New section that allows s
Source facts ↗

Documentation requirement wording · In the proposed documentation rule, the phrase requiring justification for each “allocation or assignment” was changed to “allocation of assignment.”

Source facts −
each allocation or assig
Source facts ↗
Source facts +
ated or assigned in an e
Source facts ↗

Explicit placement of existing general rules · The new version explicitly places Principles for Proper Administration and Stewardship and Resource Requests in the proposed General Rules section without changing their text; these subsections were not identified in the old version's proposed combined-section heading.

Source facts −
diff 1. Definitions and General Mandates (Move Section 1. Definit
Source facts ↗
Source facts +
n of network routing plans. • Receipts documenting investments (equipment). • Other relevant documents. 1.2. Principles for Proper
Source facts ↗

Security and confidentiality scope · The old proposed rule protected all information entrusted to LACNIC, with documentation as an example. The new proposed rule protects all documentation presented to justify resource requests, removing the broader reference to all entrusted information.

Source facts −
tiality LACNIC shall maintain systems and practices to safeguard and protect the confidentiality of all information entrusted to LACNIC, for example, the documentation submitted to justify resource r
Source facts ↗
Source facts +
changes to the text) 1.3. Resource Requests (No changes to the text) 1.4. Security and Confidentiality LACNIC shall maintain systems and practices that safeguard and
Source facts ↗

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 decision

    accepted

    accepted

    Source facts ↗

Entities

Freshness: Stale
  1. Jordi Palet Martínez · 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 8, 2026
    Last refresh
    Aug 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    5,369
    Known gaps
    26
  • www.lacnic.net
  • lacnic-anuncios
    Earliest captured
    Aug 13, 2026
    Latest captured
    Oct 7, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,120
    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 9, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    6,125
    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 11, 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.