Subject: [manet] AODVv2 routing table entry state issue

From: Lotte Steenbrink <[email-masked]>
Date: Fri, 28 Feb 2014 17:47:21 +0100

Dear all,
I realize you're probably busy preparing for London, but maybe this is still relevant to somebody's interests.
I'd like to propose a small change to the AODVv2 Draft in order to make it a bit more exhaustive.

While the Draft states that Idle routes may be used for forwarding, it doesn't state any condition under which a route may become Active again. This didn't make sense to me, so I asked Charlie and he confirmed that an Idle route should indeed become Active when it is used for forwarding. As a consequence, I'd like to propose the following change 

On Page 11:

   When a route
   is no longer Active, it becomes an Idle route.  After an idle route
   remains Idle for MAX_IDLETIME, it becomes an Expired route.

to

   When a route
   is no longer Active, it becomes an Idle route. Whenever an Idle
   route is used for forwarding, it becomes Active. After an idle route
   remains Idle for MAX_IDLETIME, it becomes an Expired route.

As always, comments are much appreciated.

With kind regards,
Lotte Steenbrink