RSVP-TE Summary FRR Extensions draft-mtaillon-rsvpte-summary-frr-00 - - PowerPoint PPT Presentation

1 1 1 1

RSVP-TE Summary FRR Extensions

draft-mtaillon-rsvpte-summary-frr-00 Author list: Mike Taillon (mtaillon@cisco.com) Tarek Saad (tsaad@cisco.com) - Presenter Nicholas Tan (ntan@arista.com)

92nd IETF, MPLS WG, Dallas (March 2015)

2 2 2

Outline

• Requirements and Scope
• Summary
• Next Steps

3 3 3

Requirements: 1. Fast reroute [RFC4090] is widely deployed in packet RSVP-TE networks today 2. In scaled deployments, Point of Local Repair (PLR) and Merge Point (MP) nodes may host ten-of-thousands of LSPs 3. In event of failure, the PLR and MP ’s control planes becomes

• verwhelmed with control plane FRR processing (done per LSP)

4. Motivation to allow FRR control plane procedures between PLR and MP to be signaled and processed on groups of LSP Scope: 1. Signaled using RSVP-TE [RFC3209] 2. Using RSVP-TE FRR procedures [RFC4090]

Requirements and Scope

4 4 4

Outline

• Requirements and Scope
• Summary
• Next Steps

5 5 5

• 1. PLR creates and manages RSVP-TE Summary FRR LSP

groups and shares them with MP via signaling (PATH RRO)

➢ New Bypass Assignment Object (added to PATH/RESV RRO) ▪ Bypass Group Identifiers

• 2. MP learns Bypass Group Identifiers, acknowledges via

signaling (RESV RRO)

• 3. PLR receives acknowledgement from MP, handshake

complete

Summary of RSVP-TE Summary FRR (1)

6 6 6

• 1. After FRR activation, PLR notifies MP with list of affected

Bypass Group Identifiers via single PATH message

➢ New Bypass Active Object ■ List of affected Bypass Group Identifiers

• 2. MP processes normal FRR handling for each LSP identified

in Bypass Active Object

• 3. MP copies PATH Bypass Active Object and sends signal

RESV message

Summary of RSVP-TE Summary FRR (2)

7 7 7

C E

PLR MP Bypass 1 Bypass 2

Path (1) Resv (1) Path (1) Resv (1)

C E

PLR MP Bypass 1 Bypass 2

Path (n1) Resv (n1) Path (n2) Resv (n2)

RSVP-TE FRR RSVP-TE Summary FRR

Summary for Summary FRR (3)

Existing

Fk..

Egress/ Ingress

F1 Ak ..

Ingress/ Egress

A1 A2 F2 A2 Ak .. A1

Ingress/ Egress

Fk..

Egress/ Ingress

F1 F2

n1: number of LSPs rerouted over bypass 1 n2: number of LSPs rerouted over bypass 2 1 Path/Resv sent over bypass per LSP group

Proposed

8 8 8

Outline

• Requirements and Scope
• Summary
• Next Steps

9 9 9

Next Steps

• Welcome comments from WG
• Request to make this draft a WG document

10 10 10

Thank You.

11 11 11

• 1. Topology before failure

Head Tail

Path Path Path Path Path Res v Res v Res v Res v Res v

A B C D E F

PLR MP Bypass 1 Bypass 2

Backup diagram