SRv6 Multicast: Approaches and Impacts to SRv6 Architecture
draft-xie-spring-srv6-multicast-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jingrong Xie , Xuesong Geng | ||
| Last updated | 2023-09-09 (Latest revision 2023-03-08) | ||
| 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
Multicast was not originally supported with SR, as indicated in [RFC8402]: Segment Routing is defined for unicast. However, with the wide development and deployment of SR and SRv6 technology, there have been proposals to develop SR-based multicast solutions, showing the interests to develop multicast solutions that facilitate incremental deployment based on SR and SRv6. This document examines two typical SRv6 multicast approaches and considers a number of different aspects to provide a framework for understanding. The purpose is to help the working group and IETF community to understand and thus evaluate these possible impacts.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)