Operations, Administration and Maintenance (OAM) Requirements for Bit Index Explicit Replication (BIER) Layer

Status of This Memo

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 11 February 2024.¶

Copyright Notice

Copyright (c) 2023 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.¶

Table of Contents

1. Introduction

[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.¶

2. Requirements

This section lists the requirements for OAM of the BIER layer:¶

1. The listed requirements MUST be supported with any transport layer over which the BIER layer can be realized.¶
2. It MUST be possible to initialize a BIER OAM session from any Bit-Forwarding Router (BFR) of the given BIER domain.¶
3. It SHOULD be possible to initialize a BIER OAM session from a centralized controller.¶
4. BIER OAM MUST support proactive and on-demand OAM monitoring and measurement methods.¶
5. BIER OAM MUST support unidirectional OAM methods, both continuity check and performance measurement.¶
6. BIER OAM packets MUST be in-band, i.e., follow exactly the same path as data plane traffic, in the forward direction, i.e., from ingress toward egress endpoint(s) of the OAM test session.¶
7. BIER OAM MUST support bi-directional OAM methods. Such OAM methods MAY combine in-band monitoring or measurement in the forward direction and out-of-band notification in the reverse direction, i.e., from egress to ingress end point of the OAM test session.¶
8. BIER OAM MUST support proactive monitoring of BFER availability by a BFR in the given BIER domain, e.g., p2mp BFD active tail support.¶
9. BIER OAM MUST support Path Maximum Transmission Unit discovery.¶
10. BIER OAM MUST support Reverse Defect Indication (RDI) notification of the source of continuity checking BFR by Bit-Forwarding Egress Routers (BFERs), e.g., by using Diag in p2mp BFD with active tail support.¶
11. BIER OAM MUST support active and passive performance measurement methods.¶
12. BIER OAM MUST support unidirectional performance measurement methods to calculate throughput, loss, delay, and delay variation metrics. [RFC6374] provides great details for performance measurement and performance metrics.¶
13. BIER OAM MUST support defect notification mechanism, like Alarm Indication Signal. Any BFR in the given BIER domain MAY originate a defect notification addressed to any subset of BFRs within the domain.¶
14. BIER OAM MUST support methods to enable the survivability of a BIER layer. These recovery methods MAY use protection switching and restoration.¶

3. IANA Considerations

This document does not propose any IANA consideration. This section may be removed.¶

4. Security Considerations

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.¶

Contributors' Addresses

Authors' Addresses