Echo Function and Asymmetry - Timer negotiation
"Tanya Shastri \(tanyas\)" <tanyas@cisco.com> Thu, 11 August 2005 20:58 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E3K8X-0002fo-GG; Thu, 11 Aug 2005 16:58:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E3K8R-0002fc-MV for rtg-bfd@megatron.ietf.org; Thu, 11 Aug 2005 16:58:47 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27204 for <rtg-bfd@ietf.org>; Thu, 11 Aug 2005 16:58:41 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E3Kgo-0000Dj-EE for rtg-bfd@ietf.org; Thu, 11 Aug 2005 17:34:16 -0400
Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-3.cisco.com with ESMTP; 11 Aug 2005 13:58:32 -0700
X-IronPort-AV: i="3.96,100,1122879600"; d="scan'208,217"; a="331423825:sNHT50068542"
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j7BKwSoq003560 for <rtg-bfd@ietf.org>; Thu, 11 Aug 2005 13:58:30 -0700 (PDT)
Received: from xmb-sjc-213.amer.cisco.com ([171.70.151.153]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 11 Aug 2005 13:58:28 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C59EB7.6C39BDC5"
Date: Thu, 11 Aug 2005 13:58:27 -0700
Message-ID: <B6D0BC3B6B7DEA43ADAB00368CF984FA84BCC4@xmb-sjc-213.amer.cisco.com>
Thread-Topic: Echo Function and Asymmetry - Timer negotiation
Thread-Index: AcWet2u3Jl2hKs6hQBidAQ4LNHIcWg==
From: "Tanya Shastri (tanyas)" <tanyas@cisco.com>
To: rtg-bfd@ietf.org
X-OriginalArrivalTime: 11 Aug 2005 20:58:28.0306 (UTC) FILETIME=[6C4C2320:01C59EB7]
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Subject: Echo Function and Asymmetry - Timer negotiation
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
For an Asynchronous BFD session that has Asymmetric Echo function the following statements in the spec seem to be misleading, unless I am missing something. Section 6.4 says: "When a system is using the Echo function, it is advantageous to choose a sedate transmission rate for Control packets since liveness detection is being handled by the Echo packets." Shouldn't it be the receive rate - or the transmission rate of Control packets of the remote system - that should be sedate? Also the end that does not have echo mode active relies on Control packets for liveness detection and may still want to receive Control packets at a faster rate. Section 6.7.3 says: " When the Echo function is active, a system SHOULD set bfd.DesiredMinTxInterval to a value of not less than one second" >From the description in 6.7.4 this will force the remote end to have a Detect Timer no faster than 1 second, since the Detect Timer is based on the transmit rate of the remote system. Also this will not reduce the rate at which it sends control packets to the end that has echo mode active. Wouldn't it be better to suggest that "RequiredMinRxInterval" in BFD control packets should be set to a minimum of 1 second by the end that has echo function active? Thanks, Tanya
- Echo Function and Asymmetry - Timer negotiation Tanya Shastri (tanyas)
- Re: Echo Function and Asymmetry - Timer negotiati… Dave Katz
- Re: Echo Function and Asymmetry - Timer negotiati… Reshad Rahman
- RE: Echo Function and Asymmetry - Timer negotiati… richard.spencer
- Re: Echo Function and Asymmetry - Timer negotiati… Reshad Rahman
- RE: Echo Function and Asymmetry - Timer negotiati… richard.spencer
- Re: Echo Function and Asymmetry - Timer negotiati… Reshad Rahman
- RE: Echo Function and Asymmetry - Timer negotiati… richard.spencer
- Re: Echo Function and Asymmetry - Timer negotiati… Reshad Rahman