Traffic Engineering for Bit Index Explicit Replication (BIER-TE)
draft-ietf-bier-te-arch-00
| The information below is for an old version of the document | |||||
|---|---|---|---|---|---|
| Document | Type | Expired Internet-Draft (bier WG) | |||
| Last updated | 2018-07-27 (latest revision 2018-01-23) | ||||
| Replaces | draft-eckert-bier-te-arch | ||||
| Stream | IETF | ||||
| Intended RFC status | (None) | ||||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||||
| Additional URLs |
|
||||
| Stream | WG state | WG Document | |||
| Document shepherd | No shepherd assigned | ||||
| IESG | IESG state | Expired | |||
| Consensus Boilerplate | Unknown | ||||
| Telechat date | |||||
| Responsible AD | (None) | ||||
| Send notices to | (None) | ||||
https://www.ietf.org/archive/id/draft-ietf-bier-te-arch-00.txt
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 [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.
Authors
Toerless Eckert
(tte+ietf@cs.fau.de)
Gregory Cauchie
(gcauchie@bouyguestelecom.fr)
Wolfgang Braun
(wolfgang.braun@uni-tuebingen.de)
Michael Menth
(menth@uni-tuebingen.de)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)