The Resilience for BIER
draft-xiong-bier-resilience-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Quan Xiong , fangwei hu , Greg Mirsky | ||
| Last updated | 2018-09-05 (Latest revision 2018-03-04) | ||
| 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
Bit Index Explicit Replication (BIER) is an architecture that specifies a solution for the forwarding of multicast data packets. In some scenarios, the resilience should be provided to guarantee the multicast data be protected by a given backup resource and forwarded successfully to the receivers in BIER-specific network. This document discusses the resilience use cases, requirements and proposes solutions for BIER, including the protection mechanisms and detection methods.
Authors
Quan Xiong
fangwei hu
Greg Mirsky
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)