LISP Traffic Engineering draftfarinaccilispte01 Dino Farinacci Cisco Systems

LISP Traffic Engineering draft-farinacci-lisp-te-01 Dino Farinacci Cisco Systems Parantap Lahiri Microsoft Corporation Michael Kowal Cisco Systems

Problem Statement • LISP provides data-path stretch = 1 – When encapsulating from ITR to ETR • What if stretch = 1 path is congested? – Could we hair-pin as a feature? – To find a better performing data path

Re-Encapsulation Points RTR ‘Y’ decaps packet RTR ‘Y’ EID-prefix: 2001: db 8: 2: : /48 RTR ‘X’ decaps packetlookup and 2001: db 8: 2: : /48 performs on encaps packet EID-prefix: and performs lookup Locator-set: priority weight dest(x, y, ETR): EID foron ELP (if ELPs provisioned Locator-set: (x, y, ETR): priority weight 100 to ETR 1, 1, 1, Locator-set: (x, y, ETR): priority weight 100 not cached) dest EID for ELP (if via Programmable ITR encapsulates EID MS/MR a. a. a. 0/24 b. b. b. 0/24 c. c. c. 0/24 d. d. 0. 0/16 RLOC w. x. y. 1 x. y. w. 2 z. q. r. 5 EID RLOC a. a. a. 0/24 b. b. b. 0/24 c. c. c. 0/24 d. d. 0. 0/16 not cached) Interface to RLOC ‘X’ A RTR X Y B C § ITR EID a. a. a. 0/24 b. b. b. 0/24 c. c. c. 0/24 d. d. 0. 0/16 D w. x. y. 1 x. y. w. 2 z. q. r. 5 RLOC w. x. y. 1 x. y. w. 2 z. q. r. 5 ETR LISP encapsulation

Recursion EID-prefix: RTR-Y ETR Locator-set: (e, f, y): priority 1, weight 100 Locator-set: (y) (x, e, f, y, ETR): 1, 100 weight 100 : priority 2, weight (x, y, ETR): priority 2, weight 100 RTR E F RTR A lookup RTR X Y B C § ITR RTR ‘X’ L-bit setting for performs‘Y’ lookup determines: on ETR ‘ETR’ re-encap or D ETR LISP encapsulation

Service Chaining s. EID ITR ETR RTR Service Chain described by ELP Scrubber Service described by EID in mapping database d. EID Honey-pot Deep Packet Inspection