Re: [manet] Request table and ID FIFO cache of DSR

Dave Maltz <dmaltz+ietf@cs.cmu.edu> Fri, 15 August 2003 19:26 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10424 for <manet-archive@odin.ietf.org>; Fri, 15 Aug 2003 15:26:16 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nkCr-0005Oc-3R for manet-archive@odin.ietf.org; Fri, 15 Aug 2003 15:25:49 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7FJPnmj020742 for manet-archive@odin.ietf.org; Fri, 15 Aug 2003 15:25:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nkCq-0005OT-SO for manet-web-archive@optimus.ietf.org; Fri, 15 Aug 2003 15:25:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10380 for <manet-web-archive@ietf.org>; Fri, 15 Aug 2003 15:25:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19nkCp-0005M1-00 for manet-web-archive@ietf.org; Fri, 15 Aug 2003 15:25:47 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19nkCo-0005Ly-00 for manet-web-archive@ietf.org; Fri, 15 Aug 2003 15:25:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nkC5-0005F3-UU; Fri, 15 Aug 2003 15:25:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nkBQ-0005ER-21 for manet@optimus.ietf.org; Fri, 15 Aug 2003 15:24:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10312 for <manet@ietf.org>; Fri, 15 Aug 2003 15:24:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19nkBO-0005Ks-00 for manet@ietf.org; Fri, 15 Aug 2003 15:24:18 -0400
Received: from wexford-2.cmcl.cs.cmu.edu ([128.2.198.115]) by ietf-mx with smtp (Exim 4.12) id 19nkBN-0005Kl-00 for manet@ietf.org; Fri, 15 Aug 2003 15:24:17 -0400
Received: from wexford-2.cmcl.cs.cmu.edu ([127.0.0.1]) by wexford-2.cmcl.cs.cmu.edu id aa09479; 15 Aug 2003 15:23 EDT
From: Dave Maltz <dmaltz+ietf@cs.cmu.edu>
To: Young-Jun Lee <gte393q@mail.gatech.edu>
cc: manet@ietf.org, dmaltz@cs.cmu.edu
Subject: Re: [manet] Request table and ID FIFO cache of DSR
References: <Pine.SOL.4.33.0307291734020.27129-100000@acmex.gatech.edu>
Date: Fri, 15 Aug 2003 15:23:27 -0400
Message-Id: <E19nkBN-0005Kl-00@ietf-mx>
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>

In message <Pine.SOL.4.33.0307291734020.27129-100000@acmex.gatech.edu>, Young-J
un Lee writes:
>I'm trying to implement DSR protocol in a simulation tool.
>While reading the DSR draft (draft-ietf-manet-dsr-08.txt),
>I found the request table structure a little bit confusing.
>
>In Page 28 of the draft, it says route request table records information
>about route request, i.e. <id, dst> using ID fifo cache.
>Does this mean that this ID fifo cache is a field of request table entry?
>Or, is the ID fifo cache a separate data structure?

My intention was that the ID cache is a field of the request table
entry, although you do not have to design it that way.  The DSR spec
only defines the conceptual data structure for a Route Request table.

The requirments are that given a src and an ID, a node must be able to
determine whether it has already forwarded route request #ID from that
src.  The node should not remember more than RequestTableIds IDs.

>I checked the DSR model in ns-2 and the DSR linux implementation by univ.
>Colorado, but both do not have any data structure like ID fifo cache.
>I'd appreciate it if anybody gives me some hints on this.

The reason for limiting the cache to contain only RequestTableIds IDs
is that when a node reboots it may lose track of what IDs were on its
recent Route Requests.  If the node is extremely unlucky, it might
reuse IDs it had already sent, causing neighbors to drop the new Route
Requests as duplicates.  Limiting the amount of history the neighbors
can store limits the total length of time the node can be unlucky (the
counter balancing factor that keeps us from setting RequestTableIds to
1 is that for Route Discovery to be most efficient, a single node
should not have more than RequestTableIds Route Requests outstanding
at one time).

Since we did not intend our ns-2 simulations to model individual nodes
crashing and rebooting, we did not implement the ID cache in the ns-2
model.

We did implement it in our FreeBSD kernel implementation.  (available
from www.monarch.rice.edu, see freebsd/sys/dsr/requesttable.h)

Cheers,
 -dam

_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet