Re: Direct BFD over Ethernet?

Stewart Bryant <stewart.bryant@gmail.com> Tue, 11 June 2019 07:18 UTC

Return-Path: <stewart.bryant@gmail.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 D92F9120119 for <rtg-bfd@ietfa.amsl.com>; Tue, 11 Jun 2019 00:18:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 c7NnLz9D89Sp for <rtg-bfd@ietfa.amsl.com>; Tue, 11 Jun 2019 00:18:57 -0700 (PDT)
Received: from mail-wm1-x330.google.com (mail-wm1-x330.google.com [IPv6:2a00:1450:4864:20::330]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59046120047 for <rtg-bfd@ietf.org>; Tue, 11 Jun 2019 00:18:57 -0700 (PDT)
Received: by mail-wm1-x330.google.com with SMTP id w9so1222394wmd.1 for <rtg-bfd@ietf.org>; Tue, 11 Jun 2019 00:18:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=eUk0rolTXyjP61soSHv0t0Q2K/5lo1jO/ELO6yllTyo=; b=NwBmDm/+wyL5W71tWLsuCsoZaKPuyYXx/s8iooNeSZ6eV68XB+e4FAaXMX2q5/aAwq QV8p9TswhlMvhG/9wZSXa95cZ5EXLqHdv0Y8QGGyVqF6Y20cSOdR60/v29h/tuJbxZzu d5MZOnxjFUmsc5gUW21p8NrV/l59Mvqe0hN2Rkh9oecNLKPvVYuq9oTmwBnFYdLH4dfQ MK6lBFis46gvJlnhKEjEqsXFDnmyHj/FFBjJWAu2/uUi+SFKraQwWbmUUr2Vvc5gxyUR 7XjHlGr6kRhLMYdfVA8rZwrK5lvRdhl3cXy7YgJPgAzgkuXuniczoXzogM7WkrLS9zP7 lf3g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=eUk0rolTXyjP61soSHv0t0Q2K/5lo1jO/ELO6yllTyo=; b=Me+okIkjKkdxUL1JwcaLTY/SAsOIiwDg9u7Fap2VktQpnzBQRKbLbRNDvF718l4Bpa OeOr8v76oFLqbeNfwP5a1yRjRHdGJ3R+WTHe+yBHu+q2sMJg5PvAyYJWB0EBS5yHMWf9 89GlXSMmipjYL6jFNsPKK15cCnqb4TJ5UD80NM18u++5qMhdagDI/awqnqEpwqv2UTEg PfNg6IuEocK15Ck5VcfR2gPks61g8bIonRrmU97DZwh6EbtftrFLQI3Z4KXKb03kljaA XKnCbu8x1Z/f2pL/pAYzc2dwjCjc+/mdGURIjfGcbaDaXrKV0V7HwPONZBGrbevfQdR0 B32A==
X-Gm-Message-State: APjAAAVnfPpkN+k+XudgG24HJkF8DYQbj+5Z6CZRMrHlEskSEma+buwK +NSwSukWYmkhuz511q0KwjY=
X-Google-Smtp-Source: APXvYqwE2c3zPL6IZ0Q45zVMTiPkZiaa225NVZq2XucatPl2QHDF5+pYC1me2xo5L2/iKzmc35NrMw==
X-Received: by 2002:a1c:1bc1:: with SMTP id b184mr17669571wmb.42.1560237535747; Tue, 11 Jun 2019 00:18:55 -0700 (PDT)
Received: from [192.168.2.105] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id o11sm1893763wmh.37.2019.06.11.00.18.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Jun 2019 00:18:55 -0700 (PDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-A693B73F-E862-49F5-BE4E-586E069EF263
Mime-Version: 1.0 (1.0)
Subject: Re: Direct BFD over Ethernet?
From: Stewart Bryant <stewart.bryant@gmail.com>
X-Mailer: iPad Mail (16F203)
In-Reply-To: <8e213e313f2c4fcab9fa9481b8cbc7df@etas.com>
Date: Tue, 11 Jun 2019 08:18:54 +0100
Cc: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, Santosh P K <santosh.pallagatti@gmail.com>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, Jeffrey Haas <jhaas@pfrc.org>
Content-Transfer-Encoding: 7bit
Message-Id: <B4CBD764-40F4-4206-B9AA-5A8AB0C2AE43@gmail.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> <8e213e313f2c4fcab9fa9481b8cbc7df@etas.com>
To: "Schwarz Albrecht (ETAS/ESY1)" <Albrecht.Schwarz@etas.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/kRK3_U1J3obW61F0rkGyOnp3zMQ>
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: Tue, 11 Jun 2019 07:19:01 -0000

If you have an Ethernet that is not carrying IP, and want to use BFD you could still wrap the BFD in IP, and pull those packets off by recognising the IP Ethertype. No other protocol on the wire can be using that Ethertype, so there is no ambiguity. You no need to send the payload to an IP handler if there is no IP, just treat the IP as opaque data.

If you do have IP on the Ethernet and want to check before the packet gets to the IP handler you could use a well-known IP address and pull those packets off first as a special case.

- Stewart

Sent from my iPad

> On 11 Jun 2019, at 08:04, Schwarz Albrecht (ETAS/ESY1) <Albrecht.Schwarz@etas.com> wrote:
> 
> Thanks Sasha,
> understood. There are two different types of served user instances (routing logic versus fault/alarm management of operators).
>  
> Santosh,
> >    Just curious to know why do you have this use case? I mean why not use CFM itself? 
> we are considering a use case of
> 1.     a private network domain,
> 2.     with roughly 80% Ethernet and 20% non-Ethernet at link layer, and
> 3.     a traffic mix of IP-based and IP-less applications,
> 4.     primarily static routing,
> and with the objective of
> 5.     continuity supervision (at link segments) and
> 6.     connectivity supervision (end-to-end, at network routes).
>  
> IEEE CFM might be then the candidate for (5) and Ethernet, but not the non-Ethernet link layer technologies.
> IETF BFD would be the candidate for (6), for IP, but also non-IP-based end-to-end transport connections.
>  
> The engineering goal would be preferably a single supervision technology (for 5 and 6, for IP and non-IP, for Ethernet and non-Ethernet link level connections).
> And that technology for this networking use case might be BFD, particularily when we could cover the 80% of Ethernet links as well.
>  
> Regards,
> Albrecht
> 
> From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> 
> Sent: 08 June 2019 14:46
> To: Schwarz Albrecht (ETAS/ESY1) <Albrecht.Schwarz@etas.com>
> Cc: rtg-bfd@ietf.org; Stewart Bryant <stewart.bryant@gmail.com>om>; Jeffrey Haas <jhaas@pfrc.org>
> Subject: Re: Direct BFD over Ethernet?
>  
> Albrecht,
> I guess you are right and it is indeed mainly the technology ownership issue.
> 
> To the best of my recollection the BFD WG hss tried to cooperate with IEEE 802.1, but these attempts have failed.
> 
> At the same time I think there is a difference in the overall attitude with regard to OAM between IETF and IEEE 802.1.
> 
> The former seems to consider OAM sessions (and, specifically, BFD) as "helpers" for some other protocols (e.g., routing): these sessions are usually set up when the "client protocol" peers establish a peering relationship, and failure of the OAM session is an indication of failure of the peering relationship of the client protocol (see RFC 5882 for details). 
> 
> The latter seems to treat OAM mainly as providing indications (alarms) to the operator.
> 
> My 2c.
> 
> Thumb typed by Sasha Vainshtein
>  
> From: Schwarz Albrecht (ETAS/ESY1)
> Sent: Saturday, June 8, 11:47
> Subject: RE: Direct BFD over Ethernet?
> To: Jeffrey Haas, Stewart Bryant
> Cc: Alexander Vainshtein, rtg-bfd@ietf.org 
> 
> 
> 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 Sent: 07 June 2019 13:56 To: Stewart Bryant Cc: Alexander Vainshtein ; Schwarz Albrecht (ETAS/ESY1) ; 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
> 
> 
> ___________________________________________________________________________
> 
> 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.
> ___________________________________________________________________________