Designed Routing in BIER Forwarding
draft-zhang-bier-designed-routing-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Zheng Zhang , Bo Wu | ||
| Last updated | 2016-05-04 (Latest revision 2015-11-01) | ||
| RFC stream | (None) | ||
| Intended RFC status | (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 specifies a new architecture for the forwarding of multicast data packets. As the [I-D.ietf-bier-architecture] said, in the BIER domain, it does not require a protocol for explicitly building multicast distributing trees, nor does it require intermediate nodes to maintain any per-flow state. In some deployments, some specific multicast flows may be forwarded by special routing; it cannot be achieved by the forwarding rule that is provided. In this document we will defined a new routing list in BIER header, the packets will be steered according to the routing list.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)