Skip to main content

Encapsulation for Bit Index Explicit Replication (BIER) in MPLS and Non-MPLS Networks
RFC 8296

Revision differences

Document history

Date By Action
2019-02-22
(System) Received changes through RFC Editor sync (added Errata tag)
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/
2018-01-12
(System) IANA registries were updated to include RFC8296
2018-01-12
(System)
Received changes through RFC Editor sync (created alias RFC 8296, changed title to 'Encapsulation for Bit Index Explicit Replication (BIER) in MPLS and Non-MPLS …
Received changes through RFC Editor sync (created alias RFC 8296, changed title to 'Encapsulation for Bit Index Explicit Replication (BIER) in MPLS and Non-MPLS Networks', changed abstract to 'Bit Index Explicit Replication (BIER) is an architecture that provides optimal multicast forwarding through a "multicast domain", without requiring intermediate routers to maintain any per-flow state or to engage in an explicit tree-building protocol.  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 details of the encapsulation depend on the type of network used to realize the multicast domain.  This document specifies a BIER encapsulation that can be used in an MPLS network or, with slight differences, in a non-MPLS network.', changed pages to 24, changed standardization level to Experimental, changed state to RFC, added RFC published event at 2018-01-12, changed IESG state to RFC Published)
2018-01-12
(System) RFC published