RFC 8444: OSPFv2 Extensions for Bit Index Explicit Replication (BIER)
In plain English — editorial summary, not part of the RFC
Bit Index Explicit Replication (BIER) is an architecture that provides optimal multicast forwarding through a "BIER domain" without requiring intermediate routers to maintain multicast-related, per- flow state. BIER also does not require an explicit tree-building protocol for its operation. A multicast data packet enters a BIER domain at a Bit-Forwarding Ingress Router (BFIR) and leaves the BIER domain at one or more Bit-Forwarding Egress Routers (BFERs). The BFIR adds a BIER packet header to the packet. The BIER packet header contains a BitString in which each bit represents exactly one BFER to forward the packet to. The set of BFERs to which the multicast packet needs to be forwarded is expressed by the set of bits in the BIER packet header. This document describes the OSPF protocol extension (from RFC 2328) that is required for BIER with MPLS encapsulation (which is defined in RFC 8296). Support for other encapsulation types and the use of multiple encapsulation types are outside the scope of this document.
Document record
- Document ID
- RFC8444
- Published
- November 2018
- Authors
- P. Psenak; N. Kumar; IJ. Wijnands; A. Dolganow; T. Przygienda; J. Zhang; S. Aldrin
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 12
- Also known as
- —
- Updated by:
- RFC 9272
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8453Framework for Abstraction and Control of TE Networks (ACTN)Current
August 2018
- RFC 8454Information Model for Abstraction and Control of TE Networks (ACTN)Current
September 2018
- RFC 8432A Framework for Management and Control of Microwave and Millimeter Wave Interface ParametersCurrent
October 2018
- RFC 8431A YANG Data Model for the Routing Information Base (RIB)Current
September 2018
- RFC 8430RIB Information ModelCurrent
September 2018
- RFC 8459Hierarchical Service Function Chaining (hSFC)Current
September 2018
- RFC 8426Recommendations for RSVP-TE and Segment Routing (SR) Label Switched Path (LSP) CoexistenceCurrent
July 2018
- RFC 8424Extensions to RSVP-TE for Label Switched Path (LSP) Ingress Fast Reroute (FRR) ProtectionCurrent
August 2018
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?