Explicit Tracking with Wildcard Routes in Multicast VPN
RFC 8534

Changed author "Z. Zhang": changed name from "Zhaohui Zhang" to "Z. Zhang", changed affiliation from "Juniper Networks" to "Juniper Networks, Inc.", cleared country (was "United States of America"), changed order from "3" to "4"

Changed author "E. Rosen": changed name from "Eric Rosen" to "E. Rosen", changed is_editor from "False" to "True", changed affiliation from "Juniper Networks" to "Juniper Networks, Inc.", cleared country (was "United States of America"), changed order from "2" to "3"

Received changes through RFC Editor sync (created alias RFC 8534, changed title to 'Explicit Tracking with Wildcard Routes in Multicast VPN', changed abstract to 'The base Multicast VPN (MVPN) specifications (RFCs 6513 and 6514) 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, 7524, 7582, and 7900.', changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2019-02-19, changed IESG state to RFC Published, created updates relation between draft-ietf-bess-mvpn-expl-track and RFC 6514, created updates relation between draft-ietf-bess-mvpn-expl-track and RFC 6625, created updates relation between draft-ietf-bess-mvpn-expl-track and RFC 7524, created updates relation between draft-ietf-bess-mvpn-expl-track and RFC 7582, created updates relation between draft-ietf-bess-mvpn-expl-track and RFC 7900)