[arin-ppml] [arin-announce] Policy Proposal: Open Access To IPv6

Matthew Kaufman matthew at matthew.at
Fri May 29 19:39:02 EDT 2009


Ted Mittelstaedt wrote:
>
> By contrast, the problem of table bloat in routers is very real.  
Absolutely, but should not be ARIN's problem. ARIN should make it 
possible for organizations (be they ISPs or not) to obtain unique 
allocations from ARIN's portion of the IPv6 address space. It should be 
easy to get allocations which are aggregated in such a way that they are 
less expensive to route, but that shouldn't drive policy.
> You
> are essentially asking thousands of orgs out there to put money into
> tens of thousands of routers out there to replace them with new gear
> that will hold and manage a fantastically gigantic IPv6 table,
No. We are asking ARIN to fairly allocate reasonably-sized parts of IPv6 
to entities that ask, in return for no more than reasonable compensation.
> just to
> make it a slight bit easier for small orgs to advertise a /32, who
> have absolutely no use for a /32 and would be happy with a /48, and
> who are getting the /32 because they are still scared to death about the
> old renumbering bugaboo - which doesn't even exist with IPv6 anyway.
That is between an org that wishes to *advertise their address space to 
the global Internet routing infrastructure* and the transit provider who 
is doing that for them (and entering into peering and/or transit 
relationships with other providers in order to make that work)

There's even better solutions to routing table bloat if you want ARIN to 
be even more heavy-handed. For instance, ARIN could hold a lottery to 
determine the one and only provider who is allowed to get address space 
within the ARIN region and then everyone else would need to be customers 
of the winner. Then the inter-provider table would be tiny.

Matthew Kaufman




More information about the ARIN-PPML mailing list