RFC 7432: BGP MPLS-Based Ethernet VPN
In plain English — editorial summary, not part of the RFC
This document describes procedures for BGP MPLS-based Ethernet VPNs (EVPN). The procedures described here meet the requirements specified in RFC 7209 -- "Requirements for Ethernet VPN (EVPN)".
Document record
- Document ID
- RFC7432
- Published
- February 2015
- Authors
- A. Sajassi; R. Aggarwal; N. Bitar; A. Isaac; J. Uttaro; J. Drake; W. Henderickx
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 56
- Also known as
- —
Referenced by
5 later RFCs formally update or obsolete part of this document.
- RFC 8584Framework for Ethernet VPN Designated Forwarder Election ExtensibilityUpdated
April 2019
- RFC 9161Operational Aspects of Proxy ARP/ND in Ethernet Virtual Private NetworksCurrent
January 2022
- RFC 9572Updates to EVPN Broadcast, Unknown Unicast, or Multicast (BUM) ProceduresCurrent
May 2024
- RFC 9573MVPN/EVPN Tunnel Aggregation with Common LabelsCurrent
May 2024
- RFC 9746BGP EVPN Multihoming Extensions for Split-Horizon FilteringCurrent
March 2025
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7431Multicast-Only Fast RerouteCurrent
August 2015
- RFC 7436IP-Only LAN Service (IPLS)Current
January 2015
- RFC 7438Multipoint LDP (mLDP) In-Band Signaling with WildcardsCurrent
January 2015
- RFC 7439Gap Analysis for Operating IPv6-Only MPLS NetworksCurrent
January 2015
- RFC 7441Encoding Multipoint LDP (mLDP) Forwarding Equivalence Classes (FECs) in the NLRI of BGP MCAST-VPN RoutesCurrent
January 2015
- RFC 7442Carrying Protocol Independent Multicast - Sparse Mode (PIM-SM) in Any-Source Multicast (ASM) Mode Trees over Multipoint LDP (mLDP)Current
February 2015
- RFC 7420Path Computation Element Communication Protocol (PCEP) Management Information Base (MIB) ModuleCurrent
December 2014
- RFC 7419Common Interval Support in Bidirectional Forwarding DetectionCurrent
December 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?