P2MP MPLS-TE Fast Reroute with P2MP Bypass Tunnels
draft-leroux-mpls-p2mp-te-bypass-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jean-Louis Le Roux | ||
| Last updated | 2010-01-05 (Latest revision 2007-03-07) | ||
| Replaced by | draft-ietf-mpls-p2mp-te-bypass | ||
| 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-ietf-mpls-p2mp-te-bypass | |
| 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
This document defines procedures for fast reroute protection of Point-To-MultiPoint (P2MP) Traffic Engineering Label Switched Paths (TE-LSP) in MultiProtocol Label Switching (MPLS) networks, based upon Point-To-MultiPoint bypass tunnels. The motivation for using P2MP bypass tunnels is to avoid potentially expensive data duplication along the backup path that could occur if point-to-point bypass tunnels where used, i.e. to optimize the bandwidth usage, during fast reroute protection of a link or a node. During link or node failure the traffic carried onto a protected P2MP TE-LSP is tunnelled within one or several P2MP bypass tunnels towards a set of Merge Points. To avoid data duplication backup labels (i.e. inner labels) are assigned by the Point of Local Repair (PLR) following the RSVP-TE upstream label assignment procedure.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)