[bess] Last Call: <draft-ietf-bess-evpn-optimized-ir-08.txt> (Optimized Ingress Replication solution for EVPN) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Tue, 24 August 2021 14:33 UTC

Return-Path: <iesg-secretary@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 D63623A10F5; Tue, 24 Aug 2021 07:33:59 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 7.36.0
Auto-Submitted: auto-generated
Precedence: bulk
CC: Matthew Bocci <matthew.bocci@nokia.com>, bess-chairs@ietf.org, bess@ietf.org, draft-ietf-bess-evpn-optimized-ir@ietf.org, martin.vigoureux@nokia.com, matthew.bocci@nokia.com
Reply-To: last-call@ietf.org
Sender: <iesg-secretary@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <162981563985.25202.16010718144605304046@ietfa.amsl.com>
Date: Tue, 24 Aug 2021 07:33:59 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/WonfjGwBHEc0nBUP8KIn4dnCV9Q>
Subject: [bess] Last Call: <draft-ietf-bess-evpn-optimized-ir-08.txt> (Optimized Ingress Replication solution for EVPN) to Proposed Standard
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 24 Aug 2021 14:34:09 -0000

The IESG has received a request from the BGP Enabled ServiceS WG (bess) to
consider the following document: - 'Optimized Ingress Replication solution
for EVPN'
  <draft-ietf-bess-evpn-optimized-ir-08.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2021-09-07. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   Network Virtualization Overlay (NVO) networks using EVPN as control
   plane may use Ingress Replication (IR) or PIM (Protocol Independent
   Multicast) based trees to convey the overlay 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 NVO core network.  IR avoids the dependency
   on PIM in the NVO network core.  While IR provides a simple multicast
   transport, some NVO 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 IR in NVO
   networks.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-optimized-ir/



No IPR declarations have been submitted directly on this I-D.