RFC 9624: EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Using Bit Index Explicit Replication (BIER)
In plain English — editorial summary, not part of the RFC
This document specifies protocols and procedures for forwarding Broadcast, Unknown Unicast, or Multicast (BUM) traffic of Ethernet VPNs (EVPNs) using Bit Index Explicit Replication (BIER).
Document record
- Document ID
- RFC9624
- Published
- August 2024
- Authors
- Z. Zhang; T. Przygienda; A. Sajassi; J. Rabadan
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 13
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9625EVPN Optimized Inter-Subnet Multicast (OISM) ForwardingCurrent
August 2024
- RFC 9616Delay-Based Metric Extension for the Babel Routing ProtocolCurrent
September 2024
- RFC 9633Deterministic Networking (DetNet) YANG Data ModelCurrent
October 2024
- RFC 9634Operations, Administration, and Maintenance (OAM) for Deterministic Networking (DetNet) with the IP Data PlaneCurrent
October 2024
- RFC 9613Requirements for Solutions that Support MPLS Network Actions (MNAs)Current
August 2024
- RFC 9612Bidirectional Forwarding Detection (BFD) Reverse Path for MPLS Label Switched Paths (LSPs)Current
July 2024
- RFC 9638Network Virtualization over Layer 3 (NVO3) Encapsulation ConsiderationsCurrent
September 2024
- RFC 9604Carrying Binding Label/SID in PCE-Based NetworksUpdated
August 2024
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?