RFC 9135: Integrated Routing and Bridging in Ethernet VPN (EVPN)
In plain English — editorial summary, not part of the RFC
Ethernet VPN (EVPN) provides an extensible and flexible multihoming VPN solution over an MPLS/IP network for intra-subnet connectivity among Tenant Systems and end devices that can be physical or virtual. However, there are scenarios for which there is a need for a dynamic and efficient inter-subnet connectivity among these Tenant Systems and end devices while maintaining the multihoming capabilities of EVPN. This document describes an Integrated Routing and Bridging (IRB) solution based on EVPN to address such requirements.
Document record
- Document ID
- RFC9135
- Published
- October 2021
- Authors
- A. Sajassi; S. Salam; S. Thoria; J. Drake; J. Rabadan
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 30
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9657Time-Variant Routing (TVR) Use CasesCurrent
October 2024
- RFC 9854AODV-RPL: The Routing Protocol for Low-Power and Lossy Networks (RPL) Based on Ad Hoc On-Demand Distance Vector (AODV) RoutingCurrent
October 2025
- RFC 9063Host Identity Protocol ArchitectureCurrent
July 2021
- RFC 8446The Transport Layer Security (TLS) Protocol Version 1.3Obsoleted
August 2018
- RFC 8387Practical Considerations and Implementation Experiences in Securing Smart Object NetworksCurrent
May 2018
- RFC 9897Datagram Congestion Control Protocol (DCCP) Extensions for Multipath Operation with Multiple AddressesCurrent
January 2026
- RFC 8371Mobile Node Identifier Types for MIPv6Current
July 2018
- RFC 7411Multicast Listener Extensions for Mobile IPv6 (MIPv6) and Proxy Mobile IPv6 (PMIPv6) Fast HandoversCurrent
November 2014
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?