Re: [Idr] [Lsr] draft-merciaz-idr-bgp-bfd-strict-mode

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Sun, 28 July 2019 00:23 UTC

Return-Path: <ginsberg@cisco.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 980A71200C1; Sat, 27 Jul 2019 17:23:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 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, URIBL_BLOCKED=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=QnQavhbr; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=jk+Aa/2d
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 JvSx4KB8pZGO; Sat, 27 Jul 2019 17:23:11 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72CF8120047; Sat, 27 Jul 2019 17:23:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=32546; q=dns/txt; s=iport; t=1564273391; x=1565482991; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Aqz/zxEjc47HwZ6mXS0u3TwIPOOZotpTkyS1zcuSYTY=; b=QnQavhbrgTCQzI8asrAIwFpIikkSgggdV16tdtb5ZIuUyCsgtmSTc3Rf 6JWGdGX8jznYTvwMwFz+z4BE/+yd2jzNChH8a1HOpiB42+lgXWnbUpkJS +y1e6GAY9+bzIYZOw8Q1OS3/jYfCbzQTDHkcMa9JCugjUYYe8aRvk6giY 0=;
IronPort-PHdr: =?us-ascii?q?9a23=3AGMpJjhL8zGxrOZqX3dmcpTVXNCE6p7X5OBIU4Z?= =?us-ascii?q?M7irVIN76u5InmIFeBvKd2lFGcW4Ld5roEkOfQv636EU04qZea+DFnEtRXUg?= =?us-ascii?q?Mdz8AfngguGsmAXEL6KuXgYjY1NM9DT1RiuXq8NBsdFQ=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AdAACC6Txd/5FdJa1mGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBVgEBAQEBAQsBgRQvUANtVSAECyqEHoNHA40Aglt+iFa?= =?us-ascii?q?Nf4JSA1QJAQEBDAEBGAEKCgIBAYRAAheCSyM3Bg4BAwEBBAEBAgEGbYUeDIV?= =?us-ascii?q?KAQEBAQMBARARChMBASwLAQ8CAQgRAwEBASEHAwICAh8GCxQJCAIEAQ0FCBq?= =?us-ascii?q?DAYEdTQMdAQIMny8CgTiIYHGBMoJ6AQEFhQMNC4ITAwaBNAGLXxeBQD+BEUa?= =?us-ascii?q?BTkk1PoIaRwEBgWMeDQmCVTKCJowmNYFyMYR/lhEtQAkCghqQHYQSmA6NO4k?= =?us-ascii?q?/jhcCBAIEBQIOAQEFgWYigVhwFTuCbIJCDBeDToUUhT4BcoEpjTUBAQ?=
X-IronPort-AV: E=Sophos;i="5.64,315,1559520000"; d="scan'208,217";a="604058173"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 28 Jul 2019 00:23:09 +0000
Received: from XCH-RCD-014.cisco.com (xch-rcd-014.cisco.com [173.37.102.24]) by rcdn-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id x6S0N95w009222 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 28 Jul 2019 00:23:09 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-RCD-014.cisco.com (173.37.102.24) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sat, 27 Jul 2019 19:23:08 -0500
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sat, 27 Jul 2019 20:23:07 -0400
Received: from NAM04-BN3-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Sat, 27 Jul 2019 19:23:07 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=K8URrcXJX8xmRLEmxMUkTZtvKe5wajaxU5m9cgro+x4JZ/qfbxLxf9xPcxM8iIp2VlB369xv2FWZG9F3xVa9OMb7MqWQGQG9DbxkwrwIZ6kDpgkepaMc9PCcm281K2GRl7QvZifunNXzIJEM/3h686K2F/z5KYl31H4OtVKUnwfjaSyj8baL+J2HhrBwmhBNrelPvdPc5A5uO7Z795ySQkhDXfCnaFdmIL4+yrMy6nb1klubmsLbh/RmV1k1oCdVRiUj5ufitEemh0lDa551UDT08zv8m1DNc5HzgBGq9nWAhTlY2KF7curbWHDjttU8fZ1aPTSgY4VyXHF66rQ/SQ==
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=Aqz/zxEjc47HwZ6mXS0u3TwIPOOZotpTkyS1zcuSYTY=; b=O3n9Yaw41MLlZg+U/BHx8btNTutGhuDVq2HSJZurGPTU/weaEbxFBxo1yi42ZZlY5pjSt9+h3rrUngjz8IM3eyiQgRoRzdYCWIVKBr/ZjwdO8cZbJ8wukjTo/tb8DJI8CCu+HGNB3FOt1QYwR3Tx+xiWk1fheVqNzAyA3PVi0qMwKtrxSIJeysmMpuK9qzFk6l2NTJEXt0pSuSXDfFZSDbRE0aOtKOMAbPwoanD2r5PnjCmxB3yF8ncPFJOaXdI6hVNDezxWVZfht8NRtm6qbm7Lonp3stS0B/slRQqlk/T+bNAlM4nD7XPgG4INqBL0M8WH3DaWaQFqwRYeuoAOYw==
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=Aqz/zxEjc47HwZ6mXS0u3TwIPOOZotpTkyS1zcuSYTY=; b=jk+Aa/2dvizZv0yJ0VS1iV1TxllQaNSQGZJsoPSSS0WVOo/+/7t725D0tki8prUg4OFFxyEY1dqSTET3Psd2jKyXbuy4ceWZHE0DL/e1YhI+ojlMwVPN8KIks40gaiqQGTZIWXr5q6rSsQ8ymLMnQj/nxy0w0lvw/RSApGSRb5s=
Received: from BYAPR11MB3638.namprd11.prod.outlook.com (20.178.237.19) by BYAPR11MB3430.namprd11.prod.outlook.com (20.177.225.208) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2115.15; Sun, 28 Jul 2019 00:23:06 +0000
Received: from BYAPR11MB3638.namprd11.prod.outlook.com ([fe80::c8b3:b0b0:581d:e1ce]) by BYAPR11MB3638.namprd11.prod.outlook.com ([fe80::c8b3:b0b0:581d:e1ce%6]) with mapi id 15.20.2115.005; Sun, 28 Jul 2019 00:23:06 +0000
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Greg Mirsky <gregimirsky@gmail.com>, "Acee Lindem (acee)" <acee@cisco.com>
CC: "idr@ietf.org" <idr@ietf.org>, Albert Bloomberg <afu14@bloomberg.net>, "Ketan Talaulikar (ketant)" <ketant@cisco.com>, "lsr@ietf.org" <lsr@ietf.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, Albert F <albert.f168@gmail.com>, Susan Hares <shares@ndzh.com>
Thread-Topic: [Lsr] [Idr] draft-merciaz-idr-bgp-bfd-strict-mode
Thread-Index: AQHVQyZEtts3+6RaKECqEhu8TqXFdqbbxrOAgAABiACAAA0QgIAAE0EAgAAFSACAAz5oIA==
Date: Sun, 28 Jul 2019 00:23:05 +0000
Message-ID: <BYAPR11MB36380DEC34EF63CE660D4E07C1C20@BYAPR11MB3638.namprd11.prod.outlook.com>
References: <5D3A0EB4029103460087056A_0_2148724@msclnypmsgsv03> <01c901d54326$80a67af0$81f370d0$@ndzh.com> <DM5PR11MB202727A18322CE10B30D93F2C1C10@DM5PR11MB2027.namprd11.prod.outlook.com> <CAEaWqmokZiFUVYr2Wcnk8hK38xZyL918RnBmrKaiPjh213hS=A@mail.gmail.com> <82732FCE-F604-4501-AED0-EE35E86A72B8@cisco.com> <CA+RyBmW4ArDmej-U0Mad+qmawx-D8wcvv836Xjjo6PB8tNLEkg@mail.gmail.com>
In-Reply-To: <CA+RyBmW4ArDmej-U0Mad+qmawx-D8wcvv836Xjjo6PB8tNLEkg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ginsberg@cisco.com;
x-originating-ip: [2001:420:c0c8:1004::1fa]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b91cca3c-e5fd-4adf-274d-08d712f1c2cd
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BYAPR11MB3430;
x-ms-traffictypediagnostic: BYAPR11MB3430:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <BYAPR11MB343001881B0216354CC36A46C1C20@BYAPR11MB3430.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01128BA907
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(396003)(366004)(346002)(136003)(39860400002)(51444003)(189003)(199004)(81166006)(81156014)(76116006)(8676002)(8936002)(7696005)(102836004)(110136005)(53546011)(6506007)(6306002)(54896002)(99286004)(236005)(9686003)(53936002)(54906003)(25786009)(55016002)(46003)(790700001)(6116002)(256004)(66556008)(64756008)(66446008)(52536014)(71190400001)(71200400001)(86362001)(76176011)(66946007)(66476007)(2906002)(68736007)(229853002)(6436002)(7736002)(14444005)(11346002)(6246003)(316002)(5660300002)(446003)(4326008)(33656002)(486006)(186003)(476003)(74316002)(6636002)(478600001)(966005)(14454004)(606006); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB3430; H:BYAPR11MB3638.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: dysd+0kWgx6+BiRCoRddhqwb0iyVI4cxYMMkahSLhxvUPslt8p6jTlTj2juFEwX++fqCdWkc3xJz5bZzJEiDp53nAInI7Bn6C18OEOuVXbWyr9++ewK++OIA9APRDUCuqQJqJsU6wqIDZLlw43P/itg3UPUjFnw4T8HsgKBasps8trjON5mu4X92OWhCDc086u81APZqZSMaac/7tnI2qsnhIkcOCNVGPjMex5Hb6Gpyc/YVY1In4o4LTk5ZhkcaB0KF9BLo+GCSUe9XfSNwTRGFZW4hQ6gLIxWri+0PJlI/mM28//7wTdtVUKbW1hq4Xo77KUEk1pQpBWe0myVZDVTs5I120djLLDsH2AgwwGFpoBZy4x5dXyEFA6EIVzb5ePnxwVKcEbsV/z3AJXcSS3VrcuIJusuj6XlmaP98Piw=
Content-Type: multipart/alternative; boundary="_000_BYAPR11MB36380DEC34EF63CE660D4E07C1C20BYAPR11MB3638namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: b91cca3c-e5fd-4adf-274d-08d712f1c2cd
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Jul 2019 00:23:05.9328 (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: ginsberg@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3430
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.24, xch-rcd-014.cisco.com
X-Outbound-Node: rcdn-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/GlEeicRBx6KjcFn1nFkv5P69t2s>
Subject: Re: [Idr] [Lsr] draft-merciaz-idr-bgp-bfd-strict-mode
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Jul 2019 00:23:15 -0000

Greg –

I have a very different opinion.

Dampening should always be done at the lowest layer possible.
In most cases this argues for interface layer, but there are cases (switches in the path to the directly connected neighbor) where interface dampening doesn’t always tell you what you need to know.  So I acknowledge the usefulness of dampening at the BFD layer.
But doing it at the BFD client layer is wasteful. It forces the same logic to be implemented in multiple places and introduces race conditions where what BFD thinks and what the BFD client thinks about the same state differ.
I would argue against such an approach.

I have a related question:

In the case where the BGP neighbor is multiple hops away, what benefit does BFD dampening provide?
(Note that I am assuming that there likely would be single hop BFD sessions used by the IGPs (for example) along the path to the BGP neighbor and expecting that BFD dampening would be use for the single hop sessions when appropriate.)

   Les

From: Lsr <lsr-bounces@ietf.org> On Behalf Of Greg Mirsky
Sent: Thursday, July 25, 2019 3:41 PM
To: Acee Lindem (acee) <acee@cisco.com>
Cc: idr@ietf.org; Albert Bloomberg <afu14@bloomberg.net>et>; Ketan Talaulikar (ketant) <ketant@cisco.com>om>; lsr@ietf.org; rtg-bfd@ietf.org; Albert F <albert.f168@gmail.com>om>; Susan Hares <shares@ndzh.com>
Subject: Re: [Lsr] [Idr] draft-merciaz-idr-bgp-bfd-strict-mode

Hi Acee,
I imagine that there could be multiple clients of the same BFD session with different requirements in regard to dampening behavior. For example, the delay each client desires to use may be different for each client of the BFD session. If that is a plausible use case, I think that placing dampening to a client may be a better choice.

Regards,
Greg

On Thu, Jul 25, 2019 at 6:23 PM Acee Lindem (acee) <acee@cisco.com<mailto:acee@cisco.com>> wrote:
Hi Albert, Ketan,
The authors will document dampening in the operational considerations. I’m also of the mind that the dampening should be done in BFD rather than the BFD clients (e.g., BGP).
Thanks,
Acee

From: Lsr <lsr-bounces@ietf.org<mailto:lsr-bounces@ietf.org>> on behalf of Albert F <albert.f168@gmail.com<mailto:albert.f168@gmail.com>>
Date: Thursday, July 25, 2019 at 5:14 PM
To: "Ketan Talaulikar (ketant)" <ketant@cisco.com<mailto:ketant@cisco.com>>
Cc: IDR List <idr@ietf.org<mailto:idr@ietf.org>>, "rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>" <rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>>, Albert Bloomberg <afu14@bloomberg.net<mailto:afu14@bloomberg.net>>, Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>, "lsr@ietf.org<mailto:lsr@ietf.org>" <lsr@ietf.org<mailto:lsr@ietf.org>>
Subject: Re: [Lsr] [Idr] draft-merciaz-idr-bgp-bfd-strict-mode

Hi Ketan,

I think it will be good to mention this in the doc, as I expect most large networks concerned with network stability impacted by link flaps to enable the BFD hold-up feature.

For example, if one side has BFD hold-up enabled (> BGP hold time) and the other side does not, the BGP keepalive message from one side may be delayed even if BFD is up. This may have implication on the BGP session transitiining to established phase.

Thanks
Albert



On Thu, Jul 25, 2019, 4:27 PM Ketan Talaulikar (ketant) <ketant@cisco.com<mailto:ketant@cisco.com>> wrote:
Hi Albert,

Thanks for your feedback from an operator perspective – it is valuable. This “BFD hold up” behaviour that you desire is best handled by BFD since I would expect that similar behaviour would be desired across routing protocols (OSPF, ISIS, BGP) and perhaps other clients.

IMHO this is not something that we should be tackling within the scope of this BGP draft. Would you agree?

That said, this seems like a local implementation aspect to me. We should however discuss within the BFD WG if there is value in documenting this.

Thanks,
Ketan

From: Idr <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>> On Behalf Of Susan Hares
Sent: 25 July 2019 16:21
To: 'Albert Fu' <afu14@bloomberg.net<mailto:afu14@bloomberg.net>>; idr@ietf.org<mailto:idr@ietf.org>
Subject: Re: [Idr] draft-merciaz-idr-bgp-bfd-strict-mode

Albert:

To clarify, do you support WG adoption with the draft as is.

As a WG chair, I have to trust that all  drafts are improved during the WG process.  Can this small change be made after adoption or should it be made before the draft is considered for adoption.

Sue Hares

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Albert Fu (BLOOMBERG/ 120 PARK)
Sent: Thursday, July 25, 2019 4:19 PM
To: idr@ietf.org<mailto:idr@ietf.org>
Subject: [Idr] draft-merciaz-idr-bgp-bfd-strict-mode

I am in support of this draft, and would like to request a small change to make this draft more operationally useful.

We have encountered several traffic blackhole problems in our production network without this feature. As such, we have deployed BGP with strict BFD mode on a proprietary vendor implementation for a while.

Since a lot of MetroE circuit failures occur with interfaces still up, ie. break in the middle issues, the traditional knobs like interface hold-time/debounce timer can not be used to dampen interface flaps.

We have observed that interface issues tend to occur in bursts and would like to request that an option be added in "Section 4 Operation:" to delay BGP from coming up until BFD is proven stable continuously for a period of time (i.e. BFD hold up feature).

This is a feature that we are currently using in the proprietary vendor deployment. In our case, since we have multiple redundant paths, we have some links where we delay BGP from coming up until BFD has been stable continuously for 60 seconds.

Thanks
Albert Fu
Bloomberg

_______________________________________________
Idr mailing list
Idr@ietf.org<mailto:Idr@ietf.org>
https://www.ietf.org/mailman/listinfo/idr