Skip to main content

Explicit Reverse Path Forwarding (RPF) Vector
RFC 7891

Revision differences

Document history

Date By Action
2026-05-20
(System) Changed metadata: changed keywords to '['Path diversity', 'MoFRR', 'Maximally redundant paths']' from '[]'
2026-05-20
(System) Metadata update from RFC Editor
2026-05-20
(System) Changed author "V. Arya": changed name from "Vishal Arya" to "V. Arya", cleared country (was "United States"), changed order from "4" to "5"
2026-05-20
(System) Changed author "A. Karan": changed name from "Apoorva Karan" to "A. Karan", cleared country (was "United States"), changed order from "3" to "4"
2026-05-20
(System) Changed author "S. Krishnaswamy": changed name from "Sowmya Krishnaswamy" to "S. Krishnaswamy", cleared country (was "United States"), changed order from "2" to "3"
2026-05-20
(System)
Changed author "IJ. Wijnands": changed name from "IJsbrand Wijnands" to "IJ. Wijnands", changed is_editor from "False" to "True", cleared country (was "Belgium"), changed order from …
Changed author "IJ. Wijnands": changed name from "IJsbrand Wijnands" to "IJ. Wijnands", changed is_editor from "False" to "True", cleared country (was "Belgium"), changed order from "1" to "2"
2026-05-20
(System) Changed author "J. Asghar": changed name from "Javed Asghar" to "J. Asghar", cleared country (was "United States"), changed order from "0" to "1"
2026-05-20
(System) Metadata update from RFC Editor
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'The PIM Reverse Path Forwarding (RPF) Vector TLV defined in RFC 5496 can be included in …
Received changes through RFC Editor sync (changed abstract to 'The PIM Reverse Path Forwarding (RPF) Vector TLV defined in RFC 5496 can be included in a PIM Join Attribute such that the RPF neighbor is selected based on the unicast reachability of the RPF Vector instead of the source or Rendezvous Point associated with the multicast tree.

This document defines a new RPF Vector Attribute type such that an explicit RPF neighbor list can be encoded in the PIM Join Attribute, thus bypassing the unicast route lookup.')
2016-06-15
(System) RFC published