Remote-LFA Node Protection and Manageability
RFC 8102

Received changes through RFC Editor sync (changed abstract to '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.')

Received changes through RFC Editor sync (created alias RFC 8102, changed abstract to '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.', changed pages to 22, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2017-03-09, changed IESG state to RFC Published)