[manet] DSR route maintenance issue

manet user <manet_user@yahoo.com> Wed, 10 March 2004 00:03 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08276 for <manet-archive@odin.ietf.org>; Tue, 9 Mar 2004 19:03:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B0rBe-0004Nk-VW for manet-archive@odin.ietf.org; Tue, 09 Mar 2004 19:03:02 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2A032x2016840 for manet-archive@odin.ietf.org; Tue, 9 Mar 2004 19:03:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B0rBe-0004NX-Pf for manet-web-archive@optimus.ietf.org; Tue, 09 Mar 2004 19:03:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08244 for <manet-web-archive@ietf.org>; Tue, 9 Mar 2004 19:02:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B0rBb-0000O8-00 for manet-web-archive@ietf.org; Tue, 09 Mar 2004 19:02:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B0rAk-0000DC-00 for manet-web-archive@ietf.org; Tue, 09 Mar 2004 19:02:06 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B0r9r-00001Y-00 for manet-web-archive@ietf.org; Tue, 09 Mar 2004 19:01:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B0r9j-00043p-EQ; Tue, 09 Mar 2004 19:01:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B0r8u-00042X-Ck for manet@optimus.ietf.org; Tue, 09 Mar 2004 19:00:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08156 for <manet@ietf.org>; Tue, 9 Mar 2004 19:00:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B0r8r-0007ds-00 for manet@ietf.org; Tue, 09 Mar 2004 19:00:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B0r7p-0007TN-00 for manet@ietf.org; Tue, 09 Mar 2004 18:59:05 -0500
Received: from web61101.mail.yahoo.com ([216.155.196.103]) by ietf-mx with smtp (Exim 4.12) id 1B0r6v-00079X-00 for manet@ietf.org; Tue, 09 Mar 2004 18:58:09 -0500
Message-ID: <20040309235739.77247.qmail@web61101.mail.yahoo.com>
Received: from [141.156.71.10] by web61101.mail.yahoo.com via HTTP; Tue, 09 Mar 2004 15:57:39 PST
Date: Tue, 09 Mar 2004 15:57:39 -0800
From: manet user <manet_user@yahoo.com>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-365876440-1078876659=:76528"
Subject: [manet] DSR route maintenance issue
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL, HTML_MESSAGE autolearn=no version=2.60

Hi,
 
I have a question / concern regarding DSR route maintenance as suggested in the draft-ietf-manet-dsr-09. If i am using explicit acknowledgments for route maintenance, there are possibilities of receiving multiple duplicate packets. 
 
For instance, while forwarding data packet to next hop, i enable the bit in the packet header so that nexthop node should send me explicit ACK after receiving this data packet. If WLAN MAC layer is congested, my packet is still sitting at MAC to be retransmitted, whereas my ACK timer (50ms as suggested in draft) expires. I will retransmit the same data packet. This will lead to duplicate packets at destination. Under heavy traffic scenarios, this situation will happen frequently.
 
I did not find any measures in the draft for the same. Am i missing something in implemenation ? Please help. Thanks in advance.
 
-MU


---------------------------------
Do you Yahoo!?
Yahoo! Search - Find what you’re looking for faster.