8
TRILL: Traffic engineering draft-hu-trill-traffic-engineering-00.txt Fangwei Hu [email protected] Jacni Qin [email protected] Donald Eastlake 3rd [email protected] Radia Perlman [email protected] August 2012 1 TRILL: Traffic Engineering

TRILL: Traffic engineering draft-hu-trill-traffic-engineering-00.txt Fangwei Hu [email protected]@zte.com.cn Jacni Qin [email protected]@jacni.com

Embed Size (px)

Citation preview

Page 1: TRILL: Traffic engineering draft-hu-trill-traffic-engineering-00.txt Fangwei Hu hu.fangwei@zte.com.cnhu.fangwei@zte.com.cn Jacni Qin jacni@jacni.comjacni@jacni.com

TRILL: Traffic Engineering 1

TRILL: Traffic engineering draft-hu-trill-traffic-engineering-00.txt

Fangwei Hu [email protected] Qin [email protected] Eastlake 3rd [email protected] Perlman [email protected]

August 2012

Page 2: TRILL: Traffic engineering draft-hu-trill-traffic-engineering-00.txt Fangwei Hu hu.fangwei@zte.com.cnhu.fangwei@zte.com.cn Jacni Qin jacni@jacni.comjacni@jacni.com

TRILL: Traffic Engineering 2

TRILL TE• TE(Traffic Engineering) is a flexible technique

that can enhance the performance of an operational network at both the traffic and resource.

• Extension to support TE in TRILL campus

August 2012

Page 3: TRILL: Traffic engineering draft-hu-trill-traffic-engineering-00.txt Fangwei Hu hu.fangwei@zte.com.cnhu.fangwei@zte.com.cn Jacni Qin jacni@jacni.comjacni@jacni.com

TRILL: Traffic Engineering 3

Overview

• An RBridge that is the egress for a traffic engineered route holds an extra nickname which is for TE use.

• Regular traffic has a regular nickname as egress and follows a least cost route

• TE traffic has a TE nickname as egress and follows a TE route

August 2012

RB1 RB2

RB5

RB3 RB4

RB6

Basic Path

TE Path

N1

Nte1

N2 N3 N4

Nte5 Nte6

Nte4

Page 4: TRILL: Traffic engineering draft-hu-trill-traffic-engineering-00.txt Fangwei Hu hu.fangwei@zte.com.cnhu.fangwei@zte.com.cn Jacni Qin jacni@jacni.comjacni@jacni.com

TRILL: Traffic Engineering 4

Overview

• TE path can be statically configured or calculated based on the TE metrics carried by sub-TLVs inside ISIS TLV 22

• The basic routing path and TE routing path share the same forwarding table

August 2012

RB1 RB2

RB5

RB3 RB4

RB6

Basic Path

TE Path

N1

Nte1

N2 N3 N4

Nte5 Nte6

Nte4

Page 5: TRILL: Traffic engineering draft-hu-trill-traffic-engineering-00.txt Fangwei Hu hu.fangwei@zte.com.cnhu.fangwei@zte.com.cn Jacni Qin jacni@jacni.comjacni@jacni.com

TRILL: Traffic Engineering 5

Comparison of TE with MT• MT: – Constrain frames in a particular topology– Support Multi destination and unicast frame– The number of available topologies is limited

• TE:– Only support unicast frame– The TE path can be configured or computed based

on TE cost– Can support a large number of TE paths

August 2012

Page 6: TRILL: Traffic engineering draft-hu-trill-traffic-engineering-00.txt Fangwei Hu hu.fangwei@zte.com.cnhu.fangwei@zte.com.cn Jacni Qin jacni@jacni.comjacni@jacni.com

TRILL: Traffic Engineering 6

Comparison with layer 3 IS-IS TE• TRILL TE:– Very simple in implementation– No complicated signal protocol– No explicitly tunnels– "TE Router ID TLV for TRILL" is not required

• Layer 3 IS-IS TE:– Use Router ID TLV(TLV 134) – Signal protocol

August 2012

Page 7: TRILL: Traffic engineering draft-hu-trill-traffic-engineering-00.txt Fangwei Hu hu.fangwei@zte.com.cnhu.fangwei@zte.com.cn Jacni Qin jacni@jacni.comjacni@jacni.com

TRILL: Traffic Engineering 7

TRILL TE Nickname• There are no flag bits available in the Nickname

sub-TLV• There are several reasons to mark nicknames

(or blocks of nicknames)– Nickname is for TE use– Nickname will be used as ingress (to reduce RPFC

state)– Nickname is allowed/prohibited for use in campus

or level 1 area…

August 2012

Page 8: TRILL: Traffic engineering draft-hu-trill-traffic-engineering-00.txt Fangwei Hu hu.fangwei@zte.com.cnhu.fangwei@zte.com.cn Jacni Qin jacni@jacni.comjacni@jacni.com

TRILL: Traffic Engineering 8

END

August 2012