RFC 8534

Explicit Tracking with Wildcard Routes in Multicast VPN, February 2019

Canonical URL:
https://www.rfc-editor.org/rfc/rfc8534.txt
File formats:
Plain TextPDF HTML
Status:
PROPOSED STANDARD
Updates:
RFC 6514, RFC 6625, RFC 7524, RFC 7582, RFC 7900
Authors:
A. Dolganow
J. Kotalwar
E. Rosen, Ed.
Z. Zhang
Stream:
IETF
Source:
bess (rtg)

Cite this RFC: TXT  |  XML

DOI:  10.17487/RFC8534

Discuss this RFC: Send questions or comments to bess@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF


Abstract

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.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Download PDF Reader