ARIN · RIR Watchdog
2005-1: Provider Independent IPv6 Assignments for 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-2005-1
- RIR
- ARIN
- Official status
- Adopted
- Normalized status
- Accepted
- Introduced
- Feb 15, 2005
- Last source update
- Oct 13, 2026
- Coverage
- Partial
Who actually shaped the debate?
Policy evolution
Debate timeline
Public discussion
[ppml] Proposed Policy: IPv6 Direct assignments to end sites
2 Discussion messages · 2 Entities
Source facts ↗Public discussion
[ppml] 2005-1 or its logical successor
2 Discussion messages · 2 Entities
Source facts 1 ↗Source facts 2 ↗Public discussion
[ppml] "Recommended Practices" procedure
2 Discussion messages · 2 Entities
Source facts ↗Public discussion
[ppml] Policy Proposal 2005-1: Provider-independent IPv6
19 Discussion messages · 9 Entities
Source facts ↗
Entities
- Discussion messages7First activityApr 30, 2005Last activityApr 28, 2006First explicit stanceSupportLatest explicit stanceSupportStance changes0Viewpoint consistencyNo validated consistency assessmentOther policies9
- Discussion messages7First activityAug 30, 2005Last activityApr 28, 2006First explicit stanceSupport with changesLatest explicit stanceSupportStance changes1Viewpoint consistencyNo validated consistency assessmentOther policies2
- Discussion messages7First activityNov 10, 2005Last activityApr 28, 2006First explicit stancePropose alternativeLatest explicit stanceSupportStance changes1Viewpoint consistencyConsistentOther policies4
- Discussion messages5First activityDec 8, 2004Last activityApr 28, 2006First explicit stanceSupport with changesLatest explicit stanceSupportStance changes1Viewpoint consistencyConsistentOther policies15
- Discussion messages4First activityAug 30, 2005Last activityApr 27, 2006First explicit stancePropose alternativeLatest explicit stancePropose alternativeStance changes0Viewpoint consistencyConsistentOther policies4
- Discussion messages3First activityApr 27, 2006Last activityApr 28, 2006First explicit stancePropose alternativeLatest explicit stancePropose alternativeStance changes0Viewpoint consistencyNo validated consistency assessmentOther policies1
- Vince Fuller · Identity unresolvedDiscussion messages3First activityApr 27, 2006Last activityApr 28, 2006First explicit stanceOpposeLatest explicit stanceOpposeStance changes0Viewpoint consistencyNo validated consistency assessmentOther policies2Freshness: Stale · Last refresh: · The latest refresh failed. The last successful result is shown.
- Discussion messages
- 3
- First activity
- Apr 27, 2006
- Last activity
- Apr 28, 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
- 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 … 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 ↗ - Apr 27, 2006 · Oppose
[ppml] Policy Proposal 2005-1: Provider-independent IPv6
Once again, I will submit myself to the definition of insanity by trying … again (and no doubt failing) to explain a little bit about Internet scaling. … In fairness, it is difficult to comprehend the issues and complexities of … large network scaling until one has worked first hand in a large network … This "analysis" completely misses the point. IMHO, it is also simply wrong. … Growth trends clearly show that the fraction of Internet sites which are multi … homed and/or which engage in traffic engineering via more-specifics is on the … rise. Expect this trend to accelerate as the Internet becomes more mission- … critical for businesses of all sizes. A substantial fraction (20%? 50%? … more?) of the number of worldwide businesses would be a good guess at the … eventual number of multihomed sites. How many businesses today don't have … mission-critical phone service? There is good reason to believe that Internet … access will be just as important in the future, particularly if the vision … of the "converged network" comes to pass (not that I'm drinking that … kool-aide... but that is a separate conversation). Multi-homing will drive … the creation of enormous global routing state if the expedient "provider … independant space" approach is taken in favor of the more difficult task … of fixing the architecture (and no, I do not believe that shim6 will be … a viable alternative). Believe it or not, consumer Internet usage also … continues to grow at a super-linear rate, thanks to the emergence of … applications which appeal to mainstream users (for example, peer-to-peer … file sharing). As traditional telephony and other services are moved to … the packet network, this trend will accelerate. … As I probably mentioned in an earlier message, exponential and polynomial … growth curves often don't look very exciting during the shallow, early stage … of growth, when small numbers mask what will become an impressive trend. … This statement belies a fundamental lack of understanding of the IETF and … the history of operator participation over the past 10 to 15 years. During … that period, the IETF has been almost completely devoid of operational focus, … partly due to low operator participation (see below for why some operators … feel alienated) and partly due to active bias against "evil greedy bastard" … ISPs. The output of the IETF, most notably in ipv6's lack of a scalable … routing and addressing architecture, reflects this. In that particular case, … those with operational experience were greeted with outright hostility; as … the political consensus-building process converged on ipv6-nee-SIP, some … operators did speak up and say "this isn't going to work... you are ignoring … the fundamental scaling problems in routing and addressing". They were told … "too bad" and actively discouraged from participating. Meanwhile the ipv6 … brain trust said, to paraphrase a "talking Barbie" doll of the 1970s, that … "math [solving that problem] is hard, let's go shopping [design packet … headers] instead". … This statement couldn't be more wrong. In fact, I had to read it several … times to make sure that I had parsed it correctly. … I would be very interested in understanding your operational experience, … particularly as it pertains to large ISP networks. In my experience in … working for regional, then national, then international ISP networks from … 1988 until 2001, it was abundantly clear that equipment vendors viewed "that … Internet stuff" as a small, sometimes-profitable but low margin sidelight … to enterprise networking. This was true when token ring source-route bridging … (remember that?) and IBM terminal emulation were implemented more quickly and … more correctly than sorely needed ISP features like OSPF, IS-IS, or BGP. It … remains true today. … This "conspiracy of the vendors and the big ISPs" has more in common with … analysis of the Zapruder tape and theories about the grassy knoll than it … does with business reality. It really is time to give it a rest already.
Source facts ↗ - Apr 28, 2006 · Unknown
[ppml] Policy Proposal 2005-1: Provider-independent IPv6
Validated evidence is unavailable.
Source facts ↗
Per-policy stance timelines:ARIN-2005-1 · Oppose · No validated consistency assessmentARIN-prop-18 · Oppose · No validated consistency assessmentARIN-prop-10 · Oppose · No validated consistency assessmentTotal policy messages: 5
- Discussion messages2First activityJan 24, 2006Last activityApr 18, 2006First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies1
- Michel Py · Identity unresolvedDiscussion messages2First activityApr 27, 2006Last activityApr 28, 2006First explicit stanceSupportLatest explicit stanceSupportStance changes0Viewpoint consistencyNo validated consistency assessmentOther policies3
- Unknown · Identity unresolvedDiscussion messages2First activityJan 8, 2003Last activityDec 9, 2004First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies13
- Discussion messages1First activityApr 27, 2006Last activityApr 27, 2006First explicit stancePropose alternativeLatest explicit stancePropose alternativeStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies1
- Discussion messages1First activityApr 27, 2006Last activityApr 27, 2006First explicit stanceSupportLatest explicit stanceSupportStance changes0Viewpoint consistencyNo validated consistency assessmentOther policies1
- John M. Brown · Identity unresolvedDiscussion messages1First activityJan 9, 2003Last activityJan 9, 2003First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies3
- McBurnett, Jim · Identity unresolvedDiscussion messages1First activityJan 8, 2003Last activityJan 8, 2003First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies5
- Tony Hain · Identity unresolvedDiscussion messages1First activityNov 2, 2005Last activityNov 2, 2005First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies0
- marcelo bagnulo braun · Identity unresolvedDiscussion messages1First activityDec 8, 2004Last activityDec 8, 2004First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies2
- Discussion messages1First activityFeb 21, 2006Last activityFeb 21, 2006First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies2
- Discussion messages1First activityApr 28, 2006Last activityApr 28, 2006First explicit stanceSupportLatest explicit stanceSupportStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies7
- Discussion messages1First activityApr 26, 2006Last activityApr 26, 2006First explicit stanceSupportLatest explicit stanceSupportStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies1
- Discussion messages1First activityDec 8, 2004Last activityDec 8, 2004First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies4
- Bill Van Emburg · Identity unresolvedDiscussion messages1First activityApr 6, 2006Last activityApr 6, 2006First explicit stanceSupportLatest explicit stanceSupportStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies2
- Pekka Savola · Identity unresolvedDiscussion messages1First activityApr 25, 2006Last activityApr 25, 2006First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies0
- Discussion messages1First activityApr 27, 2006Last activityApr 27, 2006First explicit stanceOpposeLatest explicit stanceOpposeStance changes0Viewpoint consistencyNo validated consistency assessmentOther policies0
- Discussion messages1First activityApr 26, 2006Last activityApr 26, 2006First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies8
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,210
- 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,142
- 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,437
- 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 13, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 6,577
- Known gaps
- 0
- arin-arin-ppml
- Earliest captured
- Aug 2, 2026
- Latest captured
- Oct 13, 2026
- Last refresh
- Oct 13, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 5,335
- 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,038
- 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,840
- 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
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.
