Skip to main content

ARIN · RIR Watchdog

2007-21: PIv6 for legacy holders with RSA and efficient use

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-2007-21
RIR
ARIN
Official status
Adopted
Normalized status
Accepted
Introduced
Aug 28, 2007
Last source update
Oct 14, 2026
Coverage
Partial

Who actually shaped the debate?

3Total participants
2Discussion contributors
1Formal actors
2Discussion messages
2Effective participants
100%Top-five discussion share
1People covering 50%
2People covering 80%

BTW Analysis

BTW Analysis

What changed

ARIN's archived 14 April 2008 text broadens the criteria for direct IPv6 assignments to end-user organizations. An organization must not be an IPv6 LIR and must either qualify under the IPv4 policy then in effect or demonstrate efficient use of all its direct IPv4 assignments and allocations, each covered by a current ARIN RSA. The second route addresses legacy holders with small multihomed IPv4 blocks that could otherwise fail the size-based qualification path. It makes access to IPv6 a reason to formalize existing resource holdings and demonstrate utilization; it is not a requirement that every legacy holder seek IPv6 or sign an agreement.

What the debate was really about

The two retained contributions expose a tension between removing an obstacle to IPv6 deployment and using that opportunity to bring legacy IPv4 holdings under contractual and utilization requirements. Bill Herrin explains why multihomed /23 and /24 holders need provider-independent IPv6 access, while asking how staff would handle inefficiently used holdings. Marla Azinger explicitly remains undecided: she wants IPv6 adoption and the return of unused legacy space, and sees those aims pulling in different directions. Her interpretation of the existing RSA is her stated reasoning, not an independently established legal conclusion.

Arguments that prevailed

  • The final archived text retains a route for efficiently used IPv4 holdings covered by current ARIN RSAs, alongside the existing IPv4-qualification route. This is consistent with broadening IPv6 eligibility while preserving contractual and utilization conditions. The record does not show that either retained contributor caused that outcome.

Decision vs debate

The official archive labels the proposal adopted and lists implementation on 5 August 2008. Its retained proposal text is dated 14 April 2008, after the two August 2007 contributions assessed here. The archive also lists successive last calls, a remand and a revision. These establish a reported outcome and procedural sequence, but the associated meeting decisions and intervening draft texts have not been reviewed here. The two early messages cannot establish which argument determined the final wording or the exact adoption date.

Participation concentration

The assessed discussion contains two messages from two contributors on two dates, plus one separately recorded formal actor. Each contributor supplies half of the observed messages, so the effective participant count is two. That equal split describes this small retained sample; it is not evidence of broad community participation, balanced influence or full debate coverage. Neither contributor has a second assessed message on this proposal from which to infer persuasion or a change of position.

Chokepoint analysis

The eligibility test places practical control at the point where ARIN evaluates utilization and the applicable registration agreement. The policy offers IPv6 access while tying the additional qualification route to conditions on existing IPv4 holdings. Herrin's questions about returning space versus renumbering show why implementation procedure matters: those choices can change the cost of satisfying the policy even when the written criteria stay the same. The archive identifies Advisory Council and Board stages, but this evidence does not establish how particular actors exercised influence within them.

Uncertainties

  • Only two discussion messages are assessed here; the complete mailing-list and meeting debate remains unreconciled.
  • The April 2008 text is available, but earlier draft versions and the underlying decisions behind the listed procedural milestones have not been compared.
  • The source reports adoption and an implementation date; the structured record does not establish a separate exact adoption date.
  • The operational treatment of inefficiently used holdings cannot be determined from Herrin's questions or the policy text alone.
  • Marla's undecided position must not be converted into support or opposition, and the draft and numbered proposal links must not be counted as independent statements.

Policy evolution

01265066f52f09314a06d1470054122d70a22a290544123aa2e6c17100fb94c1
Accepted · Adopted
Apr 14, 2008
Source facts ↗

Debate timeline

  1. Introduced

    Introduced

    Source facts ↗
  2. Official version

    Accepted

    Accepted · Adopted

    Source facts ↗

