[address-policy-wg] Source of routing table growth

Hi,


> Hello,
> 
> Yes, IPv4 only is a problem ;-))
> 
> Please, do not create more problem now! The limits of the content addressable memory on line card are problematic!
> 
> Unfortunately the IPv4 address space trading will increase the memory size needed for IPv4 already. 
> 
> If you introduce IPv6 PI address space, who could stop to explode this space in the near future?

i'm officially out of arguments now.

We already have IPv6 PI, that's not gonna change.
We're only about to level the IPv4 and IPv6 PI policies.

You can either have people stay with IPv4 for a longer period as necessary, creating a faster and faster
IPv4 table growth because they stick with this old legacy protocol, buying (and announcing) smaller and smaller 
IPv4 prefixes because they cannot migrate to IPv6 due to the policies being different,
or you can allow the same rules for both worlds, give everyone their (most likely only ever) IPv6 prefix and have the v4 table
stop growing earlier because people migrate faster.

I think it's clear what we should chose.

-- 
Mit freundlichen Grüßen / Kind Regards

Sascha Lenz [SLZ-RIPE]
Senior System- & Network Architect