Dale, Thanks for your reply.
> Once a request is sent or received, the UA > maintains a transaction state for that transaction. > In the UAS, this transaction state keeps a > record of the sent response,............. > ...... In a UAS, then the longest > allowed re-transmission time has expired, the > transaction state is destroyed (as a retransmitted > request can no longer be received). All this makes perfect sense if you are writing software for UA(s) only. IMHO one of the most powerful concept in 3261 is the separation of TU and Txn layer, which lies at the center of this issue/bug, where I had the question. > In the end, do not take the algorithms in 3261 > too literally. Instead, understand the > *purpose* of the algorithms. Agreed, but in this case it is not one of the several excellent algorithms/patterns that is in question but the transaction state machine *behavior*. Which is not only deterministic and nicely specified in state machine diagrams but also affects interoperability. Finally I learnt yesterday that this bug is going to be addressed by the WG in the next IETF timeframe. Thanks Nasir Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
