RFC 9624 on EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Using Bit Index Explicit Replication (BIER)

rfc-editor@rfc-editor.org Sat, 31 August 2024 19:20 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
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 ietfa.amsl.com (Postfix) with ESMTPS id 58F40C14F5E8; Sat, 31 Aug 2024 12:20:49 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id C12517FA95; Sat, 31 Aug 2024 12:20:48 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9624 on EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Using Bit Index Explicit Replication (BIER)
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240831192048.C12517FA95@rfcpa.rfc-editor.org>
Date: Sat, 31 Aug 2024 12:20:48 -0700
Message-ID-Hash: FYZ6HKDPL75LS2JJNQSR2GPZJXWDT67K
X-Message-ID-Hash: FYZ6HKDPL75LS2JJNQSR2GPZJXWDT67K
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.9rc4
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/Hdd5_2N2195dFLbC8vI61eObhEE>
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 9624

        Title:      EVPN Broadcast, Unknown Unicast, or 
                    Multicast (BUM) Using Bit Index Explicit 
                    Replication (BIER) 
        Author:     Z. Zhang,
                    T. Przygienda,
                    A. Sajassi,
                    J. Rabadan
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2024
        Mailbox:    zzhang@juniper.net,
                    prz@juniper.net,
                    sajassi@cisco.com,
                    jorge.rabadan@nokia.com
        Pages:      13
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-bier-evpn-14.txt

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

        DOI:        10.17487/RFC9624

This document specifies protocols and procedures for forwarding
Broadcast, Unknown Unicast, or Multicast (BUM) traffic of Ethernet
VPNs (EVPNs) using Bit Index Explicit Replication (BIER).

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
Association Management Solutions, LLC