Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs)
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 28
- Abstract
- Network Virtualization Overlay (NVO) networks using Ethernet VPNs (EVPNs) as their control plane may use trees based on ingress replication or Protocol Independent Multicast (PIM) to convey the overlay Broadcast, Unknown Unicast, or Multicast (BUM) traffic. PIM provides an efficient solution that prevents sending multiple copies of the same packet over the same physical link; however, it may not always be deployed in the NVO network core. Ingress replication avoids the dependency on PIM in the NVO network core. While ingress replication provides a simple multicast transport, some NVO networks with demanding multicast applications require a more efficient solution without PIM in the core. This document describes a solution to optimize the efficiency of ingress replication trees.
- Publication Date
- 2024-05-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC9574- Link
- https://doi.org/10.17487/RFC9574
- Author(s)
- Jorge RabadanSenthil SathappanWen LinMukul KatiyarAli Sajassi
- Keyword(s)
- Assisted Replication, AR, AR-Replicator, Pruned Flood List, Pruned Flooding List
Latest version of IETF RFC 9574
Document Versions — IETF RFC 9574
-
▶ IETF RFC 9574 (2024-05-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 6513 [Active*]
- IETF RFC 6514 [Active*]
- IETF RFC 7432 [Active*]
- IETF RFC 7902 [Active*]
- IETF RFC 8174 [Active*]
- IETF RFC 8365 [Active*]
- IETF RFC 9572 [Active*]
Bibliographic Reference(s)
- IETF RFC 4023 [Active*]
- IETF RFC 7348 [Active*]
- IETF RFC 7637 [Active*]
- IETF RFC 9161 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC9574.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 9574, Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs). Available at https://doi.org/10.17487/RFC9574
Snippet:
IETF RFC 9574, Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs). Available at https://doi.org/10.17487/RFC9574
HTML (ISO 690 compliant)
Preview:
IETF RFC 9574, Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs). Available at https://doi.org/10.17487/RFC9574
Snippet:
<span class="citation"><cite>IETF RFC 9574</cite>, Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs). Available at <a href="https://doi.org/10.17487/RFC9574" target="_blank" rel="noopener">https://doi.org/10.17487/RFC9574</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 9574, Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs)
doi: 10.17487/RFC9574
url: https://doi.org/10.17487/RFC9574
doi: 10.17487/RFC9574
url: https://doi.org/10.17487/RFC9574
Snippet:
<li> <cite id="bib-rfc9574">IETF RFC 9574</cite>, Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs) <span class="doi">10.17487/RFC9574</span> </li>
Referenced By
- IETF RFC 9685 [Active*]