RE: Direct BFD over Ethernet?

"Schwarz Albrecht (ETAS/ESY1)" <> Wed, 12 June 2019 14:29 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 64A6B12011B for <>; Wed, 12 Jun 2019 07:29:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id zJH107NfV0Gu for <>; Wed, 12 Jun 2019 07:29:42 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8FD331200A4 for <>; Wed, 12 Jun 2019 07:29:35 -0700 (PDT)
Received: from (unknown []) by (Postfix) with ESMTPS id 45P8QN3Fy9z1XLDR1; Wed, 12 Jun 2019 16:29:32 +0200 (CEST)
Received: from (unknown []) by (Postfix) with ESMTPS id 45P8QN2vryz1Qg; Wed, 12 Jun 2019 16:29:32 +0200 (CEST)
X-AuditID: 0a3aad0d-173ff700000036fe-3e-5d010c4c3334
Received: from ( []) (using TLS with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by (SMG Outbound) with SMTP id 60.ED.14078.C4C010D5; Wed, 12 Jun 2019 16:29:32 +0200 (CEST)
Received: from (unknown []) by (Postfix) with ESMTPS id 45P8QN0BZJznqf; Wed, 12 Jun 2019 16:29:32 +0200 (CEST)
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.1713.5; Wed, 12 Jun 2019 16:29:31 +0200
Received: from ([fe80::187:74e0:f8c8:c9b1]) by ([fe80::187:74e0:f8c8:c9b1%4]) with mapi id 15.01.1713.006; Wed, 12 Jun 2019 16:29:31 +0200
From: "Schwarz Albrecht (ETAS/ESY1)" <>
To: Alexander Vainshtein <>, Jeffrey Haas <>
CC: "" <>, Stewart Bryant <>
Subject: RE: Direct BFD over Ethernet?
Thread-Topic: Direct BFD over Ethernet?
Thread-Index: AdUdHwIY3QLc2dE1SwCr012LbinkaAAAvtBv///ghQCAAAoAgP/+hUYwgAMa5gCABUeEgIABGwoA///cAzA=
Date: Wed, 12 Jun 2019 14:29:31 +0000
Message-ID: <>
References: <> <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: de-DE, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA21Tb0wTdxjmd3dtr4Vjx1HouxYCuSgujDFkOprNEb+NLSb6wZi40G2HHLSR ttgrDPywFJFISERCRGiFyZ+OOcGJiJUKg9jINglhE5J1dOokkjCFiRvsD8yUXTmw/bAvl+ee P+/7+z2XI3FmgNSSJoudt1m4ElauIlRvXU5+bV8MMmR916XSN11/hutHb/0m0y8/9yD9+ENu L5HXH/wW5Xld9xV5bvcqljd9+rrsAPGBak8hX2Iq522v536sMgbOt8lLW3UVrd1LMgdqS6xD ShLoXfD8brOiDqlIhnZiUH92TBESGLoXwZqbloQlBL/fDGDSywiCyUt+ecglp/fCnR+rN7Ca zofVlpaNNE4fgoWOhg0+nk6DqYlfZZJnB8w55jEJF8DVgJeoQyRJ0NthoTMjBCk6BwZ6dkmr /Dh8dWqaCNmVtAFWhq/gIYzoZOjr+x6XVmkgMHcBk25Dg3tY4oFOgMePgjIJp4J/fJ6Q/BnQ PvSHXMKvQnfHwoafouPgjnOOaEAaV8RYV0TEFRFxRUTaEXEJJQqmrHJzVvbunDczbQW8cDxr Z+YRq7kfSR+QGkSTfxX5EE0iNoaKkyMDI+PKhUqzD+0mMTaBShuNMjCxBdbCSiMnGD+ylZXw Aqulkn54P5+Jf0ELZQVmkyCYrBYfAhJn1VT2UTFHFXKVx3mbVYr5kI4kWA1VTO7PZ+hizs4f 5flS3ralvk2SLFDz0eIZ4mx8MV9RZCqxb8lsMoWioqKYxEglci1GKn3oDTJG3L0tNIISSjmz YCrejL8sxZktNhwdR++RDY/bOnHy1thnnThDWKwWXquhDoWm0CG/sczy4hzaJGqxaj2fSYgQ wrOeoBkkNhlPvasSwzHi3xI+AVC6UGlxm2Q4lP25mKE9DLSvncFg4sQoBj1Tqxi4/vwFh8GT szi0+N0EnFx4QMB6l1sG9cF/ZBBs7JDD8vSwHC42r8th5uGAAlpmvQrw1i4roPbeUyU0/t0a DTO9NbFw4Rvx4RmYegkmGhwMBL5sZODp0H0GvBfvqeHmv+uJ8KCvVgODK26AnxZ7ATq7bgPM Dq1poWelWwdn6vy6J2K9mFjvwaFgvlivnbP/T72bbPh2WgfaNkRXRZO3y8fSPz19qvuKp73p xitFX/QmVfXnnk8ZUVeeKwhU/zxCnW2t3z55znHMuye39Jr6ampTSlzGJzrntQpiMaemqebD sh13n71zLD0Td6bcaN+Hj3jYg40nfLF2trpZX3QgdqA71ZcaiymP9HLGoCnta4NzbMq9NOw9 /IglBCO3Mx23Cdx/fS0c3scEAAA=
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 12 Jun 2019 14:29:46 -0000

Thanks again all for recommendations and background information.

With regards to RFC 7130:
> Bidirectional Forwarding Detection (BFD) on Link Aggregation Group (LAG) Interfaces

Actually, I was thinking about a group size of one ("whereas the normal LAG is > 1") to emulate BFD over a single physical Ethernet link, - something like a dedicated  "BFD-over-LAG protocol profile".
However, didn't investigate so far the overhead.


-----Original Message-----
From: Alexander Vainshtein <> 
Sent: 12 June 2019 16:16
To: Jeffrey Haas <>
Cc: Schwarz Albrecht (ETAS/ESY1) <>om>;; Stewart Bryant <>
Subject: RE: Direct BFD over Ethernet?

Lots of thanks for a prompt response.

I tend to agree with your statement that " IETF doesn't have a useful OAM model".
But I would add that, in spite of that, IETF has a rich set of OAM tools that are widely deployed and serve the real needs of the IETF community reasonably well, and from time to time adds to this set when new issues are identified.

Whether a useful OAM model is really needed in his situation, or not, is, IMHO, a matter of personal preferences.

"If it is not broken we don't fix it".

My 2c,

Office: +972-39266302
Cell:      +972-549266302

-----Original Message-----
From: Jeffrey Haas <>
Sent: Wednesday, June 12, 2019 12:23 AM
To: Alexander Vainshtein <>
Cc: Schwarz Albrecht (ETAS/ESY1) <>om>;; Stewart Bryant <>
Subject: Re: Direct BFD over Ethernet?

On Sat, Jun 08, 2019 at 12:45:50PM +0000, Alexander Vainshtein wrote:
> To the best of my recollection the BFD WG hss tried to cooperate with IEEE 802.1, but these attempts have failed.

I think that's a mis-characterization.

Bidirectional Forwarding Detection (BFD) on Link Aggregation Group (LAG) Interfaces

IEEE wasn't really interested in having BFD running native.  Much of this has to do with the OAM and layering models that IEEE has for Ethernet.

And yet, IETF was getting push to solve at least a problem relating to layer 3 issues for traffic balancing over LAGs.  That was somewhat out of the realm of IEEE.

So, while it took us a while to frame the problem, we eventually found a place where we were able to solve our respective problems without stepping too much on organizational and layer-wise boundaries.

> At the same time I think there is a difference in the overall attitude with regard to OAM between IETF and IEEE 802.1.

I think I would state this as "IETF doesn't have a useful OAM model".  Many people would prefer us to have one, and see BFD as a useful component for it.  However, that's bigger work than just BFD.

-- Jeff


This e-mail message is intended for the recipient only and contains information which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this transmission in error, please inform us by e-mail, phone or fax, and then delete the original and all copies thereof.