Internet-Draft | OAM Requirements for BIER | November 2024 |
Mirsky, et al. | Expires 8 May 2025 | [Page] |
This document describes a list of functional requirements toward Operations, Administration and Maintenance (OAM) toolset in Bit Index Explicit Replication (BIER) layer of a network.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 8 May 2025.¶
Copyright (c) 2024 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] introduces and explains Bit Index Explicit Replication (BIER) architecture and how it supports forwarding of multicast data packets.¶
This document lists the OAM requirements for the BIER layer of the multicast domain. The list can further be used for gap analysis of available OAM tools to identify possible enhancements of existing or whether new OAM tools are required to support proactive and on-demand path monitoring and service validation.¶
The term "BIER OAM" used in this document interchangeably with longer version "set of OAM protocols, methods, and tools for BIER layer".¶
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.¶
BFR: Bit-Forwarding Router¶
BFER: Bit-Forwarding Egress Router¶
BIER: Bit Index Explicit Replication¶
OAM: Operations, Administration and Maintenance¶
This section lists the requirements for OAM of the BIER layer:¶
This document does not propose any IANA consideration. This section may be removed.¶
This document lists the OAM requirement for a BIER-enabled domain and thus inherits security considerations discussed in [RFC8279] and [RFC8296]. Another general security aspect results from using active OAM protocols, according to the [RFC7799], in a multicast network. Active OAM protocols inject specially constructed test packets, and some active OAM protocols are based on the echo request/reply principle. In the multicast network, test packets are replicated as data packets, thus creating a possible amplification effect of multiple echo responses being transmitted to the sender of the echo request. Thus, an implementation of BIER OAM MUST protect the control plane from spoofed replies. Also, an implementation of BIER OAM MUST provide control of the number of BIER OAM messages sent to the control plane.¶