260 likes | 356 Views
This document explores the infrastructure requirements for various applications such as bandwidth, latency, security, and more. It discusses the balance points, capabilities, and needs of smart devices and US Ignite apps. Additionally, it delves into the concept of Locavore Infrastructure and the future goals for infrastructure development.
E N D
What An Application Wants Glenn Ricart June 5, 2014
An InfrastructureThat Meets Its Needs Affordable Price Required / DesirableProperties
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
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
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
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
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)
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)
SDXes • Integral to inter-domain application infrastructure • Either • Do not impact a property when inserted • Are considered as part of the balance Transparent
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).
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
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
Public-private partnership 501(c)(3)
OUR GOALS 1 60 next-generation applications Infrastructure 2 200 community test beds Next-Gen Applications Economic Leadership Coordinate best practices 3
Today’s Infrastructure Home or Small Business 10 Mbps
Locavore Infrastructure Home or Small Business Gig Definition of LOCAVORE one who eats foods grown locally whenever possible (courtesy Miriam-Webster)
Locavore Infrastructure Home or Small Business Gig Definition of LOCAVORE one who eats foods grown locally whenever possible (courtesy Miriam-Webster)
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