[bess] WG Last Call: draft-ietf-bess-extended-evpn-optimized-ir-09 (Ends 2026-11-16)

Stephane Litkowski via Datatracker <noreply@ietf.org> Mon, 02 November 2026 15:32 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stephane Litkowski via Datatracker <noreply@ietf.org>
To: bess-chairs@ietf.org, bess@ietf.org, draft-ietf-bess-extended-evpn-optimized-ir@ietf.org, slitkows@cisco.com
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <179363354198.1103795.4337085951653741229@dt-datatracker-7dc874ff8f-5wfjq>
Date: Mon, 02 Nov 2026 07:32:21 -0800
Message-ID-Hash: XQSNVKWKEHENGOCQQW3B4GZ32RPG3Z5Q
Reply-To: Stephane Litkowski <slitkows.ietf@gmail.com>
Subject: [bess] WG Last Call: draft-ietf-bess-extended-evpn-optimized-ir-09 (Ends 2026-11-16)
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/_sT533R1MF9WqSSeVCWhl1aRvrs>

This message starts a WG Last Call for:
draft-ietf-bess-extended-evpn-optimized-ir-09

This Working Group Last Call ends on 2026-11-16

Abstract:
   In the Virtualization Overlay (NVO) network with Ethernet VPN (EVPN),
   optimized ingress replication uses Assisted-Replication (AR) to
   achieve more efficient delivery of Broadcast and Multicast (BM)
   traffic.  An AR-LEAF, which is a Network Virtualization Edge (NVE)
   device, forwards received BM traffic from its tenant system to an AR-
   REPLICATOR.  The AR-REPLICATOR then replicates it to the remaining
   AR-LEAFs in the network.  However, when replicating the packet on
   behalf of its multihomed AR-LEAF, an AR-REPLICATOR may face
   challenges in retaining the source IP address or including the
   expected Ethernet Segment Identifier (ESI) label that is required for
   EVPN split-horizon filtering.  This document extends the optimized
   ingress replication procedures to address such limitations.  The
   extended procedures specified in this document allow the support of
   EVPN multihoming on the AR-LEAFs as well as optimized ingress
   replication for the rest of the EVPN NVO network.

File can be retrieved from:
https://www.ietf.org/archive/id/draft-ietf-bess-extended-evpn-optimized-ir-09.txt

Please review and indicate your support or objection to proceed with the
publication of this document by replying to this email keeping bess@ietf.org
in copy. Objections should be explained and suggestions to resolve them are
highly appreciated.

Authors, and WG participants in general, are reminded of the Intellectual
Property Rights (IPR) disclosure obligations described in BCP 79 [1].
Appropriate IPR disclosures required for full conformance with the provisions
of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
Sanctions available for application to violators of IETF IPR Policy can be
found at [3].

Thank you.

[1] https://datatracker.ietf.org/doc/bcp78/
[2] https://datatracker.ietf.org/doc/bcp79/
[3] https://datatracker.ietf.org/doc/rfc6701/

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

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

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-bess-extended-evpn-optimized-ir-09

[bess] WG Last Call: draft-ietf-bess-extended-evp… Stephane Litkowski via Datatracker