what an application wants glenn ricart june 5, 2014

26
What An Application Wants Glenn Ricart June 5, 2014

Upload: finna

Post on 23-Feb-2016

30 views

Category:

Documents


0 download

DESCRIPTION

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 - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: What An Application Wants Glenn Ricart June 5, 2014

What An Application WantsGlenn Ricart

June 5, 2014

Page 2: What An Application Wants Glenn Ricart June 5, 2014

2

An InfrastructureThat Meets Its Needs

Page 3: What An Application Wants Glenn Ricart June 5, 2014

3

An InfrastructureThat Meets Its Needs

Required / DesirableProperties

Affordable Price

Page 4: What An Application Wants Glenn Ricart June 5, 2014

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

Page 5: What An Application Wants Glenn Ricart June 5, 2014

5

Federation PropertiesAn application might care about

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

CapabilitiesService levelsPerformanceSecurityMonitoringMeasurementPricing

Page 6: What An Application Wants Glenn Ricart June 5, 2014

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

Page 7: What An Application Wants Glenn Ricart June 5, 2014

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

Page 8: What An Application Wants Glenn Ricart June 5, 2014

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)

Page 9: What An Application Wants Glenn Ricart June 5, 2014

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)

Page 10: What An Application Wants Glenn Ricart June 5, 2014

10

CASA Radar

Page 11: What An Application Wants Glenn Ricart June 5, 2014

11Courtesy Mike Zink

Page 12: What An Application Wants Glenn Ricart June 5, 2014

12Courtesy Mike Zink

Page 13: What An Application Wants Glenn Ricart June 5, 2014

13Courtesy Mike Zink

Page 14: What An Application Wants Glenn Ricart June 5, 2014

14

SDXes• Integral to inter-domain application

infrastructure• Either

– Do not impact a property when inserted– Are considered as part of the balance

Transparent

Page 15: What An Application Wants Glenn Ricart June 5, 2014

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

Page 16: What An Application Wants Glenn Ricart June 5, 2014

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

Page 17: What An Application Wants Glenn Ricart June 5, 2014

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 Gbp

s

Commercially Available

Terra Incognita

10 M

bps

100 G

bps

Mob

ile d

ata

caps

Wire

d da

ta

caps

Web page

Netflix movie

Loca

vore

Gigabit benefits

Online backup

Page 18: What An Application Wants Glenn Ricart June 5, 2014

Public-private partnership

501(c)(3)

Page 19: What An Application Wants Glenn Ricart June 5, 2014

60 next-generation applications

200 community test beds

Coordinate best practices

1

2

3

20

OUR GOALS

Infrastructure

Next-Gen Applications

Economic Leadership

Page 20: What An Application Wants Glenn Ricart June 5, 2014

21

Current Partners

Page 21: What An Application Wants Glenn Ricart June 5, 2014

22

Page 22: What An Application Wants Glenn Ricart June 5, 2014

23

Today’s Infrastructure

10 Mbps

Home or Small Business

Page 23: What An Application Wants Glenn Ricart June 5, 2014

24

Locavore Infrastructure

Gig

Home or Small Business

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

Page 24: What An Application Wants Glenn Ricart June 5, 2014

25

Locavore Infrastructure

Gig

Home or Small Business

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

Page 25: What An Application Wants Glenn Ricart June 5, 2014

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

Page 26: What An Application Wants Glenn Ricart June 5, 2014