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?
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
- 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 policies27
- Discussion messages1First activityApr 11, 2003Last activityApr 11, 2003First explicit stanceSupport with changesLatest explicit stanceSupport with changesStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies1Freshness: 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.orgVerified public profiles
- Discussion messages
- 1
- First activity
- Apr 11, 2003
- Last activity
- Apr 11, 2003
- First explicit stance
- Support with changes
- Latest explicit stance
- Support with changes
- Stance changes
- 0
- Viewpoint consistency
- Insufficient evidence to assess consistency
- Other policies
- 1
First explicit stance: Support with changes → Latest explicit stance: Support with changes · 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.
- Apr 11, 2003 · Support with changes
sobre la politica propuesta para microasignaciones para UF multi-homed (era: Re: [Politicas] Working Groups Results / Resultado Grupos de Trabajo/ Resultado Grupos deTrabalho
Conditions:
Add an explicit requirement to return the microallocation when the end user ceases to be multihomed.
Distinguishes multihoming eligibility from permanent provider-independent ownership and identifies routing-table cost.
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.
Source facts ↗
Per-policy stance timelines:Multihomed End User Microallocation (2003) · Support with changes · Insufficient evidence to assess consistencyResource Allocation for Experimental Use (2003) · Propose alternative · Insufficient evidence to assess consistencyTotal 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,678
- Known gaps
- 26
- www.lacnic.net
- lacnic-anuncios
- Earliest captured
- Aug 13, 2026
- Latest captured
- Oct 7, 2026
- Last refresh
- Oct 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,189
- Known gaps
- 0
- lacnic-ietf-lac
- Earliest captured
- May 30, 2013
- Latest captured
- Dec 30, 2015
- Last refresh
- Oct 14, 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 14, 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 14, 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,546
- Known gaps
- 3
- lacnic-lactf
- Earliest captured
- Apr 13, 2004
- Latest captured
- Dec 29, 2006
- Last refresh
- Oct 14, 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 14, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1,356
- Known gaps
- 0
Coverage
Partial
Earliest captured: Oct 21, 1999
Latest captured: Oct 14, 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.
