RE: Direct BFD over Ethernet?

"Schwarz Albrecht (ETAS/ESY1)" <Albrecht.Schwarz@etas.com> Sat, 08 June 2019 08:47 UTC

Return-Path: <Albrecht.Schwarz@etas.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 08F2A12002E for <rtg-bfd@ietfa.amsl.com>; Sat, 8 Jun 2019 01:47:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Avfvy6meUiwN for <rtg-bfd@ietfa.amsl.com>; Sat, 8 Jun 2019 01:47:18 -0700 (PDT)
Received: from de-out1.bosch-org.com (de-out1.bosch-org.com [139.15.230.186]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3853F1200EA for <Rtg-bfd@ietf.org>; Sat, 8 Jun 2019 01:47:14 -0700 (PDT)
Received: from fe0vm1650.rbesz01.com (unknown [139.15.230.188]) by fe0vms0186.rbdmz01.com (Postfix) with ESMTPS id 45LY195KLvz1XLFjK; Sat, 8 Jun 2019 10:47:08 +0200 (CEST)
Received: from fe0vm7918.rbesz01.com (unknown [10.58.172.176]) by fe0vm1650.rbesz01.com (Postfix) with ESMTPS id 45LY184LxQz1CL; Sat, 8 Jun 2019 10:47:08 +0200 (CEST)
X-AuditID: 0a3aad10-03fff70000007f88-9b-5cfb760c534a
Received: from si0vm1950.rbesz01.com ( [10.58.173.29]) (using TLS with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by fe0vm7918.rbesz01.com (SMG Outbound) with SMTP id D7.B4.32648.C067BFC5; Sat, 8 Jun 2019 10:47:08 +0200 (CEST)
Received: from SI-MBX2055.de.bosch.com (unknown [10.3.230.149]) by si0vm1950.rbesz01.com (Postfix) with ESMTPS id 45LY1827sKz5ff; Sat, 8 Jun 2019 10:47:08 +0200 (CEST)
Received: from SI-MBX2054.de.bosch.com (10.3.230.148) by SI-MBX2055.de.bosch.com (10.3.230.149) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.1713.5; Sat, 8 Jun 2019 10:47:08 +0200
Received: from SI-MBX2054.de.bosch.com ([fe80::187:74e0:f8c8:c9b1]) by SI-MBX2054.de.bosch.com ([fe80::187:74e0:f8c8:c9b1%4]) with mapi id 15.01.1713.006; Sat, 8 Jun 2019 10:47:07 +0200
From: "Schwarz Albrecht (ETAS/ESY1)" <Albrecht.Schwarz@etas.com>
To: Jeffrey Haas <jhaas@pfrc.org>, Stewart Bryant <stewart.bryant@gmail.com>
CC: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, "Rtg-bfd@ietf.org" <Rtg-bfd@ietf.org>
Subject: RE: Direct BFD over Ethernet?
Thread-Topic: Direct BFD over Ethernet?
Thread-Index: AdUdHwIY3QLc2dE1SwCr012LbinkaAAAvtBv///ghQCAAAoAgP/+hUYw
Date: Sat, 8 Jun 2019 08:47:07 +0000
Message-ID: <7a42f74e46484476a8b642a29649a471@etas.com>
References: <e06e6a9189eb4174a6777da720d31294@etas.com> <AM0PR03MB3828C11241B4118A96BAFB7A9D100@AM0PR03MB3828.eurprd03.prod.outlook.com> <f6450c2f-a436-7127-251d-e09b79ba15f9@gmail.com> <20190607115617.GC15506@pfrc.org>
In-Reply-To: <20190607115617.GC15506@pfrc.org>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.142.225.76]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA21TbUwbdRzm37uWo/TkOOj6o4DRyiBhE8E3ilvqPhiDxkS/6AfSbF7loNXS kl4hQHwBTZa6SER0AWrsxniJLnthKEwGWFvWTF6mhDJ1OBwIy4BKA0My3qTecbD2g1/+ee55 /s/ze/nnCIz+kVATJoudtVkYs0Ymx+XPnU99XFG+qc9u2QDtya4lTOv2LEq1K1vdSDs0xRzB 8zu3r6H8HudkdH5r67ok31/bJX0NL5AfLmTNpnLW9oTuTbnx7uBUdKlPXjG/6MOq0QRxAsUQ QD0NXw+NoxNITtBUowQcf6zKxI9zCBo//lIi3KKpIILawH5R6EfQf31FJggy6ggM/voRjwki kXoFBgc5gcaoQhjbXN25kkClw9jInFTAiVQGzFbflYj4Rfi3pm0H41QaNLiXcQGTVC7ca57F xVrTCBZGa5AgxFBZMH6neicIUanQ0fELJhZTwcTsKYk4DgWtfSIPlBLmZ7alIn4UPmu5IRXv H4TTvfdkIj4A7c0BTCwcD4NNs3gdUjkjYp0RFmeExRlhOY3ws0hZxGaXl+Tm5WizbAaWq8rO yXrLWtKJxAekvkc9Q0VeRBFIoyAbjm3qaSlTzlWWeNEzhESjJO1xG3r6IYO1sNLIcMZjtjIz y2nUZMroy3o64QHNlRlKTBxnslq8CAhMk0iWj67pabKQqaxibVbR5kXJBK5RkcXEq3qaKmbs 7DssW8ra9tRDBKEB0mfne4i3scVsRZHJbN+TNakkioqKovdFKpFlJUSMFz1FKPja7RwfQXKl TAlnKt61J4l2eo8NW4fQ60Td/FdnMMLjc/Gn/zfhDK63nMFo3GK1sGoVOSUkUoLXWGZ50JM6 hXy74b6eVkYI4dwFdBPxW00gG4SJFPyfE+4GyGRhgfG7ZNj0ZBvvocZl0Hl7GIPt+mYZNE73 RMO56eOxcDHkiAWXqzcW5kZ+UkB9yK+Aq/4LJGw0nYyD7u/G4uD39s+VcGUztA/+7HCowN35 M0Dw5qVUcF8eeARWnQ1p4NieSoPxzftp4K71pENoZisdXH1XMuAL11YGOG6tZULjUv8BcPy1 nsXHT+TBRH2fDgLL558H79ngCxD0/JO/wK9awq/6om9DWLWdsf/PqnfZ8HTqalR3fTLvVm9g ZjJXt6HWXrgxPCx9w/+YteJ46FnVu0mXWM3U7R9GA2u04WDB30meD0cWP5DIj37adLjXHdQe PdVSHQi9N9ddcMh6R5KSXNWmy0ybyLXItLrSrRrX0tXQwLr5JWL7Yfza8jcGL1PqKfykqUu2 X2647FlJHkjkvvW/r8E5I5OTidk45j9VV0W10wQAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/AqDAVkLVEdV1_Jcr7STWJYuoB_0>
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: Sat, 08 Jun 2019 08:47:23 -0000

Thanks Sasha, Jeff & Stewart for your reply!

OK, understood, more a technology ownership question (IEEE 802 vs IETF) than a technical issue.
Running BFD directly over Ethernet would (at least) require to assign an Ethertype codepoint (https://www.iana.org/assignments/ieee-802-numbers/ieee-802-numbers.xml ) for BFD.

But BFD-over-Ethernet seems to be then in direct competition with the IEEE 802.1ag defined OAM capabilities (guess the Connectivity Fault Management protocols), i.e., the IEEE Continuity Check protocol.
My rough understanding.

Thanks again!
Albrecht

-----Original Message-----
From: Jeffrey Haas <jhaas@pfrc.org> 
Sent: 07 June 2019 13:56
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>om>; Schwarz Albrecht (ETAS/ESY1) <Albrecht.Schwarz@etas.com>om>; Rtg-bfd@ietf.org
Subject: Re: Direct BFD over Ethernet?

On Fri, Jun 07, 2019 at 12:20:30PM +0100, Stewart Bryant wrote:
> 
> +1
> 
> However if you really want BFD, you only need a lightweight IP 
> implementation to carry it.

During the work for BFD for LAG, IETF already went a bit too close to stepping into IEEE territory.  Raw BFD over Ethernet would not be received very well by that organization, I think.  (Even if it'd be trivial to
specify.)

-- Jeff