[bess] I-D Action: draft-ietf-bess-evpn-redundant-mcast-source-08.txt
internet-drafts@ietf.org Mon, 08 January 2024 10:46 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: bess@ietf.org
Delivered-To: bess@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DADD2C15152C; Mon, 8 Jan 2024 02:46:44 -0800 (PST)
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
X-Test-IDTracker: no
X-IETF-IDTracker: 12.2.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: bess@ietf.org
Message-ID: <170471080487.15557.17220839546943623214@ietfa.amsl.com>
Date: Mon, 08 Jan 2024 02:46:44 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/IXzte6-MsbNeaebjh11QjhjN_ak>
Subject: [bess] I-D Action: draft-ietf-bess-evpn-redundant-mcast-source-08.txt
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.39
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jan 2024 10:46:44 -0000
Internet-Draft draft-ietf-bess-evpn-redundant-mcast-source-08.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-08.txt Pages: 33 Dates: 2024-01-08 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-08 A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-bess-evpn-redundant-mcast-source-08 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts
- [bess] I-D Action: draft-ietf-bess-evpn-redundant… internet-drafts