What An Application Wants

Glenn RicartJune 5, 2014

2

An InfrastructureThat Meets Its Needs

3

An InfrastructureThat Meets Its Needs

Required / DesirableProperties

Affordable Price

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

AverageMaximumMinimumCumulativeRelative priority forStability ofPrice of

5

Federation PropertiesAn application might care about

• Lingua franca• Resource descriptions• Service descriptions• Orchestrations• Identity• Authorization• Platform capabilities• Isolation• Location mobility

CapabilitiesService levelsPerformanceSecurityMonitoringMeasurementPricing

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

11Courtesy Mike Zink

12Courtesy Mike Zink

13Courtesy 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

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 G

bps

Commercially Available

Terra Incognita

10 M

bps

100

Gbp

s

Mob

ile d

ata

caps

Wire

d da

ta

caps

Web page

Netflix movie

Lo

cavo

re

Gigabit benefits

Online backup

Public-private partnership

501(c)(3)

60 next-generation applications

200 community test beds

Coordinate best practices

1

2

3

20

OUR GOALS

Infrastructure

Next-Gen Applications

Economic Leadership

21

Current Partners

22

23

Today’s Infrastructure

10 Mbps

Home or Small Business

24

Locavore Infrastructure

Gig

Home or Small Business

Definition of LOCAVORE  one who eats foods grown locally whenever possible (courtesy Miriam-Webster)

25

Locavore Infrastructure

Gig

Home or Small Business

Definition of LOCAVORE  one who eats foods grown locally whenever possible (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