Re: [manet] AODV: previous hop for RREP

Bart Braem <bart.braem@ua.ac.be> Mon, 01 November 2004 15:44 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 KAA22294 for <manet-web-archive@ietf.org>; Mon, 1 Nov 2004 10:44:29 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COeb6-0001XE-6r for manet-web-archive@ietf.org; Mon, 01 Nov 2004 10:59:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COcd0-0002wm-8d; Mon, 01 Nov 2004 08:53:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COZiz-0008MC-KK for manet@megatron.ietf.org; Mon, 01 Nov 2004 05:47:45 -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 FAA14782 for <manet@ietf.org>; Mon, 1 Nov 2004 05:47:44 -0500 (EST)
Received: from oola.is.scarlet.be ([193.74.71.23]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COZxp-00046O-Aq for manet@ietf.org; Mon, 01 Nov 2004 06:03:09 -0500
Received: from (u81-11-142-183.adsl.scarlet.be [81.11.142.183]) by oola.is.scarlet.be with ESMTP id iA1AlVG21155 for <manet@ietf.org>; Mon, 1 Nov 2004 11:47:31 +0100
From: Bart Braem <bart.braem@ua.ac.be>
To: manet@ietf.org
Subject: Re: [manet] AODV: previous hop for RREP
Date: Mon, 01 Nov 2004 11:47:31 +0100
User-Agent: KMail/1.7
References: <A4E682B8A936374A9190A3A0FEE412F213987A@xmail10.ad.ua.ac.be>
In-Reply-To: <A4E682B8A936374A9190A3A0FEE412F213987A@xmail10.ad.ua.ac.be>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200411011147.31553.bart.braem@ua.ac.be>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
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>
Sender: manet-bounces@ietf.org
Errors-To: manet-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit

> Well basicaly, it means that when you receive a RREP, you just forward it
> as it would be expected: sending it in the direction of the node which
> originated the RREQ. You have a route to that node, because that route
> has been reated when you received the RREQ (in the old AODV drafts
> terminology: the reverse route (the route that goes from the destination
> till the originator that is created when RREQ is being forwarded).
>
> But you don't send it to the originator node directly. You just
> forward it to the next hop of the route to the originator.
> And that next hop will do the same. And so on, till it
> reaches the node that originated the RREQ.

Okay I understand the principle. So that previous hop mentioned in the first 
paragraph is the next node which will send the RREP to the originator of the 
RREQ.
But what happens when no valid route to the previous hop is found? It says "If 
needed, a route is created for the previous hop, but without a valid sequence 
number." I can create a new route table entry but then the RREP is stuck with 
me... A little bit further: "...  the node consults its route table entry    
for the originating node to determine the next hop for the RREP packet, and 
then forwards the RREP towards the originator using the information in that 
route table entry." So a route to the next hop of presumed?

Thanks for your help
Bart

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