Multicast Using Bit Index Explicit Replication
RFC 8279, “Multicast Using Bit Index Explicit Replication”, is a Proposed Standard document published in November 2017 by IJ. Wijnands, E. Rosen, A. Dolganow, T. Przygienda, S. Aldrin. The canonical text is published by the RFC Editor.
Abstract
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8279 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8280 Research into Human Rights Protocol Considerations
- RFC 8277 Using BGP to Bind MPLS Labels to Address Prefixes
- RFC 8281 Path Computation Element Communication Protocol Extensions for PCE-Initiated LSP Setup in a Stateful PCE Model
- RFC 8276 File System Extended Attributes in NFSv4
- RFC 8282 Extensions to the Path Computation Element Communication Protocol for Inter-Layer MPLS and GMPLS Traffic Engineering
- RFC 8275 Allowing Inheritable NFSv4 Access Control Entries to Override the Umask
- RFC 8283 An Architecture for Use of PCE and the PCE Communication Protocol in a Network with Central Control
- RFC 8274 Incident Object Description Exchange Format Usage Guidance