LACNIC · RIR Watchdog
Remove the reference to a provider’s "multihomed or non-multihomed status".
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
- LAC-2016-3
- RIR
- LACNIC
- Official status
- Abandoned
- Normalized status
- Abandoned
- Introduced
- Feb 17, 2016
- Last source update
- Oct 9, 2026
- Coverage
- Partial
Who actually shaped the debate?
Policy evolution
Scope and form of the proposed amendment · The old version called for removing the term “multihomed” from sections 2.3.3.1, 2.3.3.3, and 2.3.3.4.3 without exception. The new version instead presents a specific replacement amendment for section 2.3.3.1.2.
Source facts −
erm "multihomed" appears in sections 2.3.3.1, 2.3.3.3 and 2.3.3.4.3, and should be removed without exception. New tSource facts ↗
Source facts +
e following changes should made to the Policy Manual: a. Replace the following text from section 2.3.3.1.2: “Source facts ↗
Provider autonomous-system information requirement · The old version's blanket removal instruction was replaced by language requiring the applying ISP to specify the names and autonomous-system numbers of its providers, without conditioning that requirement on multihomed status.
Source facts −
erm "multihomed" appears in sections 2.3.3.1, 2.3.3.3 and 2.3.3.4.3, and should be removed without exception. New tSource facts ↗
Source facts +
the names and numbers of the autonomous system of its providers. If the aSource facts ↗
Interconnection plan and timeline requirement · The new version adds explicit replacement language requiring a detailed plan and timeline when the applicant needs to interconnect with other autonomous systems; the old version instead directed that multihomed references be removed without exception and did not supply this replacement clause.
Source facts −
erm "multihomed" appears in sections 2.3.3.1, 2.3.3.3 and 2.3.3.4.3, and should be removed without exception. New tSource facts ↗
Source facts +
pplicant needs to interconnect with other autonomous systems, describe in detail the corresponding plan and timeline (presenting signed contracts or letters of intent is recommended). New texSource facts ↗
Remote-area socioeconomic rationale · The old version stated only that physical or economic limitations can make redundancy nonviable in remote areas. The new version adds that lack of economic viability affects communities, prevents Internet use, and harms the goal of universal web access.
Source facts −
Physical and/or economic limitations exist in remote areas that make redundancy not viable. CuSource facts ↗
Source facts +
e lack of economic viability affects the communities involved and prevents their use of the Internet, thus hurting the universal desire for universal access to the World Wide Web. CSource facts ↗
Debate timeline
Entities
- Gianina Pensky · Identity unresolvedDiscussion messages6First activityFeb 20, 2016Last activityMar 15, 2016First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies23
- Alex Ojeda · Identity unresolvedDiscussion messages2First activityFeb 18, 2016Last activityMay 19, 2016First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies11
- Juan Alejo Peirano · Identity unresolvedDiscussion messages2First activitySep 9, 2016Last activityOct 6, 2016First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies23
- Unknown · Public sources found; identity verification pendingDiscussion messages2First activityNov 7, 2016Last activityDec 13, 2016First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies19
- Discussion messages1First activityApr 18, 2016Last activityApr 18, 2016First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies17
- Roque Gagliano · Identity unresolvedDiscussion messages1First activityJul 17, 2009Last activityJul 17, 2009First explicit stanceSupport with changesLatest explicit stanceSupport with changesStance changes0Viewpoint consistencyConsistentOther policies0
- Discussion messages0First activityUnknownLast activityUnknownFirst explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies0
- Discussion messages0First activityUnknownLast activityUnknownFirst explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies0
Sources and coverage
Official policy sources
Public discussion archives
- lacnic-politicas
- Earliest captured
- Oct 21, 1999
- Latest captured
- Oct 8, 2026
- Last refresh
- Aug 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 5,258
- Known gaps
- 26
- www.lacnic.net
- lacnic-anuncios
- Earliest captured
- Aug 13, 2026
- Latest captured
- Oct 7, 2026
- Last refresh
- Oct 9, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,088
- Known gaps
- 0
- lacnic-ietf-lac
- Earliest captured
- May 30, 2013
- Latest captured
- Dec 30, 2015
- Last refresh
- Oct 9, 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 9, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 287
- Known gaps
- 0
- lacnic-iot
- Earliest captured
- Oct 6, 2015
- Latest captured
- Jul 11, 2017
- Last refresh
- Oct 9, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 373
- Known gaps
- 0
- lacnic-lacnog
- Earliest captured
- Aug 1, 2026
- Latest captured
- Oct 8, 2026
- Last refresh
- Oct 9, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 5,951
- Known gaps
- 0
- lacnic-lactf
- Earliest captured
- Apr 13, 2004
- Latest captured
- Dec 29, 2006
- Last refresh
- Oct 9, 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 9, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1,356
- Known gaps
- 0
Coverage
Partial
Earliest captured: Oct 21, 1999
Latest captured: Oct 9, 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.
