RAIDER: RAIDER: Responsive Responsive Architecture for - - PowerPoint PPT Presentation

RAIDER: RAIDER: Responsive Responsive Architecture for Architecture for Inter Inter-Domain Economics and

• Domain Economics and

Routing Routing

Nirmala Shenoy Nirmala Shenoy, Rochester Institute of T , Rochester Institute of Technology echnology Murat Murat Yuksel, University of Nevada Reno uksel, University of Nevada Reno Aparna Gupta, Koushik Kar Aparna Gupta, Koushik Kar, Rensselaer Polytechnic Inst , Rensselaer Polytechnic Inst Vi Victor Perotti, Rochester Institute of Technology Manish Karir Manish Karir, Merit Networks , Merit Networks National Science Foundation funded.. National Science Foundation funded..

Outline Outline

 Goals of RAIDER –> Future Internet

Goals of RAIDER –> Future Internet

 Components of RAIDER

Components of RAIDER

 Networking Component

Networking Component

 Floating Cloud T

Floating Cloud Tiered Internetworking Model iered Internetworking Model  Service Provisioning Component

Service Provisioning Component

 Contract-Based Inter Domain Routing

Contract-Based Inter Domain Routing  Economic Component

Economic Component

 Inter

Inter-Domain Economics and Risk Management

• Domain Economics and Risk Management

 Summary

Summary

Position paper – Individual results Position paper – Individual results

Goals of RAIDER Goals of RAIDER

 An internetworking architecture

An internetworking architecture

 Highly Flexible and Scalable

Highly Flexible and Scalable

 Te

Technically and Economically -

 Respond to future needs of Network

Respond to future needs of Network Users and Providers Users and Providers

RAIDER – T RAIDER – Technical and echnical and Economic Components Economic Components

 Floating Cloud T

Floating Cloud Tiered iered Internetwork Internetworking ing Model Model

 Contract Switching

Contract Switching

Inter er-D

• Dom
• main Econ
• nom
• mics

and Risk Managem emen ent

Floating Cloud T Floating Cloud Tiered (FCT) iered (FCT) Internetwork Internetworking Model ing Model

 Te

Technically Responsive Architecture

 Modularity

Modularity

 Granularity

Granularity

 Structure to leverage

Structure to leverage

 High Interconnections

High Interconnections

 Address mechanism

Address mechanism

 > Implement structure, avoid logical

> Implement structure, avoid logical address based routing address based routing

FCT Internetworking Model FCT Internetworking Model

 Building Blocks

Building Blocks

 Network Clouds – ISPs, POPs,

Network Clouds – ISPs, POPs, Backbone routers…… Backbone routers……

 Nested Clouds

Nested Clouds

 Ti

Tiers – Global Level – ISPs, AS – backbone, distribution, access… backbone, distribution, access…

 Nested T

Nested Tiers iers

FCT – FCT – Applied – ISP Applied – ISP Level Level

Nested Clouds, T Nested Clouds, Tiers, iers, Addresses Addresses

Tier 1 ISP C Access AS D Access Tier 2 Tier 3 Distribution Distribution Backbone 1.1 2.1:1 2.1:2 3.1:1:1 3.1:1:2 Inside a POP

Nested Nested Address 1.1{3.1:1:2} Address 1.1{3.1:1:2} Nested T Nested Tiers iers

Contract Contract Switching Switching

10

Inter Inter-domain Struggles…

• domain Struggles…

 When crossing domains, all bets are off..

When crossing domains, all bets are off..

 End-to-end reliability or performance-criticality

End-to-end reliability or performance-criticality requires requires

 assurance of single-domain performance, i.e., “

assurance of single-domain performance, i.e., “contract”s contract”s

 efficient concatenation of single-domain contracts

efficient concatenation of single-domain contracts

 Inter

Inter-domain routing needs to be aware of economic

• domain routing needs to be aware of economic

semantics semantics

 contract routing + risk management

contract routing + risk management

 We

We address translation of these struggles to architectural problems architectural problems

11

Contract-switching:

A Paradigm Shift…

Circuit-s

• switching

Pa Packet et-s

• switching

Con

• ntract-s
• switching

ISP A ISP C ISP B

e2 e2e e circuits

ISP A ISP C ISP B

rou

• utable

e datagrams datagrams

ISP A ISP C ISP B

con

• ntracts
• v
• ver

erlaid on

• n

rou

• utable

e datagrams datagrams

12

Basic Building Block: Intra- domain Dynamic Contracts

 Contract components

Contract components

 performance

performance component, e.g., capacity component, e.g., capacity

 financial

financial component, e.g., price component, e.g., price

 time

time component, e.g., term component, e.g., term

Network Core

accessed only by contracts

Customers

Edge Router Edge Router Edge Router Edge Router Edge Router Edge Router

Stations of the provider computing and advertising local prices for edge-to- edge contracts. Stations of the provider computing and advertising local prices for edge-to- edge contracts.

13

Contract Link

 An ISP

An ISP is abstracted as a is abstracted as a set of “contract links” set of “contract links”

 Contract link

