RFC 8102

Remote-LFA Node Protection and Manageability, March 2017

File formats:
icon for text file icon for PDF icon for HTML
Status:
PROPOSED STANDARD
Authors:
P. Sarkar, Ed.
S. Hegde
C. Bowers
H. Gredler
S. Litkowski
Stream:
IETF
Source:
rtgwg (rtg)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC8102

Discuss this RFC: Send questions or comments to the mailing list rtgwg@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 8102


Abstract

The loop-free alternates (LFAs) computed following the current remote-LFA specification guarantees only link protection. The resulting remote-LFA next hops (also called "PQ-nodes") may not guarantee node protection for all destinations being protected by it.

This document describes an extension to the remote-loop-free-based IP fast reroute mechanisms that specifies procedures for determining whether or not a given PQ-node provides node protection for a specific destination. The document also shows how the same procedure can be utilized for the collection of complete characteristics for alternate paths. Knowledge about the characteristics of all alternate paths is a precursor to applying the operator-defined policy for eliminating paths not fitting the constraints.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search