[bess] I-D Action: draft-ietf-bess-evpn-irb-mcast-08.txt

internet-drafts@ietf.org Mon, 28 November 2022 14:07 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: bess@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: bess@ietf.org
Message-ID: <166964446771.46991.16703521127495352200@ietfa.amsl.com>
Date: Mon, 28 Nov 2022 06:07:47 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/1fgmmpIlDouyvwTqdHZgt87C56Y>
Subject: [bess] I-D Action: draft-ietf-bess-evpn-irb-mcast-08.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the BGP Enabled ServiceS WG of the IETF.

        Title           : EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding
        Authors         : Wen Lin
                          Zhaohui Zhang
                          John Drake
                          Eric C. Rosen
                          Jorge Rabadan
                          Ali Sajassi
  Filename        : draft-ietf-bess-evpn-irb-mcast-08.txt
  Pages           : 78
  Date            : 2022-11-28

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 IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-irb-mcast/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-irb-mcast-08

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-evpn-irb-mcast-08


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts

[bess] I-D Action: draft-ietf-bess-evpn-irb-mcast… internet-drafts