Re: Direct BFD over Ethernet?

Jeffrey Haas <jhaas@pfrc.org> Fri, 07 June 2019 11:55 UTC

Return-Path: <jhaas@slice.pfrc.org>
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 BA4EE120086 for <rtg-bfd@ietfa.amsl.com>; Fri, 7 Jun 2019 04:55:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 WezPU3muNcSH for <rtg-bfd@ietfa.amsl.com>; Fri, 7 Jun 2019 04:55:23 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 2B537120158 for <Rtg-bfd@ietf.org>; Fri, 7 Jun 2019 04:55:22 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 666671E2F1; Fri, 7 Jun 2019 07:56:18 -0400 (EDT)
Date: Fri, 7 Jun 2019 07:56:17 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, "Schwarz Albrecht (ETAS/ESY1)" <albrecht.schwarz@etas.com>, "Rtg-bfd@ietf.org" <Rtg-bfd@ietf.org>
Subject: Re: Direct BFD over Ethernet?
Message-ID: <20190607115617.GC15506@pfrc.org>
References: <e06e6a9189eb4174a6777da720d31294@etas.com> <AM0PR03MB3828C11241B4118A96BAFB7A9D100@AM0PR03MB3828.eurprd03.prod.outlook.com> <f6450c2f-a436-7127-251d-e09b79ba15f9@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <f6450c2f-a436-7127-251d-e09b79ba15f9@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/94VDL6s2RwgPmscfMcm0-xqXCq8>
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: Fri, 07 Jun 2019 11:55:25 -0000

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