[bess] RFC 9625 on EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding

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

        RFC 9625

        Title:      EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding 
        Author:     W. Lin,
                    Z. Zhang,
                    J. Drake,
                    E. Rosen, Ed.,
                    J. Rabadan,
                    A. Sajassi
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2024
        Mailbox:    wlin@juniper.net,
                    zzhang@juniper.net,
                    jdrake@juniper.net,
                    erosen52@gmail.com,
                    jorge.rabadan@nokia.com,
                    sajassi@cisco.com
        Pages:      63
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-bess-evpn-irb-mcast-11.txt

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

        DOI:        10.17487/RFC9625

Ethernet VPN (EVPN) provides a service that allows a single Local
Area Network (LAN), comprising a single IP subnet, to be divided into
multiple segments.  Each segment may be located at a different site,
and the segments are interconnected by an IP or MPLS backbone. 
Intra-subnet traffic (either unicast or multicast) always appears to
the end users to be bridged, even when it is actually carried over
the IP or MPLS backbone.  When a single tenant owns multiple such
LANs, EVPN also allows IP unicast traffic to be routed between those
LANs.  This document specifies new procedures that allow inter-subnet
IP multicast traffic to be routed among the LANs of a given tenant
while still making intra-subnet IP multicast traffic appear to be
bridged.  These procedures can provide optimal routing of the
inter-subnet multicast traffic and do not require any such traffic to
egress a given router and then ingress that same router.  These
procedures also accommodate IP multicast traffic that originates or
is destined to be external to the EVPN domain.

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
Association Management Solutions, LLC