BTW.Media
Daily editionStrategic Internet Intelligence
Sign InRegister

ARIN · RIR Watchdog

2006-2: Micro-allocations for Internal Infrastructure

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-2006-2
RIR
ARIN
Official status
Adopted
Normalized status
Accepted
Introduced
Feb 17, 2006
Last source update
Oct 14, 2026
Coverage
Partial

Who actually shaped the debate?

12Total participants
12Discussion contributors
UnknownFormal actors
16Discussion messages
10.7Effective participants
56.3%Top-five discussion share
4People covering 50%
9People covering 80%

Policy evolution

c2e3d6d9844e2ff705acb502fa36ca714f230861c34876c5fb96405e0743ef72
Accepted · Adopted
Unknown
Source facts ↗

Debate timeline

  1. Official version

    Accepted

    Accepted · Adopted

    Source facts ↗

  2. Introduced

    Introduced

    Source facts ↗

  3. Public discussion

    [ppml] Policy Proposal 2006-2: Micro-allocations for Internal Infrastructure - to be revised

    4 Discussion messages · 4 Entities

    Source facts ↗

  4. Public discussion

    [ppml] Resurrecting ULA Central [was: Re: Policy Proposal 2006-2: Micro-allocations for Internal Infrastructure - to be revised ]

    3 Discussion messages · 2 Entities

    Source facts ↗

  5. Public discussion

    [ppml] Resurrecting ULA Central [was: Re: Policy Proposal 2006-2: Micro-allocations for Internal Infrastructure - to be revised ]

    2 Discussion messages · 2 Entities

    Source facts ↗

  6. Public discussion

    [ppml] Resurrecting ULA Central [was: Re: Policy Proposal 2006-2: Micro-allocations for Internal

    2 Discussion messages · 2 Entities

    Source facts ↗

Entities

Freshness: Stale · Last refresh: · The latest refresh failed. The last successful result is shown.
  1. Thomas Narten
    Discussion messages2
    First activityApr 27, 2006
    Last activityApr 27, 2006
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyConsistent
    Other policies0
    Freshness: Stale

    Last research attempt: Sep 26, 2026

    Identity verified: Sep 26, 2026

    IETF · Historical
    From 1997 to 2005, he was an IETF Area Director for the Internet area.
    www.icann.org

    Verified public profiles

    Discussion messages
    2
    First activity
    Apr 27, 2006
    Last activity
    Apr 27, 2006
    First explicit stance
    Unknown
    Latest explicit stance
    Unknown
    Stance changes
    0
    Viewpoint consistency
    Consistent
    Other policies
    0

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

    Viewpoint consistency: Consistent

    Narten distinguishes possible contractual leverage over publicly routed addresses from the different needs of non-public ULA space, then asks what contractual and reclamation conditions actually apply to ASNs. Those questions are compatible with the earlier distinction. Neither retained message is an overall vote for or against the micro-allocation proposal.

    2006-2: Micro-allocations for Internal Infrastructure

    Assessment: Consistent · The earlier message explains a possible reason for leasing public addresses while questioning whether the same leverage is appropriate for ULA space. The later message tests the ASN analogy by asking whether a contract exists and when return can be required. Seeking those facts does not contradict the earlier conditional argument.

    Conditions: The messages discuss different resources and explicitly leave the strength and appropriateness of leverage open. · Questions about ASN contracts do not establish their legal terms, and this review makes no legal determination.

    Having said that, ULA space is different, precisely because it is not intended to be routed publically, so IMO it's much less clear that the same amount of leverage is needed/appropriate.

    Under what conditions can an AS number holder be forced to return an AS number?

    Do those that obtain ASNs enter into a formal agreement/contract with ARIN prior to obaining an ASN?

    1. Apr 27, 2006 · Procedural or neutral

      [ppml] Resurrecting ULA Central [was: Re: Policy Proposal 2006-2: Micro-allocations for Internal

      For public addresses that will be routed on the public internet, having them be "leased" rather than "owned" provides some amount of leverage … Having said that, ULA space is different, precisely because it is not intended to be routed publically, so IMO it's much less clear that the same amount of leverage is needed/appropriate.

      Source facts ↗
    2. Apr 27, 2006 · Question or clarify

      [ppml] Resurrecting ULA Central [was: Re: Policy Proposal 2006-2: Micro-allocations for Internal Infrastructure - to be revised ]

      Is this true? In what sense is an AS number "leased" or "loaned"? Under what conditions can an AS number holder be forced to return an AS number?

      Source facts ↗
    Per-policy stance timelines:ARIN-2006-2 · Unknown · Consistent

    Total policy messages: 2

  2. Jason Schiller
    Discussion messages2
    First activityApr 21, 2006
    Last activityApr 24, 2006
    First explicit stancePropose alternative
    Latest explicit stancePropose alternative
    Stance changes0
    Viewpoint consistencyNo validated consistency assessment
    Other policies1
  3. George Kuzmowycz · Identity unresolved
    Discussion messages2
    First activityApr 25, 2006
    Last activityApr 27, 2006
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies1
  4. Randy Bush
    Discussion messages2
    First activityApr 21, 2006
    Last activityApr 21, 2006
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyConsistent
    Other policies4
  5. Peter Sherbin
    Discussion messages1
    First activityApr 26, 2006
    Last activityApr 26, 2006
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies1
  6. Michel Py · Identity unresolved
    Discussion messages1
    First activityApr 24, 2006
    Last activityApr 24, 2006
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies3
  7. Kevin Loch
    Discussion messages1
    First activityApr 20, 2006
    Last activityApr 20, 2006
    First explicit stancePropose alternative
    Latest explicit stancePropose alternative
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies4
  8. Matthew Petach
    Discussion messages1
    First activityApr 22, 2006
    Last activityApr 22, 2006
    First explicit stanceSupport with changes
    Latest explicit stanceSupport with changes
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies1
  9. Unknown · Identity unresolved
    Discussion messages1
    First activityApr 25, 2006
    Last activityApr 25, 2006
    First explicit stancePropose alternative
    Latest explicit stancePropose alternative
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies0
  10. Stacy Taylor · Identity unresolved
    Discussion messages1
    First activityApr 20, 2006
    Last activityApr 20, 2006
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies0
  11. Greg Stilwell · Identity unresolved
    Discussion messages1
    First activityApr 21, 2006
    Last activityApr 21, 2006
    First explicit stancePropose alternative
    Latest explicit stancePropose alternative
    Stance changes0
    Viewpoint consistencyInsufficient evidence to assess consistency
    Other policies0
  12. Member Services · Public profile research pending
    Discussion messages1
    First activityOct 4, 2006
    Last activityOct 4, 2006
    First explicit stanceUnknown
    Latest explicit stanceUnknown
    Stance changes0
    Viewpoint consistencyNo explicit position stated
    Other policies3

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,289
    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,170
    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,444
    Known gaps
    3
  • 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,673
    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,420
    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,054
    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,885
    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 14, 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 14, 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 14, 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 14, 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 14, 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 14, 2026
    Coverage
    Current
    Loading
    0
    Known gaps
    0
  • arin-policy
    Earliest captured
    Oct 12, 1999
    Latest captured
    Mar 26, 2003
    Last refresh
    Oct 14, 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 14, 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 14, 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 14, 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 14, 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: · 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.