metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 7891: Explicit Reverse Path Forwarding (RPF) Vector

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC7891
Published
June 2016
Authors
J. Asghar; IJ. Wijnands; S. Krishnaswamy; A. Karan; V. Arya
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
9
Also known as
—

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/7891-explicit-reverse-path-forwarding-rpf-vector