IETF Logo Mail Archive

Re: Direct BFD over Ethernet?

Stewart Bryant <stewart.bryant@gmail.com> Fri, 07 June 2019 11:20 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 359D11200FB for <rtg-bfd@ietfa.amsl.com>; Fri, 7 Jun 2019 04:20:32 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 bkEVVs43SZDB for <rtg-bfd@ietfa.amsl.com>; Fri, 7 Jun 2019 04:20:30 -0700 (PDT)
Received: from mail-wm1-x333.google.com (mail-wm1-x333.google.com [IPv6:2a00:1450:4864:20::333]) (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 A1269120045 for <Rtg-bfd@ietf.org>; Fri, 7 Jun 2019 04:20:30 -0700 (PDT)
Received: by mail-wm1-x333.google.com with SMTP id v19so1535448wmj.5 for <Rtg-bfd@ietf.org>; Fri, 07 Jun 2019 04:20:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=EFWA5s+ocAGsIy9Y+LU6oCiGNLYtWR5SVWC2f4PoKXE=; b=YG907I3ZIDxX533LFFBlot8EXUarjfgDc5/ZjVOqLv0N3iychSuwK87fuGszvNffAe mKqDU5SpZQ1B4eEf5c0AZDeHmwwlrxyLL184RF8PCueYyvvnB/c3PY/VobdD6lbGGN1F AJdoTDtx9Xr7w2/CbiLDLRkLpVtWNiG8K4mZZPKwD+PZR2bjCHv5R4Xe7LBAV1ypK/aN q0+MG3W5Ulyd2zHV50gkj0LGGHK18A1L5hcTNvct0rVC+CXztJTpiq62nfTmRjq4UTKA VL919Bpu17Uotp25io7ygFBfZUKhAkSEPZ50i/xdbBOnZMKA+p84mhQZtI1XXw/Omh7R aORg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=EFWA5s+ocAGsIy9Y+LU6oCiGNLYtWR5SVWC2f4PoKXE=; b=NiE4/fF4sHZXVvxQxliH00QqXH47K9QCxYvo5XlJ3liF5hm2TnG6js+vnawMbHHc7x yFMqWRJ+bi21h3YL3OEuEOrLJ/G9QLm+Vgg5Z8n/LW3GfkdCdc8bR/vBojLFii0mBc6G PqWmw23HD+1cpUNtOp43TECJ+WQVAFZiG/oOoY8AJ8zgq4nYQYpT5VKg/CTPEmxJAlZ/ xiIpGbYlp/KijB+bV69HaBIVb8kPhh2J3qzWd6e4AYASUN/0/TKBHeYl8sU+ePt45s91 tePERv1SIqvBsq4BojqzVX1LkipvCvT3OCQJ9ck8nI2TJg8bwmi/B0tePuYpQDbsJuz2 jvJA==
X-Gm-Message-State: APjAAAWxepaNUD6syR9Fg5/cyIjGF1GTwRalikl++D9MWoSBxgeQqFr1 xAGV71SR2apUZj1PFe4yffhjW71n
X-Google-Smtp-Source: APXvYqzQ5jAQV1pHGb0CabAgsADllIQiz4/72PFFHrtgqY90nF6oqhvQ7xlbTLah3lo4aBYDVAkWPA==
X-Received: by 2002:a1c:7ec3:: with SMTP id z186mr3534849wmc.76.1559906428952; Fri, 07 Jun 2019 04:20:28 -0700 (PDT)
Received: from [192.168.178.22] ([62.3.64.16]) by smtp.gmail.com with ESMTPSA id q15sm1042068wrr.19.2019.06.07.04.20.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 07 Jun 2019 04:20:28 -0700 (PDT)
Subject: Re: Direct BFD over Ethernet?
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, "Schwarz Albrecht (ETAS/ESY1)" <albrecht.schwarz@etas.com>
Cc: "Rtg-bfd@ietf.org" <Rtg-bfd@ietf.org>
References: <e06e6a9189eb4174a6777da720d31294@etas.com> <AM0PR03MB3828C11241B4118A96BAFB7A9D100@AM0PR03MB3828.eurprd03.prod.outlook.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <f6450c2f-a436-7127-251d-e09b79ba15f9@gmail.com>
Date: Fri, 07 Jun 2019 12:20:30 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <AM0PR03MB3828C11241B4118A96BAFB7A9D100@AM0PR03MB3828.eurprd03.prod.outlook.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/ImukIa0jVJcHrUtY9Kz9K611SPU>
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:20:32 -0000

+1

However if you really want BFD, you only need a lightweight IP 
implementation to carry it.

Stewart



On 07/06/2019 12:13, Alexander Vainshtein wrote:
> Albrecht,
> AFAIK there is no such thing.
> 
> IMHO and FWIW IEEE802.1ag is the closest thing to what you are probably 
> looking for, but it is quite different from BFD.
> 
> Thumb typed by Sasha Vainshtein
> 
> 
> 
> From: Schwarz Albrecht (ETAS/ESY1)
> Sent: Friday, June 7, 13:52
> Subject: Direct BFD over Ethernet?
> To: rtg-bfd@ietf.org
> 
> 
> Dear BFD experts,
> just a simple question: which BFD RFC would be applicable for applying 
> BFD over an Ethernet link (no VLAN, no LAG)?
> Direct over Ethernet, without IP.
> 
> Thanks,
> Albrecht
> 
> Mit freundlichen Grüßen / Best regards
> 
> *Dr. Albrecht Schwarz*
> 
> Systems Engineering (ETAS/ESY1)
> Tel. +49 711 3423-2380 | Mobil +49 173 9792 632 | 
> Albrecht.Schwarz@etas.com <mailto:Albrecht.Schwarz@etas.com>
> 
> 
> 
> 
> 
> ___________________________________________________________________________
> 
> 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.
> ___________________________________________________________________________

v2.23.0 | Report a Bug | By Email