[bess] evpn instance and vlans
dexter i <dexter.ietf@gmail.com> Fri, 23 August 2019 04:49 UTC
Return-Path: <dexter.ietf@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 35FDB12010E for <bess@ietfa.amsl.com>; Thu, 22 Aug 2019 21:49:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 BYxWTWDaAuPz for <bess@ietfa.amsl.com>; Thu, 22 Aug 2019 21:49:57 -0700 (PDT)
Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (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 4D597120096 for <bess@ietf.org>; Thu, 22 Aug 2019 21:49:57 -0700 (PDT)
Received: by mail-lj1-x22f.google.com with SMTP id x18so7647597ljh.1 for <bess@ietf.org>; Thu, 22 Aug 2019 21:49:57 -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=LXZ/9m79Oc6uRNi//D/AHEU33D3fXAtaK1aqc9GdIuA=; b=hPNhvsd45wPqNSakIqfplMEuQeC+Loj2ZbmAbw1KiG/r4k0ZPTzrZw/zz7bnjv0zCU qsElQTR8F7mwZCYrl3Hzs7V9XZWrp13ihLAc7p3SpDwyfa54tCoSazgBcQWsNfiqp16C LGPo7Bm+dUn7W5qPmfJijvbcMW77h6QaNdYPE7n1rhfbIkZiPe5ZaXhTpeEkqZ09pE0b slCIXmL82f2QKxFpJAAxQnx7bGBosgnq2jRYfX0vzCkN+PNqp1zC5A1GRVZBhMICxK1j vsD5oKyIPuVh/06XrQ3cv2qGbk9uueyWevE4ggXzV+fOxlrExVd74gOPqBPaioR1Is7j THrw==
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=LXZ/9m79Oc6uRNi//D/AHEU33D3fXAtaK1aqc9GdIuA=; b=CgZMxqP857xszj9WOsU0ZhMnWTyByUyBNSZvj9NqB9LZN6ienFIvgfeSXW5ats1H6X CPCVQMfxQHUtlZQFyZBueLhCKzj32XA1RVghz0ZOV2nu3cjcfTpoo8wJXnTd7LUGZ/+E Fcdhla0ZLOF2nkWE/GYOafl/hzl5t8nFlQdH39AbFKT2FRdAPN8Gu8IJtMHsJjiHzyJn ZqZT1EeAuwMVPeiUe9DGnGy8sbyzEaKHhKReZDc5pQuorop+QFVy88byf7hT6GP6z2K2 rPwatsavqHsc5tIfXXZPatWFJXmeSK6alb1+1SOwTV0SjgKvOYJhaXFPn3WoMjMkmdeW KBvw==
X-Gm-Message-State: APjAAAWEmLnLfq4Vjjap/PYZmZhDeofE266hjhYe8C5gjQ0Fg2NMKK3K lee/ZaZ0lgZNzy1QmHJnjuDk/hsVQirb/7qq07HKcc5y
X-Google-Smtp-Source: APXvYqw6Bqu9Z9QoSemaWtCL5hCQkvoSuqbMo2wFmWjyVYHCWlXdFiZySmm1BaAHljzXqKqLQyFnGnWoDYlvld3rA+M=
X-Received: by 2002:a2e:8004:: with SMTP id j4mr1572346ljg.231.1566535795349; Thu, 22 Aug 2019 21:49:55 -0700 (PDT)
MIME-Version: 1.0
From: dexter i <dexter.ietf@gmail.com>
Date: Fri, 23 Aug 2019 10:19:44 +0530
Message-ID: <CAM9prMKkAyj+4c-Bb-pwcpL7NLmEcL7TXBamitTz+fV3hW2nMA@mail.gmail.com>
To: bess@ietf.org
Content-Type: multipart/alternative; boundary="0000000000009c1c850590c1898e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/_5iVw3K8BmX2dk8iPSV2r6qJbbQ>
Subject: [bess] evpn instance and vlans
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: Fri, 23 Aug 2019 04:49:59 -0000
Hi, If an EVPN instance has multiple non unique VLANs part of it. Do we need to create multiple bridge domains per VLAN or a single bridge domain is enough. What's the recommendation? Also, I see many documents use bridge domain and broadcast domain interchangeably. Do they mean different meanings? Thanks Dexter
- [bess] evpn instance and vlans dexter i