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

rfc-editor@rfc-editor.org Mon, 29 June 2026 23:49 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from celery-6fb6b66788-xmtjs (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 3E59010A47ED6; Mon, 29 Jun 2026 16:49:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1782776971; bh=2tkE1/Qj6UezaVT1OVPn74LoSWz20ovjUZbM++slTe4=; h=Subject:From:To:Cc:Date; b=Paa5rSCcDbIebi6IB/hpTrccVZdVNpqikZ0oUlUVe0Pi+Lrw51QF5LNCOPcfsNhwR rWphlyBqMJGdqhO4r/7nMweeLzFSdH12xNU56/VKVuy/msju+oJJ2Tj8w29cIo5nyN Yl7ol0vFE2Xe5hmbPYRu7WyCgGazcAVEc50UWn7I=
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: RFC 9974 on Operations, Administration, and Maintenance (OAM) Requirements for the Bit Index Explicit Replication (BIER) Layer
From: rfc-editor@rfc-editor.org
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Date: Mon, 29 Jun 2026 23:49:31 -0000
message-id: <178277697116.14.8730523213814010838@rfc-editor.org>
Message-ID-Hash: 4MX44SE3SN2XUZXAFCJRWW53SVOJ44FJ
X-Message-ID-Hash: 4MX44SE3SN2XUZXAFCJRWW53SVOJ44FJ
X-MailFrom: rfc-editor@rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: bier@ietf.org, rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/I0ZfJlwmttf9sD_m0eRHjEOiJTg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>

A new Request for Comments is now available in online RFC libraries.

        RFC 9974

        Title:      Operations, Administration, and Maintenance (OAM) Requirements 
                    for the Bit Index Explicit Replication (BIER) Layer
        Author:     G. Mirsky, Ed.,
                    N. Kumar,
                    M. Chen,
                    S. Pallagatti, Ed.
        Status:     Informational
        Stream:     IETF
        Date:       June 2026
        Mailbox:    gregimirsky@gmail.com,
                    nagendrakumar.nainar@gmail.com,
                    mach.chen@huawei.com,
                    santosh.pallagatti@gmail.com
        Pages:      9


        I-D Tag:    draft-ietf-bier-oam-requirements-21

        URL:        https://www.rfc-editor.org/info/rfc9974

        DOI:        10.17487/RFC9974

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 a product of the Bit Indexed Explicit Replication Working Group of the IETF.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search/
For downloading RFCs, see https://www.rfc-editor.org/series/rfc-download/

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team