RFC 9744: EVPN Virtual Private Wire Service (VPWS) Flexible Cross-Connect (FXC) Service
In plain English — editorial summary, not part of the RFC
This document describes a new EVPN Virtual Private Wire Service (VPWS) service type specifically for multiplexing multiple attachment circuits across different Ethernet Segments (ESs) and physical interfaces into a single EVPN-VPWS service tunnel and still providing Single-Active and All-Active multi-homing. This new service is referred to as the EVPN-VPWS Flexible Cross-Connect (FXC) service. This document specifies a solution based on extensions to EVPN-VPWS (RFC 8214), which in turn is based on extensions to EVPN (RFC 7432). Therefore, a thorough understanding of RFCs 7432 and 8214 are prerequisites for this document.
Document record
- Document ID
- RFC9744
- Published
- March 2025
- Authors
- A. Sajassi; P. Brissette; J. Uttaro; J. Drake; S. Boutros; J. Rabadan
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9722Fast Recovery for EVPN Designated Forwarder ElectionCurrent
May 2025
- RFC 9786EVPN Port-Active Redundancy ModeCurrent
June 2025
- RFC 9489Label Switched Path (LSP) Ping Mechanisms for EVPN and Provider Backbone Bridging EVPN (PBB-EVPN)Current
November 2023
- RFC 9469Applicability of Ethernet Virtual Private Network (EVPN) to Network Virtualization over Layer 3 (NVO3) NetworksCurrent
September 2023
- RFC 8560Seamless Integration of Ethernet VPN (EVPN) with Virtual Private LAN Service (VPLS) and Their Provider Backbone Bridge (PBB) EquivalentsCurrent
May 2019
- RFC 8388Usage and Applicability of BGP MPLS-Based Ethernet VPNCurrent
May 2018
- RFC 6718Pseudowire RedundancyCurrent
August 2012
- RFC 4665Service Requirements for Layer 2 Provider-Provisioned Virtual Private NetworksCurrent
September 2006
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?