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

internet-drafts@ietf.org Mon, 25 April 2022 23:35 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: bier@ietf.org
Subject: I-D Action: draft-ietf-bier-te-arch-13.txt
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: bier@ietf.org
Message-ID: <165092973546.575.5032839855293220014@ietfa.amsl.com>
Date: Mon, 25 Apr 2022 16:35:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/i-d-announce/gYqT_NtW9N-bdpoT55k6A9bytNk>

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Bit Indexed Explicit Replication WG of the IETF.

        Title           : Tree Engineering for Bit Index Explicit Replication (BIER-TE)
        Authors         : Toerless Eckert
                          Michael Menth
                          Gregory Cauchie
	Filename        : draft-ietf-bier-te-arch-13.txt
	Pages           : 65
	Date            : 2022-04-25

Abstract:
   This memo describes per-packet stateless strict and loose path
   steered replication and forwarding for "Bit Index Explicit
   Replication" (BIER, RFC8279) packets.  It is called BIER Tree
   Engineering (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" (BP).  They
   indicate adjacencies of the network topology, as opposed to (non-TE)
   BIER in which BPs indicate "Bit-Forwarding Egress Routers" (BFER).  A
   BIER-TE packets BitString therefore indicates the edges of the (loop-
   free) tree that the packet is forwarded across 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 "sub-domains" (SDs).
   Except for the optional routed adjacencies, BIER-TE does not require
   a BIER routing underlay, and can therefore operate without depending
   on an "Interior Gateway Routing protocol" (IGP).


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-bier-te-arch/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-bier-te-arch-13

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-bier-te-arch-13


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts

I-D Action: draft-ietf-bier-te-arch-13.txt internet-drafts