1. What An Application Wants Glenn Ricart June 5, 2014

2. An Infrastructure That Meets Its Needs 2

3. 3 Required / Desirable Properties Affordable Price

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

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

6. Complexities Both 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 6

7. Balance Points Might 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 7

8. US Ignite Apps Want At 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) 8

9. Smart Things Want At 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

10. 10 CASA Radar

11. 11 Courtesy Mike Zink

12. 12 Courtesy Mike Zink

13. 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 14 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). 15

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 16

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

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

19. NextGen Technologies Next-Gen Infra- structure Next-Gen Apps

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

21. 21 Current Partners

22. 22

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

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

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

26. 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 26