The Reverse Path Forwarding (RPF) Vector TLV

Metadata

Publisher: IETF
Doc Type: Standard
Pages: 8
Abstract: 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]
Publication Date: 2009-03-01
Status Note: Proposed Standard
DOI: 10.17487/RFC5496
Link: https://doi.org/10.17487/RFC5496
Author(s): IJsbrand Wijnands
A Boers
Eric C. Rosen
Keyword(s): PIM

Latest version of IETF RFC 5496

Document Versions — IETF RFC 5496

▶ IETF RFC 5496 (2009-03-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

IETF RFC 2119 [Active*]
IETF RFC 4601 [Superseded*]
IETF RFC 4607 [Active*]
IETF RFC 5015 [Active*]
IETF RFC 5384 [Active*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC5496.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 5496, The Reverse Path Forwarding (RPF) Vector TLV. Available at https://doi.org/10.17487/RFC5496

Snippet:

IETF RFC 5496, The Reverse Path Forwarding (RPF) Vector TLV. Available at https://doi.org/10.17487/RFC5496

HTML (ISO 690 compliant)

Preview:

IETF RFC 5496, The Reverse Path Forwarding (RPF) Vector TLV. Available at https://doi.org/10.17487/RFC5496

Snippet:

<span class="citation"><cite>IETF RFC 5496</cite>, The Reverse Path Forwarding (RPF) Vector TLV. Available at <a href="https://doi.org/10.17487/RFC5496" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5496</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 5496, The Reverse Path Forwarding (RPF) Vector TLV
doi: 10.17487/RFC5496
url: https://doi.org/10.17487/RFC5496

Snippet:

<li>
<cite id="bib-rfc5496">IETF RFC 5496</cite>, The Reverse Path Forwarding (RPF) Vector TLV
<span class="doi">10.17487/RFC5496</span>
</li>

Referenced By

IETF RFC 5565 [Active*]
IETF RFC 6830 [Superseded*]
IETF RFC 6831 [Active*]