metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 5015: Bidirectional Protocol Independent Multicast (BIDIR-PIM)

Still current, but amended. Parts of this document are changed or extended by RFC 8736, RFC 9436. Read both.

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

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]

Document record

Document ID
RFC5015
Published
October 2007
Authors
M. Handley; I. Kouvelas; T. Speakman; L. Vicisano
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
43
Also known as
—
Updated by:
RFC 8736, RFC 9436

Topics

Referenced by

2 later RFCs formally update or obsolete part of this document.

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/5015-bidirectional-protocol-independent-multicast-bidir-pim