1 / 9

Fast Reroute for Receiver-Driven mRSVP -TE draft-zlj-mpls-mrsvp-te-frr-00.txt

84th IETF @ Vancouver. Fast Reroute for Receiver-Driven mRSVP -TE draft-zlj-mpls-mrsvp-te-frr-00.txt. Katherine Zhao (katherine.zhao @huawei.com ) Richard Li (renwei.li @huawei.com ) Christian Jacquenet ( christian.jacquenet@orange.com ). Why N eed FRR Extension for mRSVP-TE.

jennis
Download Presentation

Fast Reroute for Receiver-Driven mRSVP -TE draft-zlj-mpls-mrsvp-te-frr-00.txt

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 84th IETF @ Vancouver Fast Reroute for Receiver-Driven mRSVP-TEdraft-zlj-mpls-mrsvp-te-frr-00.txt Katherine Zhao (katherine.zhao@huawei.com) Richard Li (renwei.li@huawei.com) Christian Jacquenet (christian.jacquenet@orange.com)

  2. WhyNeed FRR Extension for mRSVP-TE • The existing FRR mechanisms for sender-driven RSVP-TE is no longer applicable • FRR is well accepted and must have for HA FRR Relevant Terminologies • PLR: Point of Local Repair, a LSR that detects failure event and redirects traffic from protected LSP to backup mLSP. PLR does not initiate backup LSP setup with mRSVP-TE. • MP: Merge Point, a LSR that merges user traffic from a backup LSP to the primary LSP. MP initiates backup LSP setup considering PLR as the root of the backup LSR. • N: The node being protected, a LSR located between PLR and MP over the primary LSP. • FRR Domain: A set of links and LSRs crossover the protected sub-LSP(s) and backup LSP. The domain is between PLR and MP(s)

  3. FRR Extension to mRSVP-TE Supports 1) Detour Protection Mode • Detour backup applies to One-to-One protection with local repair technology • A separate backup LSP is established for each protected LSP • The backup path is called “Detour LSP” in this mode. P4 P1 P2 P3 Sender Receiver P6 P5 Protected PATH Backup PATH 2) Facility Protection Mode • Facility backup applies to one-to-n protection • A bypass tunnel is used to protect one or more LSPs that traverse the PLR and the MP(s). • The backup path is called “bypass tunnel” or “backup LSP” in this mode P1 P9 P8 Receiver Sender P5 P2 P4 P3 Receiver Sender P7 P6

  4. FRR Extension to mRSVP-TE Supports 1) Basic Link Protection with mRSVP-TE Receiver Protected Tunnel Backup Tunnel PE2 PATH P1 RESV P2 PE1 Source PE3 P3 Receiver 2) Basic Node Protection with mRSVP-TE P4 PE2 Receiver P1 P2 PE1 Source PE3 P3

  5. Link and Node Protection in Detour Mode Lp1 Lp5 Lp4 Lp-pe2 Lb2 Lb3 Lp1 Lp3 Lp-pe2 Protected Path Detour Path Protected Path Sender Sender PE1 PE1 BFD BFD Lp1->Lp2,MP FRR: Lp1->Lb3, TMP Lp1 Lp1 P1(PLR) P1(PLR) Detour Path Lp5 Lp1->Lp3, N FRR: Lp1->Lb5, TMP1 Lp2 FRR Domain Lp2 Lb3 P5(TMP1) Lb5 P2(MP) Lp3 Lb2 P3(TMP) P2(N) Lp3->Lp-pe2,PE2 FRR: Lb3->Lp-pe2, PE2 Lp2->Lp-pe2,PE2 FRR: Lb2->Lp-pe2, PE2 Lb4 PE2 Lp-pe2 Lb3 P3(MP) Receiver Lp#: the label for protected path Lb#: the label for backup path Lp-pe2 P4(TMP2) Link Protection in Detour Backup Mode PE2 FRR Domain The Procedure Includes: Receiver Detour LSP Setup Initiated by MP via PATH/RESV Messages Single Label Assigning and Binding; FRR Entry Creation Link or Node Failure Repair Re-convergence after Local Repair Node Protection In Detour Mode

  6. Link and Node Protection in Facility Mode Lb5 Lb4 Lb3 Lb3 Lb2 Lp1 Lp1 Lp2 Lp-pe2 Lp2 Lp2 Lp-pe2 Lp2 Lp2 Sender Protected Path Backup Path PE1 Sender Protected Path BFD PE1 BFG Lp1 Lp1 Lp1->Lp2, MP FRR: Lp2, Lp1->Lb3, TMP P1(PLR) P1(PLR) Lp2 Backup Path Lp1->Lp2, N FRR: Lp2, Lp1->Lb5, TMP1 Lb3 Lp2 P2(MP) P5(TMP1) Lb5 Lb2 P3(TMP) Lp2 P2(N) Lp2 -> Lp-pe2, PE2 FRR: Lp2,Lp2>Lp-pe2,PE2 PE2 P3(MP) Lb4 Lp-pe2 Lb3 Receiver Lp2>Lp-pe2,PE2 FRR: Lp2, Lb3->Lp-pe2, PE2 P4(TMP2) Lp#: the label for protected path Lb#: the label for backup path Lp-pe2 PE2 Link Protection In Facility Backup Receiver The Procedure Includes: Node Protection In Facility Backup Mode Detour LSP Setup Initiated by MP via PATH/RESV Messages Dual-Label Assigning and Binding; FRR Entry Creation; ULA for Node Protection Link or Node Failure Repair Re-convergence after Local Repair

  7. P2MP/MP2MP Node Protection with mRSVP-TE PLR PLR • Protected LSP is a P2MP session • Protected LSP is a P2MP session Pn • Backup LSP is a P2MP session Pn N N Pn • Backup LSP is multiple P2P sessions MP MP MP MP Protection Option 2 Protection Option 1 • . • Option 1: • P2MP (or MP2MP) LSP can be protected by a single backup P2MP (or MP2MP) LSP. • Option 2: • P2MP (or MP2MP) LSP can be protected by multiple P2P LSP(s)

  8. P2MP Node Protection in Facility Mode with mRSVP-TE Sender Data Flow on Protected LSP1 PE1 P1(PLR): Lp1->lg2, N Ly1->Ly2,N FRR: Lp2, Lp1->Lb5, TMP1 FRR: Ly2, Ly1->Lb5, TMP1 Data Flow on Backup LSP Ly1 Ly2 Lp2 Lp1 P1(PLR, Root) P7(MP3): Ly2->Lp-pe7, PE7 Ly2->Lp-pe6, PE6 FRR: Ly2, Lb7->Lp-pe7,PE7 FRR: Ly2, Lb7->Lp-pe6, PE6 Data Flow on Protected LSP 2 Lb5 Lb4 Ly2 Lb4 Lp2 Lp2 P5(TMP1) Ly2 Ly2 P7(MP3) Lp-pe7 PE7 Ly2 Lb7 P2(N) Lp2 Lp-pe6 Lb4 Lp2 P6(MP2) Lb6 Lb6 PE6 Lb3 P4 (TMP2) P3(MP1) Lp-pe3 PE5 P3(MP1) : Lp2 -> Lp-pe2, PE2 Lp2 -> Lp-pe3, PE3 FRR: Lp2, Lb3->Lp-pe2, PE2 FRR: Lp2, Lb3->Lp-pe3, PE3 PE4 Lp-pe2 PE3 Leaf PE1 PE2

  9. Next Steps • Looking for feedbacks from you! • Suggestions? Questions? Comments? 84th IETF @ Vancouver

More Related