I-D Action: draft-skr-bess-evpn-redundant-mcast-source-02.txt

internet-drafts@ietf.org Mon, 02 November 2020 10:36 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
Subject: I-D Action: draft-skr-bess-evpn-redundant-mcast-source-02.txt
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <160431337850.21994.9417574605402896721@ietfa.amsl.com>
Date: Mon, 02 Nov 2020 02:36:18 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/i-d-announce/idYX1I8j44ZFyZsbld_lOtMaHqY>

A New Internet-Draft is available from the on-line Internet-Drafts directories.


        Title           : Multicast Source Redundancy in EVPN Networks
        Authors         : Jorge Rabadan
                          Jayant Kotalwar
                          Senthil Sathappan
                          Zhaohui Zhang
                          Wen Lin
                          Eric C. Rosen
	Filename        : draft-skr-bess-evpn-redundant-mcast-source-02.txt
	Pages           : 29
	Date            : 2020-11-02

Abstract:
   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: 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 draft is:
https://datatracker.ietf.org/doc/draft-skr-bess-evpn-redundant-mcast-source/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-skr-bess-evpn-redundant-mcast-source-02
https://datatracker.ietf.org/doc/html/draft-skr-bess-evpn-redundant-mcast-source-02

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


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

I-D Action: draft-skr-bess-evpn-redundant-mcast-s… internet-drafts