ARIN · RIR Watchdog
ARIN-prop-36: Removal of IPv6 Operational Information from NRPM
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-36
- RIR
- ARIN
- Official status
- Unknown
- Normalized status
- Unknown
- Introduced
- Feb 10, 2007
- Last source update
- Oct 15, 2026
- Coverage
- Partial
Who actually shaped the debate?
Policy evolution
Debate timeline
Entities
- Discussion messages1First activityFeb 22, 2007Last activityFeb 22, 2007First explicit stanceUnknownLatest explicit stanceUnknownStance changes0Viewpoint consistencyInsufficient evidence to assess consistencyOther policies7Freshness: Stale
Last research attempt: Sep 28, 2026
Identity verified: Oct 13, 2026
Electric Lightwave · Historical IP Address Engineer, Electric IP Address Engineer, Electric LightwaveLightwave, 2002 , 2002 –– 20062006
www.arin.netFrontier Communications & Citizens · Historical IP Address Engineer, Frontier Communications & Citizens, 2003
www.arin.netARIN Advisory Council · Historical Chair, 2007Chair, 2007
www.arin.netARIN Advisory Council · Historical Member, 2005 Member, 2005 –– 20072007
www.arin.netFrontier Communications · Historical Frontier AS5650 Peering Coordinator, 2007
www.arin.netIETF Routing and Addressing Directorate · Historical IETF Routing and Addressing Directorate, Member 2007
www.arin.netVerified public profiles
- Discussion messages
- 1
- First activity
- Feb 22, 2007
- Last activity
- Feb 22, 2007
- First explicit stance
- Unknown
- Latest explicit stance
- Unknown
- Stance changes
- 0
- Viewpoint consistency
- Insufficient evidence to assess consistency
- Other policies
- 7
First explicit stance: Unknown → Latest explicit stance: Unknown · Stance changes: 0
Viewpoint consistency: Insufficient evidence to assess consistency
Eight reviewed dated contributions cover four proposal subjects. Marla consistently describes 2004-3 as clarification of existing practice and separately accepts that policy can change. In August 2007 she explicitly remains undecided on both the longer additional-request timeframe and the legacy-holder IPv6 proposal, balancing distinct concerns. Those undecided positions do not establish a reversal, and the draft and numbered entries repeat the same messages rather than adding independent evidence. The limited record does not support a complete longitudinal judgement.
2004-3: Global Addresses for Private Network Inter-Connectivity
Assessment: Consistent · Marla's April 2004 and April 2005 explanations consistently present 2004-3 as clearer wording for a use already permitted. The initial request for both pro and con comments is meeting preparation, not a contrary stance.
Conditions: Her description of historical practice is attributed to her; it does not independently prove every past application decision.
it just seems it needs to be re-textualized in a very point blank manner.
This policy is simply striving to achieve clarification.
Its not a change. Its a clarification.
2005-1: Provider Independent IPv6 Assignments for End-sites
Assessment: Insufficient evidence to assess consistency · One contribution regards 2005-1 as a solution to several issues and argues that policy can change when there is reason and support. It does not establish how her position evolved.
Conditions: A suggestion that policy motivate technical improvement is not evidence that such improvement occurred.
I see 2005-1 as one solution for a couple different "issues".
Policy is not set in stone and can always be changed if given reason and support to do so.
2004-3: Global Addresses for Private Network Inter-Connectivity · 2005-1: Provider Independent IPv6 Assignments for End-sites
Assessment: Consistent · Calling 2004-3 a clarification of existing practice is compatible with accepting that 2005-1 or another policy may later change. The first describes the claimed effect of a particular text; the second concerns the ability to revise policies with reasons and support.
Conditions: The proposals and claims have different subjects, so their wording cannot be used to manufacture a reversal.
Its not a change. Its a clarification.
Policy is not set in stone and can always be changed if given reason and support to do so.
2007-22: Expand timeframe of Additional Requests
Assessment: Insufficient evidence to assess consistency · Marla explicitly remains undecided on extending the timeframe for additional requests. She summarizes arguments about aggregation, equal treatment, staff scrutiny and hoarding without adopting either side. A single dated undecided contribution cannot establish stability or reversal.
Conditions: The draft and numbered proposal entries refer to the same message; they are not independent positions. · The surrounding original proposal explains the subject but is not her authored endorsement.
Not sure if I am for or against this one.
Below is are the pro's and con's I pulled from ppml and I can understand.
Thus...leading to my indecision at this point.
ARIN-prop-55: Expand timeframe of Additional Requests
Assessment: Insufficient evidence to assess consistency · Marla explicitly remains undecided on extending the timeframe for additional requests. She summarizes arguments about aggregation, equal treatment, staff scrutiny and hoarding without adopting either side. A single dated undecided contribution cannot establish stability or reversal.
Conditions: The draft and numbered proposal entries refer to the same message; they are not independent positions. · The surrounding original proposal explains the subject but is not her authored endorsement.
Not sure if I am for or against this one.
Below is are the pro's and con's I pulled from ppml and I can understand.
Thus...leading to my indecision at this point.
2007-21: PIv6 for legacy holders with RSA and efficient use
Assessment: Insufficient evidence to assess consistency · Marla explicitly remains undecided between encouraging IPv6 adoption and obtaining the return of unused legacy IPv4 blocks. Her reading of the current RSA explains the tension she sees; it is not an unqualified vote for the proposal or proof that her view later changed.
Conditions: This is one contribution represented under both draft and numbered entries. · Her reading of the RSA is attributed to her and is not treated as an independently established legal conclusion.
Undecided on this one.
We need anyone that is willing to go to Ipv6 space. But we also need Legacy blocks to be handed back in that arent being used. I feel stuck in the middle.
ARIN-prop-54: PIv6 for legacy holders with RSA and efficient use
Assessment: Insufficient evidence to assess consistency · Marla explicitly remains undecided between encouraging IPv6 adoption and obtaining the return of unused legacy IPv4 blocks. Her reading of the current RSA explains the tension she sees; it is not an unqualified vote for the proposal or proof that her view later changed.
Conditions: This is one contribution represented under both draft and numbered entries. · Her reading of the RSA is attributed to her and is not treated as an independently established legal conclusion.
Undecided on this one.
We need anyone that is willing to go to Ipv6 space. But we also need Legacy blocks to be handed back in that arent being used. I feel stuck in the middle.
2005-1: Provider Independent IPv6 Assignments for End-sites · 2007-21: PIv6 for legacy holders with RSA and efficient use
Assessment: Insufficient evidence to assess consistency · Seeing provider-independent IPv6 policy as useful in 2006 is compatible with being undecided in 2007 about the conditions for legacy holders. The later message still values IPv6 adoption while weighing reclamation and contractual requirements. It does not establish withdrawal of the earlier position, but it also does not provide a settled view on the later proposal.
Conditions: Different eligibility conditions must not be collapsed into a single yes-or-no position on IPv6. · A single contribution on each proposal leaves the longer-term comparison limited.
I see 2005-1 as one solution for a couple different "issues".
We need anyone that is willing to go to Ipv6 space.
I feel stuck in the middle.
- Feb 22, 2007 · Unknown
[ppml] Policy Proposal: Removal of Ipv6 Operational Informationfrom NRPM
Validated evidence is unavailable.
Source facts ↗
Per-policy stance timelines:ARIN-2004-3 · Support · ConsistentARIN-2005-1 · Support · Insufficient evidence to assess consistencyARIN-2005-6 · Unknown · No explicit position statedARIN-2007-21 · Unknown · Insufficient evidence to assess consistencyARIN-2007-22 · Unknown · Insufficient evidence to assess consistencyARIN-prop-36 · Unknown · No explicit position statedARIN-prop-54 · Unknown · Insufficient evidence to assess consistencyARIN-prop-55 · Unknown · Insufficient evidence to assess consistencyTotal policy messages: 13
Sources and coverage
Official policy sources
Public discussion archives
- arin-ppml
- Earliest captured
- Sep 1, 1999
- Latest captured
- Oct 8, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 31,069
- Known gaps
- 0
- www.arin.net
- arin-arin-announce
- Earliest captured
- Aug 4, 2026
- Latest captured
- Oct 7, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 3,165
- Known gaps
- 11
- 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,385
- Known gaps
- 26
- arin-arin-discuss
- Earliest captured
- Aug 2, 1999
- Latest captured
- Aug 21, 2007
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 716
- Known gaps
- 0
- arin-arin-issued
- Earliest captured
- Aug 2, 2026
- Latest captured
- Oct 15, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 6,777
- Known gaps
- 0
- arin-arin-ppml
- Earliest captured
- Aug 2, 2026
- Latest captured
- Oct 13, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 5,403
- Known gaps
- 0
- arin-arin-regrws
- Earliest captured
- Unknown
- Latest captured
- Unknown
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1
- Known gaps
- 0
- arin-arin-rpki-pilot
- Earliest captured
- Jul 7, 2009
- Latest captured
- Jul 7, 2009
- Last refresh
- Oct 15, 2026
- Coverage
- Current
- Loading
- 0
- Known gaps
- 0
- arin-arin-suggestions
- Earliest captured
- Aug 26, 2026
- Latest captured
- Oct 14, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1,056
- Known gaps
- 0
- arin-arin-tech-discuss
- Earliest captured
- Aug 13, 2026
- Latest captured
- Oct 5, 2026
- Last refresh
- Oct 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 1,855
- Known gaps
- 0
- arin-arin-whoisrws
- Earliest captured
- Oct 9, 2009
- Latest captured
- Sep 6, 2010
- Last refresh
- Oct 15, 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 15, 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 15, 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 15, 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 15, 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 15, 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 15, 2026
- Coverage
- Current
- Loading
- 0
- Known gaps
- 0
- arin-policy
- Earliest captured
- Oct 12, 1999
- Latest captured
- Mar 26, 2003
- Last refresh
- Oct 15, 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 15, 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 14, 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 15, 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 15, 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 15, 2026
- Coverage
- Source coverage is incomplete.
- Loading
- 129
- Known gaps
- 0
Coverage
Partial
Earliest captured: Jan 1, 1997
Latest captured: Oct 16, 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.
