Re: Tuning BFD session times

Ashesh Mishra <mishra.ashesh@outlook.com> Sun, 01 April 2018 17:17 UTC

Return-Path: <mishra.ashesh@outlook.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 4AD88127023 for <rtg-bfd@ietfa.amsl.com>; Sun, 1 Apr 2018 10:17:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Level:
X-Spam-Status: No, score=-2.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outlook.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 Dcx7zdgk-0xP for <rtg-bfd@ietfa.amsl.com>; Sun, 1 Apr 2018 10:17:43 -0700 (PDT)
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (mail-oln040092006100.outbound.protection.outlook.com [40.92.6.100]) (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 D4583126DCA for <rtg-bfd@ietf.org>; Sun, 1 Apr 2018 10:17:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=LHct8foE0VpcYc8o0r6rHujTJLK5yVFEj4Ez3Zo+Okk=; b=m+SlX/1JvRjARy2Q8dihLz6AfDb5bxX+2QLy9Rc0Eek8pjWRNviboGQbgYyq22dhsdGN7yb5UG8PqE5J5BHzUVHxPa3JClsGPvDA1yTMu6rZA09phl4Arfnlo0fbzLpByeAjvoGNQuDKGho8PdouQkj4hlS35S7WMmYg8w+6Rgmr7a7/VvEYv/wrLk4F3Ki+qiQgwhq5Izo2AC2sL7YTqpYAXCk/JgMjzFCJThIABvq64CiGFGidDImM42cFBnkJn856j+gbPqnnEC3+YvpBOA9R2Z0D99DqYN/VyJBhphTT/XEy4xs8TyffFpN5g3mWPRFpKE11IMwWiECyWSyYtg==
Received: from BY2NAM03FT004.eop-NAM03.prod.protection.outlook.com (10.152.84.59) by BY2NAM03HT076.eop-NAM03.prod.protection.outlook.com (10.152.85.28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.631.7; Sun, 1 Apr 2018 17:17:42 +0000
Received: from BL0PR0102MB3345.prod.exchangelabs.com (10.152.84.58) by BY2NAM03FT004.mail.protection.outlook.com (10.152.84.66) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.631.7 via Frontend Transport; Sun, 1 Apr 2018 17:17:42 +0000
Received: from BL0PR0102MB3345.prod.exchangelabs.com ([fe80::a5f3:348:c9a1:1754]) by BL0PR0102MB3345.prod.exchangelabs.com ([fe80::a5f3:348:c9a1:1754%3]) with mapi id 15.20.0631.013; Sun, 1 Apr 2018 17:17:42 +0000
From: Ashesh Mishra <mishra.ashesh@outlook.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
CC: Jeffrey Haas <jhaas@pfrc.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Subject: Re: Tuning BFD session times
Thread-Topic: Tuning BFD session times
Thread-Index: AQHTxsWKBNltmss7WESLSBbS7Nadv6Pr+FuygAAnGYCAAAl1kg==
Date: Sun, 01 Apr 2018 17:17:41 +0000
Message-ID: <BL0PR0102MB33453186C4DE4B6646FD67FEFAA70@BL0PR0102MB3345.prod.exchangelabs.com>
References: <20180328184959.GB25442@pfrc.org> <BL0PR0102MB3345EC535EE558FC4CC692E6FAA70@BL0PR0102MB3345.prod.exchangelabs.com>, <DB3PR03MB0969877EE63E4514F3975D6C9DA70@DB3PR03MB0969.eurprd03.prod.outlook.com>
In-Reply-To: <DB3PR03MB0969877EE63E4514F3975D6C9DA70@DB3PR03MB0969.eurprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-incomingtopheadermarker: OriginalChecksum:78DC7C1312B4EF5199C13460FB9DF0AB6F33CE83B4BB55C68466346427798FFA; UpperCasedChecksum:FD70B3F6A6789B22B4F64B39E6315BD28E3B43832D615467E51F3068CB9CDACE; SizeAsReceived:7264; Count:47
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [K5tKdIFfLPI082GOu5S63TeNzrPwgiYE]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BY2NAM03HT076; 7:fYVsog3ZXFPEzUQV+kvm2IMZU4pf/NGr900AZq+amt4VbjN4FpKeesKSBhu4G5GNx4ucojDcDYqWD5vRv099372sD8NS5LneqP0KDSxce3TBRMOSjCfHTA+XJVUbiwD8dfPrCdGPzud1bbku6ePk5kbk3RnYHxobrJhEWmH/8xsfs9v01qnqlozstIU9s8mw7XbO/4jOH+yUmAw0RM9CIQ61dUVO8teiWVeHtcFNA72O606z/2KpE9oTU4t5A0xz
x-incomingheadercount: 47
x-eopattributedmessage: 0
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1601125374)(1603101448)(1701031045); SRVR:BY2NAM03HT076;
x-ms-traffictypediagnostic: BY2NAM03HT076:
x-ms-office365-filtering-correlation-id: e48d1911-8763-4386-3112-08d597f47a40
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:BY2NAM03HT076; BCL:0; PCL:0; RULEID:; SRVR:BY2NAM03HT076;
x-forefront-prvs: 06290ECA9D
x-forefront-antispam-report: SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:BY2NAM03HT076; H:BL0PR0102MB3345.prod.exchangelabs.com; FPR:; SPF:None; LANG:;
x-microsoft-antispam-message-info: SKBJwbXx7IKgW7tkJyrx5eJJ9dvVnGtX8X2OZSFw0Q5jujQEnS06djebme50u4MyN/CNpkYBn5fZws6gweCTCcvuA2PT0fef9CjSmj5+jkGIeY0ROrYs+9hU759OWXOGMCAYNvvsCfmEnzRsndqFGpQSYM/mR7Mcfd1Z3vmeNdEBFm2MDQUPLxHZOLhp2aaP
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BL0PR0102MB33453186C4DE4B6646FD67FEFAA70BL0PR0102MB3345_"
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: e48d1911-8763-4386-3112-08d597f47a40
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Apr 2018 17:17:41.8041 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2NAM03HT076
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/bIh8XJNOuj9Egv0XCeiiC-lbGKM>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 01 Apr 2018 17:17:47 -0000

Hi Sasha,


There are two scenarios here and they depend on whether the satellite is in geo-stationary orbit (GEO) or non-geo-stationary orbit (NGSO).


Scenario-1: Non-Geostationary Satellites: This is the scenario that you described. Satellites in Middle Earth Orbit (MEO) or Low Earth Orbit (LEO) move relative to the earth and hence, their distance from the ground terminals varies as they pass over a given location. This results in varying RTT (sometimes by as much as 30ms). The issue in this scenario is not necessarily that the BFD detect interval must change frequently but that it's difficult to accurately select the intervals as the RTT depends on the location of the terminal and the gateway (and this gets quite complex). If the session can automatically decide the interval, then the complexity in starting a new service is reduced. Another complicating factor is when the terminal moves (ship or aircraft, for example) as this increases the variance of the RTT. We typically set the intervals to a high enough level but that affects the performance. We see the same varying RTT in GEO when the terminal is mobile but the percentage change is much smaller than the overall RTT of GEO (because GEO satellites are much farther away from the earth at ~36,000kms vs MEO at ~8,000kms and LEO at ~200-1000kms).


Scenario-2: Low-latency link backed up by high-latency link: In this case a GEO satellite backs up NGSO-based connection or fiber (or other terrestrial wired/wireless WAN options). The end-to-end service then has very different RTT when the primary is active versus when the backup is active. The typical solution is to base timers on the backup RTT, which is very inefficient.


Regards,

Ashesh

________________________________
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Sent: Sunday, April 1, 2018 9:28:43 AM
To: Ashesh Mishra
Cc: Jeffrey Haas; rtg-bfd@ietf.org
Subject: RE: Tuning BFD session times


Ashesh,

I would like to understand better the use case with satellite links that you have described.

In particular, can you please explain why long RTT affects the BFD detection times?

As I see it, what could really affect these times is variable delay introduced in some cases by the satellite links since the distance between the satellite and the terrestrial antennae may change significantly with time.



What did I miss?



Regards,

Sasha



Office: +972-39266302

Cell:      +972-549266302

Email:   Alexander.Vainshtein@ecitele.com



From: Rtg-bfd [mailto:rtg-bfd-bounces@ietf.org] On Behalf Of Ashesh Mishra
Sent: Sunday, April 1, 2018 5:54 PM
To: Jeffrey Haas <jhaas@pfrc.org>; rtg-bfd@ietf.org
Subject: Re: Tuning BFD session times



Jeff, thanks for kicking-off this discussion on the list!



One additional comment that I wanted to make was around automation. There were questions during the meeting around the need for auto-tuning and that the process of determining the interval can/should be manual.



The automation of control in all aspects of dynamic behavior is a priority for network operators. When configuring manually, parameters such BFD intervals are typically set at very conservative values because human latency is very high when responding to changing network conditions. Manual configuration also takes a lot of time and is accounts for significant number of lost opportunities and value for operators.



[JH] "applications should generally choose a detection interval that is reasoanble for their application rather than try to dynamically discover the lowest possible stable detection interval. "

[AM] This depends on the use-case. From the point-of-view of a service provider that delivers long-haul connectivity (typical scenario in which the link characteristics have large variance) then the intent is to provide the best performance. As such providers deliver connectivity to critical applications, and are often the only way of delivering connectivity in such places, the ability to tune the system to deliver an up-time that is superior drives significant value. Consider a scenario where there is a 130ms RTT link (MEO satellite, LEO will be in the 20-60ms range) and its backup is a 600ms RTT link (GEO satellite), and are being used to deliver transit connectivity. The rate at which the end-to-end service can run BFD is significantly faster when MEO is active versus when GEO is active. The application, in this scenario, may survive the RTT, but the business continuity is critical in many cases. Since the provider of long-haul can not control the application, it must provide the best possible failover performance.



[JH] "1. BFD is asymmetric..  This means a receiving BFD implementation must provide feedback to a sending implementation in order for it to understand perceived reliability."

[AM] May not need to be the BFD implementation providing the feedback if there are other performance mechanisms running. The challenge is to standardize the mechanism that BFD can use (if the measurement is not self-contained in BFD). You're right in pointing out the challenge in accounting for the CPU delays and that was the reason for the original proposal for BFD performance measurement. If the measurement is within the BFD realm, it will account for the CPU delays. However, most good BFD engines have relatively deterministic performance and are quite optimized so the variance with scale and time is not significant (but I concede that not all BFD implementations are good).



[JH] "2. Measurement infrastructure may negatively impact session scale.  Greg, I believe, made this point when discussing host processing issues vs. BFD ingress/egress."

[AM] This is an issue if using a measurement mechanism within BFD (other performance measurement methods are always running in network for SLA reporting and/or network optimization). Within a metro-area with fiber or terrestrial wireless (microwave, LTE, etc.) connectivity, I would likely not need constant auto-tuning. The variance in the primary and backup links in such network will not be significant to affect the BFD parameters. In long-haul links, this may be a valuable feature in which case, the additional overhead may be justified. So it depends on the use-case whether continuous auto-tuning is required or if it is one-time.



[JH] "3. Detection interval calculations really need to take into account things that are greater than simple packet transmission times.  As an example, if your measurement is always taken during low system CPU or network activity, how high is your confidence about the interval?  What about scaling vs. number of total BFD sessions?"

[AM] Great questions. Typically when running BFD or CFM (or similar) high frequency OAM, CPU peaks should not affect the OAM performance (a variety of methods, based on the system on which OAM is running, can ensure that). CPU peaks become a bigger issue if BFD is used to detect continuity for a particular flow (or QoS).



--

Asheh

________________________________

From: Rtg-bfd <rtg-bfd-bounces@ietf.org<mailto:rtg-bfd-bounces@ietf.org>> on behalf of Jeffrey Haas <jhaas@pfrc.org<mailto:jhaas@pfrc.org>>
Sent: Wednesday, March 28, 2018 11:49 AM
To: rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>
Subject: Tuning BFD session times



Working Group,

We had very active discussion (yay!) at the microphone as part of Mahesh's
presentation on BFD Performance Measurement.
(draft-am-bfd-performance)

I wanted to start this thread to discuss the greater underlying issues this
discussion raised.  In particular, active tuning of BFD session parameters.
Please note that opinions I state here are as an individual contributor.

BFD clients typically want the fastest, most stable detection interval that
is appropriate to their application.  That stability component is very
important since too aggressive of timers can result in unnecessary BFD
session instability which will impact the subscribing application.  Such
stability is a function of many things, scale of the system running BFD
being a major one.

In my opinion, applications should generally choose a detection interval
that is reasoanble for their application rather than try to dynamically
discover the lowest possible stable detection interval.  This is because a
number of unstable factors, such as CPU load, contention with other network
traffic and other things that are outside the general control of many
sytems may impact such scale.

That said, here's a few thoughts on active feedback mechanisms:
1. BFD is asymmetric.  This means a receiving BFD implementation must provide
   feedback to a sending implementation in order for it to understand
   perceived reliability.
2. Measurement infrastructure may negatively impact session scale.  Greg, I
   believe, made this point when discussing host processing issues vs. BFD
   ingress/egress.
3. Detection interval calculations really need to take into account things
   that are greater than simple packet transmission times.  As an example,
   if your measurement is always taken during low system CPU or network
   activity, how high is your confidence about the interval?  What about
   scaling vs. number of total BFD sessions?

I have no strong conclusions here, just some cautionary thoughts.

What are yours?

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