RSVP-TE Extensions For Associated Co-routed Bidirectional Label Switched Paths (LSPs)
draft-gandhi-shah-teas-assoc-corouted-bidir-00

Document Type Replaced Internet-Draft (individual)
Last updated 2016-01-11
Replaced by draft-gandhishah-teas-assoc-corouted-bidir
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-gandhishah-teas-assoc-corouted-bidir
Telechat date
Responsible AD (None)
Send notices to (None)

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-gandhi-shah-teas-assoc-corouted-bidir-00.txt

Abstract

In transport networks, there are requirements where reverse unidirectional LSP of a bidirectional LSP needs to follow the same path as its forward unidirectional LSP. This document describes how RSVP Extended ASSOCIATION Object can be used to bind two co-routed point-to-point unidirectional LSPs into an associated co-routed bidirectional LSP in single-sided provisioning case. The RSVP REVERSE_LSP Object is used to enable an endpoint to trigger creation of the reverse LSP along the same path as the forward LSP. Fast-reroute procedures to ensure that the traffic flows on the co- routed path after a failure event are also described.

Authors

Rakesh Gandhi (rgandhi@cisco.com)
Himanshu Shah (hshah@ciena.com)
Jeremy Whittaker (jeremy.whittaker@verizon.com)

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