Traffic Engineering for Bit Index Explicit Replication (BIER-TE)
This is an older version of an Internet-Draft that was ultimately published as RFC 9262.
Expired & archived
|Authors||Toerless Eckert , Gregory Cauchie , Wolfgang Braun , Michael Menth|
|Last updated||2018-07-27 (Latest revision 2018-01-23)|
|RFC stream||Internet Engineering Task Force (IETF)|
GENART Last Call review (of -10) by Robert Sparks Ready with Nits
|Additional resources||Mailing list discussion|
|Stream||WG state||WG Document|
|Send notices to||(None)|
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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 [RFC8279]. 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.
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)