 |
 |
 |
 |
|
 |
|
 |
|
 |
|
 |
|
|
|
|
|
|
|
|
|
|
|
|
|
Hi
David,
I
thought Detection Multiplier is a parameter sent by a local system to a remote
system, so that the remote system can compute the Detection Interval Timer. What
do you mean by "Detection Multiplier is a Local matter"? If it is a local matter
then why is it communicated to the remote system?
I
think I am not clear on the definition of Detection Multiplier. The base draft
defines it as:
Detect Mult "Detection time multiplier. The negotiated transmit interval, multiplied by this value, provides the Detection Time for the transmitting system in Asynchronous mode."
May be you could explain it in the following example: A
------------------------------->B BFD packets send from A --> B: Detect Mult=A1, Desired Min Tx Interval = A2, Require Min RX Interval =A3 BFD packets send from B --> A: Detect Mult=B1, Desired Min Tx Interval = B2, Require Min RX Interval =B3 The Detection Window at B = A1 * Max (A2, B3) The Detection Window at A = B1 * Max (B2, A3) Is this computation correct?
Thanks,
Shahram
From: David Ward [mailto:dward at cisco.com] Sent: Tuesday, August 18, 2009 10:22 PM To: Shahram Davari Cc: David Ward; rtg-bfd at ietf.org Subject: Re: Parameter change 6.8 and 10 clearly state that the rules of 6.8.3 apply. I don't believe
there is a need for more verbiage than exists.
6.8.12 is discussing a different attribute, the detect multiplier. It
clearly states that a poll sequence is not necessary. This should be obvious as
the detectmult is a local matter and doesn't affect anything on the remote
end.
You do need to use the poll sequence in all cases. Demand mode setting is
orthogonal.
-DWard
On Aug 18, 2009, at 9:30 PM, Shahram Davari wrote:
|