RFC 9793 on BGP Extensions for Bit Index Explicit Replication (BIER)
rfc-editor@rfc-editor.org Fri, 13 June 2025 17:47 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id BB57B34B0278; Fri, 13 Jun 2025 10:47:16 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 8F5D2265CF2; Fri, 13 Jun 2025 10:47:16 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9793 on BGP Extensions for Bit Index Explicit Replication (BIER)
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20250613174716.8F5D2265CF2@rfcpa.rfc-editor.org>
Date: Fri, 13 Jun 2025 10:47:16 -0700
Message-ID-Hash: 5GUNWIYLFXP6WBQGKLGXCJMU6COR5AU2
X-Message-ID-Hash: 5GUNWIYLFXP6WBQGKLGXCJMU6COR5AU2
X-MailFrom: wwwrun@rfcpa.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: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, bier@ietf.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/6p9o33k04gWRz2H0oIpCLrHyH24>
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 9793 Title: BGP Extensions for Bit Index Explicit Replication (BIER) Author: X. Xu, M. Chen, K. Patel, IJ. Wijnands, T. Przygienda, Z. Zhang, Ed. Status: Standards Track Stream: IETF Date: June 2025 Mailbox: xuxiaohu@cmss.chinamobile.com, mach.chen@huawei.com, keyur@arrcus.com, ice@braindump.be, prz@juniper.net, zzhang@juniper.net Pages: 12 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-bier-idr-extensions-19.txt URL: https://www.rfc-editor.org/info/rfc9793 DOI: 10.17487/RFC9793 Bit Index Explicit Replication (BIER) is a multicast forwarding architecture that doesn't require an explicit tree-building protocol and doesn't require intermediate routers to maintain per-tree multicast states. Some BIER-specific information and states, which are only in proportion to the number of BIER routers but not per-tree, do need to be advertised, calculated, and maintained. This document describes BGP extensions for advertising the BIER information and methods for calculating BIER states based on the advertisements. This document is a product of the Bit Indexed Explicit Replication Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. 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/retrieve/bulk 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