Explicit Tracking with Wild Card Routes in Multicast VPN
draft-dolganow-bess-mvpn-expl-track-02

Document Type Replaced Internet-Draft (bess WG)
Last updated 2016-06-05 (latest revision 2016-02-16)
Replaced by draft-ietf-bess-mvpn-expl-track
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state Adopted by a WG
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-bess-mvpn-expl-track
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-dolganow-bess-mvpn-expl-track-02.txt

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 (andrew.dolganow@alcatel-lucent.com)
Jayant Kotalwar (jayant.kotalwar@alcatel-lucent.com)
Eric Rosen (erosen@juniper.net)
Zhaohui Zhang (zzhang@juniper.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)