Subject: Re: Soft State

From: Bob Braden <[email-masked]>
Date: Tue, 30 Nov 1999 11:18:38 -0800 (PST)

*> 
  *> one sender, one router and one receiver.
  *> 
  *> The sender sends a path message. Once the receiver gets it, it  sends a
  *> Resv msg. Because the receiver fails to receive several consecutive path

So, your question raises a number of questions.

Why does the receiver fail to receive several consecutive Path msgs?
According to the RSVP spec, this should almost never happen (the fact
that it does happen is the reason the WG is planning to change the spec
to include reliable delivery of RSVP messages).

  *> messages, the path and correspondent reservation are released at the
  *> receiver. After that, a path msg finally arrives to the receiver and the
  *> path state is reestablished in there. The application has not sent any

This scenario can happen more simply: the receiver application hangs out a
Resv before it receives a Path.  You could regard this as a synchronization
bug in the app, or you could just say that the app should be able to
start sending a Resv at any time without waiting for a Path upcall.

  *> other Resv request because it is happy with the current reservation. So,
  *> how may the reservation be reestablished if the application does not
  *> start to send Resv requests again?

This was answered by a later msg from Ramesh.

Bob Braden

  *> 
  *> I'm not considering tear down messages for the current version of my
  *> model.
  *> 
  *> Thank in advance.
  *> 
  *> 
  *> Maria
  *> 
  *> 
  *> 
  *> --
  *> Maria Elena Villapol
  *> PhD Student
  *> Institute for Telecommunications Research
  *> University of South Australia
  *> 
  *> email: [email-masked]
  *>        [email-masked]
  *> 
  *> Web Page: http://www.itr.unisa.edu.au/~maria/index.htm
  *> 
  *>