1 / 5

Extensions to RSVP-TE for LSP Ingress Local Protection

Extensions to RSVP-TE for LSP Ingress Local Protection. draft-ietf-mpls-rsvp-ingress-protection-01. Huaimo Chen, Raveendra Torvi Ning So, Autumn Liu, Alia Atlas, Yimin Shen Fengman Xu, Mehmet Toy, Lei Liu. Updates on Ingress Failure Detection Modes Source Detects Failure ( Enhanced)

chiara
Télécharger la présentation

Extensions to RSVP-TE for LSP Ingress Local Protection

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. Extensions to RSVP-TE for LSP Ingress Local Protection draft-ietf-mpls-rsvp-ingress-protection-01 Huaimo Chen, Raveendra Torvi Ning So, Autumn Liu, Alia Atlas, Yimin Shen Fengman Xu, Mehmet Toy, Lei Liu

  2. Updates on Ingress Failure Detection Modes • Source Detects Failure (Enhanced) • Backup and Source Detect Failure • Backup Detects Failure (Removed) • Next Hops Detect Failure (Removed) • DM (Detection Modes) field (Removed ) • Try to converge to one failure detection mode Updates from the last version One Detection Mode

  3. Source Detects Failure Source (CE1) quickly detects ingress (PE1) failure and switches traffic to backup ingress(PE2) Backup Ingress (PE2) always ready to import traffic into backup LSP reliably detects ingress failure, sends Path message Primary LSP 1. Ingress PE1 fails Backup LSP 2. Source CE1 quickly detects failure by BFD and switches traffic to PE2 PE3 BFD Data PE4 PE1 CE3 BFD CE1 P1 4. Traffic merged into primary LSP at P1 Source PE2 PE5 Data CE4 PE6 3. Backup Ingress PE2 imports traffic into backup LSP 5. Backup ingress PE2 reliably detects PE1 failure by IGP/routing and sends/refreshes PATH messages as needed 3

  4. Some Questions Ingress Failure Detection Modes: • Any issues on Source Detects Failure? • Should we use one failure detection mode? • Should we provide multiple modes and let operator to select one? Request comments on: Relay-Message Method and Proxy-Ingress Method

  5. Next Step • Welcome comments

More Related