The IESG has received a request from the BGP Enabled ServiceS WG (bess) to
consider the following document: - 'EVPN Optimized Inter-Subnet Multicast
(OISM) Forwarding'
  <draft-ietf-bess-evpn-irb-mcast-09.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-c...@ietf.org mailing lists by 2023-10-05. Exceptionally, comments may
be sent to i...@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   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 external to the EVPN domain.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-irb-mcast/


The following IPR Declarations may be related to this I-D:

   https://datatracker.ietf.org/ipr/3245/






_______________________________________________
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Reply via email to