Multicast in SR Networks
draft-zzhang-pim-sr-multicast-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Zhaohui (Jeffrey) Zhang , IJsbrand Wijnands , Andrew Dolganow , Liang Geng | ||
| Last updated | 2019-02-16 (Latest revision 2018-08-15) | ||
| Replaced by | draft-zzhang-mboned-non-source-routed-sr-mcast | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-zzhang-mboned-non-source-routed-sr-mcast | |
| 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
With Segment Routing (SR) architecture [rfc8402], a unicast flow can be routed through an SR network following an explicit path specified in the packet, w/o the need for per-flow state in the network. As a result, the otherwise needed protocols to signal the per-flow unicast state can also be removed from the network. This document discusses options for multicast in an SR network.
Authors
Zhaohui (Jeffrey) Zhang
IJsbrand Wijnands
Andrew Dolganow
Liang Geng
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)