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

 
Document Type Replaced Internet-Draft (individual)
Last updated 2013-11-15 (latest revision 2012-07-09)
Replaced by draft-chen-mpls-p2mp-ingress-protection
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-chen-mpls-p2mp-ingress-protection
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-torvi-mpls-rsvp-ingress-protection-00.txt

Abstract

Protection against node failure is important for RSVP-TE LSPs, whether point-to-point or point-to-multipoint. While [RFC4090] provides a mechanism for node protection, it does not specify how to protect against failure of the ingress node. This document specifies the RSVP extensions to support ingress node protection and describes the necessary processing behavior.

Authors

Alia Atlas (akatlas@juniper.net)
Raveendra Torvi (rtorvi@juniper.net)
Markus Jork (mjork@juniper.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)