Mallik, We have made delay measurement an optional feature secondly we can measure RX side delay locally it is Tx side which is a problem and hence we have time stamping. We did mention that we can send timestamping info to central unit where the calculation can be done in that case BFD packet need not carry any timestamp. Did I answer your question?
Thanks Santosh P K From: MALLIK MUDIGONDA (mmudigon) [mailto:[email protected]] Sent: Friday, June 12, 2015 2:03 PM To: Santosh P K; [email protected] Subject: Re: New Version Notification for draft-ashesh-bfd-stability-03.txt Hi, I need a quick clarification on the need for the sender time stamp here. If the delay is measured by comparing the time stamps of two consecutive packets, it can be done on the local end. Why send it to the other end? Receive time stamp can still happen to measure the Rx path delays. I understand that we need to always maintain the previous packets TS to achieve this. Asking this because we can measure these delays independently at both ends unless you are also looking at accommodating transit delays over the link. Thanks Regards Mallik From: Santosh P K <[email protected]<mailto:[email protected]>> Date: Thursday, 11 June 2015 11:48 To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: FW: New Version Notification for draft-ashesh-bfd-stability-03.txt Hello All, A new version of draft has been submitted. Below are the changes made. 1. Added use cases for BFD stability. 2. Addressed review comments given in BFD working group. 3. Added delay measurement details. Please do review and get back to us with review comments. Thanks Santosh P K > -----Original Message----- > From: [email protected]<mailto:[email protected]> > [mailto:[email protected]] > Sent: Wednesday, June 10, 2015 2:19 PM > To: Mach Chen; Ankur Saxena; Mahesh Jethanandani; Santosh P K; Santosh P > K; Ankur Saxena; Ashesh Mishra; Peng Fan; Mach Chen; Mahesh > Jethanandani; Peng Fan; Ashesh Mishra > Subject: New Version Notification for draft-ashesh-bfd-stability-03.txt > > > A new version of I-D, draft-ashesh-bfd-stability-03.txt has been successfully > submitted by Santosh Pallagatti and posted to the IETF repository. > > Name: draft-ashesh-bfd-stability > Revision: 03 > Title: BFD Stability > Document date: 2015-06-10 > Group: Individual Submission > Pages: 7 > URL: > https://www.ietf.org/internet-drafts/draft-ashesh-bfd-stability-<https://www.ietf.org/internet-drafts/draft-ashesh-bfd-stability-03.txt> > 03.txt<https://www.ietf.org/internet-drafts/draft-ashesh-bfd-stability-03.txt> > Status: https://datatracker.ietf.org/doc/draft-ashesh-bfd-stability/ > Htmlized: https://tools.ietf.org/html/draft-ashesh-bfd-stability-03 > Diff: > https://www.ietf.org/rfcdiff?url2=draft-ashesh-bfd-stability-03 > > Abstract: > This document describes extensions to the Bidirectional Forwarding > Detection (BFD) protocol to measure BFD stability. Specifically, it > describes a mechanism for detection of BFD frame loss. > > > > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > The IETF Secretariat
