Skip to main content

LACNIC · RIR Watchdog

IPv4 address block allocation policies — Working Group 3 (2002)

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
unnumbered-ipv4-working-group-3-2002
RIR
LACNIC
Official status
Approved. Implemented in 12/11/2002
Normalized status
Accepted
Introduced
Aug 6, 2002
Last source update
Oct 11, 2026
Coverage
Partial

Who actually shaped the debate?

3Total participants
3Discussion contributors
UnknownFormal actors
6Discussion messages
2.6Effective participants
100%Top-five discussion share
1People covering 50%
2People covering 80%

BTW Analysis

BTW Analysis

What changed

The 2002 Working Group 3 effort assembled a framework for IPv4 allocation and administration. The September announcement covered sections 3.1 and 3.2 and reported unresolved agreement on allocation validity and suballocation supervision. October notices circulated a final report covering chapter 3. The retained proposal addresses justified need, initial and additional allocations, renumbering, documentation and registry oversight. The two retained English copies differ mainly in layout and text extraction; their existence alone does not demonstrate a substantive change between drafts.

What the debate was really about

The identifiable tension was how conservation and routing objectives would be enforced, and how much continuing control would rest with the registry and upstream providers. Section 3.2.10 describes conditions under which LACNIC could invalidate an allocation; section 3.2.12 sets consultation, audit and registration duties for suballocations. These are the two sections explicitly reported as lacking working-group consensus in September. The retained six messages do not preserve the participants' detailed arguments on those clauses, so the balance of support and opposition cannot be reconstructed from this sample.

Arguments that prevailed

  • LACNIC's historical table records the policy as approved and implemented. Its archived proposal sets out allocation based on demonstrated need, slow-start allocation, utilization checks and documentation. This establishes the recorded institutional outcome and proposed mechanisms, not which speaker's argument caused approval.

Arguments that did not prevail

  • The September notice reports a lack of consensus on sections 3.2.10 and 3.2.12. The supplied discussion does not establish that a particular objection was rejected, withdrawn or resolved, or identify a losing side.

Decision vs debate

The historical table lists submission on 6 August 2002, implementation on 12 November 2002 and Board ratification on 11 December 2002. Those are separate source-reported events; the implementation date preceding ratification should be preserved, not silently reordered. The six linked messages from 2 September through 9 October circulate reports or translations. Their authors' procedural activity is not evidence of personal endorsement, a vote or the complete consensus process.

Participation concentration

This retained discussion sample contains six message records from three people across four active days. One person accounts for three messages, another for two, and the third for one: the largest share is 50%, the HHI is about 0.389 and the effective participant count is about 2.57. These figures describe report circulation in this sample. All six assessed positions are procedural or neutral, with zero observed stance transitions; the counts do not establish who controlled the decision or measure the breadth of the full community debate. No formal actors are independently established for this policy in the supplied evidence.

Chokepoint analysis

The proposal concentrates practical control at several recurring checkpoints. LACNIC determines initial and further allocations from demonstrated use, can withhold additional space where documentation is inadequate, and describes invalidation conditions tied to use, records, contracts and responses to information requests. Suballocation consultation and NIR audits extend oversight downstream. Return-and-renumber requirements also leave upstream providers with practical control when connectivity ends. These mechanisms can serve conservation and aggregation while making operators dependent on the administration of eligibility and continuity rules. The historical proposal alone does not establish how that discretion was exercised, whether it was abused, or the present legal status of address holdings.

Uncertainties

  • The surviving messages are report and translation circulations, not a complete record of the working-group negotiations or the final consensus call.
  • The archive's approval label does not independently prove that every clause in the attached proposal was adopted without amendment.
  • Exact publication dates and a substantive revision order for the two retained English PDF copies are not established.
  • The separate implementation and Board-ratification dates are reported as the historical table gives them; the supplied material does not explain their ordering.
  • No personal support, opposition, persuasion or broader viewpoint consistency can be inferred from these six neutral observations.

Policy evolution

Working Group 3 final report, English circulation, October 2002
Unknown
Source facts ↗

Debate timeline

  1. Official version

    Official archive proposal text, LACNIC III (2002)

    Source facts ↗
  2. Official version

    Working Group 3 final report, English circulation, October 2002

    Source facts ↗
  3. Introduced

    Introduced

    Source facts ↗
  4. Official decision

    accepted

    accepted

    Source facts ↗

Entities

Freshness: Stale
  1. Discussion messages3
    First activitySep 2, 2002
    Last activityOct 9, 2002
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies5
  2. Discussion messages2
    First activitySep 4, 2002
    Last activitySep 4, 2002
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies0
  3. Discussion messages1
    First activityOct 9, 2002
    Last activityOct 9, 2002
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies27

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,689
    Known gaps
    26
  • www.lacnic.net
  • lacnic-anuncios
    Earliest captured
    Aug 13, 2026
    Latest captured
    Oct 7, 2026
    Last refresh
    Oct 15, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,200
    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 13, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    6,563
    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.