[bess] Notification of new bess-related ID for discussion

Aaron Bamberger <abamberger@arista.com> Thu, 16 March 2023 21:31 UTC

Return-Path: <abamberger@arista.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8FC6C14068D for <bess@ietfa.amsl.com>; Thu, 16 Mar 2023 14:31:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.093
X-Spam-Level:
X-Spam-Status: No, score=-2.093 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=arista.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BB4PYAQuy2JU for <bess@ietfa.amsl.com>; Thu, 16 Mar 2023 14:31:39 -0700 (PDT)
Received: from mail-pf1-x434.google.com (mail-pf1-x434.google.com [IPv6:2607:f8b0:4864:20::434]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D1DFC151548 for <bess@ietf.org>; Thu, 16 Mar 2023 14:31:38 -0700 (PDT)
Received: by mail-pf1-x434.google.com with SMTP id q14so1967252pff.10 for <bess@ietf.org>; Thu, 16 Mar 2023 14:31:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=arista.com; s=google; t=1679002298; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=Hib5ar29KxHRbMCfOTBxQAobCHf+Q6uqy4l9HE442hc=; b=PhoyXKIFzEIggOISqPYcdz0NV854Y6dBFhJ4rhoXTsoxRYcBP+oicBvJZ8N4W7sy00 hw0iEc8C8uR35VZT9+ZLAx3mpEFkKhLzUOEeIhjbG2LMx+Q8HGgRkNMWnq96eAp9HC3x Z9TGxODI3/rqs+A3AWLngjj0wbYAcqmjnIkVZk2igjvfGH1WtMZfYHvvEBhwa4srKGB9 Tar6G8RS7n4UzNhoPI2hs/P8LPQY5yGn4keZBRZAJpuyb+OzcLgQF1isXSfIQ3U0+o22 oASc9pICDOlEwdDp/gGO5mDBuG24adzqw1shfWlrS1fbFstSSq3iRuxp/SHllk3zC25z oR6A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679002298; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=Hib5ar29KxHRbMCfOTBxQAobCHf+Q6uqy4l9HE442hc=; b=bGSBc7seSsh3YAm7zkNZa46V+EVEhjKyGl99kKb2gvoarEGcsC+MS3l5lfHcSlhED1 lLsz9jkJwQ+sZeejxNnnR329N3XXSbILCCxIXxr+Drdw5/iIkj642Ih3RSMYR2pbaGz4 xvu6IYF1d9/qwmy3Z2iD1FFDN1g9kNPOUl54tOO208oArj34hcHaPLRwd8rcYRH9i+4L ctv1Mc3plS3SSr+vm2m7Xvh32ktYhHpnscAxY8feK3+luhM+RE8PQfhvR+4aivQ9xGyX 2YTXP9BfEqgoh7uu5XAeKw7tzHDs+wmPaAP1hZVl0sbsuFCBU1iHi4rVrKwqwpnVKQ1J SdAQ==
X-Gm-Message-State: AO0yUKU450nPzp1D0s6LxiAwTfc309Wd/KNS8aUyized535IwIK18zW1 gqVn8gB47uyN/NvqPSahHd3g7o3dUxq2BXPw+I4DhfPMUta3rykyFA==
X-Google-Smtp-Source: AK7set/RTeN1lWX8j8xo9UzVLyXyqR7CYibRcTh1Q4f7AEdnVejtddjMWxB14QJ4Fpu8hy6LHIfLKm7kBZWnyZ5NEXI=
X-Received: by 2002:a65:44ca:0:b0:508:9e77:5bb2 with SMTP id g10-20020a6544ca000000b005089e775bb2mr1309502pgs.9.1679002297920; Thu, 16 Mar 2023 14:31:37 -0700 (PDT)
MIME-Version: 1.0
From: Aaron Bamberger <abamberger@arista.com>
Date: Thu, 16 Mar 2023 16:31:27 -0500
Message-ID: <CACEdC8Kxgpc0ugRGxT9qv_J2pebQ6G+h7fsbYsnzLpTBRqKgBw@mail.gmail.com>
To: bess@ietf.org
Content-Type: multipart/alternative; boundary="0000000000008bee3905f70b2fb2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/-tg7FZ7JDSS7gyugFMnCQ0s30pw>
Subject: [bess] Notification of new bess-related ID for discussion
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
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: Thu, 16 Mar 2023 21:32:46 -0000

Hello all,

I had assumed an automated notification for this would have been generated
on the bess mailing list when it was submitted to the datatracker as it's
targeted at this group, but that apparently didn't happen.  I wanted to
post here just to bring folk's attention to and invite discussion of this
draft.

Title           : IMET Route Filtering for Ethernet VPN (EVPN) Ethernet
Tree (E-Tree) with
                  VXLAN Encapsulation
Authors         : Aaron Bamberger
                     Akhil Shashidhar
                     Sergey Kolobov
                     Arivudainambi Appachi Gounder
Filename        : draft-bamberger-bess-imet-filter-evpn-etree-vxlan-00.txt
Pages           : 15
Date            : 2023-03-01

Abstract:
   RFC 8317 defines EVPN Ethernet Tree (E-Tree) and associated filtering
   rules for both known unicast and broadcast, unknown unicast, and
   multicast (BUM) traffic, using Multiprotocol Label Switching (MPLS)
   encapsulation.  The processes and protocols specified in RFC 8317 for
   performing E-Tree filtering on known unicast traffic are implemented
   entirely with EVPN routes, and are thus also applicable to networks
   using Virtual Extensible LAN (VXLAN) encapsulation.  However, E-Tree
   filtering for BUM traffic is accomplished using specific features of
   MPLS encapsulation, and is thus not applicable for networks using
   VXLAN encapsulation.

   In networks where E-Tree root/leaf role classification is done per-
   provider edge (PE) device, or per-attachment circuit (AC) on each PE
   device, an extension to EVPN type-3 inclusive multicast (IMET) routes
   can be added to allow E-Tree filtering for BUM traffic in networks
   using VXLAN encapsulation.  Additionally, this proposal specifies
   filtering BUM traffic on ingress, as opposed to the egress filtering
   specified by RFC 8317, which can be considered to be more optimal, as
   it reduces the amount of unnecessary BUM traffic transmitted over the
   network.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-bamberger-bess-imet-filter-evpn-etree-vxlan/