| RFC 9974 | OAM Requirements for BIER | May 2026 |
| Mirsky, et al. | Informational | [Page] |
This document specifies a list of functional requirements for Operations, Administration, and Maintenance mechanisms, protocols, and tools that support operations in the Bit Index Explicit Replication layer of a network.¶
This document is not an Internet Standards Track specification; it is published for informational purposes.¶
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are candidates for any level of Internet Standard; see Section 2 of RFC 7841.¶
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc9974.¶
Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
[RFC8279] specifies a Bit Index Explicit Replication (BIER) architecture and how it supports forwarding of multicast data packets.¶
This document lists the Operations, Administration, and Maintenance (OAM) requirements for the BIER layer (see Section 4.2 of [RFC8279]) of the multicast domain. The list can further be used for gap analysis of available OAM tools to identify whether possible enhancements of existing or new OAM tools are required to support proactive and on-demand path monitoring and service validation.¶
The reader is expected to be familiar with:¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
The requirements language is used in Section 2 and applies to implementations of BIER OAM conformant to the listed requirements.¶
This section lists the requirements for OAM of the BIER layer:¶
BIER OAM MUST support the ability of any BFR in the given BIER domain to proactively monitor Bit-Forwarding Egress Router (BFER) availability.¶
This requirement provides helpful clarification to the combination of Requirements 2 and 4. The P2MP BFD with active tail support [RFC9780] is an example of a protocol that provides notifications about the loss of connectivity in a multicast distribution tree.¶
BIER OAM MUST support downstream path continuity checking.¶
Bidirectional Forwarding Detection (BFD) [RFC8562] is an example of a protocol that monitors the continuity of a multicast distribution tree.¶
BIER OAM MUST support downstream performance measurement.¶
Simple Two-way Active Measurement Protocol (STAMP) [RFC8762] is an example of a protocol that supports measurement of performance metrics, e.g., packet loss ratio, delay, and delay variation.¶
In the downstream direction, a BIER OAM solution MUST support transmission of OAM packets to traverse the same set of nodes and links and receive the same forwarding treatment (including QoS) as the monitored BIER flow.¶
In some cases, e.g., when monitoring a composite data flow that includes several sub-flows characterized by different Class-of-Service (CoS) marking, an operator may choose to monitor the continuity of the path at the highest CoS, not at every CoS value in the data flow. In that case, BIER OAM packets traverse the same set of nodes and links as the composite data flow while receiving the same forwarding treatment as the highest CoS sub-flow. In this scenario, the state of path continuity for lower CoS sub-flows can be derived from the state of the highest CoS, as determined by the BIER OAM protocol performing continuity verification (e.g., BFD).¶
BIER OAM MUST support bidirectional OAM methods. In the downstream direction, these methods of monitoring or measurement MUST conform to Requirement 11. In the reverse direction (i.e., from the egress toward the ingress endpoint of the BIER OAM test session), BIER OAM packets MAY deviate from traversing the same set of nodes and links, or receive a different forwarding treatment (including QoS) as the monitored BIER flow.¶
Point-to-Multipoint (P2MP) BFD with active tail [RFC9780] is an example of the bidirectional mechanism of continuity checking.¶
BIER OAM MUST support Path Maximum Transmission Unit Discovery (PMTUD).¶
The PMTUD using ICMP [RFC1191] is an example of the mechanism.¶
BIER OAM MUST support an RDI mechanism to notify the BFR, the source of the continuity checking by BFERs.¶
The Diagnostic field in P2MP BFD with active tail support, as described in Section 5 of [RFC9780], is an example of the RDI mechanism.¶
BIER OAM MUST support downstream performance measurement method(s) that (together) calculate performance metrics, e.g., throughput, loss, delay, and delay variation metrics [RFC6374].¶
STAMP ([RFC8762] and [RFC8972]) is an example of an active performance measurement method of performance metrics that may be applied in a BIER domain. The Alternate-Marking Method, described in [RFC9341] and [RFC9342], is an example of a hybrid measurement method [RFC7799] that may be applied in a BIER domain.¶
BIER OAM MUST support defect notification mechanism(s).¶
Alarm Indication Signal [RFC6427] is an example of the defect notification mechanism.¶
BIER OAM MUST support a way for any BFR in the given BIER domain to originate a fault management message addressed to any subset of BFRs within the domain.¶
[RFC6427] provides an example of a Fault Management messaging mechanism.¶
BIER OAM MUST support methods to enable the survivability of a BIER layer.¶
Protection switching and restoration are examples of survivability methods.¶
This document has no IANA actions.¶
This document lists the OAM requirements for a BIER-enabled domain and it thus inherits the security considerations discussed in [RFC8279] and [RFC8296]. Another general security aspect results from using active OAM protocols [RFC7799] in a multicast network.¶
Active OAM protocols inject specially constructed test packets. Some active OAM protocols are based on the echo request/reply principle of using those test packets. In the multicast network, test packets are replicated as data packets, thus creating a possible amplification effect of multiple echo replies being transmitted to the sender of the echo request. Therefore, the following security-related requirements are defined for BIER OAM:¶
The authors would like to thank Gunter van de Velde for the comments and suggestions that helped improve this document.¶