Traffic Engineering for Bit Index Explicit Replication BIER-TE

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Last updated 2017-01-09 (latest revision 2016-07-08)
Replaced by draft-ietf-bier-te-arch
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


This document proposes an architecture for BIER-TE: Traffic Engineering for Bit Index Explicit Replication (BIER). BIER-TE shares part of its architecture with BIER as described in [I-D.ietf-bier-architecture]. It also proposes to share the packet format with BIER. BIER-TE forwards and replicates packets like BIER based on a BitString in the packet header but it does not require an IGP. It does support traffic engineering by explicit hop-by-hop forwarding and loose hop forwarding of packets. It does support Fast ReRoute (FRR) for link and node protection and incremental deployment. Because BIER-TE like BIER operates without explicit in-network tree- building but also supports traffic engineering, it is more similar to SR than RSVP-TE.


Toerless Eckert (
Gregory Cauchie (
Wolfgang Braun (
Michael Menth (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)