RFC 8388: Usage and Applicability of BGP MPLS-Based Ethernet VPN
In plain English — editorial summary, not part of the RFC
This document discusses the usage and applicability of BGP MPLS-based Ethernet VPN (EVPN) in a simple and fairly common deployment scenario. The different EVPN procedures are explained in the example scenario along with the benefits and trade-offs of each option. This document is intended to provide a simplified guide for the deployment of EVPN networks.
Document record
- Document ID
- RFC8388
- Published
- May 2018
- Authors
- J. Rabadan; S. Palislamovic; W. Henderickx; A. Sajassi; J. Uttaro
- Status
- INFORMATIONAL
- 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 8560Seamless Integration of Ethernet VPN (EVPN) with Virtual Private LAN Service (VPLS) and Their Provider Backbone Bridge (PBB) EquivalentsCurrent
May 2019
- RFC 9469Applicability of Ethernet Virtual Private Network (EVPN) to Network Virtualization over Layer 3 (NVO3) NetworksCurrent
September 2023
- RFC 9489Label Switched Path (LSP) Ping Mechanisms for EVPN and Provider Backbone Bridging EVPN (PBB-EVPN)Current
November 2023
- RFC 9722Fast Recovery for EVPN Designated Forwarder ElectionCurrent
May 2025
- RFC 9744EVPN Virtual Private Wire Service (VPWS) Flexible Cross-Connect (FXC) ServiceCurrent
March 2025
- RFC 9786EVPN Port-Active Redundancy ModeCurrent
June 2025
- RFC 8390RSVP-TE Path Diversity Using Exclude RouteCurrent
July 2018
- RFC 8385Transparent Interconnection of Lots of Links (TRILL) Transparent Transport over MPLSCurrent
June 2018
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?