RFC 9136
IP Prefix Advertisement in Ethernet VPN (EVPN), October 2021
- File formats:
- Also available: XML file for editing
- Status:
- PROPOSED STANDARD
- Authors:
- J. Rabadan, Ed.
W. Henderickx
J. Drake
W. Lin
A. Sajassi - Stream:
- IETF
- Source:
- bess (rtg)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC9136
Discuss this RFC: Send questions or comments to the mailing list bess@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 9136
Abstract
The BGP MPLS-based Ethernet VPN (EVPN) (RFC 7432) mechanism provides a flexible control plane that allows intra-subnet connectivity in an MPLS and/or Network Virtualization Overlay (NVO) (RFC 7365) network. In some networks, there is also a need for dynamic and efficient inter-subnet connectivity across Tenant Systems and end devices that can be physical or virtual and do not necessarily participate in dynamic routing protocols. This document defines a new EVPN route type for the advertisement of IP prefixes and explains some use-case examples where this new route type is used.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.