[Bier] RFC 9262 on Tree Engineering for Bit Index Explicit Replication (BIER-TE)

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

        RFC 9262

        Title:      Tree Engineering for Bit Index 
                    Explicit Replication (BIER-TE) 
        Author:     T. Eckert, Ed.,
                    M. Menth,
                    G. Cauchie
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2022
        Mailbox:    tte@cs.fau.de,
                    menth@uni-tuebingen.de,
                    gregory@koevoo.tech
        Pages:      43
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-bier-te-arch-13.txt

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

        DOI:        10.17487/RFC9262

This memo describes per-packet stateless strict and loose path
steered replication and forwarding for "Bit Index Explicit
Replication" (BIER)  packets (RFC 8279); it is called "Tree
Engineering for Bit Index Explicit Replication" (BIER-TE) and is
intended to be used as the path steering mechanism for Traffic
Engineering with BIER.

BIER-TE introduces a new semantic for "bit positions" (BPs). These
BPs indicate adjacencies of the network topology, as opposed to
(non-TE) BIER in which BPs indicate "Bit-Forwarding Egress Routers"
(BFERs).  A BIER-TE "packets BitString" therefore indicates the edges
of the (loop-free) tree across which the packets are forwarded by
BIER-TE. BIER-TE can leverage BIER forwarding engines with little
changes. Co-existence of BIER and BIER-TE forwarding in the same
domain is possible -- for example, by using separate BIER
"subdomains" (SDs). Except for the optional routed adjacencies,
BIER-TE does not require a BIER routing underlay and can therefore
operate without depending on a routing protocol such as the "Interior
Gateway Protocol" (IGP).

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