BTW.Media
Daily editionStrategic Internet Intelligence
Sign InRegister

ARIN · RIR Watchdog

ARIN-prop-18: IPv6 Direct assignments to end sites

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
ARIN-prop-18
RIR
ARIN
Official status
Implemented
Normalized status
Accepted
Introduced
Aug 29, 2005
Last source update
Oct 13, 2026
Coverage
Partial

Who actually shaped the debate?

10Total participants
10Discussion contributors
UnknownFormal actors
17Discussion messages
7.4Effective participants
70.6%Top-five discussion share
3People covering 50%
7People covering 80%

Policy evolution

Debate timeline

  1. Introduced

    Introduced

    Source facts ↗

  2. Public discussion

    [ppml] Proposed Policy: IPv6 Direct assignments to end sites

    10 Discussion messages · 6 Entities

    Source facts ↗

  3. Public discussion

    [ppml] Proposed Policy: IPv6 Direct assignments to end sites

    2 Discussion messages · 2 Entities

    Source facts ↗

  4. Public discussion

    [ppml] Policy Proposal 2005-1: Provider-independent IPv6

    2 Discussion messages · 2 Entities

    Source facts ↗

Entities

Freshness: Stale · Last refresh: · The latest refresh failed. The last successful result is shown.
  1. Kevin Loch
    Discussion messages4
    First activityAug 30, 2005
    Last activityAug 30, 2005
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies4
  2. Marshall Eubanks
    Discussion messages3
    First activityAug 30, 2005
    Last activityAug 30, 2005
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies2
  3. marcelo bagnulo braun · Identity unresolved
    Discussion messages2
    First activityAug 30, 2005
    Last activityAug 30, 2005
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies2
  4. Lee Howard
    Discussion messages2
    First activityAug 29, 2005
    Last activityAug 31, 2005
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies8
  5. John M. Brown · Identity unresolved
    Discussion messages1
    First activityJan 7, 2003
    Last activityJan 7, 2003
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies3
  6. Stephen Sprunk
    Discussion messages1
    First activityApr 27, 2006
    Last activityApr 27, 2006
    First explicit stanceSupport
    Latest explicit stanceSupport
    Stance changes0
    Viewpoint consistencyNo validated consistency assessment
    Other policies9
  7. Member Services · Identity unresolved
    Discussion messages1
    First activityAug 29, 2005
    Last activityAug 29, 2005
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies24
  8. Ray Plzak
    Discussion messages1
    First activityAug 30, 2005
    Last activityAug 30, 2005
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies1
  9. Vince Fuller
    Discussion messages1
    First activityApr 27, 2006
    Last activityApr 27, 2006
    First explicit stanceOppose
    Latest explicit stanceOppose
    Stance changes0
    Viewpoint consistencyNo validated consistency assessment
    Other policies2
    Freshness: Stale · Last refresh: · The latest refresh failed. The last successful result is shown.

    Last research attempt: Oct 13, 2026

    Identity verified: Oct 13, 2026

    Cisco Systems · Historical
    V. Fuller Request for Comments: 4632 Cisco Systems
    www.rfc-editor.org
    Discussion messages
    1
    First activity
    Apr 27, 2006
    Last activity
    Apr 27, 2006
    First explicit stance
    Oppose
    Latest explicit stance
    Oppose
    Stance changes
    0
    Viewpoint consistency
    No validated consistency assessment
    Other policies
    2

    First explicit stance: Oppose → Latest explicit stance: Oppose · Stance changes: 0

    Viewpoint consistency: No validated consistency assessment

    1. Apr 27, 2006 · Oppose

      [ppml] Policy Proposal 2005-1: Provider-independent IPv6

      No, you are completely missing the point. Establishing a policy that … defines "provider independent space" sets a precedent that, for all … practical purposes, will not be revokable. Once early adopters are … granted "PI space", the genie will be surely and truly out of the bottle; … those recipients of a valuable commodity will not be easily persuaded to … give it up nor will their service providers cut-off paying customers by … ceasing to route "de-authorized" prefixes. Those assignhments will be … permanent, just as all SRI-NIC-era assignments ("the swamp space") are … still filling the IPv4 routing table more than 10 years after they were … last granted. Future applicants will rightly cry "foul" when told that … they aren't going to be given the same "PI space" that early adopters … were given. … Nonsense. Once something is given it is almost impossible to get it back. … And creating a two-tiered society of "early adopters with PI space" vs. … "late adopters who get something less valuable" is going to run into all … sorts of issues. … And the hundreds of thousands of routes that are of concern to those who … think about "big Internet" scaling problems are what we *will* see if a … "PI space" policy is adopted. Not by years end but most certainly if ipv6 … is widely adopted in the absence of a scalable multihoming solution (and … no, the existing ipv6 strict topology-based addressing plan doesn't cut … it, either; the protocol MUST be fixed to replace the "address" with a … topology-based locator and a endpoint id that does not need to ever be … renumbered once assigned before ipv6 can be ubiqitously deployed). … Ooh, the "restraint of trade boogieman". … I would be rather more concerned over lawsuits regarding unfair and … inconsistant business practices should an RIR establish the precedent of … granting a valuable asset ("PI space") to early adopters and then refusing … to offer equal treatment to later adopters. Or of tring to revoke the use … of an existing "PI space" allocation that is in use for critical business … purposes. … Some organizations were good enough to transition off of pre-RIR IPv4 … assignments (anybody remember net 36.0.0.0) because of a sense of community … and of doing good for the collective; that sense of community has long since … vanished from the commercial Internet, so past behavior is most certainly … not a good indicator of future behavior. … Fix the routing and addressing architecture *NOW*; don't try to kludge … around it and hope that it is possible to retrofit a fix later.

      Source facts ↗
    Per-policy stance timelines:ARIN-2005-1 · Oppose · No validated consistency assessmentARIN-prop-10 · Oppose · No validated consistency assessmentARIN-prop-18 · Oppose · No validated consistency assessment

    Total policy messages: 5

  10. Owen DeLong
    Discussion messages1
    First activityAug 29, 2005
    Last activityAug 29, 2005
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies15

