[address-policy-wg] getting second IPv6 PA as a LIR

On 05/03/2011 08:50 AM, Mikael Abrahamsson wrote:
> Oki, I don't know enough about the ripe billing system , but I do know
> that if we get many more hundreds of thousands of PI assignments
> (regardless of v4 or v6), the global routing system is going to be in
> real trouble.

You'll not solve this problem by any RIPE policy. Deaggregation of
assigned address space is here in both IPv4 and IPv6. >40% of announced
IPv4 prefixes into global table are unnecessary and this is NOT problem
of PI address existence, it's human problem - people are deaggregating
their address space. Almost the same thing starts to be happening in
IPv6 table.

And comercial ISPs simply will NOT filter these deaggregated blocks,
because of money - there're only few operators, where clean network
setup is necessary - but majority just accepts and announces to the
world anything from the customer, because customer is paying money for
that. Almost nobody realy cares about PI/PA separation or aggregation,
address is just a number from the router point of view. CIDR reports are
good proof of this - that's the reality of internet routing.

If there will not be regular PI from RIPE (or very limited by the
policy), market just finds another "solution" of the problem. And the
easy solution is - yes, yes... deaggregation of assigned /32. Some LIRs
started carving their /32 IPv6 PA already. I don't think, that blocking
IPv6 PI assigments will reduce table growth or bring more members/LIRs.

2007-01 is just cleanup of historic mess. If we'll apply this to IPv6 PI
assigments, I don't see reason for blocking IPv6 PI assigments using
similar rules, as we have in IPv4 already. Policies for IPv6 should not
bring more limitations for assigment compared to IPv4 policies - this
will simply slow down IPv6 deployment in networks, where IPv4 PI is used
these days. And I'm not supporting any policy, what will slow down IPv6
deployment in real words.

And yes, I understand troubles mentioned, I'm aware about hardware
limitations of many routing platforms used worldwide. But as I mentioned
already, I don't think, that problem of growing global table can be
solved just by reducing PI assigments, this is minor part of whole issue...

With regards,
Daniel