MVPN/EVPN C-Multicast Routes Enhancements
draft-zzhang-bess-mvpn-evpn-cmcast-enhancements-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2019-09-12 (latest revision 2019-03-11) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-zzhang-bess-mvpn-evpn-cmcast-enhancements-01.txt
Abstract
[RFC6513] and [RFC6514] specify procedures for originating, propagating, and processing "C-multicast routes". However, there are a number of MVPN use cases that are not properly or optimally handled by those procedures. This document describes those use cases, and specifies the additional procedures needed to handle them. Some of the additional procedures are also applicable to EVPN SMET routes [I- D.ietf-bess-evpn-igmp-mld-proxy].
Authors
Zhaohui Zhang
(zzhang@juniper.net)
Robert Kebler
(rkebler@juniper.net)
Wen Lin
(wlin@juniper.net)
Eric Rosen
(erosen52@gmail.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)