Sources and coverage

Official policy sources

Public discussion archives

  • arin-ppml
    Earliest captured
    Sep 1, 1999
    Latest captured
    Oct 8, 2026
    Last refresh
    Oct 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    31,204
    Known gaps
    0
  • www.arin.net
  • arin-arin-announce
    Earliest captured
    Aug 4, 2026
    Latest captured
    Oct 7, 2026
    Last refresh
    Oct 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    3,144
    Known gaps
    0
  • arin-arin-consult
    Earliest captured
    Aug 14, 2026
    Latest captured
    Sep 15, 2026
    Last refresh
    Oct 11, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    2,438
    Known gaps
    3
  • arin-arin-discuss
    Earliest captured
    Aug 2, 1999
    Latest captured
    Aug 21, 2007
    Last refresh
    Oct 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    716
    Known gaps
    0
  • arin-arin-issued
    Earliest captured
    Aug 2, 2026
    Latest captured
    Oct 12, 2026
    Last refresh
    Oct 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    6,568
    Known gaps
    0
  • arin-arin-ppml
    Earliest captured
    Aug 2, 2026
    Latest captured
    Oct 8, 2026
    Last refresh
    Oct 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    5,329
    Known gaps
    0
  • arin-arin-regrws
    Earliest captured
    Unknown
    Latest captured
    Unknown
    Last refresh
    Oct 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    0
    Known gaps
    0
  • arin-arin-rpki-pilot
    Earliest captured
    Jul 7, 2009
    Latest captured
    Jul 7, 2009
    Last refresh
    Oct 13, 2026
    Coverage
    Current
    Loading
    0
    Known gaps
    0
  • arin-arin-suggestions
    Earliest captured
    Aug 26, 2026
    Latest captured
    Sep 4, 2026
    Last refresh
    Oct 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    1,040
    Known gaps
    0
  • arin-arin-tech-discuss
    Earliest captured
    Aug 13, 2026
    Latest captured
    Oct 5, 2026
    Last refresh
    Oct 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    1,841
    Known gaps
    0
  • arin-arin-whoisrws
    Earliest captured
    Oct 9, 2009
    Latest captured
    Sep 6, 2010
    Last refresh
    Oct 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    0
    Known gaps
    0
  • arin-clew
    Earliest captured
    May 6, 1999
    Latest captured
    Nov 7, 2002
    Last refresh
    Oct 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    56
    Known gaps
    0
  • arin-dbwg
    Earliest captured
    Apr 22, 1999
    Latest captured
    Dec 30, 2004
    Last refresh
    Oct 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    443
    Known gaps
    0
  • arin-iana-transition
    Earliest captured
    Oct 13, 2014
    Latest captured
    Jun 9, 2016
    Last refresh
    Oct 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    145
    Known gaps
    0
  • arin-icp2_review
    Earliest captured
    Apr 14, 2025
    Latest captured
    Nov 10, 2025
    Last refresh
    Oct 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    0
    Known gaps
    0
  • arin-naipr
    Earliest captured
    Jan 1, 1997
    Latest captured
    Nov 3, 1997
    Last refresh
    Oct 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    1,964
    Known gaps
    0
  • arin-nrr-blueprint
    Earliest captured
    Oct 9, 2002
    Latest captured
    Oct 29, 2002
    Last refresh
    Oct 13, 2026
    Coverage
    Current
    Loading
    0
    Known gaps
    0
  • arin-policy
    Earliest captured
    Oct 12, 1999
    Latest captured
    Mar 26, 2003
    Last refresh
    Oct 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    100
    Known gaps
    0
  • arin-rtma
    Earliest captured
    Apr 18, 2000
    Latest captured
    Dec 28, 2001
    Last refresh
    Oct 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    269
    Known gaps
    0
  • arin-services-wg
    Earliest captured
    Apr 20, 2016
    Latest captured
    Jan 20, 2018
    Last refresh
    Oct 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    29
    Known gaps
    0
  • arin-v6wg
    Earliest captured
    Nov 8, 2000
    Latest captured
    Mar 1, 2005
    Last refresh
    Oct 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    145
    Known gaps
    0
  • arin-vwp
    Earliest captured
    Oct 18, 2000
    Latest captured
    Jul 10, 2001
    Last refresh
    Oct 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    232
    Known gaps
    0
  • arin-general-members
    Earliest captured
    Jun 3, 2022
    Latest captured
    Jun 25, 2026
    Last refresh
    Oct 13, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    129
    Known gaps
    0

