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

        RFC 10018

        Title:      Multicast and Ethernet VPN with Segment Routing 
                    Point-to-Multipoint (P2MP) and Ingress Replication
        Author:     R. Parekh, Ed.,
                    D. Voyer, Ed.,
                    C. Filsfils,
                    H. Bidgoli,
                    Z. Zhang
        Status:     Proposed Standard
        Stream:     IETF
        Date:       August 2026
        Mailbox:    [email protected],
                    [email protected],
                    [email protected],
                    [email protected],
                    [email protected]
        Pages:      21
        Updates:    RFC 6514, RFC 7988


        I-D Tag:    draft-ietf-bess-mvpn-evpn-sr-p2mp-18

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

        DOI:        10.17487/RFC10018

A Point-to-Multipoint (P2MP) tree in a Segment Routing (SR) domain carries 
traffic from a Root to a set of Leaves. This document specifies extensions to 
BGP encodings and procedures for P2MP trees and Ingress Replication used in 
BGP/MPLS IP VPNs and Ethernet VPNs (EVPNs) in an SR domain. This document 
updates RFCs 6514 and 7988.

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

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and
suggestions for improvements. 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/series/rfc-download/

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team

_______________________________________________
rfc-dist mailing list -- [email protected]
To unsubscribe send an email to [email protected]
http://www.rfc-editor.org

Reply via email to