Bidirectional Protocol Independent Multicast (BIDIR-PIM), October 2007
- File formats:
- PROPOSED STANDARD
- Updated by:
- RFC 8736, RFC 9436
- M. Handley
- pim (rtg)
Discuss this RFC: Send questions or comments to the mailing list firstname.lastname@example.org
This document discusses Bidirectional PIM (BIDIR-PIM), a variant of PIM Sparse-Mode that builds bidirectional shared trees connecting multicast sources and receivers. Bidirectional trees are built using a fail-safe Designated Forwarder (DF) election mechanism operating on each link of a multicast topology. With the assistance of the DF, multicast data is natively forwarded from sources to the Rendezvous-Point (RP) and hence along the shared tree to receivers without requiring source-specific state. The DF election takes place at RP discovery time and provides the route to the RP, thus eliminating the requirement for data-driven protocol events. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.