Re: [bess] Signaling Control Word in EVPN => please strip recipients

<> Wed, 10 October 2018 10:44 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DB999130E4E for <>; Wed, 10 Oct 2018 03:44:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id sjKA8tqJ6hld for <>; Wed, 10 Oct 2018 03:44:48 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9AEC6130E4D for <>; Wed, 10 Oct 2018 03:44:47 -0700 (PDT)
Received: from (unknown [xx.xx.xx.6]) by (ESMTP service) with ESMTP id 42VW256V7fz7vVP for <>; Wed, 10 Oct 2018 12:44:45 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.62]) by (ESMTP service) with ESMTP id 42VW255bfhz1xns for <>; Wed, 10 Oct 2018 12:44:45 +0200 (CEST)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM5E.corporate.adroot.infra.ftgroup ([fe80::6958:931c:a396:f51e%19]) with mapi id 14.03.0415.000; Wed, 10 Oct 2018 12:44:45 +0200
To: "" <>
Thread-Topic: [bess] Signaling Control Word in EVPN => please strip recipients
Thread-Index: AdRghgn4gpIZR82pRzW1hgwqsVbd1w==
Date: Wed, 10 Oct 2018 10:44:44 +0000
Message-ID: <12938_1539168285_5BBDD81D_12938_260_1_9E32478DFA9976438E7A22F69B08FF924B2D7F7E@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_9E32478DFA9976438E7A22F69B08FF924B2D7F7EOPEXCLILMA4corp_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [bess] Signaling Control Word in EVPN => please strip recipients
X-Mailman-Version: 2.1.29
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, 10 Oct 2018 10:44:50 -0000

Hi Folks,

We are receiving a lot of moderation requests for this topic due to the long list of recipients.
Please keep only BESS list as a recipient for any further message so the message will be published automatically on the list.

Thanks in advance,

From: BESS [] On Behalf Of Andrew G. Malis
Sent: Tuesday, October 09, 2018 16:54
Cc: Muthu Arul Mozhi Perumal; Alexander Vainshtein;;;;;;; Rotem Cohen
Subject: Re: [bess] Signaling Control Word in EVPN


Agreed. We touched on that in section 7 of draft-ietf-pals-ethernet-cw, where we advised operators that enabling post-CW DPI for ECMP calculations could cause misordering.


On Tue, Oct 9, 2018 at 10:35 AM James Bensley <<>> wrote:
On Tue, 9 Oct 2018 at 15:16, Andrew G. Malis <<>> wrote:
> James,

Hi Andy,

> It's much harder to mandate use of EL than the CW for several reasons:

I didn't say it should be mandated, but recommended.

> - CW implementation is much more common than EL implementation
> - PWs and/or EVPN are rarely the only traffic in an MPLS traffic tunnel, rather, they will be multiplexed with other MPLS-based applications that are using the traffic tunnel to reach a common destination. Thus, by using the CW, you can disable ECMP only for those MPLS packets that cannot tolerate reordering.

The CW does not disable ECMP. Any LSR on the path between ingress and
egress LER is free to look beyond the MPLS label stack and
misinterpret the 0x00 0x00 at the start of a control-word as a valid
MAC that starts 00:00:XX:XX:XX:XX and try to hash on Ethernet headers
starting directly after the MPLS label stack, and not label stack + 4
bytes. This is my point. The PWMCW doesn't stop re-ording in all
cases, but it does in most. So yes, not all devices support EL, but CW
doesn't stop re-ordering in all cases, so?

> That said, I'm also concerned that because of the existing text in 7432, implementations may not be using the CW even for P2P EVPN.
> And we still don't have a good answer for Muthu's original question. :-)

Sorry my intention is not to send this thread off-topic.



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.