Coverage

Partial
Earliest captured: Jan 1, 1997
Latest captured: Oct 13, 2026

Freshness

Freshness: Stale · Last refresh: · The latest refresh failed. The last successful result is shown.

Known gaps

  • www.arin.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • www.arin.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • arin-ppml: Source coverage is incomplete. · The source boundary has not yet been reached.
  • www.arin.net: Source coverage is incomplete. · The source boundary has not yet been reached.
  • arin-arin-announce: Source coverage is incomplete. · The source boundary has not yet been reached.
  • arin-arin-consult: Source coverage is incomplete. · The source boundary has not yet been reached.
  • arin-arin-discuss: Source coverage is incomplete. · The source boundary has not yet been reached.
  • arin-arin-issued: Source coverage is incomplete. · The source boundary has not yet been reached.
  • arin-arin-ppml: Source coverage is incomplete. · The source boundary has not yet been reached.
  • arin-arin-regrws: Source coverage is incomplete. · The source boundary has not yet been reached.
  • arin-arin-suggestions: Source coverage is incomplete. · The source boundary has not yet been reached.
  • arin-arin-tech-discuss: Source coverage is incomplete. · The source boundary has not yet been reached.
  • arin-clew: Source coverage is incomplete. · The source boundary has not yet been reached.
  • arin-dbwg: Source coverage is incomplete. · The source boundary has not yet been reached.
  • arin-iana-transition: Source coverage is incomplete. · The source boundary has not yet been reached.
  • arin-naipr: Source coverage is incomplete. · The source boundary has not yet been reached.
  • arin-policy: Source coverage is incomplete. · The source boundary has not yet been reached.
  • arin-rtma: Source coverage is incomplete. · The source boundary has not yet been reached.
  • arin-services-wg: Source coverage is incomplete. · The source boundary has not yet been reached.
  • arin-v6wg: Source coverage is incomplete. · The source boundary has not yet been reached.
  • arin-vwp: Source coverage is incomplete. · The source boundary has not yet been reached.
  • arin-general-members: Source coverage is incomplete. · The source boundary has not yet been reached.