RFC 7891
Explicit Reverse Path Forwarding (RPF) Vector, June 2016
- File formats:
- Status:
- PROPOSED STANDARD
- Authors:
- J. Asghar
IJ. Wijnands, Ed.
S. Krishnaswamy
A. Karan
V. Arya - Stream:
- IETF
- Source:
- pim (rtg)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC7891
Discuss this RFC: Send questions or comments to the mailing list pim@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 7891
Abstract
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.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.