LDP Extensions to Support Maximally Redundant Trees
draft-atlas-mpls-ldp-mrt-00
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
---|---|---|---|
Authors | Alia Atlas , Kishore Tiruveedhula , Jeff Tantsura , IJsbrand Wijnands | ||
Last updated | 2014-01-13 (Latest revision 2013-07-12) | ||
Replaced by | draft-ietf-mpls-ldp-mrt, RFC 8320 | ||
RFC stream | (None) | ||
Formats | |||
Additional resources | |||
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 specifies extensions to LDP to support the creation of label-switched paths for Maximally Redundant Trees (MRT). A prime use of MRTs is for unicast and multicast IP/LDP Fast-Reroute (MRT- FRR). The sole protocol extension to LDP is simply the ability to advertise an MRT Capability. This document describes that extension and the associated behavior expected for LSRs and LERs advertising the MRT Capability. MRT-FRR uses LDP multi-topology extensions and requires three different multi-topology IDs to be allocated from the LDP MT-ID space.
Authors
Alia Atlas
Kishore Tiruveedhula
Jeff Tantsura
IJsbrand Wijnands
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)