RFC 5496: The Reverse Path Forwarding (RPF) Vector TLV
In plain English — editorial summary, not part of the RFC
This document describes a use of the Protocol Independent Multicast (PIM) Join Attribute as defined in RFC 5384, which enables PIM to build multicast trees through an MPLS-enabled network, even if that network's IGP does not have a route to the source of the tree. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5496
- Published
- March 2009
- Authors
- IJ. Wijnands; A. Boers; E. Rosen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5501Requirements for Multicast Support in Virtual Private LAN ServicesCurrent
March 2009
- RFC 5060Protocol Independent Multicast MIBCurrent
January 2008
- RFC 5015Bidirectional Protocol Independent Multicast (BIDIR-PIM)Updated
October 2007
- RFC 6517Mandatory Features in a Layer 3 Multicast BGP/MPLS VPN SolutionCurrent
February 2012
- RFC 7887Hierarchical Join/Prune AttributesCurrent
June 2016
- RFC 7899Multicast VPN State DampingCurrent
June 2016
- RFC 2934Protocol Independent Multicast MIB for IPv4Current
October 2000
- RFC 9128YANG Data Model for Protocol Independent Multicast (PIM)Current
October 2022
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?