rsvp te summary frr extensions
play

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

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) 1 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) 1 1 1 1

  2. Outline • Requirements and Scope • Summary • Next Steps 2 2 2

  3. Requirements and Scope 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 overwhelmed 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] 3 3 3

  4. Outline • Requirements and Scope • Summary • Next Steps 4 4 4

  5. Summary of RSVP-TE Summary FRR (1) 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 5 5 5

  6. Summary of RSVP-TE Summary FRR (2) 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 6 6 6

  7. Summary for Summary FRR (3) Existing n1: number of LSPs rerouted over bypass 1 Path (n1) n2: number of LSPs rerouted over bypass 2 RSVP-TE FRR Resv (n1) Bypass 1 A1 F1 Ingress/ F2 Egress/ A2 Egress Ingress C E Bypass 2 Fk.. Ak .. PLR MP Path (n2) Resv (n2) Proposed 1 Path/Resv sent over bypass per LSP group Path (1) RSVP-TE Summary FRR Resv (1) Bypass 1 A1 F1 Ingress/ A2 F2 Egress/ Egress Ingress C E Bypass 2 Fk.. Ak .. PLR MP Path (1) Resv (1) 7 7 7

  8. Outline • Requirements and Scope • Summary • Next Steps 8 8 8

  9. Next Steps • Welcome comments from WG • Request to make this draft a WG document 9 9 9

  10. Thank You. 10 10 10

  11. Backup diagram 1. Topology before failure Bypass 1 Bypass 2 Head Tail Path Path Path Path Path Res Res Res Res Res A B C D E F v v v v v PLR MP 11 11 11

Recommend


More recommend