Explicit Tracking with Wild Card Routes in Multicast VPN
draft-dolganow-bess-mvpn-expl-track-02
| Document | Type |
Replaced Internet-Draft
(bess WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Andrew Dolganow , Jayant Kotalwar , Eric C. Rosen , Zhaohui (Jeffrey) Zhang | ||
| Last updated | 2016-06-05 (Latest revision 2016-02-16) | ||
| Replaced by | draft-ietf-bess-mvpn-expl-track | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-bess-mvpn-expl-track | |
| 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
The MVPN specifications provide procedures to allow a multicast ingress node to invoke "explicit tracking" for a multicast flow or set of flows, thus learning the egress nodes for that flow or set of flows. However, the specifications are not completely clear about how the explicit tracking procedures work in certain scenarios. This document provides the necessary clarifications. It also specifies a new, optimized explicit tracking procedure. This new procedure allows an ingress node, by sending a single message, to request explicit tracking of each of a set of flows, where the set of flows is specified using a wildcard mechanism. This document updates RFC6625.
Authors
Andrew Dolganow
Jayant Kotalwar
Eric C. Rosen
Zhaohui (Jeffrey) Zhang
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)