LACNIC · RIR Watchdog
Update End-User and End-Site Definitions
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-2021-5
- RIR
- LACNIC
- Official status
- Abandoned
- Normalized status
- Abandoned
- Introduced
- Sep 20, 2022
- Last source update
- Oct 10, 2026
- Coverage
- Partial
Who actually shaped the debate?
Policy evolution
Definition of End-Site (Section 1.7) · The definition of 'End-Site' was refined to explicitly refer to the 'location' of an End-User and changed the relationship description from 'legal or commercial' to 'business or legal'. The bullet points were rephrased for clarity (e.g., 'transporting' to 'carrying', 'announcing' to 'advertising').
Source facts −
o solve) Right now, the definitions of “end-user” and “end-site” are not clearly differentiated, possibly because they were introduced with an IPv4 mind-set. The reality, however, is that they are different concepts —a fact that is increasingly evident in IPv6— and that even the same end user may have several end sites that requireSource facts ↗
Source facts +
you intend to solve) Right now, the definitions of end “end-user” and “end-site” are not clearly differentiated, possibly because they are based on concepts that apply to IPv4. The reality, however, is that they are different concepts —a fact that is increasingly evident in IPv6— and that even the same end-user may have several enSource facts ↗
Definition of End-User (Section 1.8) · A new section 1.8 defining 'End User' was added as a subscriber or customer of an LIR, whereas previously the term was part of Section 1.7 ('End Site or End User') without a separate definition.
Section Numbering (IPv6 Assignments) · The section numbers for direct assignment of portable IPv6 addresses were changed from 4.5.x to 4.4.x.
Assignment Size Specification · The phrasing for IPv6 assignment sizes was changed from 'Assignments will be made in blocks always greater than or equal to a /48' to 'The minimum size of the assignment is a /48 per End-Site'.
Source facts −
of access which may require separate /48s, yet these cannot even be aggregatSource facts ↗
Source facts +
different providers or means of access which may require separate /48s, yetSource facts ↗
Presentation History · The proposal presentation history was updated from LACNIC 36 (11/10/2021) to LACNIC 38 (04/10/2022).
Debate timeline
Entities
- Discussion messages0First activityUnknownLast activityUnknownFirst explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies39
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,388
- Known gaps
- 26
- www.lacnic.net
- lacnic-anuncios
- Earliest captured
- Aug 13, 2026
- Latest captured
- Oct 7, 2026
- Last refresh
- Oct 11, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,118
- Known gaps
- 0
- lacnic-ietf-lac
- Earliest captured
- May 30, 2013
- Latest captured
- Dec 30, 2015
- Last refresh
- Oct 10, 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 10, 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 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 373
- Known gaps
- 0
- lacnic-lacnog
- Earliest captured
- Aug 1, 2026
- Latest captured
- Oct 9, 2026
- Last refresh
- Oct 11, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 6,123
- Known gaps
- 0
- lacnic-lactf
- Earliest captured
- Apr 13, 2004
- Latest captured
- Dec 29, 2006
- Last refresh
- Oct 10, 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 10, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1,356
- Known gaps
- 0
Coverage
Partial
Earliest captured: Oct 21, 1999
Latest captured: Oct 11, 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.
