BIER Egress Protection
draft-chen-bier-egress-protect-04
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Huaimo Chen , Mike McBride , Aijun Wang , Gyan Mishra , Yisong Liu , Michael Menth , Boris Khasanov , Xuesong Geng , Yanhe Fan , Lei Liu , Xufeng Liu | ||
| Last updated | 2023-06-25 (Latest revision 2022-12-22) | ||
| RFC stream | (None) | ||
| Formats | |||
| 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 describes a mechanism for fast protection against the failure of an egress node of a "Bit Index Explicit Replication" (BIER) domain. It is called BIER egress protection. It does not require any per-flow state in the core of the domain. With BIER egress protection the failure of a primary BFER (Bit Forwarding Egress Router) is protected with a backup BFER such that traffic destined to the primary BFER in the BIER domain is fast rerouted by a neighbor BFR to the backup BFER on the BIER layer. The mechanism is applicable if all BIER traffic sent to the primary BFER can reach its destination also via the backup BFER. It is complementary to BIER- FRR which cannot protect against the failure of a BFER.
Authors
Huaimo Chen
Mike McBride
Aijun Wang
Gyan Mishra
Yisong Liu
Michael Menth
Boris Khasanov
Xuesong Geng
Yanhe Fan
Lei Liu
Xufeng Liu
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)