Protection Methods for BIER-TE
draft-eckert-bier-te-frr-03

Document Type Expired Internet-Draft (individual)
Authors Toerless Eckert  , Gregory Cauchie  , Wolfgang Braun  , Michael Menth 
Last updated 2018-09-06 (latest revision 2018-03-05)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) 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
https://www.ietf.org/archive/id/draft-eckert-bier-te-frr-03.txt

Abstract

This document proposes protection methods for the BIER-TE architecture [I-D.ietf-bier-te-arch]. These include 1+1 (live-live) path/tree [RFC7431] redundancy, 1:1 path/tree protection, as well as fast reroute (FRR) methods. The latter may protect against link and/ or node failures and leverage infrastructure tunnels, BIER-in-BIER encapsulation, or header modification for implementation. In particular, this memo describes FRR for BIER-TE in detail. FRR for BIER-TE requires support from the BIER-TE controller and the BFRs that are attached to a link/adjacency for which FRR protection is desired. FRR relies on the BIER header described in [RFC8279] which is also used by BIER-TE. It does not require extensions or modifications to existing BIER-TE tables. However, the presented FRR procedures need some additional forwarding plane logic on the BFR. An additional table is needed that carries information about pre- computed backup paths. When a failure is detected, the information from this table is used to modify the bitstring in the BIER header before forwarding a packet over a backup path. To prevent undesired packet duplication, packets should be tunneled on the backup paths.

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.)