[rfc-dist] RFC 9469 on Applicability of Ethernet Virtual Private Network (EVPN) to Network Virtualization over Layer 3 (NVO3) Networks

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

        RFC 9469

        Title:      Applicability of Ethernet Virtual Private 
                    Network (EVPN) to Network Virtualization over 
                    Layer 3 (NVO3) Networks 
        Author:     J. Rabadan, Ed.,
                    M. Bocci,
                    S. Boutros,
                    A. Sajassi
        Status:     Informational
        Stream:     IETF
        Date:       September 2023
        Mailbox:    jorge.rabadan@nokia.com,
                    matthew.bocci@nokia.com,
                    sboutros@ciena.com,
                    sajassi@cisco.com
        Pages:      23
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-nvo3-evpn-applicability-06.txt

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

        DOI:        10.17487/RFC9469

An Ethernet Virtual Private Network (EVPN) provides a unified control
plane that solves the issues of Network Virtualization Edge (NVE)
auto-discovery, tenant Media Access Control (MAC) / IP dissemination,
and advanced features in a scablable way as required by Network
Virtualization over Layer 3 (NVO3) networks. EVPN is a scalable
solution for NVO3 networks and keeps the independence of the underlay
IP Fabric, i.e., there is no need to enable Protocol Independent
Multicast (PIM) in the underlay network and maintain multicast states
for tenant Broadcast Domains. This document describes the use of EVPN
for NVO3 networks and discusses its applicability to basic Layer 2
and Layer 3 connectivity requirements and to advanced features such
as MAC Mobility, MAC Protection and Loop Protection, multihoming,
Data Center Interconnect (DCI), and much more. No new EVPN procedures
are introduced.

This document is a product of the Network Virtualization Overlays Working Group of the IETF.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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
Association Management Solutions, LLC