LDP Extensions to Support Maximally Redundant Trees
draft-atlas-mpls-ldp-mrt-03
| Document | Type | Replaced Internet-Draft (mpls WG) | |
|---|---|---|---|
| Last updated | 2014-12-15 | ||
| Replaced by | RFC 8320 | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | Loa Andersson | ||
| IESG | IESG state | Replaced by draft-ietf-mpls-ldp-mrt | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-atlas-mpls-ldp-mrt-03.txt
Abstract
This document specifies extensions to the Label Distribution Protocol(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, which we will refer to as 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
(akatlas@juniper.net)
Kishore Tiruveedhula
(kishoret@juniper.net)
Chris Bowers
(cbowers@juniper.net)
Jeff Tantsura
(jeff.tantsura@ericsson.com)
IJsbrand Wijnands
(ice@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)