> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 15, 2001 8:50 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: [Sip-implementors] 100 Reliablility...
>
>
>
>
> Hi,
> According to the 100rel-03 draft, a UAS may send
> subsequent provisional responses (after receiving PRACK
> for the first) without waiting for acknowledgements of
> the previous RPR's. Sending RPR's in sequence (after each
> is PRACK'ed) is only _RECOMMENDED_ in the draft.
>
> This adds some complication to implementations. In
> reality, will such a scenario occur often ?
I don't know. I can think of cases where it might. For example, consider a
call queueing app thats using provisional responses to indicate the queue
size. A new provisional response is sent each time the queue size decreases
by one. It can certainly happen that two people are serviced one after the
other, in which case you might want to send one RPR right after another.
One could, alternatively, buffer the RPR and still do one transaction at a
time. At the moment, requests work this way. Bis-03 explicitly says that you
can't have more than one re-INVITE outstanding at a time. I don't know if we
have considered fully the implications of that, but if the consensus is that
that is indeed the approach taken, I would argue that for consistencies
sake, reliable provisional responses should work the same way.
-Jonathan R.
---
Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Ave.
Chief Scientist First Floor
dynamicsoft East Hanover, NJ 07936
[EMAIL PROTECTED] FAX: (973) 952-5050
http://www.jdrosen.net PHONE: (973) 952-5000
http://www.dynamicsoft.com
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
