RE: Direct BFD over Ethernet?

Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Wed, 12 June 2019 14:16 UTC

Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25E0612024A for <rtg-bfd@ietfa.amsl.com>; Wed, 12 Jun 2019 07:16:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.701
X-Spam-Level:
X-Spam-Status: No, score=-1.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=eci365.onmicrosoft.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 0w6YPKyh8iaM for <rtg-bfd@ietfa.amsl.com>; Wed, 12 Jun 2019 07:16:16 -0700 (PDT)
Received: from mail1.bemta25.messagelabs.com (mail1.bemta25.messagelabs.com [195.245.230.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FB161201D5 for <rtg-bfd@ietf.org>; Wed, 12 Jun 2019 07:16:16 -0700 (PDT)
Received: from [46.226.53.55] (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits)) by server-3.bemta.az-c.eu-west-1.aws.symcld.net id 62/2E-09115-D29010D5; Wed, 12 Jun 2019 14:16:13 +0000
X-Brightmail-Tracker: H4sIAAAAAAAAA1WSf0wTZxjH+95dy0E4dhQZD/VHtCoy4DrKELs /0MW/Oh3RZVuywZrtoGfbpLSsLSm4xBCyZVTHBDTNIDiUMaLCzGS2k3QIg4nIZOVHJY7RyqRI wZjFKtEZBuv10G1/3ed9v9/neb7v5SFxaY9ERnIVNs5iYo1ySRyR+9KTbQwTizTZrlPrVe0Bt ar3p/ti1cNlN1INz7CvEeoTzj5M3d3kj1G3tf2FqSdqXeKDRKHYYCo2V3wo1j+6PB1TtkpXTA U+xarQ39RRFEcS9Lc4DNcGMf4gpesxcFd14sLhNoJQ/UhEiSUldD50dfglPK+jt0DLqiPKON2 AwDdJ8ZxEp8H4jZBY8OyAYNU8JnARhBur0VFERsZth+7jFfw1RWsg2DePhFmrGPzS4yB4IZZW wFLXg2gtol+Ex8OdmDArBaaCLVEGmoa2H724wMmwMLsiFvzFcHvuDBLut8CXgeYYgTfCeMuxa AagC8DlqBRwK1wKafgIQM8iOHn12lppBlx8HBQLLIOhsatrbAT3nRpC4DT4YdK7FmcDuEYcuN DonAR8tZ5oNildAkPND9cKNsH52j8IwTSKQ5P7Ol6Hspr+8zaBs+C0JywROBPaz9zDm6I/LBG uNwaJ04g4j3YVWww6va2UNRgZZXY2o1TmMDmRb16egj3MlCi4csbOWW2MUsHarQprZWmJUasw cbYuFNkkbdnQ3suo4+d7in6USmLyZCqtV6SRJhSbtZV61qr/wFJu5Kz9aANJyoF6GoM00kQLp +MqDhmMkX18JgMZL19HUbxMWcvYUqtBJ0jDiCHrFk614lLCZDZxshRqljfRvElfbnre4tlWj6 ONsiQKiUQiaXwZZyk12P6vL6IUEsmTKDPfJd5gsj2ftBgJgUVCvO1ZeT8Swsb+K8mqsN6p8N6 E0cKljFsNhPV3jbtBPHLDpT5hVzcsveBttefEfXIoWZTbk7351/dcPXbD/ievjmVlOpl5zcv5 yuMzBZuOqD733jE6/QcWd3/nWdlv6NyZ/Erxub708DJzaeTCriMLE42NJ78JffGZ97eiVFfHu /cXKuem5y/YugvO5u28UuAXpSYdjmWZxfSa9rvNX9fM79663nTgzWuvuwf/XMkx4lUPYvbkT0 L5V7655G0zRWa/JRzuLUn/KPdmHO2o2ex7FEITzjeWBwcsA87u6u/HtIXTe3SDPs+czjdz09v p3N5q6N/nuFW0Y0R39+PMmdErdU9n6wfy30oMBC4mvKOtPiYnrHpWmYFbrOw/mudoRVAEAAA=
X-Env-Sender: Alexander.Vainshtein@ecitele.com
X-Msg-Ref: server-11.tower-307.messagelabs.com!1560348969!9734111!1
X-Originating-IP: [52.41.248.36]
X-SYMC-ESS-Client-Auth: mailfrom-relay-check=pass
X-StarScan-Received:
X-StarScan-Version: 9.31.5; banners=ecitele.com,-,-
X-VirusChecked: Checked
Received: (qmail 24140 invoked from network); 12 Jun 2019 14:16:12 -0000
Received: from us-west-2a.mta.dlp.protect.symantec.com (HELO EUR04-VI1-obe.outbound.protection.outlook.com) (52.41.248.36) by server-11.tower-307.messagelabs.com with AES256-SHA256 encrypted SMTP; 12 Jun 2019 14:16:12 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ECI365.onmicrosoft.com; s=selector1-ECI365-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=7HF5LNnAgu0cSsPQIXAqcp2T+27eLM8t/Oh9qjWoeJA=; b=Gdt/u/U166dxC+3mq43g5ht18hfBBsKo3AJTe9XElLdHdhktX/whg9ofoTxzfm+qk/QOzRJEg/t5J/ed38jrnsxUEWylDpb+YAhlhhji7fNIoPqzDUx80Py5O4yjFdmCzh7rxwzKOnYx1Os0grqx6NzRU1kNGrg7tSWbUcBYmBk=
Received: from AM0PR03MB3828.eurprd03.prod.outlook.com (52.135.146.159) by AM0PR03MB4689.eurprd03.prod.outlook.com (20.177.41.202) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1987.11; Wed, 12 Jun 2019 14:16:08 +0000
Received: from AM0PR03MB3828.eurprd03.prod.outlook.com ([fe80::91f3:6bd1:1631:9b4a]) by AM0PR03MB3828.eurprd03.prod.outlook.com ([fe80::91f3:6bd1:1631:9b4a%6]) with mapi id 15.20.1965.017; Wed, 12 Jun 2019 14:16:08 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Jeffrey Haas <jhaas@pfrc.org>
CC: "Schwarz Albrecht (ETAS/ESY1)" <albrecht.schwarz@etas.com>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, Stewart Bryant <stewart.bryant@gmail.com>
Subject: RE: Direct BFD over Ethernet?
Thread-Topic: Direct BFD over Ethernet?
Thread-Index: AdUdHwIY3QLc2dE1SwCr012LbinkaAAAvtBvAABBlQAAAT/tgAArr1KAAAfpV5kAqV1XgAAjL4Lg
Date: Wed, 12 Jun 2019 14:16:08 +0000
Message-ID: <AM0PR03MB382870144F1E38857FCF247B9DEC0@AM0PR03MB3828.eurprd03.prod.outlook.com>
References: <e06e6a9189eb4174a6777da720d31294@etas.com> <AM0PR03MB3828C11241B4118A96BAFB7A9D100@AM0PR03MB3828.eurprd03.prod.outlook.com> <f6450c2f-a436-7127-251d-e09b79ba15f9@gmail.com> <20190607115617.GC15506@pfrc.org> <7a42f74e46484476a8b642a29649a471@etas.com> <AM0PR03MB3828A71E881294059A5BB8829D110@AM0PR03MB3828.eurprd03.prod.outlook.com> <20190611212305.GB12590@pfrc.org>
In-Reply-To: <20190611212305.GB12590@pfrc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.234.241.1]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: e022da39-93b9-4e11-de4b-08d6ef4083ce
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(4618075)(2017052603328)(7193020); SRVR:AM0PR03MB4689;
x-ms-traffictypediagnostic: AM0PR03MB4689:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <AM0PR03MB4689694621213D4008C02C739DEC0@AM0PR03MB4689.eurprd03.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0066D63CE6
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(39860400002)(396003)(366004)(346002)(376002)(13464003)(51444003)(199004)(189003)(72206003)(229853002)(3480700005)(478600001)(86362001)(966005)(2906002)(54906003)(316002)(8936002)(71190400001)(14454004)(71200400001)(6116002)(3846002)(66476007)(4326008)(6916009)(6436002)(66946007)(76116006)(73956011)(52536014)(6246003)(6306002)(9686003)(66556008)(64756008)(66446008)(55016002)(53936002)(5660300002)(11346002)(256004)(476003)(486006)(25786009)(446003)(68736007)(33656002)(186003)(74316002)(305945005)(66066001)(7696005)(99286004)(6506007)(26005)(102836004)(7736002)(81166006)(8676002)(53546011)(81156014)(76176011); DIR:OUT; SFP:1102; SCL:1; SRVR:AM0PR03MB4689; H:AM0PR03MB3828.eurprd03.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: ecitele.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: hBQDAlq0eZgTOFd2SKQrqpB5zPC/YIL4kNbgOuCbetjBeBr4MOiYk321/FL13xaywDKrB7ttUxF5VRuTSvKm5UmmJa2XhqlWiOPMvpTMt+hiCT2T9Hz4HKOEREFJWRNfs/8spbjx6sl0xqRGZe8LdBBuJXf5WF+iwoIEBLXJutHMbn1wwavHpnCzcutL2C7UQ69VHv6M6aD3aYocVLI+Dmlp/j8Exemgsp4hjkPqChj3oQj4YHwWVjMRx9Nt8FJPTB3Lv+KZ0rjAzIvmuFtYtvhdlL/hbvAcYJ4MgMbn5aVLzu5dPreb7WQuCVeq/ud0dgRyGJSZFf/j5oMyUp6/MilEQcl8MJBjnWAmcuJJxHvH1xcYyNres4DKyvMpELgkb7gpONbTwW5uv64xvAN7LRBOMDq/0ysKME2hJZ/H0P4=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
X-MS-Exchange-CrossTenant-Network-Message-Id: e022da39-93b9-4e11-de4b-08d6ef4083ce
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Jun 2019 14:16:08.5143 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2c514a61-08de-4519-b4c0-921fef62c42a
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: alexvain@ecitele.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR03MB4689
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/OBBBAs3X2YB5jdUZNotV5_02788>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jun 2019 14:16:25 -0000

Jeffrey,
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,
Sasha

Office: +972-39266302
Cell:      +972-549266302
Email:   Alexander.Vainshtein@ecitele.com

-----Original Message-----
From: Jeffrey Haas <jhaas@pfrc.org> 
Sent: Wednesday, June 12, 2019 12:23 AM
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Cc: Schwarz Albrecht (ETAS/ESY1) <albrecht.schwarz@etas.com>om>; rtg-bfd@ietf.org; Stewart Bryant <stewart.bryant@gmail.com>
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
https://tools.ietf.org/html/rfc7130

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.
___________________________________________________________________________