Re: Direct BFD over Ethernet?

Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Sat, 08 June 2019 12:46 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 4B2C8120091 for <rtg-bfd@ietfa.amsl.com>; Sat, 8 Jun 2019 05:46:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, 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 KSrnM17Oxp_B for <rtg-bfd@ietfa.amsl.com>; Sat, 8 Jun 2019 05:46:01 -0700 (PDT)
Received: from mail1.bemta25.messagelabs.com (mail1.bemta25.messagelabs.com [195.245.230.4]) (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 93C5E120019 for <rtg-bfd@ietf.org>; Sat, 8 Jun 2019 05:46:00 -0700 (PDT)
Received: from [46.226.52.101] (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits)) by server-4.bemta.az-a.eu-west-1.aws.symcld.net id E5/FE-22125-50EABFC5; Sat, 08 Jun 2019 12:45:57 +0000
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrJJsWRWlGSWpSXmKPExsViougQq8u67ne Mwfq3rBbL7nlY7D8IZHz+s43R4tSDRAcWj8nTDjB57Jx1l91jyZKfTB6Xe7eyBrBEsWbmJeVX JLBm/F/uXnDXvKL/1ifWBsZT+l2MXBwsAmuZJZ7eX88O4ggJTGCSaNm+jgnCucco0XroGHMXI ycHm4CtxKbVd9lAbBEBO4nDHf+Aijg4mAVKJCa8CQUJCwuoSZx7f5IVokRd4knDcyYI20/izb rlYK0sAioSp668ZwGxeQViJQ5snscGsauLSaLj6GRGkASngIVE87l2sAZGATGJ76fWgA1iFhC XuPVkPpgtISAgsWTPeWYIW1Ti5eN/rBD1SRL3ny5khIgrSZxp7oeql5W4NL8bKu4r0f3hPTvI /RICyhJbXsSC3CAh8JhR4t3nVewQNVoS3zpOQ9k5EqtOzYOy1SRuvOmA2isjcW7vaUaI5lVsE msaL4EdLSSQLHFizmcWiCI5iVW9D1kgii4wS9z9AdHNLJAnsfT7E/YJjFqzkDw3C0lqFjiUBC VOznzCAhHXkViw+xMbhK0tsWzha2YY+8yBx0zI4gsY2VcxmicVZaZnlOQmZuboGhoY6BoaGuk aWhrrmpvqJVbpJuqlluqWpxaX6BrqJZYX6xVX5ibnpOjlpZZsYgSmtpSCg947GE8feK13iFGS g0lJlLeE/1eMEF9SfkplRmJxRnxRaU5q8SFGGQ4OJQneV2t+xwgJFqWmp1akZeYA0yxMWoKDR 0mEtxckzVtckJhbnJkOkTrF6Mox4eXcRcwcl6/PA5Lvfi4Gkh9XLQGS30GkEEtefl6qlDgv51 qgZgGQ5ozSPLjRsBxxiVFWSpiXkYGBQYinILUoN7MEVf4VozgHo5Iw7z+QE3gy80rgLngFdBw T0HHrj/4COa4kESEl1cA0kyHNyXjGRPWeW7HeGZul9u60eDWF32S/+J6VGoWb5uwR+PKC0WvW FOuax9kPy+USJh4OtnzT2Os47/a+0MrQVuUb94wv217mZTzNlWq/MDFqYVtbTkr+x1Ubjqi2t IkU/3ryr0+4Ib3l2FkN+zO7mt9vLFE48P+a9a17q3y8nu6xbrJeXlh2cPI/NpfohB9GTI0Wuw 8ePLz8dEiz3Orbhzo7eV+e31o9t/twY820sP1SXgWmzF95fL9OeXTwYuKDRl/HFZPO/G6MiF9 h8jI66FNDUdqvFsGnJgYpDRzKTEfktTMDTS7k7Hx6QTnE5aEbc9w/6/A++dW7Hs+4GfVn0QX7 5c4hJbNWaNt3cU9VYinOSDTUYi4qTgQAJK1KC4wEAAA=
X-Env-Sender: Alexander.Vainshtein@ecitele.com
X-Msg-Ref: server-20.tower-265.messagelabs.com!1559997953!279725!1
X-Originating-IP: [52.33.64.93]
X-SYMC-ESS-Client-Auth: mailfrom-relay-check=pass
X-StarScan-Received:
X-StarScan-Version: 9.43.9; banners=ecitele.com,-,-
X-VirusChecked: Checked
Received: (qmail 24995 invoked from network); 8 Jun 2019 12:45:56 -0000
Received: from us-west-2b.mta.dlp.protect.symantec.com (HELO EUR01-VE1-obe.outbound.protection.outlook.com) (52.33.64.93) by server-20.tower-265.messagelabs.com with ECDHE-RSA-AES256-SHA384 encrypted SMTP; 8 Jun 2019 12:45:56 -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=MIYorKrZeWt0kUpfoyPXt5cCTZVeR+zUERF0/7z/JEM=; b=G1AVn1lY9Mr1dhsJLYUkpDTqReYJ4pUr3wENLT2NfCNQ6tF9f9FwnegM7F2IWSlk1VznIBeQ+lG6VHqOoZ8jliR7LF4um2Lrvji00yxbKd5HKNOOvi7dU6WoL8bi4f6gqxN+mw4SBi/8bOQvGk+FjbdvLcHcESRnsOSF5i9M0c0=
Received: from AM0PR03MB3828.eurprd03.prod.outlook.com (52.135.146.159) by AM0PR03MB3844.eurprd03.prod.outlook.com (52.135.146.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1965.15; Sat, 8 Jun 2019 12:45:51 +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; Sat, 8 Jun 2019 12:45:51 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "Schwarz Albrecht (ETAS/ESY1)" <albrecht.schwarz@etas.com>
CC: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, Stewart Bryant <stewart.bryant@gmail.com>, Jeffrey Haas <jhaas@pfrc.org>
Subject: Re: Direct BFD over Ethernet?
Thread-Topic: Direct BFD over Ethernet?
Thread-Index: AdUdHwIY3QLc2dE1SwCr012LbinkaAAAvtBvAABBlQAAAT/tgAArr1KAAAfpV5k=
Date: Sat, 8 Jun 2019 12:45:50 +0000
Message-ID: <AM0PR03MB3828A71E881294059A5BB8829D110@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>
In-Reply-To: <7a42f74e46484476a8b642a29649a471@etas.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [52.142.119.221]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d255e346-7875-40e2-8b31-08d6ec0f3cfe
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:AM0PR03MB3844;
x-ms-traffictypediagnostic: AM0PR03MB3844:
x-microsoft-antispam-prvs: <AM0PR03MB384443487B01A2F4C717FB539D110@AM0PR03MB3844.eurprd03.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0062BDD52C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39850400004)(136003)(366004)(396003)(346002)(376002)(199004)(189003)(13464003)(76116006)(6436002)(91956017)(26005)(53936002)(6116002)(3846002)(66556008)(478600001)(64756008)(5660300002)(4326008)(7696005)(8676002)(316002)(6306002)(54896002)(66446008)(256004)(66066001)(54906003)(25786009)(72206003)(9686003)(14444005)(66946007)(68736007)(74316002)(73956011)(66476007)(229853002)(76176011)(14454004)(6246003)(102836004)(99286004)(7736002)(86362001)(55016002)(186003)(446003)(6916009)(11346002)(476003)(486006)(3480700005)(2906002)(6506007)(71190400001)(71200400001)(81156014)(53546011)(33656002)(81166006)(8936002)(52536014); DIR:OUT; SFP:1102; SCL:1; SRVR:AM0PR03MB3844; 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: 7STjR5JkG0Ht+ZKNBWDboiqBRBDIDfUYKOjVwPoFmksR4tqilLf3uVfqj7MWaTdhJ5vvs0dqxHL83o4IxkzfBWKN3hM2CdSkHUxfTkHVWcxEN1U2Jlm2DRbQnhC90fe8qR9l6UTqavn+yjCQKmgsGOSP/goXotLXYP7kfctHfGEz2mYdGxWAsJVCS9HJjhIiiyecf4jl13W3VIFqw2NvjyjZRfps6e60pIIA8mNzcsE4VECiHfEuZOljwcTM095xNl9n8lu4//sDkx3ZkTztfbWI3CLsPjyNAWIpvE5zE2utPWVpv6c0VnXE94ktejCbD4qft2mVM/gLEdpLaSCPP2aDRfCkYpbUVb4dBL2Ty31qOY7/dOfAWOpQ+GxoTXo+9iHTxmBvq3M19X70wdnxlE8PfQh2CE47JQwzrKDC5e8=
Content-Type: multipart/alternative; boundary="_000_AM0PR03MB3828A71E881294059A5BB8829D110AM0PR03MB3828eurp_"
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d255e346-7875-40e2-8b31-08d6ec0f3cfe
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Jun 2019 12:45:50.9674 (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: AM0PR03MB3844
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/zgwTWHoZOXrlAVSKPLVGF144GeI>
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 12:46:04 -0000

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