[bess] VXLAN BGP EVPN Question

Gyan Mishra <hayabusagsm@gmail.com> Wed, 22 April 2020 21:57 UTC

Return-Path: <hayabusagsm@gmail.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 A31133A0B75 for <bess@ietfa.amsl.com>; Wed, 22 Apr 2020 14:57:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l8JpEkjYZC2z for <bess@ietfa.amsl.com>; Wed, 22 Apr 2020 14:57:48 -0700 (PDT)
Received: from mail-il1-x132.google.com (mail-il1-x132.google.com [IPv6:2607:f8b0:4864:20::132]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3285C3A0B70 for <bess@ietf.org>; Wed, 22 Apr 2020 14:57:48 -0700 (PDT)
Received: by mail-il1-x132.google.com with SMTP id w6so3593304ilg.1 for <bess@ietf.org>; Wed, 22 Apr 2020 14:57:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=yU0f54nBPuNBwaTb+B5su6YcvgNhZNm10WtAl1Xyf/s=; b=k/8y7tAoBIq8ihioEE/FS6LN8aGU8mcx8Wc++nUBZFPcxVfgyhjhq7/NmuwOszkOLS GpdLQJ1AVgOAqnQQQJB60HHH/5oqIZO/wbPld+OCa3wVg3r56fFeXSY82V4AOPceZxdZ 0zs36MxztqjA3HsgCIraEHLxEqWdkSZgfcFfg8UkAgUsK4Cvj4CY74nu7/03OlV3zEkg jtkO5rUpRCM59IqI7zdZnT3XKzgGADW+KnLdtTAI8S5NAeftyLwarvcO/1C/GSBtTy4a l8zZTQFZBZsZS3yEmTxgvuce5SMx2Vi40xMmG/vbPd+wCALofgJcTFMKyiBnaXiqeYMZ +VNQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=yU0f54nBPuNBwaTb+B5su6YcvgNhZNm10WtAl1Xyf/s=; b=qWJa3EKjzWZcdaVx8EvNb4JjJwkXHIV0NkF7faKkOe7Kf52r4+qUZxgbfMV33NkBWm OI0x26TO3WcYCjJlTpWXFUPYvJYa1IvXEaDnkJetLUSk6w2x7z2i9UVX6x5CBpS/lJjO NdHHeGSBMo7q0KfVYj582Qu1QmMJcasZfrMR9N48PP68cTiA8Chvo5WP8l/S2Ywr3iJ7 sxEdFt2FsrvIndYM3ceisPTtTUCzslyPQdkdB2EBptSy++m5Yn6/YHjWm7qphMQzJCY7 BdbfbsyHpcqQGnmcqzHJHz3lNwJ+TnQUMUWWPthlZTo1myjsNIMEOghmvOa65PxCoH1v omog==
X-Gm-Message-State: AGi0PuaE6iCpLr8zmojr8S4LyiJz6oiHnL/r/nAfiJw4F2kEzpIJezsj G5u7FOUgVC7vB5cJJzPKoIeT3qCfIaJ6+BrQhLLcJ8UZHC8=
X-Google-Smtp-Source: APiQypJG6LorMloUXbXzASt4OfO7aLPtJ9XUJXgqby5Noah6Jlsc2e6NXSuF6zKSxGwKecqUSG2pO3/8zt8NNcfc0n4=
X-Received: by 2002:a05:6e02:4cd:: with SMTP id f13mr541015ils.300.1587592667089; Wed, 22 Apr 2020 14:57:47 -0700 (PDT)
MIME-Version: 1.0
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Wed, 22 Apr 2020 17:57:35 -0400
Message-ID: <CABNhwV1kPDhRcuqS8GOpTiKoyk_QHKVXa582JUznLvKfXQe54w@mail.gmail.com>
To: BESS <bess@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f8516605a3e83849"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/6WJ4cAqnWprMXH_sbDXHk1hw2jE>
Subject: [bess] VXLAN BGP EVPN Question
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 22 Apr 2020 21:57:51 -0000

All

Had a question related to vxlan BGP EVPN architecture specifications
defined in BGP EVPN NVO3 overlay RFC 8365 and VXLAN data plane RFC 7348.

In a Data Center environment where you have a multiple PODs individual
fabrics per POD connected via a super spine extension using a Multi site
feature doing auto rewrite of RTs to stitch the NVE tunnel between pods
similar to inter-as option A.

So in this scenario where you have vlan sprawl everywhere with L2 and L3
VNIs everywhere as if it were a a single L2 domain.  The topology is a
typical vxlan spine leaf topology where the L3 leafs are the TOR switch so
very small physical  L2 fault domain. So I was wondering if with the vxlan
architecture if this feature below is possible or if their is a way to do
so in the current specification.

Cisco use to have a DC product called “fabric path” which was based on
conversation learning.

Is there any way with existing vxlan BGP evpn specification or maybe future
enhancement to have a Mac conversation learning capability so that only the
active mac’s that are part of a conversations flow are the mac that are
flooded throughout the vxlan fabric.  That would really help tremendously
with arp storms so if new arp entries are generated locally on a leaf they
are not flooded through the fabric unless their are active flows between
leafs.

Also is there a way to filter type 2 Mac mobility routes between leaf
switches at the control plane level based on remote vtep or maybe other
parameters.  That would also reduce arp storms BUM traffic.

Kind regards

Gyan
-- 

Gyan  Mishra

Network Engineering & Technology

Verizon

Silver Spring, MD 20904

Phone: 301 502-1347

Email: gyan.s.mishra@verizon.com