[bess] I-D Action: draft-ietf-bess-evpn-redundant-mcast-source-10.txt

internet-drafts@ietf.org Wed, 14 August 2024 21:53 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
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <172367238507.1101532.5952012661173816973@dt-datatracker-6df4c9dcf5-t2x2k>
Date: Wed, 14 Aug 2024 14:53:05 -0700
Message-ID-Hash: 5ET34P5AHCOAP7ZNOIFVCY4OPMRUWF72
CC: bess@ietf.org
Reply-To: bess@ietf.org
Subject: [bess] I-D Action: draft-ietf-bess-evpn-redundant-mcast-source-10.txt
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/0sa2HGVSM75t1asjJizaxVcEkeM>

Internet-Draft draft-ietf-bess-evpn-redundant-mcast-source-10.txt is now
available. It is a work item of the BGP Enabled ServiceS (BESS) WG of the
IETF.

   Title:   Multicast Source Redundancy in EVPN Networks
   Authors: Jorge Rabadan
            Jayant Kotalwar
            Senthil Sathappan
            Zhaohui Zhang
            Wen Lin
   Name:    draft-ietf-bess-evpn-redundant-mcast-source-10.txt
   Pages:   33
   Dates:   2024-08-14

Abstract:

   Ethernet Virtual Private Network (EVPN) supports intra and inter-
   subnet IP multicast forwarding.  However, EVPN (or conventional IP
   multicast techniques for that matter) do not have a solution for the
   case where the following two statements are true at the same time: a)
   a given multicast group carries more than one flow (i.e., more than
   one source), and b) it is desired that each receiver gets only one of
   the several flows.  Existing multicast techniques assume there are no
   redundant sources sending the same flow to the same IP multicast
   group, and, in case there were redundant sources, the receiver's
   application would deal with the received duplicated packets.  This
   document extends the existing EVPN specifications and assumes that IP
   Multicast source redundancy may exist.  It also assumes that, in case
   two or more sources send the same IP Multicast flows into the tenant
   domain, the EVPN PEs need to avoid that the receivers get packet
   duplication by following the described procedures.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-redundant-mcast-source/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-redundant-mcast-source-10

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-bess-evpn-redundant-mcast-source-10

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

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