Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updated by:

RFC 8736,RFC 9436

Authors:

M. Handley
I. Kouvelas
T. Speakman
L. Vicisano

Stream:

IETF

Source:

pim (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC5015

Discuss this RFC: Send questions or comments to the mailing listpim@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 5015

Abstract

This document discusses Bidirectional PIM (BIDIR-PIM), a variant of PIMSparse-Mode that builds bidirectional shared trees connectingmulticast sources and receivers. Bidirectional trees are builtusing a fail-safe Designated Forwarder (DF) election mechanismoperating on each link of a multicast topology. With theassistance of the DF, multicast data is natively forwarded fromsources to the Rendezvous-Point (RP) and hence along the shared treeto receivers without requiring source-specific state. The DFelection takes place at RP discovery time and provides the routeto the RP, thus eliminating the requirement for data-drivenprotocol events. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.