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 ]
Florian Weimer
fweimer at bfk.de
Tue May 3 12:55:35 CEST 2011
* Mikael Abrahamsson: > On Tue, 3 May 2011, Florian Weimer wrote: > >> * Mikael Abrahamsson: >> >>> 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. >> >> And why wouldn't the Internet work with 600,000 prefixes in the DFZ? > > Now all of a sudden for instance Cisco 7600 3CXL isn't enough to old a > full table (at around 750k). 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. > Also, IPv6 uses twice the TCAM resources as IPv4... This is an implementation detail of one particular vendor. 8-) -- Florian Weimer <fweimer at bfk.de> BFK edv-consulting GmbH http://www.bfk.de/ Kriegsstraße 100 tel: +49-721-96201-1 D-76133 Karlsruhe fax: +49-721-96201-99
- 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 ]