Hi Ross, |> We already know that we're growing the table faster than technology |> can keep up. That much is clear. (Tony Li) | |First the question: What do you mean by "we're growing the table faster |than technology can keep up". Are you referring to Forwarding Table |size, BGP processing and traffic loads, or something else?
I'm referring to the growth rate of the full set of prefixes and the capabilities of the control plane to support it. Note that I've been saying this pretty consistently for two full years now. |Do you mean |"with a table of 100,000,000 entries, there will need to be at |a minimum |some incremental update to existing deployed implementations" (to which |my teenage daughter might say "duh!"), or do you mean "it won't be |economically reasonable to build products unless we make some localized |internal (within a router) change to a few algorithms?", or do you mean |"it will be financially too expensive to build products that can handle |some future table size", or do you mean "it will not be technically |possible to build the routers", or do you mean something else? Once again, with feeling: The growth rate of prefixes that are circulating within the DFZ exceeds the rate of speed improvement in the underlying DRAM that we use to implement the control plane. This will undoubtedly result in architectural changes and cost increases. The concern then becomes that over the long term, as this continues, the cost increases must be absorbed somewhere in the system, and it is most likely to propagate to the end users, with a net detriment to the growth of the network. |Secondly, depending upon precisely what you mean by "faster than the |technology can keep up", speaking as an individual, it is quite likely |that I disagree. I hope that any disagreement is not automatically |declared to be off-topic. You're more than welcome to disagree. However, I hope that we can have a more constructive discussion that simply reiterating the size of our personal FIB. Tony _______________________________________________ rrg mailing list [email protected] https://www.irtf.org/mailman/listinfo/rrg
