I support for WGLC. Thanks Krishna
From: Matthew Bocci via Datatracker <[email protected]> Date: Monday, January 19, 2026 at 4:52 AM To: [email protected] <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]>, Mankamana Mishra (mankamis) <[email protected]> Subject: [bess] WG Last Call: draft-ietf-bess-evpn-mvpn-seamless-interop-10 (Ends 2026-02-02) This message starts a WG Last Call for: draft-ietf-bess-evpn-mvpn-seamless-interop-10 This Working Group Last Call ends on 2026-02-02 Abstract: Ethernet Virtual Private Network (EVPN) solution is becoming pervasive for Network Virtualization Overlay (NVO) services in data center (DC), Enterprise networks as well as in service provider (SP) networks. As service providers transform their networks in their Central Offices (COs) towards the next generation data center with Software Defined Networking (SDN) based fabric and Network Function Virtualization (NFV), they want to be able to maintain their offered services including Multicast VPN (MVPN) service between their existing network and their new Service Provider Data Center (SPDC) network seamlessly without the use of gateway devices. They want to have such seamless interoperability between their new SPDCs and their existing networks for a) reducing cost, b) having optimum forwarding, and c) reducing provisioning. This document describes a unified solution based on RFCs 6513 & 6514 for seamless interoperability of Multicast VPN between EVPN and MVPN PEs. Furthermore, it describes how the proposed solution can be used as a routed multicast solution in data centers with only EVPN PEs. File can be retrieved from: Please review and indicate your support or objection to proceed with the publication of this document by replying to this email keeping [email protected] in copy. Objections should be explained and suggestions to resolve them are highly appreciated. Authors, and WG participants in general, are reminded of the Intellectual Property Rights (IPR) disclosure obligations described in BCP 79 [1]. Appropriate IPR disclosures required for full conformance with the provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any. Sanctions available for application to violators of IETF IPR Policy can be found at [3]. Please reply to this email if you are aware of an undisclosed IPR that applies to this document. Thank you. [1] https://datatracker.ietf.org/doc/bcp78/ [2] https://datatracker.ietf.org/doc/bcp79/ [3] https://datatracker.ietf.org/doc/rfc6701/ The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-mvpn-seamless-interop/ There is also an HTMLized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-mvpn-seamless-interop-10 A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-bess-evpn-mvpn-seamless-interop-10 _______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
_______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
