BIER-TE Fast ReRoute
draft-chen-bier-te-frr-05
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Huaimo Chen , Mike McBride , Yisong Liu , Aijun Wang , Gyan Mishra , Yanhe Fan , Lei Liu , Xufeng Liu | ||
| Last updated | 2024-01-31 (Latest revision 2023-07-30) | ||
| 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 re-route (FRR) protection against the failure of a transit node or link on an explicit point to multipoint (P2MP) multicast path/tree in a "Bit Index Explicit Replication" (BIER) Traffic Engineering (TE) domain. It does not have any per-path state in the core. For a multicast packet to traverse a transit node along an explicit P2MP path, when the node fails, its upstream hop node as a PLR reroutes the packet around the failed node along the P2MP path once it detects the failure.
Authors
Huaimo Chen
Mike McBride
Yisong Liu
Aijun Wang
Gyan Mishra
Yanhe Fan
Lei Liu
Xufeng Liu
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)