[arin-ppml] Policy Proposal 107: Rework of IPv6 assignment criteria

[William Herrin]

On Sun, Jan 17, 2010 at 1:04 PM, David Farmer <farmer at umn.edu> wrote:
> I would like to find a replacement for HD-Ratios
> too.  But I haven't figured that out just yet

My observation here is that IPv6 addressing seems to be LAN-centric
rather than host-centric. That is, it's driven by the number of /64
LANs deployed rather than the number of individual computers.


>> 2. I'm concerned about assignments to non-connected networks where
>> qualification is based on the promise that they won't ever connect to
>> the Internet and therefore won't introduce a route into the IPv6
>> backbone. If the promise is meant to be kept, I don't think such
>> assignments should be made from address blocks within 2000::/3.
>> 2000::/3 is intended to be the block used on the public Internet.
>
> I understand the concern, I share it, I am open to suggestions.

Speaking off the cuff, I think I'd shape it like this:

1. Ask IANA for a /16 delegation of of the existing ULA space, e.g.
FC42::/16.Failing that, simply assert regiistration over a portion of
ULA space e.g. FD42::/16.

2. With a mostly automated web-based system, accept registration of
/48's within the space.

3. A registration account costs $10/year. No concept of organizations;
just accounts each billed seperately.

4. All /48's in the account must be contiguous to the maximum extent
possible. Each /48 registered costs an additional $1/year. In ULA
parlance, each /48 is "one Global ID."

5. Private registration available if desired at no cost. If private,
ARIN will publish a relay email address that can be used to contact
the registrant's real email address. They'll publish no other
information. After all, do we really need to know that the DOJ is
using a particular range of private IP addresses privately inside
their private system? I don't think we do.

6. RNDS delegation in the public DNS if desired. Let the registrants
decide for themselves if they want leaky name lookups to lead back
inside. Could be very helpful in a large private network where you
don't want every participant to have to plug lots of exceptions into
his DNS server.

7. Registration is non-binding. ARIN guarantees only that if both
networks participate in registration then they won't have conflicting
address use.


The $10 supports operating a heavily automated registry.
The $1 provides mild back-pressure against wasteful consumption of /48's.
The contiguity requirement mildly encourages smart aggregation practices.


Regards,
Bill Herrin


-- 
William D. Herrin ................ herrin at dirtside.com  bill at herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004