1 / 5

Ingress Protection for RSVP-TE p2p and p2mp LSPs draft-torvi-mpls-rsvp-ingress-protection-00

Ingress Protection for RSVP-TE p2p and p2mp LSPs draft-torvi-mpls-rsvp-ingress-protection-00. Alia Atlas , Raveendra Torvi, Markus Jork IETF 84, Vancouver, B.C. Basic Problem & Proposed Solution. Solution : Proxy-Ingress Node & RSVP Signaling via the Backup Node

nansen
Download Presentation

Ingress Protection for RSVP-TE p2p and p2mp LSPs draft-torvi-mpls-rsvp-ingress-protection-00

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. Ingress Protection for RSVP-TE p2p and p2mp LSPsdraft-torvi-mpls-rsvp-ingress-protection-00 Alia Atlas, Raveendra Torvi, Markus Jork IETF 84, Vancouver, B.C.

  2. Basic Problem & Proposed Solution Solution: • Proxy-Ingress Node & RSVP Signaling via the Backup Node • Backup can be on-forwarding-path OR off-forwarding-path • Backup Nodes Uses Bypass Tunnels to reach MPs as in RFC4090. Traffic Source Ingress Backup Backup MP Proxy Ingress Ingress MP A MP B Path Resv Forwarding Egress 1 Egress 2 Problem: Protect against ingress-node failure for an LSP

  3. Failure Detection & Traffic 3 Different Scenarios – signaled in new INGRESS-PROTECTION object After IGP shows failure, Backup can use make-before-break for global repair.

  4. RSVP Protocol Changes • New INGRESS-PROTECTION object • Exchanged ONLY from Proxy Ingress to Backup to Ingress (and potentially to MP for MP-detection) 0 1 2 3 +-------------+-------------+-----------------+-------------+ | Length (bytes) | Class-Num | C-Type | +-------------+-------------+-----------------+-------------+ | Backup Node Address | +-------------+-------------+-----------------+-------------+ | Ingress Node Address | +-------------+-------------+-----------------+-------------+ | Application Traffic Identifier | +-------------+-------------+-----------------+-------------+ | Secondary LSP ID | Protection | Flags | | | Scenario | | +-------------+-------------+-----------------+-------------+

  5. Summary Next Steps • Get feedback on Proposed Solution (on mailing list) • Clarify if any use-cases for reversion back to ingress Simple extension based on proxy-ingress (signaled by ingress) and 1 new RSVP object. Backup can be on or off the forwarding path. Backup can use any bypass LSP (p2p or p2mp) for sending traffic as in RFC 4090.

More Related