RFC 8293: A Framework for Multicast in Network Virtualization over Layer 3
In plain English — editorial summary, not part of the RFC
This document provides a framework for supporting multicast traffic in a network that uses Network Virtualization over Layer 3 (NVO3). Both infrastructure multicast and application-specific multicast are discussed. It describes the various mechanisms that can be used for delivering such traffic as well as the data plane and control plane considerations for each of the mechanisms.
Document record
- Document ID
- RFC8293
- Published
- January 2018
- Authors
- A. Ghanwani; L. Dunbar; M. McBride; V. Bannai; R. Krishnan
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8394Split Network Virtualization Edge (Split-NVE) Control-Plane RequirementsCurrent
May 2018
- RFC 7365Framework for Data Center (DC) Network VirtualizationCurrent
October 2014
- RFC 9469Applicability of Ethernet Virtual Private Network (EVPN) to Network Virtualization over Layer 3 (NVO3) NetworksCurrent
September 2023
- RFC 9638Network Virtualization over Layer 3 (NVO3) Encapsulation ConsiderationsCurrent
September 2024
- RFC 9721Extended Mobility Procedures for Ethernet VPN Integrated Routing and Bridging (EVPN-IRB)Current
April 2025
- RFC 8294Common YANG Data Types for the Routing AreaCurrent
December 2017
- RFC 8296Encapsulation for Bit Index Explicit Replication (BIER) in MPLS and Non-MPLS NetworksCurrent
January 2018
- RFC 8287Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data PlanesUpdated
December 2017
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?