1 / 13

Hardware implications of Internet routing table growth

Hardware implications of Internet routing table growth. Tony Li. Questions. Can hardware keep up with the growth of the routing table? If so, how much safety margin do we have? How else might things break?. Current trends. Recent trends show high growth

claybraswell
Download Presentation

Hardware implications of Internet routing table growth

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Hardware implications of Internet routing table growth Tony Li

  2. Questions • Can hardware keep up with the growth of the routing table? • If so, how much safety margin do we have? • How else might things break?

  3. Current trends • Recent trends show high growth • Isolate this growth as a predictor of future growth • Compare growth to Moore’s law

  4. Moore’s law Well known metric of hardware technological growth Hardware doubles every 18 months Includes clock rates, memory sizes Growth exceeding Moore’s law implies costs grow rapidly • Good news: current growth under Moore’s law

  5. Safety Margin? Current growth rate is about half of Moore’s law However: • Growth rate is ACCELERATING! • Hyperexponential growth • Will eventually outgrow Moore’s law • Moore’s law may fail

  6. Recommendations • Vendors • Continue to track Moore’s law • Forwarding table • Route processor DRAM • Route processor performance

  7. Recommendations • ISPs • Global prefix conservation • Aggregation • Limit policy exceptions • Track hardware upgrades • Deploy route reflectors • Upgrade processors before increasing exit points

  8. Recommendations • Community • New routing architecture • Multihoming must not require global prefixes • Example: IPv6 plus EIDs • Start NOW!

  9. Conclusions • Hyperexponential growth will exceed Moore’s law • Safety margins are at risk • Community needs to exercise TLC • We need concerted effort on a new routing architecture

More Related