I-D Action: draft-ietf-bess-evpn-optimized-ir-12.txt

internet-drafts@ietf.org Tue, 25 January 2022 12:58 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
Subject: I-D Action: draft-ietf-bess-evpn-optimized-ir-12.txt
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: bess@ietf.org
Message-ID: <164311551788.28450.17046307877422384352@ietfa.amsl.com>
Date: Tue, 25 Jan 2022 04:58:37 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/i-d-announce/ziAno15erkPLCMrhndEr6THixo4>

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           : Optimized Ingress Replication Solution for Ethernet VPN (EVPN)
        Authors         : J. Rabadan
                          S. Sathappan
                          W. Lin
                          M. Katiyar
                          A. Sajassi
	Filename        : draft-ietf-bess-evpn-optimized-ir-12.txt
	Pages           : 34
	Date            : 2022-01-25

Abstract:
   Network Virtualization Overlay networks using Ethernet VPN (EVPN) as
   their control plane may use Ingress Replication or PIM (Protocol
   Independent Multicast)-based trees to convey the overlay Broadcast,
   Unknown unicast and Multicast (BUM) traffic.  PIM provides an
   efficient solution to avoid sending multiple copies of the same
   packet over the same physical link, however it may not always be
   deployed in the Network Virtualization Overlay core network.  Ingress
   Replication avoids the dependency on PIM in the Network
   Virtualization Overlay network core.  While Ingress Replication
   provides a simple multicast transport, some Network Virtualization
   Overlay networks with demanding multicast applications require a more
   efficient solution without PIM in the core.  This document describes
   a solution to optimize the efficiency of Ingress Replication trees.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-optimized-ir/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-optimized-ir-12

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


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

I-D Action: draft-ietf-bess-evpn-optimized-ir-12.… internet-drafts