1 / 26

What An Application Wants Glenn Ricart June 5, 2014

What An Application Wants Glenn Ricart June 5, 2014. An Infrastructure That Meets Its Needs. An Infrastructure That Meets Its Needs. Affordable Price. Required / Desirable Properties. Network Properties An application might care about. Bandwidth Latency Jitter Reliability Packet loss

finna
Download Presentation

What An Application Wants Glenn Ricart June 5, 2014

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. What An Application Wants Glenn Ricart June 5, 2014

  2. An InfrastructureThat Meets Its Needs

  3. An InfrastructureThat Meets Its Needs Affordable Price Required / DesirableProperties

  4. Network PropertiesAn application might care about • Bandwidth • Latency • Jitter • Reliability • Packet loss • Standby / redundant diversity • Isolation • Performance • Security • In-net & edge processing / storage • Location mobility AverageMaximumMinimum Cumulative Relative priority for Stability of Price of

  5. Federation PropertiesAn application might care about • Lingua franca • Resource descriptions • Service descriptions • Orchestrations • Identity • Authorization • Platform capabilities • Isolation • Location mobility Capabilities Service levels Performance Security Monitoring Measurement Pricing

  6. ComplexitiesBoth requirements and providers can be • Time-varying • Differ by flow/stream within an application • Differ by user • Differ by circumstances (e.g. during a disaster) • Might need to be coordinated / orchestrated among applications • Determined by law or regulation

  7. Balance PointsMight be • Determined by regulators • Chosen by infrastructure providers • Be the result of priority assignment or traffic engineering • Chosen by applications from a fixed menu • Negotiated by agents for the application and infrastructure • Dynamically re-negotiated

  8. US Ignite Apps WantAt Low Cost • End-user Bandwidth (gigabit) • Highly-responsive apps (gigabit, latency, edge infrastructure (locavore infrastructure)) • Real-time high-quality video (gigabit, latency, jitter, packet loss) • Sensitive information apps (Isolation) • Mission-critical apps (reliability plus the above)

  9. Smart Things WantAt Low Cost • End-user Bandwidth (gigabit) • Highly-responsive apps (gigabit, latency, edge infrastructure (locavore infrastructure)) • Real-time high-quality video (gigabit, latency, jitter, packet loss) • Sensitive information apps (Isolation) • Mission-critical apps (reliability plus the above)

  10. CASA Radar

  11. Courtesy Mike Zink

  12. Courtesy Mike Zink

  13. Courtesy Mike Zink

  14. SDXes • Integral to inter-domain application infrastructure • Either • Do not impact a property when inserted • Are considered as part of the balance Transparent

  15. Don’t forget • Connecting heterogeneous networks (services) (those with different properties) may benefit from more than packet passing (e.g. transcoding or an application gateway).

  16. A Proposal for Proceeding • Do (just) enough to support / demonstrate a very small number of inter-domain applications • Above x3 or x5 • See some different design points • So we can see similarities and differences • Spiral with increased sophistication

  17. 1 Gbps Wired data caps 2 years Mobile data caps 10 weeks Commercially Available 1 week 16 hrs Netflix movie 100 min 10 min Online backup 1 min 10 Mbps Gigabit benefits Web page 5 sec Terra Incognita ½ sec 100 Gbps Locavore 50 ms KB MB PB TB GB

  18. Public-private partnership 501(c)(3)

  19. OUR GOALS 1 60 next-generation applications Infrastructure 2 200 community test beds Next-Gen Applications Economic Leadership Coordinate best practices 3

  20. Current Partners

  21. Today’s Infrastructure Home or Small Business 10 Mbps

  22. Locavore Infrastructure Home or Small Business Gig Definition of LOCAVORE   one who eats foods grown locally whenever possible (courtesy Miriam-Webster)

  23. Locavore Infrastructure Home or Small Business Gig Definition of LOCAVORE   one who eats foods grown locally whenever possible (courtesy Miriam-Webster)

  24. Typical App Characteristics • Real-time (apparentlly instantaneous) • Very low latency • Reliable (no hiccups) • Cyberphysical interactions • Big data to the end user / anchor institution • Visual data exploration (“fly-through”) • Collaborative (in the moment) • Distributed

More Related