Entities

Freshness: Stale
  1. Discussion messages1
    First activityAug 31, 2007
    Last activityAug 31, 2007
    First explicit stanceSupport
    Latest explicit stanceSupport
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies0
    Freshness: Stale

    Last research attempt: Sep 26, 2026

    Identity verified: Sep 26, 2026

    Dirtside Systems LLC · Current
    Dirtside Systems LLC (Seattle, WA) Owner, April 2022 - present
    bill.herrin.us

    Verified public profiles

    Discussion messages
    1
    First activity
    Aug 31, 2007
    Last activity
    Aug 31, 2007
    First explicit stance
    Support
    Latest explicit stance
    Support
    Stance changes
    0
    Viewpoint consistency
    Insufficient evidence to assess consistency
    Other policies
    0

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

    Viewpoint consistency: Insufficient evidence to assess consistency

    In the supplied August 2007 discussion, Bill Herrin supports extending independent IPv6 addressing to smaller multihomed legacy holders. He treats signing an RSA as a condition of that additional access and asks how efficient-use requirements would operate. This establishes a qualified position on 2007-21, not a record of continuity or reversal over time.

    2007-21: PIv6 for legacy holders with RSA and efficient use

    Assessment: Insufficient evidence to assess consistency · Herrin's support for wider IPv6 access is compatible with his implementation questions. He presents the RSA as optional for holders who do not seek the new benefit, and asks what happens when existing holdings fail an efficiency requirement. Those questions do not retract his support; the supplied record contains no separate later position to compare.

    Conditions: The position concerns the additional eligibility offered by 2007-21, not compulsory conversion of every legacy holding. · Returning or renumbering space is raised as a question for staff, not reported as an adopted procedure.

    Obviously this discourages their deployment of IPv6.

    you don't have to sign.

    Does the holder return sufficient space to become efficient?

    1. Aug 31, 2007 · Support

      [ppml] Policy Proposal 2007-21: PIv6 for legacy holders with RSA

      The proposal is an attempt to make IPv6 provider-independent addresses … available to multihomed folks with only /23's and /24's. … Currently IPv6 PI space is only available to folks who qualify for an … IPv4 /22 or larger regardless of whether they're multihomed. This … means that there are existing multihomed IPv4 organizations who … aren't able to multihome with IPv6 because they can't get PI space. … Obviously this discourages their deployment of IPv6. More than a few … content providers fall into this category as well as a number of … hobbyist networks held by senior network administration staff. As a … result, it creates a drag on IPv6 deployment overall. IPv6 deployment … is moving slowly enough as it is; drag-effects due to ARIN policy are … Signing the RSA for your /23 or /24 is merely the entry fee to gain … this new privilege. If you don't want or need the new privilege then … you don't have to sign. … Given the structure of filtering in the DFZ, nothing longer than a /24 … prefix is usable for multihomed organizations. I'm pretty sure that … means any utilization of a /24 for a *multihomed* user is "efficient." … procedures for dealing with a situation where a holder's use is not … efficient. Does the holder return sufficient space to become … efficient? Does he renumber into new smaller space selected from

      Source facts ↗

    Total policy messages: 1

  2. Discussion messages1
    First activityAug 22, 2007
    Last activityAug 22, 2007
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies7
  3. Scott Leibrand · Identity unresolved
    Discussion messages0
    First activityUnknown
    Last activityUnknown
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies0

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,292
    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,180
    Known gaps
    1
  • 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,434
    Known gaps
    4
  • 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 14, 2026
    Last refresh
    Oct 15, 2026
    Coverage
    Source coverage is incomplete.
    Loading
    6,707
    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,444
    Known gaps
    0
  • arin-arin-regrws
    Earliest captured
    Unknown
    Latest captured
    Unknown
    Last refresh
    Oct 15, 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 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,051
    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,882
    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 15, 2026

Freshness

Freshness: Stale · Last refresh:

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.