-----Original Message-----
From: Sunil Kumar T [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 13, 2001 1:30 AM
To: Jonathan Rosenberg
Cc: SIP implementors; Anand Vasudevan; Poornima Holla
Subject: Re: [Sip-implementors] Help required on Client and Server FSMs
Hi Jonathan,
>>> please consider bis-03.
>>>
>>> UDP
>>> -----
>>> a) pg 77, figure 10 - how long should the client wait in "COMPLETED"
>>> state? Is it 16 sec ?
>>
>>No. Once completed, you're completed. You can destroy the FSM.
>>sec 14.4.1 says "Response retransmissions cease when an ACK request is
>>received or the response has been transmitted seven times."
>
>If the FSM at client is destroyed after sending the ACK, how will the
client
>service response retransmissions sent by the server? Also, the self-loop
>(status/ACK) on COMPLETED state in fig 10 contradicts the above statement
of
>spec(sec 14.4.1)
>
>I believe this holds good in TCP also.
Oops, this is my mistake. I was confused here. It seems that the client and
server machines inconsistently define the completed state. For the server,
completed means that the machine can be destroyed. But for the client, its
not so. It needs to wait there for 16 seconds, as you point out, to handle
any stray responses that still need to be ACKed, and then it can be
destroyed. I need to add another state to that client machine.
-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
