Non-source-routed Multicast in SR Networks
draft-zzhang-mboned-non-source-routed-sr-mcast-01
| Document | Type |
Replaced Internet-Draft
(mboned WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Zhaohui (Jeffrey) Zhang , IJsbrand Wijnands , Hooman Bidgoli , Yisong Liu | ||
| Last updated | 2025-03-10 (Latest revision 2024-12-16) | ||
| Replaces | draft-zzhang-pim-non-source-routed-sr-mcast, draft-zzhang-pim-sr-multicast | ||
| Replaced by | draft-ietf-mboned-non-source-routed-sr-mcast | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-mboned-non-source-routed-sr-mcast | |
| Consensus boilerplate | Unknown | ||
| 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, a unicast flow can be source- 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. In the case of multicast, traffic can be either source-routed or non-source-routed, and this document discusses non-sourced-routed options for multicast in an SR network with either MPLS or IPv6/SRv6 data plane.
Authors
Zhaohui (Jeffrey) Zhang
IJsbrand Wijnands
Hooman Bidgoli
Yisong Liu
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)