Traffic Engineering for Bit Index Explicit Replication BIER-TE
draft-eckert-bier-te-arch-04
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
---|---|---|---|
Authors | Toerless Eckert , Gregory Cauchie , Wolfgang Braun , Michael Menth | ||
Last updated | 2017-01-09 (Latest revision 2016-07-08) | ||
Replaced by | draft-ietf-bier-te-arch, draft-ietf-bier-te-arch, draft-ietf-bier-te-arch, RFC 9262 | ||
RFC stream | (None) | ||
Formats | |||
Additional resources | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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.
Authors
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.)