Detection time in demand mode
roggie-bfd@sohu.com Sun, 20 March 2005 12:13 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10625; Sun, 20 Mar 2005 07:13:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DCzNh-0002mT-0b; Sun, 20 Mar 2005 07:18:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DCzII-0007ny-5B; Sun, 20 Mar 2005 07:12:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DCzIH-0007nt-DU for rtg-bfd@megatron.ietf.org; Sun, 20 Mar 2005 07:12:33 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10587 for <rtg-bfd@ietf.org>; Sun, 20 Mar 2005 07:12:29 -0500 (EST)
From: roggie-bfd@sohu.com
Received: from [61.135.132.204] (helo=websmtp1.mail.sohu.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DCzN5-0002lz-PZ for rtg-bfd@ietf.org; Sun, 20 Mar 2005 07:17:33 -0500
Received: from mx66.mail.sohu.com (unknown [192.168.95.81]) by websmtp1.mail.sohu.com (Postfix) with ESMTP id 73D491B342608; Sun, 20 Mar 2005 20:12:22 +0800 (CST)
Message-ID: <13616729.1111320742672.JavaMail.postfix@mx66.mail.sohu.com>
Date: Sun, 20 Mar 2005 20:12:22 +0800
To: dkatz@juniper.net
Mime-Version: 1.0
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: 8bit
X-Mailer: Sohu Web Mail 2.0.13
X-SHIP: 219.239.105.83
X-Priority: 3
X-SHMOBILE: 0
X-Sohu-Antivirus: 0
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 8bit
Cc: rtg-bfd@ietf.org
Subject: Detection time in demand mode
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
Sender: rtg-bfd-bounces@ietf.org
Errors-To: rtg-bfd-bounces@ietf.org
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 8bit
Dave, In section 6.7.4 , it said : In Demand mode, the Detection Time calculated in the local system is equal to bfd.DetectMult, multiplied by the agreed transmit interval (the greater of bfd.RequiredMinRxInterval and the last received Desired Min TX Interval.) bfd.DetectMult is (roughly speaking, due to jitter) the number of packets that have to be missed in a row to declare the session to be down. From the above sentence , i get the flowing conclosion , for example : A------------------B DM=3 DM=1 MTI=100ms MTI=10ms MRI=20ms MRI=200ms if A sends a poll sequence , the transmit interval is 200ms[max(100ms,200ms)] , the detection time is 60ms[3*max(20ms,10ms)] , is it correct?? another question : in the spec , it always said "If Demand mode is not active" , i wants to ask is it the flowing meaning if one side set to demand mode and the other side dose not set , the side setted to demand mode also MUST send period control packet ? i am not sure ! Thanks Roggie
- Detection time in demand mode roggie-bfd
- Re: Detection time in demand mode Dave Katz