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 23, 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 consistencyConsistentOther policies11
- 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 consistencyNo validated consistency assessmentOther policies20
- 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
- Discussion messages3First activityApr 27, 2006Last activityApr 28, 2006First explicit stanceOpposeLatest explicit stanceOpposeStance changes0Viewpoint consistencyNo validated consistency assessmentOther policies2
- Discussion messages2First activityJan 24, 2006Last activityApr 18, 2006First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies1Freshness: Stale · Last refresh: · The latest refresh failed. The last successful result is shown.
Last research attempt: Oct 13, 2026
Identity verified: Oct 13, 2026
Internap · Historical Scott Leibrand, Internap
www.arin.netARIN · Historical Scott Leibrand January 2008 - December 2016
www.arin.netVerified public profiles
- Discussion messages
- 2
- First activity
- Jan 24, 2006
- Last activity
- Apr 18, 2006
- First explicit stance
- Unknown
- Latest explicit stance
- Unknown
- Stance changes
- 0
- Viewpoint consistency
- Insufficient evidence to assess consistency
- Other policies
- 1
First explicit stance: Unknown → Latest explicit stance: Unknown · Stance changes: 0
Viewpoint consistency: Insufficient evidence to assess consistency
Asking which IPv6 PI criteria could win consensus and acknowledging a shim6 technical explanation do not establish opposing positions on the allocation policy.
2005-1: Provider Independent IPv6 Assignments for End-sites
Assessment: Insufficient evidence to assess consistency · Asking which IPv6 PI criteria could win consensus and acknowledging a shim6 technical explanation do not establish opposing positions on the allocation policy.
Conditions: The two statements address different questions; neither provides a final eligibility rule or a clear vote on the proposal.
I would love to hear what exactly everyone thinks is an appropriate standard for allocating IPv6 PI space so we can better gauge what would be a consensus position.
From the discussion I've seen of middle-boxes on the shim6 list, that seems to be the idea.
2005-1: Provider Independent IPv6 Assignments for End-sites · ARIN-prop-27: RSA Modification Procedure
Assessment: Insufficient evidence to assess consistency · A question about IPv6 PI eligibility and an editorial terminology change in the RSA proposal are not comparable policy commitments.
Conditions: Different subject matter and limited statements prevent a conclusion about consistency across these policies.
hear what exactly everyone thinks is an appropriate standard for allocating IPv6 PI space
We have enough acronym confusion already.
- Jan 24, 2006 · Question or clarify
[ppml] 2005-1 status
I would agree. However, 2005-1 did not reach consensus, so we need to come up with an alternative that's more likely to do so. I would love to hear what exactly everyone thinks is an appropriate standard for allocating IPv6 PI space so we can better gauge what would be a consensus position. -Scott
Source facts ↗ - Apr 18, 2006 · Procedural or neutral
Conditions:
This is a technical observation about possible interoperability between shim6 hosts and middlebox-based sites. It does not explicitly endorse or reject the PI assignment policy.
From the discussion I've seen of middle-boxes on the shim6 list, that seems to be the idea.
Source facts ↗
Per-policy stance timelines:ARIN-2005-1 · Unknown · Insufficient evidence to assess consistencyARIN-prop-27 · Propose alternative · Insufficient evidence to assess consistencyTotal policy messages: 16
- 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 policies16
- 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 policies5
- 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 consistencyNo validated consistency assessmentOther 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
- Kevin Loch · Identity unresolvedDiscussion messages0First activityUnknownLast activityUnknownFirst explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies0
- Owen DeLong · Identity unresolvedDiscussion messages0First activityUnknownLast activityUnknownFirst explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies0
- Andrew Dul · Identity unresolvedDiscussion messages0First activityUnknownLast activityUnknownFirst explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyNo explicit position statedOther policies0
Sources and coverage
Official policy sources
Public discussion archives
- arin-ppml
- Earliest captured
- Sep 1, 1999
- Latest captured
- Oct 16, 2026
- Last refresh
- Oct 23, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 23,901
- Known gaps
- 0
- www.arin.net
- arin-arin-announce
- Earliest captured
- Aug 4, 2026
- Latest captured
- Oct 21, 2026
- Last refresh
- Oct 23, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 2,278
- Known gaps
- 11
- arin-arin-consult
- Earliest captured
- Aug 14, 2026
- Latest captured
- Oct 21, 2026
- Last refresh
- Oct 21, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 909
- Known gaps
- 48
- arin-arin-discuss
- Earliest captured
- Aug 2, 1999
- Latest captured
- Aug 21, 2007
- Last refresh
- Oct 23, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 716
- Known gaps
- 0
- arin-arin-issued
- Earliest captured
- Aug 2, 2026
- Latest captured
- Oct 22, 2026
- Last refresh
- Oct 23, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 7,294
- Known gaps
- 0
- arin-arin-ppml
- Earliest captured
- Aug 27, 2026
- Latest captured
- Oct 13, 2026
- Last refresh
- Oct 23, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 31,579
- Known gaps
- 2
- arin-arin-regrws
- Earliest captured
- Unknown
- Latest captured
- Unknown
- Last refresh
- Oct 23, 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 23, 2026
- Coverage
- Current
- Loading
- 0
- Known gaps
- 0
- arin-arin-suggestions
- Earliest captured
- Jun 15, 2011
- Latest captured
- Oct 14, 2026
- Last refresh
- Oct 23, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 839
- Known gaps
- 0
- arin-arin-tech-discuss
- Earliest captured
- Sep 15, 2010
- Latest captured
- Oct 16, 2026
- Last refresh
- Oct 23, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1,186
- Known gaps
- 0
- arin-arin-whoisrws
- Earliest captured
- Oct 9, 2009
- Latest captured
- Sep 6, 2010
- Last refresh
- Oct 23, 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 23, 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 23, 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 23, 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 23, 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 23, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1,954
- Known gaps
- 0
- arin-nrr-blueprint
- Earliest captured
- Oct 9, 2002
- Latest captured
- Oct 29, 2002
- Last refresh
- Oct 23, 2026
- Coverage
- Current
- Loading
- 0
- Known gaps
- 0
- arin-policy
- Earliest captured
- Oct 12, 1999
- Latest captured
- Mar 26, 2003
- Last refresh
- Oct 23, 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 23, 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 23, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 29
- Known gaps
- 1
- arin-v6wg
- Earliest captured
- Nov 8, 2000
- Latest captured
- Mar 1, 2005
- Last refresh
- Oct 23, 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 23, 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 23, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 135
- Known gaps
- 0
Coverage
Partial
Earliest captured: Jan 1, 1997
Latest captured: Oct 23, 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.
