Re: BFD Echo mode coverage in BFD for VXLAN

"Reshad Rahman (rrahman)" <rrahman@cisco.com> Thu, 15 August 2019 22:41 UTC

Return-Path: <rrahman@cisco.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 91A591200E7; Thu, 15 Aug 2019 15:41:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=m6M3B6gG; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=lrgExp7S
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 ybhelCACQE4u; Thu, 15 Aug 2019 15:41:53 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A76B41200C7; Thu, 15 Aug 2019 15:41:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=31185; q=dns/txt; s=iport; t=1565908912; x=1567118512; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=VKcXKbiBd5qy4x3a4k7ebLfZDe8z9oz/lmhh9dT5UsI=; b=m6M3B6gGTKuutPogMNo2cVENBpf3vh5TtLDCF/qjdE9LDJzG9W5HfwKy mTm7FWgpS7n8LB4J6/L4scBToP1OyP36PYXfbZSO2NuJYJdYNWhDcrPE3 a0aI0HTlhG/Mm4BuL6NkQUJyV1e3UYngFnaurXNXTOQS+TPIDum0fdDfy 0=;
IronPort-PHdr: =?us-ascii?q?9a23=3Arh87PRKzoNeNbPBMHtmcpTVXNCE6p7X5OBIU4Z?= =?us-ascii?q?M7irVIN76u5InmIFeBvad2lFGcW4Ld5roEkOfQv636EU04qZea+DFnEtRXUg?= =?us-ascii?q?Mdz8AfngguGsmAXFfhJf7vZioSF8VZX1gj9Ha+YgBY?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A6AAAA31Vd/5pdJa1lGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBVgIBAQEBCwGBFS8kLANtVSAECyoKhBWDRwOKd4I2JYlcjge?= =?us-ascii?q?BQoEQA1QGAwEBAQwBAS0CAQGEPwIXgn0jNwYOAgQBAQQBAQECAQYEbYUnDIV?= =?us-ascii?q?KAQEBAQMSER0BATcBDwIBCBEDAQIhBwMCAgIfERQJCAIEAQ0FFA6DAAGBHU0?= =?us-ascii?q?DHQECnxUCgTiIEgFNc4EygnoBAQWFBQ0LghQJNX8Bi2gXgUA/gTgME4IeLj6?= =?us-ascii?q?CGoFyWBaCVTKCJowYgn2FDokCjW9ACQKCHY1ygkiDeRuCMYcwdY1sgjuKOQl?= =?us-ascii?q?aiVqOLQIEAgQFAg4BAQWBZiKBWHAVZQGCQYJCg3KKUgFygSmMWAGBIAEB?=
X-IronPort-AV: E=Sophos;i="5.64,389,1559520000"; d="scan'208,217";a="307424207"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 15 Aug 2019 22:41:50 +0000
Received: from XCH-ALN-017.cisco.com (xch-aln-017.cisco.com [173.36.7.27]) by rcdn-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id x7FMfnZj028091 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 15 Aug 2019 22:41:49 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-ALN-017.cisco.com (173.36.7.27) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 15 Aug 2019 17:41:49 -0500
Received: from xhs-aln-003.cisco.com (173.37.135.120) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 15 Aug 2019 18:41:47 -0400
Received: from NAM04-SN1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 15 Aug 2019 17:41:47 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=VtU/n70wE9vcD81Fopu2RY3KCJw1D9Tg8Xyn3xcPJvKyVf2uqxxfym9NRLcssdGZ/7qYJig2iHHOKjuAEF2woase1yZk2TMVkKAVGiIBT3Lj4Z3D3WzFUImVJjb7h03+H+Ds6v2S01SQD/FqNt54KEX7SjnYFFxYenktdIBYFDJ2HH+W76E1JL6IdSFWPkC+2yBv3xwRXxDzno6DLEgTIw+4AwVm0mxnpZoXRDZS7UAkkJ41U2fHv/bmtHduE0/5eVVUVnzZ3BDHuxBu8Y8/IeXE5OKJm/aTyKT30hKvhA+6BZ4X5gzAqiqaC7irUnxl+mhw3EMxt+Amo9kUhq+Tmw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=VKcXKbiBd5qy4x3a4k7ebLfZDe8z9oz/lmhh9dT5UsI=; b=dNnnutxaMg8gRniVR2o3fI8hwrV7Nnq0M3CwgRoKLt9OXhC41UN2MHY09jTEwCEaksO2cuXaEbmBBmMKa5XmqG54+SB5reqXF0Utz1pRJNAJawuyFadLzaeQ5qDvdy6BYYD9Q8rbv6ASuVAOb5hFWGgxyfAbTsCUzIvAbQa821VMOJQZtkJRwitXP5rhmBWi30YZNjg07qpxTEIYtbDgaoy4ZnXQec6DxCU18Ff+zA2l2TXi02Y9pdKaHzc8cYMUgG9eTdggfaJ6WbaLAd1J9CjXPHJGw3MksfZAGqigg2DMJajBLNgKfPCH2jwRzkMcDDwFuZQazePtOi37xMNPKg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=VKcXKbiBd5qy4x3a4k7ebLfZDe8z9oz/lmhh9dT5UsI=; b=lrgExp7SY0YwoUnDJ95KwowtJdr5dkWtKQoXutRniTpfgREkGsiFVyC4Ic5uMx33KihGQGLCrn7I+Ht5++ws67JG2PS7uDk/11BPQXngfJ4y3gA+GABSAa+LNyhenoxIX2jDhupc63yqem6ttqkiWAoR54mwqDaRl4p1B2uzhcw=
Received: from MN2PR11MB4157.namprd11.prod.outlook.com (20.179.150.223) by MN2PR11MB3647.namprd11.prod.outlook.com (20.178.251.26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2157.20; Thu, 15 Aug 2019 22:41:46 +0000
Received: from MN2PR11MB4157.namprd11.prod.outlook.com ([fe80::80bb:d4b:bc47:7daf]) by MN2PR11MB4157.namprd11.prod.outlook.com ([fe80::80bb:d4b:bc47:7daf%3]) with mapi id 15.20.2157.022; Thu, 15 Aug 2019 22:41:46 +0000
From: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
To: Greg Mirsky <gregimirsky@gmail.com>, "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
CC: rtg-bfd WG <rtg-bfd@ietf.org>, "bfd-chairs@ietf.org" <bfd-chairs@ietf.org>, Martin Vigoureux <martin.vigoureux@nokia.com>
Subject: Re: BFD Echo mode coverage in BFD for VXLAN
Thread-Topic: BFD Echo mode coverage in BFD for VXLAN
Thread-Index: AQHVS9triMvwRR2g4EqtQzCYegAm1qbwdoSAgAFtu4CAAA/cgIAKpPWA
Date: Thu, 15 Aug 2019 22:41:46 +0000
Message-ID: <2952AB5F-FBD5-4113-BA1B-CD22FC11B58F@cisco.com>
References: <CA+RyBmVZeLz-wuC04_V3QJxXDG_qOc_3KO0d3N5h0Y-dDTTFXQ@mail.gmail.com> <3747ADED-2F3A-42B8-BD72-20218D167DEE@cisco.com> <CA+RyBmURk5ew+DuHm9S_6yv0op=ALadoMfwWw9Qs5XLpsog2fA@mail.gmail.com> <CA+RyBmVwSyD3aERjprcTJChAVqkwf1R1JsV_TerZ4Sw54UaDDQ@mail.gmail.com>
In-Reply-To: <CA+RyBmVwSyD3aERjprcTJChAVqkwf1R1JsV_TerZ4Sw54UaDDQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1a.0.190609
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rrahman@cisco.com;
x-originating-ip: [173.38.117.85]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: cbfb6f0a-bb9c-40eb-70d7-08d721d1c10f
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR11MB3647;
x-ms-traffictypediagnostic: MN2PR11MB3647:
x-ms-exchange-purlcount: 2
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <MN2PR11MB36479F4C4F91D2E750311343ABAC0@MN2PR11MB3647.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01304918F3
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(39860400002)(136003)(366004)(396003)(376002)(346002)(189003)(199004)(53754006)(6506007)(446003)(476003)(64756008)(11346002)(2616005)(486006)(6246003)(26005)(4326008)(76176011)(5660300002)(186003)(102836004)(53546011)(25786009)(76116006)(66446008)(66556008)(66476007)(66946007)(33656002)(7736002)(8676002)(81166006)(81156014)(36756003)(256004)(58126008)(86362001)(14444005)(71190400001)(71200400001)(8936002)(110136005)(6116002)(99286004)(316002)(3846002)(229853002)(54896002)(6306002)(6512007)(6486002)(66066001)(236005)(6636002)(53936002)(478600001)(6436002)(54906003)(2906002)(14454004); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3647; H:MN2PR11MB4157.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: oUl9THjRvXbX1AtVP2Pd2d178zO7cET3XdYbm3R9eT+o+iUm5MzI+Hj2lUqDGyM9RrYf9xj/lj2di4kICpdkCzjEtUZouDX6gTqTbrm79c/DIls62L2YwrtQ8ZOjsoRU3Zci8VAe/e5K68ZCNBzyYZdrZtSVJwvbl9aXO4E7AZek1TBSlpxnz5/WJmiO8WiZjig49UNRNuW1q0ktjx7r4NecWtYup7BtOIBXrZ2TP9Ynrf2td2QVTvtG2O83auATTh/ayiSMTT5JYjtzi+nx7vEdvMX0breURvea/lpHqlKE1DU3rMsM3GU93j5WzDqF7Hm/OHil1Xdq69X2AhmhTX4EiOsKnC7H8FggVbJ02rFca7dnZZpboSMS+EdbE9d3B2yGSYuYzWr8ik1g/AeKAaTrqxTtrZdGDveYsbGgfso=
Content-Type: multipart/alternative; boundary="_000_2952AB5FFBD54113BA1BCD22FC11B58Fciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: cbfb6f0a-bb9c-40eb-70d7-08d721d1c10f
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Aug 2019 22:41:46.6580 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: DES7ujZU4eMJ/bUtAMpRSJ4TbYuvydSYyq3tzgs8VanTG5g98Y8EA/ulbODYUAiy50eoyOOqyjqP/A5wDmiRzQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3647
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.27, xch-aln-017.cisco.com
X-Outbound-Node: rcdn-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/788kdCVp7G_gh0szbXt2a8xJV8w>
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: Thu, 15 Aug 2019 22:41:56 -0000

Hi all,

It is up to the WG to decide whether echo support is desired for BFD over VxLAN (any other BFD use-cases also).  Since this hasn’t been brought up in the WG before, my take is that the WG isn’t interested in having echo for BFD over VxLAN. So if anybody feels that we need echo support, please speak up asap. Because it’s holiday season, let’s take 3 weeks instead of the usual 2, so please respond by September 5th.

Regards,
Reshad (co-chair hat).

From: Greg Mirsky <gregimirsky@gmail.com>
Date: Thursday, August 8, 2019 at 8:04 PM
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>rg>, "bfd-chairs@ietf.org" <bfd-chairs@ietf.org>rg>, Martin Vigoureux <martin.vigoureux@nokia.com>
Subject: Re: BFD Echo mode coverage in BFD for VXLAN
Resent-From: <alias-bounces@ietf.org>
Resent-To: Jeffrey Haas <jhaas@pfrc.org>rg>, <rrahman@cisco.com>
Resent-Date: Thursday, August 8, 2019 at 8:04 PM

Dear All,
I was pointed out that my previous e-mail asking for WG help to progress BFD over VXLAN document by sharing opinions regarding coverage of the BFD Echo mode may be overstepping the bounds of an Editor. I apologize, that was not my intention. I'm asking WG Chairs to help to arrive at the conclusion of this question in a reasonable time.

Regards,
Greg

On Thu, Aug 8, 2019 at 4:06 PM Greg Mirsky <gregimirsky@gmail.com<mailto:gregimirsky@gmail.com>> wrote:
Dear All,
I have not set the when this poll closes. I hope that two weeks would be sufficient time for the WG community to express their thoughts.

Dear Carlos,
thank you for sharing your opinion on the scope of the document in regard to BFD Echo mode. You've expressed support for exploring the applicability of the BFD Echo mode. Would you support that effort by contributing some text, if WG decides that documenting the applicability of the Echo mode in BFD over VXLAN is useful?

Regards,
Greg


On Wed, Aug 7, 2019 at 6:18 PM Carlos Pignataro (cpignata) <cpignata@cisco.com<mailto:cpignata@cisco.com>> wrote:
Dear Greg,

The option of replacing the existing text for something more ambiguous and implicit does not seem like progress in my humble opinion. The spec ends up with the same capabilities, but the text is more obscure. I do not support that option.

My recommendation for your consideration would be:

  1.  Explore if it is possible to run BFD Echo as a single-hop.
  2.  If yes, add text supporting it.
  3.  If no, add text explaining why not on technical grounds.

A less desirable option would be if the WG does not care about BFD Echo, to explicitly keep it out of scope (not on technical grounds).

Best,

Carlos.


On Aug 5, 2019, at 6:16 PM, Greg Mirsky <gregimirsky@gmail.com<mailto:gregimirsky@gmail.com>> wrote:

Dear All,
in course of reviews of the draft, several times a question was asked about the rationale for excluding BFD Echo from the scope of this document:

7.  Echo BFD

   Support for echo BFD is outside the scope of this document.
Much appreciate your consideration of the following options:

  *   describe the applicability of BFD Echo in VXLAN environment in the document;
  *   remove Section 7 and clarify in the Introduction
NEW TEXT:
This specification describes procedures only for BFD Asynchronous mode.

  *   make no changes at all.
Regards,
Greg