Contract link: : an an advertisable advertisable contract contract

 between peering/edge points

between peering/edge points i and j of an ISP and j of an ISP

 with flexibility of

with flexibility of advertising different prices advertising different prices for edge-to-edge (g2g) intra- for edge-to-edge (g2g) intra- domain paths domain paths

capability of

• f managing value

e fl flow

• ws

at a fi finer er granularity than poi

• int-t
• to-
• anywher

ere e dea eals

14

How to Achieve e2e QoS?

 Contract Routing:

Contract Routing:

 Compose e2e inter

Compose e2e inter-domain “contract paths” over available

• domain “contract paths” over available

contract links satisfying the contract links satisfying the QoS QoS requirements requirements

 Calculate the contract paths by shortest-path

Calculate the contract paths by shortest-path algos algos with with metrics customized metrics customized w. w.r.t. contract . contract QoS QoS metrics metrics

 Tw

Two ways:

 link-state contract routing

link-state contract routing at macro time-scales at macro time-scales

 path-vector contract routing

path-vector contract routing at micro time-scales at micro time-scales

 Monitor and verify that each ISP

Monitor and verify that each ISP involved in an e2e involved in an e2e contract path is doing the job contract path is doing the job

 Punish the ISPs not doing their job, e.g. as a money-

Punish the ISPs not doing their job, e.g. as a money- back guarantee to the others involved in the e2e back guarantee to the others involved in the e2e contract path contract path

15

Path-V Path-Vector Contract Routing: ector Contract Routing:

Micro-level, On-demand, Reactive Micro-level, On-demand, Reactive

 Provider

Provider initiates… initiates…

 ISP

ISP C wants to C wants to advertise advertise availability of a availability of a short-term short-term contract link contract link

User X 2 3 5 ISP A ISP C ISP B 1 4 [C, 5-4, 30Mb/s, 45mins, $9] [C-B, 5-4-2, 20Mb/s, 45mins, $6+$5] [C-B-A, 5-4-2-1, 20Mb/s, 30mins, $7.3+$3] [C, 5-3, 10Mb/s, 30mins, $5] [C-A, 5-3-1, 5Mb/s, 15mins, $1.25+$1.2]

path announcement p a t h a n n

• u

n c e m e n t

16

Path-V Path-Vector Contract Routing: ector Contract Routing:

Micro-level, On-demand, Reactive Micro-level, On-demand, Reactive

 User initiates…

 User X wants to know if it can

reach 5 with 10-30Mb/s for 15-45mins in a $10 budget

User X 2 3 5 ISP A ISP C ISP B 1 4 [5, A-B, 1-2-4, 15-20Mb/s, 20-30mins, $4] [5, A, 1-2, 15-30Mb/s, 15-30mins, $8] [5, 10-30Mb/s, 15-45mins, $10] [5, A, 1-3, 5-10Mb/s, 15-20mins, $7]

Paths to 5 are found and ISP C sends replies to the user with two specific contract- path-vectors.

p a t h r e q u e s t path request p a t h r e q u e s t

[A-B-C, 1-2-4-5, 20Mb/s, 30mins] [A-C, 1-3-5, 10Mb/s, 15mins]

Paths to 5 are found and ISP C sends replies to the user with two specific contract- path-vectors.

reply r e p l y

17

Contract Routing over FCT Model

¡Organization ¡A ¡ Organization ¡B ¡ ISP ¡C ¡ISP ¡D ¡ISP ¡E Organization ¡C ¡ ISP ¡A ¡ Contracting ¡at ¡tier-­‑1: ¡long ¡time-­‑scale Contract ¡between ¡two ¡tier-­‑2 ¡ networks: ¡medium ¡time-­‑scale Contract ¡between ¡two ¡tier-­‑3 ¡ networks: ¡short ¡time-­‑scale ISP ¡B Tier ¡1 Tier ¡2 Tier ¡3

18

Deployment Issues

 How to motivate ISPs to participate?

How to motivate ISPs to participate?

 ISPs are very protective of their contracting

ISPs are very protective of their contracting terms – due to competition. terms – due to competition.

 But, BGP

But, BGP has similar risks too.. has similar risks too..

 Observation of opportunity costs

Observation of opportunity costs

 PVCR can be done at will..

PVCR can be done at will..

 Not much to loose if ISPs participate with their

Not much to loose if ISPs participate with their leftover bandwidth. leftover bandwidth.

 Monitoring and verification of contracts

Monitoring and verification of contracts

 Who is breaking the e2e performance?

Who is breaking the e2e performance?

 Active measurements can be OK for LSCR, but

Active measurements can be OK for LSCR, but PVCR needs lightweight techniques. PVCR needs lightweight techniques.

Summary

 A

A Future Internet A Architecture

 Te

Technically responsive

 Te

Tested on Emulab Emulab / / ProtoGENI ProtoGENI

 21 node 3 tiers

21 node 3 tiers  Economically responsive

Economically responsive

 Presented some details

Presented some details

 Collaboration on Integration ongoing.

Collaboration on Integration ongoing.

Questions