BIER with Anycast
draft-zzhang-bier-anycast-02
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Zhaohui (Jeffrey) Zhang , IJsbrand Wijnands , Zheng Zhang , Mankamana Prasad Mishra , Huaimo Chen | ||
| Last updated | 2023-09-12 (Latest revision 2023-03-11) | ||
| 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
BIER architecture currently does not support anycast, in that each BIER Forwarding Router (BFR) has its own unique BFR-prefix and BFR- ID. BIER signaling protocols also check if there are duplicate BFR- IDs advertised. This document discusses and specifies anycast support with BIER. It updates RFC 8279, RFC 8401 and RFC 8444.
Authors
Zhaohui (Jeffrey) Zhang
IJsbrand Wijnands
Zheng Zhang
Mankamana Prasad Mishra
Huaimo Chen
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)