Skip to main content

Multicast Using Bit Index Explicit Replication (BIER)
RFC 8279

Revision differences

Document history

Date By Action
2018-06-05
(System) Received changes through RFC Editor sync (changed standardization level to Proposed Standard)
2018-05-15
Amy Vezza New status of Proposed Standard approved by the IESG
https://datatracker.ietf.org/doc/status-change-bier-core-to-proposed-standard/
2017-11-20
(System)
Received changes through RFC Editor sync (created alias RFC 8279, changed title to 'Multicast Using Bit Index Explicit Replication (BIER)', changed abstract to 'This …
Received changes through RFC Editor sync (created alias RFC 8279, changed title to 'Multicast Using Bit Index Explicit Replication (BIER)', changed abstract to 'This document specifies a new architecture for the forwarding of multicast data packets.  It provides optimal forwarding of multicast packets through a "multicast domain".  However, it does not require a protocol for explicitly building multicast distribution trees, nor does it require intermediate nodes to maintain any per-flow state.  This architecture is known as "Bit Index Explicit Replication" (BIER).  When a multicast data packet enters the domain, the ingress router determines the set of egress routers to which the packet needs to be sent.  The ingress router then encapsulates the packet in a BIER header.  The BIER header contains a bit string in which each bit represents exactly one egress router in the domain; to forward the packet to a given set of egress routers, the bits corresponding to those routers are set in the BIER header.  The procedures for forwarding a packet based on its BIER header are specified in this document.  Elimination of the per-flow state and the explicit tree-building protocols results in a considerable simplification.', changed pages to 43, changed standardization level to Experimental, changed state to RFC, added RFC published event at 2017-11-20, changed IESG state to RFC Published)
2017-11-20
(System) RFC published