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

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Thu, 25 July 2019 20:26 UTC

Return-Path: <ketant@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 B22881201DB; Thu, 25 Jul 2019 13:26:58 -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=izwbBgD5; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=FucZ0aG/
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 o0nRPcivW4_2; Thu, 25 Jul 2019 13:26:56 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF6981201D1; Thu, 25 Jul 2019 13:26:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15782; q=dns/txt; s=iport; t=1564086415; x=1565296015; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=8nvCDaEqgk7pblkM1CHxEp5pvsZGQpnLHW4J7xrwpbk=; b=izwbBgD5cT30boh+9JCk6sAyG5nOgEk/n+khSSedt3tTzZsRYekZfWuM qM8+4v23ho0HPzkwNzEEhHI8Ej5G/Od6oY9asbV3+J75rnXBM2KvF9q0X W4ZaZYCfFB04SsTPgSLj4IV+GXpCP2IcE7pUyroz4aoAbRyom7JplwYCm A=;
IronPort-PHdr: =?us-ascii?q?9a23=3AvjDLMRxDLxY30BvXCy+N+z0EezQntrPoPwUc9p?= =?us-ascii?q?sgjfdUf7+++4j5YR2N/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A1RJKa5lQT1?= =?us-ascii?q?kAgMQSkRYnBZuGBFHyKuLCZC0hF8MEX1hgrDm2?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AlAABbEDpd/5pdJa1mGwEBAQEDAQE?= =?us-ascii?q?BBwMBAQGBVAUBAQELAYEUL1ADbVUgBAsqhB2DRwOMfoJbknuEV4EugSQDVAk?= =?us-ascii?q?BAQEMAQEtAgEBhEACF4JHIzUIDgEDAQEEAQECAQZthR4MhUoBAQEBAxIRChM?= =?us-ascii?q?BATcBDwIBCA4DBAEBKAMCAgIwFAkIAgQBDQUIGoMBgR1NAx0BokICgTiIYHG?= =?us-ascii?q?BMoJ6AQEFhQUYghMJgTQBi14XgUA/gRFGgkw+hEY0glUygiaMJTWCI4R/lnk?= =?us-ascii?q?JAoIalCuYDI06l1UCBAIEBQIOAQEFgVEBNoFYcBWDJ4JCDBeDTopTcoEpjSs?= =?us-ascii?q?BAQ?=
X-IronPort-AV: E=Sophos;i="5.64,308,1559520000"; d="scan'208,217";a="604508900"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 25 Jul 2019 20:26:43 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by rcdn-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id x6PKQhwT032238 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 25 Jul 2019 20:26:43 GMT
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 25 Jul 2019 15:26:42 -0500
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 25 Jul 2019 15:26:42 -0500
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 25 Jul 2019 15:26:42 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=h0orv6XR+KqbIvest1FbbDRjiRgyFAldPKCt02H6qw2p7G1E9s6baYeSInt7AXHbz/F62QLUtVXJyFV9yXv8u15EzhvnQ1PAUOy9eT+pSrHDyyILg6U8MQSDSeTOB0//fJmcn9IL6IL5wwqYzzz/3VACfvRQKqKb3bsGFxkEWd0QVTJ534EfZBEil9E1vcumQDOhRQXEOg/O4pjekuhoibqhEfo6zpG0Q4upZU727prQVxunsb5H7fMGWL4BjDgGV7YwNfHAFSSMbaOjUe26h1WTQ1jRPm9VYAD53QQjlsFWb9wripx5O8Au9R4cnkdDfihd5pNR/0sGYyL0tpbD5A==
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=8nvCDaEqgk7pblkM1CHxEp5pvsZGQpnLHW4J7xrwpbk=; b=WZh1rDfcr1X+a9tG7QwcmWL7mJ8y54roKPR6oj9c1wfneTTeTCkwmXo2Ll5qCok1wWIhxHsNt0P2PslTv3cdQ92q+L7YE1haz5jkx/rrixw+yyIRYpSOoq2jR7fzrA9vMkBU6sVqsOI7K7jAFTJG2EtaV83EeG6q5vVCs40p8SZyUsGCfkymP40nq2W8QK2skOiJgQx9+tEXAEjQfpTJXV0uUhhqcm8OAzM6TI4dOzJW7qMDzRyfOy4QXOVdJqcHvJ2CeY4j/WtZorat+tMuNsTZ3Ue/fi13HvtvDtv7L3OwzoF/h7o2/wF07yrXFRfw1Z+1vejAbPCbd7bTxmm/zw==
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=8nvCDaEqgk7pblkM1CHxEp5pvsZGQpnLHW4J7xrwpbk=; b=FucZ0aG/2X4VWkvDtlqvdS/1dib5rPOPxw0v5vtgobcgulqdq2kXDTv/Yu89A91q/826HpKhBKPxCXnl4U1L3Rzgf4+29bMOp8HDNu/MUcQceTs91xT2W2hJjp96WJCp3js5NMnRHwmdTNQJsWpjoq+R3LX093z4wJlBnXvjyWo=
Received: from DM5PR11MB2027.namprd11.prod.outlook.com (10.168.103.22) by DM5PR11MB1386.namprd11.prod.outlook.com (10.168.106.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2094.15; Thu, 25 Jul 2019 20:26:40 +0000
Received: from DM5PR11MB2027.namprd11.prod.outlook.com ([fe80::2ce9:4479:69b6:d12c]) by DM5PR11MB2027.namprd11.prod.outlook.com ([fe80::2ce9:4479:69b6:d12c%4]) with mapi id 15.20.2094.013; Thu, 25 Jul 2019 20:26:40 +0000
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: Susan Hares <shares@ndzh.com>, "'Albert Fu'" <afu14@bloomberg.net>, "idr@ietf.org" <idr@ietf.org>
CC: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: [Idr] draft-merciaz-idr-bgp-bfd-strict-mode
Thread-Index: AQHVQyZEs3uqzXY/bUCNHu2zKW3otKbbxrOAgAAA9zA=
Date: Thu, 25 Jul 2019 20:26:40 +0000
Message-ID: <DM5PR11MB202727A18322CE10B30D93F2C1C10@DM5PR11MB2027.namprd11.prod.outlook.com>
References: <5D3A0EB4029103460087056A_0_2148724@msclnypmsgsv03> <01c901d54326$80a67af0$81f370d0$@ndzh.com>
In-Reply-To: <01c901d54326$80a67af0$81f370d0$@ndzh.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=ketant@cisco.com;
x-originating-ip: [2001:420:c0c8:1002::8]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 05409174-108c-4090-3933-08d7113e66f2
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:DM5PR11MB1386;
x-ms-traffictypediagnostic: DM5PR11MB1386:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <DM5PR11MB1386EFED84E6A755A49B8BE1C1C10@DM5PR11MB1386.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0109D382B0
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(376002)(39860400002)(396003)(346002)(136003)(189003)(199004)(53936002)(81166006)(6506007)(76176011)(110136005)(7696005)(33656002)(25786009)(99286004)(54906003)(74316002)(7736002)(66946007)(52536014)(186003)(6246003)(476003)(66556008)(102836004)(5660300002)(8936002)(229853002)(76116006)(66476007)(66446008)(316002)(2906002)(64756008)(81156014)(478600001)(6306002)(2501003)(86362001)(68736007)(14454004)(55016002)(6436002)(236005)(11346002)(71200400001)(446003)(54896002)(9686003)(486006)(256004)(14444005)(6116002)(790700001)(8676002)(4326008)(53546011)(9326002)(71190400001)(46003); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR11MB1386; H:DM5PR11MB2027.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: 0BAxhPBuYG94IkA+FlHdiJd922AQ6yCy0GK2CUiyqUaN4DZR614AXMtC5AEu/QnEt3sQLYZg9Z5eFkoOXT/XqaUTC2Ozw/BNOueUAk9DZXdSwoifvEO4+pI1fT4gGX81U9AhGQfCYtI3Zdw3Zc1xWQsQzWnPfhwNGqZHLS4qXDlKizF3jDLjeoYA1VUEa5Rn3fC67i1JSnRgvi/pqOWys3CEKxegWD6KvlXsvpEh/oQ24XC59RtU+kcLG4vAiRsKoEEPvk6C3RfN7NZU5MdVq7TWDDsw7NuYtN3yXP0kCdzCEA9QvrYVtw1XKozVIvv0+FpZHcl7vyUrXcxbzcLZ2+xvZxgBWkCjRF5bcYBt8QGKltmGydAMnddg/BuNQ2snJJB93nNmTx2GvsKGBgkvwhfKcgAt5Az/loOiqn4NZnw=
Content-Type: multipart/alternative; boundary="_000_DM5PR11MB202727A18322CE10B30D93F2C1C10DM5PR11MB2027namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 05409174-108c-4090-3933-08d7113e66f2
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Jul 2019 20:26:40.7107 (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: ketant@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR11MB1386
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.13, xch-aln-003.cisco.com
X-Outbound-Node: rcdn-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/WOOyspV-70VP6NIJIU9mreKlxE0>
Subject: Re: [Idr] 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: Thu, 25 Jul 2019 20:26:59 -0000

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> On Behalf Of Susan Hares
Sent: 25 July 2019 16:21
To: 'Albert Fu' <afu14@bloomberg.net>et>; 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