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)
Expired & archived
|
|
---|---|---|---|
Authors | Rakesh Gandhi , Himanshu C. Shah , Jeremy Whittaker | ||
Last updated | 2016-01-11 | ||
Replaced by | draft-gandhishah-teas-assoc-corouted-bidir | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
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 | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
Himanshu C. Shah
Jeremy Whittaker
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)