%% You should probably cite rfc8534 instead of this I-D. @techreport{ietf-bess-mvpn-expl-track-09, number = {draft-ietf-bess-mvpn-expl-track-09}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-bess-mvpn-expl-track/09/}, author = {Andrew Dolganow and Jayant Kotalwar and Eric C. Rosen and Zhaohui (Jeffrey) Zhang}, title = {{Explicit Tracking with Wild Card Routes in Multicast VPN}}, pagetotal = 18, year = 2018, month = apr, day = 19, 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 RFCs 6514, 6625, and 7524.}, }