Re: [bess] draft-mohanty-bess-evpn-bum-opt-00 - clarification on problem description

"Satya Mohanty (satyamoh)" <> Wed, 21 March 2018 22:16 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8C8D7129C53 for <>; Wed, 21 Mar 2018 15:16:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.509
X-Spam-Status: No, score=-14.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id xnw9W5HYPJAR for <>; Wed, 21 Mar 2018 15:16:18 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 706991270A0 for <>; Wed, 21 Mar 2018 15:16:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=2620736; q=dns/txt; s=iport; t=1521670577; x=1522880177; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=Xex7FftvqrY4eKWSASxOhg/N5MXChy/5g/AINTimawg=; b=OzBvESO56q19UHwyE0f1Wpqex29n9oBJX8drglHSeVO953uHs9ZQHLqR 3OFpMTvEywd/GH6b1pROLA0FxrB7MeBfnW1ituUMiwClP8Hl62OH9bFPG aNRR5ElvHj8PVVjAl3+OaSzTdLF//xbJOSVecTDEPbVugWCFlgE10SrW8 g=;
X-Files: image001.png : 1891367
X-IronPort-AV: E=Sophos;i="5.48,341,1517875200"; d="png'149?scan'149,208,217,149";a="87513394"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Mar 2018 22:16:16 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id w2LMGF5I018774 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 21 Mar 2018 22:16:15 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 21 Mar 2018 18:16:13 -0400
Received: from ([]) by ([]) with mapi id 15.00.1320.000; Wed, 21 Mar 2018 18:16:13 -0400
From: "Satya Mohanty (satyamoh)" <>
To: "Ali Sajassi (sajassi)" <>, Sandy Breeze <>, "" <>
Thread-Topic: [bess] draft-mohanty-bess-evpn-bum-opt-00 - clarification on problem description
Thread-Index: AQHTwUI3pKI1nWgbp0ukIa0wdFUT3aPbhOcA
Date: Wed, 21 Mar 2018 22:16:12 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/mixed; boundary="_004_A1D7C338C66540A7B124378695DE949Dciscocom_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [bess] draft-mohanty-bess-evpn-bum-opt-00 - clarification on problem description
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 21 Mar 2018 22:16:21 -0000

We will take the feedback and revise the next version with the EVPN GW case as the primary use case.
Also, we will make it informational.

I need to make a mention again of what I spoke at the mic because I think it may not have been clear to everyone.
In the DF election framework draft, the weight is now a function of  the tuple(vlan, Esid, PE’s IP).
If we set the Esid to 0, then as long as each ES has the exact same set if vlans, the carving of vlans by the algorithm is the same.


From: BESS <<>> on behalf of "Ali Sajassi (sajassi)" <<>>
Date: Wednesday, March 21, 2018 at 6:27 PM
To: Sandy Breeze <<>>, "<>" <<>>
Subject: Re: [bess] draft-mohanty-bess-evpn-bum-opt-00 - clarification on problem description

Hi Sandy,

The key point in here is that the proposal is intended for EVPN GWs (and not PEs). By talking about PEs and NVEs at BESS yesterday, lot of people got confused. Although for EVPN GWs, this proposal makes better sense, for EVPN PEs, it doesn’t much because:

  1.  Vast majority (if not all) of TORs/PEs multi-homing are dual-homing which gives us zero benefit
  2.  Even for multi-homing with >2 PEs in the redundancy group, the chances of a PE not becoming a DF across all ES's in a BD is extremely low. We need to keep in mind that number of ES's are much larger than number of PEs !! And HRW algorithm in our df-framework draft takes into account the ES-id in its hash algorithm which means for the same BD, different PEs can become DF for different ES's !!
3) As soon as there is a stub node (e.g., a single-home CE) connected to any PE, then all bets are off and that PE needs to send IMET route and receive mcast traffic
4) As soon as there is a link/ES failure, then we will end-up with (3) above for dual-homing scenario and the PE with active link needs to send IMET route and receive mcast traffic
5) For mcast flow (*,G) or (S,G), the solution described in igmp-proxy draft  is the most optimal

So, I would suggest to do the following:

  1.  In the problem statement of the draft, capture the below use case clearly.
  2.  Change the name of the draft to “bum optimization for EVPN gateways”
  3.  Capture briefly why the proposal is not intended for EVPN PEs/NVEs because of the above reasons.


From: BESS <<>> on behalf of Sandy Breeze <<>>
Date: Wednesday, March 21, 2018 at 8:58 AM
To: "<>" <<>>
Subject: [bess] draft-mohanty-bess-evpn-bum-opt-00 - clarification on problem description

After some discussion, we acknowledge the problem description needs further clarification for this not to become too specific a use case.  Consider the following example of our existing live deployments;


The main points to articulate here are;

  *   PE[1..4] are at the boundary of an EVPN/MPLS domain (core side) and an EVPN/VXLAN domain (datacentre fabric side)
  *   They are responsible for L2VNI VTEP from ToR and MPLS L2VPN in core.
  *   From their point of view, 1 BD = 1 L2VNI (=1 ES).
  *   For any given DF type (modulo/HRW/etc) they distribute DF’s per-ES between them.
  *   Therefore, all nDF PE’s attract BUM for ES’s they’re not allowed to forward on and hence the waste of bandwidth in the EVPN core and cycles.

In our case, the solution we propose works very well.  We also showed this does no harm for the more typical EVPN-multihoming at the PE use case yesterday, which held up to technical scrutiny.