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?
Policy evolution
Debate timeline
Entities
- Discussion messages1First activityApr 15, 2003Last activityApr 15, 2003First explicit stanceSupportLatest explicit stanceSupportStance changes0Viewpoint consistencyNo validated consistency assessmentOther policies5Freshness: Stale
Last research attempt: Oct 14, 2026
Identity verified: Oct 14, 2026
Cisco · Current Roque Gagliano is a Principal Solutions Engineer in Cisco Sales.
blogs.cisco.comANTEL · Historical Before Cisco, he held engineering and architecture roles at LACNIC, ANTEL, and Sprint, working on Internet infrastructure and inter-domain routing.
blogs.cisco.comVerified public profiles
- Discussion messages
- 1
- First activity
- Apr 15, 2003
- Last activity
- Apr 15, 2003
- First explicit stance
- Support
- Latest explicit stance
- Support
- Stance changes
- 0
- Viewpoint consistency
- No validated consistency assessment
- Other policies
- 5
First explicit stance: Support → Latest explicit stance: Support · Stance changes: 0
Viewpoint consistency: No validated consistency assessment
- Apr 15, 2003 · Support
[Politicas] Asunto: Re: Asunto: Re: [Asig-exp] Informe de asignaciones experimentales
Conditions:
Supports regional experimental access and outreach so research groups know LACNIC resources are available.
Also advocates reconsidering broader IPv6 allocation requirements; this does not establish endorsement of every experimental-policy draft clause or of a specific formal outcome.
(Roque) Estoy de acuerdo, creo que tambi?n debemos hacer m?s para que estas organizaciones sepan que tienen los recursos de LACNIC disponibles de ser necesarios para sus trabajos.
Source facts ↗
Per-policy stance timelines:LAC-2013-2 · Unknown · No explicit position statedLAC-2016-1 · Unknown · No explicit position statedLAC-2018-3 · Unknown · No explicit position statedIPv4 address block allocation policies — Working Group 3 (2002) · Unknown · No explicit position statedMultihomed End User Microallocation (2003) · Support with changes · No validated consistency assessmentResource Allocation for Experimental Use (2003) · Support · No validated consistency assessmentTotal policy messages: 8
- Discussion messages1First activityApr 11, 2003Last activityApr 11, 2003First explicit stancePropose alternativeLatest explicit stancePropose alternativeStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies1
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
- Mar 15, 2002
- Latest captured
- Oct 7, 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 17, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1,136
- Known gaps
- 0
- lacnic-infofrida
- Earliest captured
- Aug 14, 2006
- Latest captured
- Sep 13, 2011
- Last refresh
- Oct 16, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 297
- Known gaps
- 0
- lacnic-iot
- Earliest captured
- Oct 6, 2015
- Latest captured
- Jul 11, 2017
- Last refresh
- Oct 17, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 377
- 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,539
- Known gaps
- 4
- lacnic-lactf
- Earliest captured
- Apr 13, 2004
- Latest captured
- Dec 29, 2006
- Last refresh
- Oct 16, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,270
- 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,359
- Known gaps
- 0
Coverage
Partial
Earliest captured: Oct 21, 1999
Latest captured: Oct 17, 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.