This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/address-policy-wg@ripe.net/
[address-policy-wg] getting second IPv6 PA as a LIR
- Previous message (by thread): [address-policy-wg] getting second IPv6 PA as a LIR
- Next message (by thread): [address-policy-wg] getting second IPv6 PA as a LIR
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mikael Abrahamsson
swmike at swm.pp.se
Tue May 3 13:01:37 CEST 2011
On Tue, 3 May 2011, Florian Weimer wrote: > But this happens every couple of years. The global table has outgrown > the capacity of the PFC3C, and before that, of the PFC2. So despite > seemingly unescapable hardware limitations, a gradual growth of the > prefix count is not much of a problem in itself for the network as a > whole. This is definitely solvable, it just costs money. Money it seems the "polluter" doesn't pay. Sure, one can see it as "cost of doing business" to be an ISP, but it's also easy to see that a prefix in the DFZ most likely costs more than 50EUR per year in equipment having to be paid by SOMEONE. There is no free lunch. -- Mikael Abrahamsson email: swmike at swm.pp.se
- Previous message (by thread): [address-policy-wg] getting second IPv6 PA as a LIR
- Next message (by thread): [address-policy-wg] getting second IPv6 PA as a LIR
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]