smucse 8344 qos in mpls. smucse 8344 strategy to support end-to-end qos as in ip mpls not an...

11
QoS in MPLS

Upload: rudolph-goodman

Post on 27-Dec-2015

218 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: SMUCSE 8344 QoS in MPLS. SMUCSE 8344 Strategy To support end-to-end QoS as in IP MPLS not an end-to-end protocol Efficient ways of mapping QoS to LSPs

QoS in MPLS

Page 2: SMUCSE 8344 QoS in MPLS. SMUCSE 8344 Strategy To support end-to-end QoS as in IP MPLS not an end-to-end protocol Efficient ways of mapping QoS to LSPs

Strategy

• To support end-to-end QoS as in IP• MPLS not an end-to-end protocol• Efficient ways of mapping QoS to LSPs• Traffic Engineering key to QoS

Page 3: SMUCSE 8344 QoS in MPLS. SMUCSE 8344 Strategy To support end-to-end QoS as in IP MPLS not an end-to-end protocol Efficient ways of mapping QoS to LSPs

QoS Models

• Best effort – Original IP service

• Int-serv.– Fist IP effort to support QoS

• Diff-serv.– Simple, scalable

• Future– Int+ Diff+ TE with e2e SLAs

Page 4: SMUCSE 8344 QoS in MPLS. SMUCSE 8344 Strategy To support end-to-end QoS as in IP MPLS not an end-to-end protocol Efficient ways of mapping QoS to LSPs

Integrated Services and RSVP

• Service Classes– Guaranteed service– Controlled load

• MPLS support of RSVP– New object (label object) carried inside RSVP RESV

message– Down-stream label allocation– Once the label binding is over, only the edge router

concerned with which packets belong to the reserved flow

– Can aggregate multiple micro-flows to realize pipes between sites

• New RSVP object carried in the PATH message (LABEL REQUEST)

Page 5: SMUCSE 8344 QoS in MPLS. SMUCSE 8344 Strategy To support end-to-end QoS as in IP MPLS not an end-to-end protocol Efficient ways of mapping QoS to LSPs

RSVP Scalability

• Micro-flow reservations scale badly (Not RSVP by itself)

• Aggregation will help reduction of complexity• RSVP Refresh reduction

– RSVP a soft state protocol and hence need refresh– Unreliable and hence need high frequency refresh– Solutions

• Reliable delivery through ACKS – reduced refresh rate once the ACK received

• Summary refresh – send the IDs instead of the whole message; can combine multiple message IDs

Page 6: SMUCSE 8344 QoS in MPLS. SMUCSE 8344 Strategy To support end-to-end QoS as in IP MPLS not an end-to-end protocol Efficient ways of mapping QoS to LSPs

Differential Services

• Need to map DSCP to labels– How to set the right value?– Who sets the DSCP value?– What does a router do when a packet with a DSCP value arrives?

• DSCP defines PHB (Per Hop Behavior)– Default – equivalent to best effort as in IP– Expedited Forwarding (EF)

• Should be forwarded with minimal delay• All the packets with EF marking put in a dedicated EF queue• Arrival rate less than the service rate

– Assured Forwarding• Defined in the form of AFxy – x defines the class and y specifies the drop

preference• Example AF11, AF12, AF13 …

• Who sets the values– Based on the application, hosts do it– Router sets it based on locally configured policies – arrival interface, BW

etc.

Page 7: SMUCSE 8344 QoS in MPLS. SMUCSE 8344 Strategy To support end-to-end QoS as in IP MPLS not an end-to-end protocol Efficient ways of mapping QoS to LSPs

MPLS Support for DS

• Map the DSCP to label– Map into the 3-bit EXP field (E-LSP)

• Limits the PHBs to 8 (as opposed to 64 possibilities)

• Requires Shim-label support• No additional signaling required

– What if more than 8 PHBs• Use explicit LSP (hence label distribution)to

represent PHBs (L-LSP)

Page 8: SMUCSE 8344 QoS in MPLS. SMUCSE 8344 Strategy To support end-to-end QoS as in IP MPLS not an end-to-end protocol Efficient ways of mapping QoS to LSPs

E-LSP vs. L-LSP

R1 R2 R3

R1 R2 R3

AF1y packets

Default packets

L-LSP for AF1y

L-LSP for Default

Page 9: SMUCSE 8344 QoS in MPLS. SMUCSE 8344 Strategy To support end-to-end QoS as in IP MPLS not an end-to-end protocol Efficient ways of mapping QoS to LSPs

E-LSP vs. L-LSP (Cont’d)

– E-LSP• Minimal label usage• Conforms to classical DS model

– L-LSP• Arbitrarily large no. of PHBs• Possibility engineer different paths for various

PHBs

– Combinations are also possible

Page 10: SMUCSE 8344 QoS in MPLS. SMUCSE 8344 Strategy To support end-to-end QoS as in IP MPLS not an end-to-end protocol Efficient ways of mapping QoS to LSPs

Explicit Congestion Notification (ECN)

• Congestion control vs. avoidance– Drop the packet vs. CE (Congestion experienced) bit

set

• Accommodation nodes with varying capabilities– In IP use the two bits left in the TOS field

• ECT – ECN capable transport• CE

– How to do it in MPLS• May have maximum 1-bit available• Code the possible three states into two states and do

the corresponding mapping

Page 11: SMUCSE 8344 QoS in MPLS. SMUCSE 8344 Strategy To support end-to-end QoS as in IP MPLS not an end-to-end protocol Efficient ways of mapping QoS to LSPs

CISCO QoS Framework

PR

OV

ISIO

NIN

G &

MO

NIT

OR

ING

PR

OV

ISIO

NIN

G &

MO

NIT

OR

ING

VPNsVPNsMultimediaVideo Conference,

Collaborative Computing

MultimediaVideo Conference,

Collaborative Computing

Mission Critical Services

Mission Critical ServicesVoIPVoIP

HybridHybridMPLSMPLSDiffServDiffServIntServIntServ

Signaling Techniques (RSVP, DSCP*, ATM (UNI/NNI))Signaling Techniques (RSVP, DSCP*, ATM (UNI/NNI))

Link Efficiency Mechanisms (Compression, Fragmentation)Link Efficiency Mechanisms (Compression, Fragmentation)

Congestion Avoidance Techniques (WRED)Congestion Avoidance Techniques (WRED)

Congestion Management Techniques (WFQ, CBWFQ, LLQ)Congestion Management Techniques (WFQ, CBWFQ, LLQ)

Classification & Marking Techniques (DSCP, MPLS EXP, NBAR, etc.)Classification & Marking Techniques (DSCP, MPLS EXP, NBAR, etc.)

FrameRelay

FrameRelay

PPPHDLC

PPPHDLC SDLC

SDLCATM, POSATM, POS FE,Gig.E

10GE

FE,Gig.E 10GE

WirelessFixed,Mobile

WirelessFixed,Mobile

BroadBandCable,xDSL

BroadBandCable,xDSL

PO

LIC

Y-B

AS

ED

NETW

OR

KIN

GP

OLIC

Y-B

AS

ED

NETW

OR

KIN

G

Traffic Conditioners (Policing, Shaping)Traffic Conditioners (Policing, Shaping)