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/[email protected]/
[address-policy-wg] 2009-04 New Policy Proposal (IPv4 Allocation and Assignments to Facilitate IPv6 Deployment)
- Previous message (by thread): [address-policy-wg] 2009-04 New Policy Proposal (IPv4 Allocation and Assignments to Facilitate IPv6 Deployment)
- Next message (by thread): [address-policy-wg] 2009-04 New Policy Proposal (IPv4 Allocation and Assignments to Facilitate IPv6 Deployment)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Max Tulyev
president at ukraine.su
Tue Apr 7 15:39:33 CEST 2009
I hear from Juniper they was capable of 5M routes an year ago. I think, 2020 year hardware should be capable about 500M prefixes easy. Mikael Abrahamsson wrote: > On Tue, 7 Apr 2009, Max Tulyev wrote: > >> Seriously, in that time hardware will become capable of carrying that >> easy. > > What timeframe is that? > > 10 years ago, the state of the art core routing platforms were capable > of a few hundreds of thousands of FIB routes, today it seems to be 1-2M > for the more expensive platforms. If you're talking about 2020 then by > then 3-4M might be working well, but you'd still spend a lot more than > than needed in converging a network with that many prefixes. > > For the good of the Internet, let's not put more prefixes in DFZ than > needed. > -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253 at FIDO)
- Previous message (by thread): [address-policy-wg] 2009-04 New Policy Proposal (IPv4 Allocation and Assignments to Facilitate IPv6 Deployment)
- Next message (by thread): [address-policy-wg] 2009-04 New Policy Proposal (IPv4 Allocation and Assignments to Facilitate IPv6 Deployment)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]