Re: CARD: handling of sequence numbers

Marco Liebsch wrote:
> Right, but your example assumes the successful case for sending a quick
> new request where the reply to the previous request has been received.
> What if a reply does not appear for some reasons after 500ms
> and a MN just sends a new request. 

in my earlier mail, I said it doesnt matter if there was a
reply or not to the earlier request. this is *another*
request.


> Then we can run into the timer 
> setting problem,
> which has been indicated by Henrik, on the current AR again. 

no you dont.

> Or we could 
> just
> allow the AR to "overwrite" the running timer with the new request in 
> this case
> and ignore the previous request and associated possibly outstanding 
> signaling
> messages between ARs.

there is no overwriting timers. there is no one single
timer for all requests per mobile node.

the way to implement re-transmission is very simple. after
you send a request, you put the message in a queue. you
initialize a timer, store the timer and the request in a
new data structure and add this data structre to the
re-transmission queue. when a reply is received, both the
request and the timer are removed from the queue. if the
timer expires and no reply is received, the request is sent
again. the timer is reset.

if request2 was sent while request1 is still in the
retransmission queue, the timer on request1 is not reset.
another timer is created and a new element is added to the
re-transmission queue. got it?

Vijay