Remote-LFA Node Protection and Manageability (RFC8102)
Original Publication Date: 2017-Mar-01
Included in the Prior Art Database: 2017-Mar-10
Internet Society Requests For Comment (RFCs)
P. Sarkar: AUTHOR [+5]
The Remote-LFA specification [RFC7490] provides loop-free alternates that guarantee only link protection. The resulting remote-LFA alternate next hops (also referred to as the "PQ-nodes") may not provide node protection for all destinations covered by the same remote-LFA alternate, in case of failure of the primary next-hop node, and it does not provide a means to determine the same.
Internet Engineering Task Force (IETF) P. Sarkar, Ed. Request for Comments: 8102 Arrcus, Inc. Category: Standards Track S. Hegde ISSN: 2070-1721 C. Bowers Juniper Networks, Inc. H. Gredler RtBrick, Inc. S. Litkowski Orange March 2017
Remote-LFA Node Protection and Manageability
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.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc8102.
Sarkar, et al. Standards Track [Page 1]
RFC 8102 R-LFA Node Protection and Manageability March 2017