Re: BFD Echo mode coverage in BFD for VXLAN

"Carlos Pignataro (cpignata)" <cpignata@cisco.com> Thu, 08 August 2019 01:18 UTC

Return-Path: <cpignata@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 2A5C6120116; Wed, 7 Aug 2019 18:18:07 -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=mK4HltOE; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=MxRXyLm8
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 xfFHBbSgcESw; Wed, 7 Aug 2019 18:18:05 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83241120033; Wed, 7 Aug 2019 18:18:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4533; q=dns/txt; s=iport; t=1565227085; x=1566436685; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=AvY0Z1drVktXMo5JtEmA33ny62AHJVAdjkdhIa5IsqU=; b=mK4HltOEr39e+Hh2iv6ngy6q/riyUbvcdcPnpAGw/WlqG5ecLjMDKDjf kgtSDtIiNEAsHLBdr4epAo4nDbKZCtDruN+Wu5SfkcWbcT6JM2dCcyZup ta6ZZjfxuhsNZGvpZJAG77Jfb5XhI+seW3S3KbOWtVGN14JQSs11EgISL 4=;
IronPort-PHdr: =?us-ascii?q?9a23=3Ac72aNxJahNnlCDfxfNmcpTVXNCE6p7X5OBIU4Z?= =?us-ascii?q?M7irVIN76u5InmIFeBvKd2lFGcW4Ld5roEkOfQv636EU04qZea+DFnEtRXUg?= =?us-ascii?q?Mdz8AfngguGsmAXEbjLfHsZjAzNM9DT1RiuXq8NBsdFQ=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AIAADed0td/5xdJa1mGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBUwUBAQEBCwGBRFADgUIgBAsqCodbA4RShmGMNIYngwSEWYE?= =?us-ascii?q?uFIEQA1QJAQEBDAEBLQIBAYQ/AoJSIzQJDgEEAQEEAQEDAQpthScMhUsCBBI?= =?us-ascii?q?uAQE3AQ8CAQgEOwchERQRAgQOBSKDAIEeTQMdAQKgUwKBOIhggiOCegEBBYU?= =?us-ascii?q?WDQuCFAmBNAGLYxeBQD+BOB+CHi4+ghqBcoN1giaUEYh4jWdACQKCHI1mgka?= =?us-ascii?q?DdxuYMoI5lGaLFIMOAgQCBAUCDgEBBYFQOIFYcBVlAYJBPoIEg3GKUgFygSm?= =?us-ascii?q?MXwGBIAEB?=
X-IronPort-AV: E=Sophos;i="5.64,358,1559520000"; d="scan'208,217";a="306000333"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 08 Aug 2019 01:18:04 +0000
Received: from XCH-ALN-016.cisco.com (xch-aln-016.cisco.com [173.36.7.26]) by rcdn-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id x781I2t2027834 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 8 Aug 2019 01:18:04 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-ALN-016.cisco.com (173.36.7.26) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 7 Aug 2019 20:18:01 -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; Wed, 7 Aug 2019 21:18:01 -0400
Received: from NAM02-CY1-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; Wed, 7 Aug 2019 20:18:00 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=I4RCb5EmiTUjAyEP6S/39YTboNKbNz9O86saEWyZcABYTOj0Uxi9adD9fP2RXrZkzCGX4kYxYqC2Gd6MrFNeHg7eNYzJtuQVPkW/d+9KY5LBIdXgovffwavawQNZuhhNOvUqDzD274ZI9irtRp8OXZuPUN2xXjW3TohVG3ctUv9UycYmpJtBvVFDZEUrIjVjBot/LOYuttUFtN7zbJchi2Va7LrxtN83JSmr/hT51vG05BxKczTBUMLqld6gTSrCuh4yrOAgYkkx+M0kLyVX7W2tqodC7YgkHfP+2mVSmKLVi1QaLLJxWSAcZaOOX2XPC8Trb4qYx0nfPPe3bLLtqg==
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=c5Hb1smDVjSXI6s/a+FrLPWE0dq0NyG6ZcV1QHZtL+w=; b=O6faIjsJsOhiDhJzkPvb+x23TVdRAGDMqUoDDVxh4MNEKOsAJtLTwe5/7yoGDL7tnnNmqo32SyAUJF+YnT+YqRO5d16tV1eZvBwPV7wjg/rN7JLeGAm0IPu12Y4L1iev1suk0O/JUqhDBHdyTRNg2LpRjKpaYS6Lqy30pwZF7W4eRn05Q19c2l6GLljKSrS4bJqRVTRdydAVEwuy5iXt4XPoWkeguUO8bVUK67UpWGkoXrC8ykpU1fduDIqyyURPiEj/ms5FzuzBSHaPdzgcFd80l/PxH6CAedYL7PwifFP7kwyS/6mL/vkzdWKWAFQ1l59lR7dpGB6hGEK2J7sG/w==
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=c5Hb1smDVjSXI6s/a+FrLPWE0dq0NyG6ZcV1QHZtL+w=; b=MxRXyLm8WfkWvBNvZCSGN44VsdPJSQeANVaLUD74S7J7tK7IN30nA0BNVdn2CHut95ScRBzvmv8rzJaeoafl/pw806O6X3B2368Y2NUIeqsndJJ+f+14xfD1Mu8h6auPvCofzYoSQBoJtpWNx9QmsXJBbrlb/5kVBmxt3r32APY=
Received: from BL0PR11MB3028.namprd11.prod.outlook.com (20.177.204.138) by BL0PR11MB3217.namprd11.prod.outlook.com (10.167.233.153) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2136.16; Thu, 8 Aug 2019 01:17:59 +0000
Received: from BL0PR11MB3028.namprd11.prod.outlook.com ([fe80::1129:b8ad:27b9:151f]) by BL0PR11MB3028.namprd11.prod.outlook.com ([fe80::1129:b8ad:27b9:151f%6]) with mapi id 15.20.2136.018; Thu, 8 Aug 2019 01:17:59 +0000
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Greg Mirsky <gregimirsky@gmail.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: AQHVS9ttIYFask/CDUmSDDsOiI40EabwdoSA
Date: Thu, 8 Aug 2019 01:17:59 +0000
Message-ID: <3747ADED-2F3A-42B8-BD72-20218D167DEE@cisco.com>
References: <CA+RyBmVZeLz-wuC04_V3QJxXDG_qOc_3KO0d3N5h0Y-dDTTFXQ@mail.gmail.com>
In-Reply-To: <CA+RyBmVZeLz-wuC04_V3QJxXDG_qOc_3KO0d3N5h0Y-dDTTFXQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3445.104.11)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=cpignata@cisco.com;
x-originating-ip: [173.38.117.94]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: fa67a642-df82-44c2-6228-08d71b9e40a0
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BL0PR11MB3217;
x-ms-traffictypediagnostic: BL0PR11MB3217:
x-microsoft-antispam-prvs: <BL0PR11MB321717171DFC6B9C8A2A3E5AC7D70@BL0PR11MB3217.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 012349AD1C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(376002)(366004)(346002)(39860400002)(396003)(199004)(189003)(2906002)(6246003)(4326008)(25786009)(53936002)(71200400001)(71190400001)(7736002)(6116002)(3846002)(413944005)(14454004)(57306001)(36756003)(478600001)(1411001)(66066001)(6916009)(102836004)(256004)(229853002)(6506007)(53546011)(6486002)(6436002)(76176011)(186003)(50226002)(26005)(8936002)(6512007)(11346002)(8676002)(81166006)(81156014)(446003)(54896002)(236005)(2616005)(54906003)(486006)(33656002)(66946007)(66446008)(64756008)(66556008)(66476007)(86362001)(5660300002)(316002)(476003)(76116006)(99286004); DIR:OUT; SFP:1101; SCL:1; SRVR:BL0PR11MB3217; H:BL0PR11MB3028.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX: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: oOlXdaoyseRn9gvAc5WzIFxsQ5ZRQz47gnPmbcCy1aB+ISrtQ3IJFoP+WQxw/6cTXXDsE2gLHkom2Trp8NWjnbL3pF6ZEZ2E+5MMf+u5uc/+/cxWCo3D9L/kT/8VK0PgmGG0bOC4G8Z8LC+A3ryIAnnnfmQL1yiwYBMot/C6mbLvNqndTwMn6xHZdGDE3q1TUWsjOABCDLdgY+CzeUIO4OjKI0iC2RMCexJhQMIBgAOtls6umL6+XkvPX/Kau6Tv5tT5nEMGR7Zzm0VLcryyIPdWCPH09qPjFxk2gVq9c8Ybrg9PkBVJV70HNU6BXw/8JbJDNDwdT8JFQhYcC5KtILkCJ9ws5jCAtx3J2fk8MIxY0F4PEf/iHRXDCjfOfOfJopAHiP18TGWXFbOw9k8S+O229aWob/bbVoV20NHx/X8=
Content-Type: multipart/alternative; boundary="_000_3747ADED2F3A42B8BD7220218D167DEEciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: fa67a642-df82-44c2-6228-08d71b9e40a0
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Aug 2019 01:17:59.8250 (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: cpignata@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL0PR11MB3217
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.26, xch-aln-016.cisco.com
X-Outbound-Node: rcdn-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/L57fe2clGkmLiOajjG2URp_EiJc>
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, 08 Aug 2019 01:18:07 -0000

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