Remote-LFA Node Protection and Manageability
RFC 8102, “Remote-LFA Node Protection and Manageability”, is a Proposed Standard document published in March 2017 by P. Sarkar, S. Hegde, C. Bowers, H. Gredler, S. Litkowski. The canonical text is published by the RFC Editor.
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8102 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8101 IANA Registration of New Session Initiation Protocol Resource- Priority Namespace for Mission Critical Push To Talk Service
- RFC 8103 Using ChaCha20-Poly1305 Authenticated Encryption in the Cryptographic Message Syntax
- RFC 8100 Diffserv-Interconnection Classes and Practice
- RFC 8104 Pseudowire Endpoint Fast Failure Protection
- RFC 8099 OSPF Topology-Transparent Zone
- RFC 8105 Transmission of IPv6 Packets over Digital Enhanced Cordless Telecommunications Ultra Low Energy
- RFC 8098 Message Disposition Notification
- RFC 8106 IPv6 Router Advertisement Options for DNS Configuration