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

        
        RFC 9784

        Title:      Virtual Ethernet Segments for EVPN 
                    and Provider Backbone Bridge EVPN 
        Author:     A. Sajassi,
                    P. Brissette,
                    R. Schell,
                    J. Drake,
                    J. Rabadan
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2025
        Mailbox:    saja...@cisco.com,
                    pbris...@cisco.com,
                    rick_sch...@outlook.com,
                    jdr...@juniper.net,
                    jorge.raba...@nokia.com
        Pages:      20
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-bess-evpn-virtual-eth-segment-19.txt

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

        DOI:        10.17487/RFC9784

Ethernet VPN (EVPN) and Provider Backbone Bridge EVPN (PBB-EVPN)
introduce a comprehensive suite of solutions for delivering Ethernet
services over MPLS/IP networks. These solutions offer advanced
multihoming capabilities. Specifically, they support Single-Active
and All-Active redundancy modes for an Ethernet Segment (ES), which
is defined as a collection of physical links connecting a multihomed
device or network to a set of Provider Edge (PE) devices. This
document extends the concept of an ES by allowing an ES to be
associated with a set of Ethernet Virtual Circuits (EVCs), such as
VLANs, or other entities, including MPLS Label Switched Paths (LSPs)
or pseudowires (PWs). This extended concept is referred to as virtual
Ethernet Segments (vESes). This document lists the requirements and
specifies the necessary extensions to support vES in both EVPN and
PBB-EVPN.

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-edi...@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team


_______________________________________________
BESS mailing list -- bess@ietf.org
To unsubscribe send an email to bess-le...@ietf.org

Reply via email to