P2MP MPLS-TE Fast Reroute with P2MP Bypass Tunnels
draft-ietf-mpls-p2mp-te-bypass-02
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Jean-Louis Le Roux | ||
Last updated | 2024-01-16 (Latest revision 2008-02-27) | ||
Replaces | draft-leroux-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 | Expired | |
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 were 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) according to 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.)