[Bier] RFC 9272 on Underlay Path Calculation Algorithm and Constraints for Bit Index Explicit Replication (BIER)

rfc-editor@rfc-editor.org Sat, 10 September 2022 00:00 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 53A6BC1533AF; Fri, 9 Sep 2022 17:00:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.657
X-Spam-Status: No, score=-1.657 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id R28XRAYvRRrx; Fri, 9 Sep 2022 17:00:15 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org []) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 006CCC157B45; Fri, 9 Sep 2022 17:00:14 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 9CB4AF5A58; Fri, 9 Sep 2022 17:00:14 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, bier@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20220910000014.9CB4AF5A58@rfcpa.amsl.com>
Date: Fri, 09 Sep 2022 17:00:14 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/eVij7BDxX4X9dNZM0eIqqBcsUNg>
Subject: [Bier] RFC 9272 on Underlay Path Calculation Algorithm and Constraints for Bit Index Explicit Replication (BIER)
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <bier.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bier>, <mailto:bier-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bier/>
List-Post: <mailto:bier@ietf.org>
List-Help: <mailto:bier-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bier>, <mailto:bier-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Sep 2022 00:00:19 -0000

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

        RFC 9272

        Title:      Underlay Path Calculation Algorithm and Constraints
                    for Bit Index Explicit Replication (BIER) 
        Author:     Z. Zhang,
                    T. Przygienda,
                    A. Dolganow,
                    H. Bidgoli,
                    IJ. Wijnands,
                    A. Gulko
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2022
        Mailbox:    zzhang@juniper.net,
        Pages:      6
        Updates:    RFC 8401, RFC 8444

        I-D Tag:    draft-ietf-bier-bar-ipa-13.txt

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

        DOI:        10.17487/RFC9272

This document specifies general rules for the interaction between the
BIER Algorithm (BAR) and the IGP Algorithm (IPA) used for underlay
path calculation within the Bit Index Explicit Replication (BIER)
architecture.  The semantics defined in this document update RFC 8401
and RFC 8444.  This document also updates the "BIER Algorithm"
registry established in RFC 8401.

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

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