1 / 9

Resource/traffic management architectures for NGI

Resource/traffic management architectures for NGI. Andrew Odlyzko Digital Technology Center University of Minnesota http://www.dtc.umn.edu/~odlyzko. Dumb, very fat pipes NGI is a mistake. Brief (and oversimplified) summary:. Pernicious dogma of streaming video:

rpaulette
Download Presentation

Resource/traffic management architectures for NGI

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. Resource/traffic management architectures for NGI Andrew Odlyzko Digital Technology Center University of Minnesota http://www.dtc.umn.edu/~odlyzko

  2. Dumb, very fat pipes NGI is a mistake Brief (and oversimplified) summary:

  3. Pernicious dogma of streaming video: Keynote speech by SIGCOMM 2004 lifetime contribution award winner Simon Lam, http://www.acm.org/sigs/sigcomm/talks/lam-sigcomm04.pdf Lam’s conclusions: 1. Overprovisioning not a solution 2. Flow-oriented service needed 3. More QoS research is needed 4. Widespread commercial deployment of QoS within 10 years

  4. fast file transfers incl. faster-than-real-time video file transfers Future of data networks:

  5. low transaction latency Driving force behind the deployment of data networks:

  6. Network Engineers (What’s this command do?) Power failures (What’s this switch do?) Cable cuts (Backhoes, enough said) Hardware failures (What’s that smell?) Congestion (More Bandwidth! Captain, I’m giving you all she’s got!) Attacks (malicious, you know who you are) Software bugs (Your call is very important to us....) Bandwidth was not a big problem even half a dozen years ago: Most common causes of performance problems as well as outages in networks today: In roughly the order Sean Donelan, NANOG list, July 2, 2001 Only problem no. 5 could be alleviated by QoS!

  7. Today, we start thinking about upgrading from GbE to 10GE when link load regularily exceeds 200-300 Mb/s (even when the average load over a week is much lower). —Simon Leinen of SWITCH, NANOG list, May 1, 2007 Bandwidth is even less of a problem now:

  8. Networks are likely to continue to be lightly utilized Big pipes, especially in the core Some simple QoS at edges (especially on wired-to-fiber connections) Only the lighest and least obtrusive resource management architecture are likely to be viable Heterogeneous system, including user-controlled lightpaths, isolated networks, …, all talking IP Conclusions:

  9. Further data, discussions, and speculations in papers and presentation decks at: http://www.dtc.umn.edu/~odlyzko

More Related