metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC8534
Published
February 2019
Authors
A. Dolganow; J. Kotalwar; E. Rosen; Z. Zhang
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
21
Also known as
—
Updates:
RFC 6514, RFC 6625, RFC 7524, RFC 7582, RFC 7900

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/8534-explicit-tracking-with-wildcard-routes-in-multicast-vpn