RFC 9136: IP Prefix Advertisement in Ethernet VPN (EVPN)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9136
- Published
- October 2021
- Authors
- J. Rabadan; W. Henderickx; J. Drake; W. Lin; A. Sajassi
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 31
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9721Extended Mobility Procedures for Ethernet VPN Integrated Routing and Bridging (EVPN-IRB)Current
April 2025
- RFC 9135Integrated Routing and Bridging in Ethernet VPN (EVPN)Current
October 2021
- RFC 9130YANG Data Model for the IS-IS ProtocolCurrent
October 2022
- RFC 9129YANG Data Model for the OSPF ProtocolCurrent
October 2022
- RFC 9128YANG Data Model for Protocol Independent Multicast (PIM)Current
October 2022
- RFC 9127YANG Data Model for Bidirectional Forwarding Detection (BFD)Updated
October 2021
- RFC 9145Integrity Protection for the Network Service Header (NSH) and Encryption of Sensitive Context HeadersCurrent
December 2021
- RFC 9125Gateway Auto-Discovery and Route Advertisement for Site Interconnection Using Segment RoutingCurrent
August 2021
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?