OSPFv3 Extensions for BIER
draft-psenak-bier-ospfv3-extensions-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Peter Psenak , Nagendra Kumar Nainar , IJsbrand Wijnands | ||
| Last updated | 2018-05-03 (Latest revision 2017-10-30) | ||
| Replaced by | draft-ietf-bier-ospfv3-extensions | ||
| 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 provides optimal multicast forwarding through a "BIER domain" without requiring intermediate routers to maintain any multicast related per- flow state. BIER also does not require any explicit tree-building protocol for its operation. A multicast data packet enters a BIER domain at a "Bit-Forwarding Ingress Router" (BFIR), and leaves the BIER domain at one or more "Bit-Forwarding Egress Routers" (BFERs). The BFIR router adds a BIER header to the packet. The BIER header contains a bit-string in which each bit represents exactly one BFER to forward the packet to. The set of BFERs to which the multicast packet needs to be forwarded is expressed by setting the bits that correspond to those routers in the BIER header. This document describes the OSPFv3 protocol extensions required for BIER.
Authors
Peter Psenak
Nagendra Kumar Nainar
IJsbrand Wijnands
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)