LACNIC · RIR Watchdog
Multihomed End User Microallocation (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-multihomed-end-user-microallocation-2003
- RIR
- LACNIC
- Official status
- Approved Implemented in 19/5/2003
- Normalized status
- Accepted
- Introduced
- Feb 7, 2003
- Last source update
- Oct 14, 2026
- Coverage
- Partial
Who actually shaped the debate?
4Total participants
4Discussion contributors
1Formal actors
4Discussion messages
4Effective participants
100%Top-five discussion share
2People covering 50%
4People covering 80%
Policy evolution
Debate timeline
Public discussion
sobre la politica propuesta para microasignaciones para UF multi-homed (era: Re: [Politicas] Working Groups Results / Resultado Grupos de Trabajo/ Resultado Grupos deTrabalho
3 Discussion messages · 3 Entities
Source facts ↗
Entities
Freshness: Stale
- Octavio Novoa · Identity unresolvedDiscussion messages1First activityApr 11, 2003Last activityApr 11, 2003First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies0
- Discussion messages1First activityApr 11, 2003Last activityApr 11, 2003First explicit stanceSupport with changesLatest explicit stanceSupport with changesStance changes0Viewpoint consistencyNo validated consistency assessmentOther policies5
- Discussion messages1First activityApr 11, 2003Last activityApr 11, 2003First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies27Freshness: Stale
Last research attempt: Oct 14, 2026
Identity verified: Oct 14, 2026
LACNIC · Historical Ricardo Patara (*) - Registration Service Manager.
www.lacnic.netNIC.BR · Current Actualmente se desempeña como gerente de Recursos de Numeración de Internet en NIC.BR
blog.lacnic.netVerified public profiles
- Discussion messages
- 1
- First activity
- Apr 11, 2003
- Last activity
- Apr 11, 2003
- 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
- Apr 11, 2003 · Question or clarify
[Politicas] Asunto: sobre la politica propuesta para microasignaciones para UF multi-homed (era: Re: [Politicas] Working Groups Results / Resultado Grupos de Trabajo/ Resultado Grupos deTrabalho
Conditions:
Questions how LACNIC could reliably verify that an organization remains multihomed after an allocation.
Raises an enforcement concern; the message does not reject the entire microallocation policy.
Yo pienso que ser?a muy complicado para LACNIC verificar si la organizaci?n que recibi? bloque IP de LACNIC bajo ?sta pol?tica sigue como multi-homed despu?s de un cierto timpo. No veo cual es la manera m?s segura de hacer esto.
Source facts ↗
Per-policy stance timelines:LAC-2012-8 · Unknown · No explicit position statedLAC-2013-1 · Unknown · No explicit position statedLAC-2013-2 · Unknown · No explicit position statedLAC-2013-4 · Unknown · No explicit position statedLAC-2014-2 · Unknown · No explicit position statedLAC-2014-3 · Unknown · No explicit position statedLAC-2015-2 · Unknown · No explicit position statedLAC-2015-4 · Unknown · No explicit position statedLAC-2016-2 · Unknown · No explicit position statedLAC-2016-5 · Oppose · No validated consistency assessmentLAC-2017-2 · Oppose · No validated consistency assessmentLAC-2017-5 · Oppose · No validated consistency assessmentLAC-2017-6 · Support · No validated consistency assessmentLAC-2017-8 · Propose alternative · No validated consistency assessmentLAC-2018-1 · Oppose · No validated consistency assessmentLAC-2018-12 · Support with changes · No validated consistency assessmentLAC-2018-2 · Support · No validated consistency assessmentLAC-2018-5 · Support with changes · No validated consistency assessmentLAC-2018-6 · Oppose · No validated consistency assessmentLAC-2018-7 · Unknown · No explicit position statedLAC-2018-8 · Oppose · No validated consistency assessmentLAC-2018-9 · Oppose · No validated consistency assessmentLAC-2019-12 · Unknown · No explicit position statedLAC-2020-9 · Unknown · No explicit position statedLAC-2024-4 · Unknown · No explicit position statedLAC-2026-3 · Unknown · No explicit position statedIPv4 address block allocation policies — Working Group 3 (2002) · Unknown · No explicit position statedMultihomed End User Microallocation (2003) · Unknown · No explicit position statedTotal policy messages: 69
- Discussion messages1First activityApr 11, 2003Last activityApr 11, 2003First explicit stanceSupport with changesLatest explicit stanceSupport with changesStance 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,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,650
- 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.