Skip to main content

LACNIC · RIR Watchdog

Resource Allocation for Experimental Use (2003)

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-resource-allocation-experimental-use-2003
RIR
LACNIC
Official status
Approved Implemented in 15/03/2004
Normalized status
Accepted
Introduced
Feb 7, 2003
Last source update
Oct 14, 2026
Coverage
Partial

Who actually shaped the debate?

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

Policy evolution

Spanish proposal slides linked by the LACNIC V archive (2003)
Unknown
Source facts ↗

Debate timeline

  1. Official version

    Spanish proposal slides linked by the LACNIC V archive (2003)

    Source facts ↗
  2. Official version

    Working-group proposal retained under LACNIC IV (2003)

    Source facts ↗
  3. Introduced

    Introduced

    Source facts ↗
  4. Official decision

    accepted

    accepted

    Source facts ↗

Entities

Freshness: Stale
  1. Discussion messages1
    First activityApr 15, 2003
    Last activityApr 15, 2003
    First explicit stanceSupport
    Latest explicit stanceSupport
    Stance changes0
    Viewpoint consistencyNo validated consistency assessment
    Other policies5
  2. Discussion messages1
    First activityApr 11, 2003
    Last activityApr 11, 2003
    First explicit stancePropose alternative
    Latest explicit stancePropose alternative
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies1
    Freshness: Stale

    Last research attempt: Oct 14, 2026

    Identity verified: Oct 14, 2026

    Universidad Carlos III de Madrid · Historical
    Marcelo Bagnulo Universidad Carlos III de Madrid
    datatracker.ietf.org
    Discussion messages
    1
    First activity
    Apr 11, 2003
    Last activity
    Apr 11, 2003
    First explicit stance
    Propose alternative
    Latest explicit stance
    Propose alternative
    Stance changes
    0
    Viewpoint consistency
    Insufficient evidence to assess consistency
    Other policies
    1

    First explicit stance: Propose alternative → Latest explicit stance: Propose alternative · Stance changes: 0

    Viewpoint consistency: Insufficient evidence to assess consistency

    The two comments from 11 April 2003 share a concern for justified use and community cost. They support a limited cross-policy comparison, but do not establish a change of position or consistency over time.

    Multihomed End User Microallocation (2003)

    Assessment: Insufficient evidence to assess consistency · Marcelo makes microallocation conditional on continued multihoming and calls for return when eligibility ends, citing routing-table cost. Only one authored position is available for this policy.

    Conditions: One contemporaneous comment cannot establish a reversal or enduring consistency.

    Por ello creo que se deberia agregar en la politica que el bloque resultante de la microasignacion debera ser devuelto en caso que el usuario final deje de ser multi-homed.

    Resource Allocation for Experimental Use (2003)

    Assessment: Insufficient evidence to assess consistency · Marcelo opposes LACNIC experimental IPv4 allocations while allowing a regional IPv6 approach, citing scarcity and different stages of development. This is a stated distinction, not evidence of a reversal.

    Conditions: Only this authored comment is assessed; formal authorship alone is not treated as endorsement of every policy version.

    En particualr para IPv4, yo creo que LACNIC NO deberia realizar asignaciones exprimentales.

    que puede tener sentido tener una politica de asignaciones exprimentales en IPv6 propia de LACNIC,

    Multihomed End User Microallocation (2003) · Resource Allocation for Experimental Use (2003)

    Assessment: Consistent · Both comments tie access to shared resources to a justified purpose and its community costs: continued multihoming in one case, and scarcity, evaluation and public experimental results in the other. The different recommendations address different conditions and do not contradict each other in these texts.

    Conditions: This limited alignment covers two same-day comments, not the participant's full historical record.

    pero es un bien MUY costoso para la comunidad ya que impacta con una entrada en tabla de rutas de la DFZ.

    LOs resultados de los exprimentos realizados deberan ser p?blicos y estar en una p?gina web disponible para su consulta por la comunidad en general.

    direcciones IPv4 son un recurso muy escaso.

    1. Apr 11, 2003 · Propose alternative

      Sobre las politica de asignaciones exprimentales (era: Re: [Politicas] Working Groups Results / Resultado Grupos de Trabajo/ Resultado Grupos deTrabalho)

      Conditions:

      Separate IPv4 and IPv6 treatment: opposes LACNIC experimental IPv4 allocations, while supporting a region-specific IPv6 policy.

      Requests public experiment results, notice and comment on requests, and LACNIC evaluation informed by IETF expertise.

      Judge eligibility by the experiment rather than commercial status; rejects indefinite terms and accepts a renewable one-year term as a secondary option.

      En particualr para IPv4, yo creo que LACNIC NO deberia realizar asignaciones exprimentales. … que puede tener sentido tener una politica de asignaciones exprimentales en IPv6 propia de LACNIC, … Punto c) creo que la opcion i es la mas apropiada, creo que la opcion ii es completamente inaceptable y la iii la podira aceptar.

      Source facts ↗

    Total policy messages: 2

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,710
    Known gaps
    26
  • www.lacnic.net
  • lacnic-anuncios
    Earliest captured
    Sep 1, 2026
    Latest captured
    Sep 1, 2026
    Last refresh
    Oct 16, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,052
    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 16, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    375
    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,620
    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 16, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    1,357
    Known gaps
    0

Coverage

Partial
Earliest captured: Oct 21, 1999
Latest captured: Oct 16, 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.