[bess] RFC 9744 on EVPN Virtual Private Wire Service (VPWS) Flexible Cross-Connect (FXC) Service

A new Request for Comments is now available in online RFC libraries.

        RFC 9744

        Title:      EVPN Virtual Private Wire Service (VPWS) 
                    Flexible Cross-Connect (FXC) Service 
        Author:     A. Sajassi, Ed.,
                    P. Brissette,
                    J. Uttaro,
                    J. Drake,
                    S. Boutros,
                    J. Rabadan
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2025
        Mailbox:    sajassi@cisco.com,
                    pbrisset@cisco.com,
                    juttaro@ieee.org,
                    je_drake@yahoo.com,
                    sboutros@ciena.com,
                    jorge.rabadan@nokia.com
        Pages:      15
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-bess-evpn-vpws-fxc-12.txt

        URL:        https://www.rfc-editor.org/info/rfc9744

        DOI:        10.17487/RFC9744

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.

This document is a product of the BGP Enabled ServiceS Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team