Fast Re-route using extensions to LDP
draft-kini-mpls-frr-ldp-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Sriganesh Kini , Srikanth Narayanan , Stephane Litkowski | ||
| Last updated | 2013-01-17 (Latest revision 2012-07-16) | ||
| 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
Label Distribution Protocol (LDP) is widely deployed to signal Label Switched Paths (LSPs) due to its simple operational model. Since LDP establishes LSPs along IGP routed paths, its failure recovery is gated by the interior gateway protocol's (IGP's) re-convergence. Though some mechanisms exist to do Fast Re-route (FRR) of LDP LSPs, they suffer from significant complexity or lack of full coverage or both. This document describes a method to perform FRR of LDP LSPs that retains the simple operational model of LDP. The goal is to provide 100% coverage for all failure scenarios including Shared Risk Link Group (SRLG) failure with recovery characteristics similar to the methods in Resource Reservation Protocol - Traffic Engineering FRR (RSVP-TE-FRR).
Authors
Sriganesh Kini
Srikanth Narayanan
Stephane Litkowski
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)