> IMO the issues you raise were not considered during > the development of session timer, and it doesn't > really address them. As a result there are some > ambiguities.
Hi Paul, The comments were raised; however I'm not sure they were considered. :) http://www1.ietf.org/mail-archive/web/sip/current/msg10194.html And similar race conditions have been raised concerning things updatable within a dialog by things like INVITE, UPDATE, SUBSCRIBE, 2xx, and other requests. https://lists.cs.columbia.edu/pipermail/sip-implementors/2002-November/0 04089.html <snip> > As a result, we can speculate on the best way to handle > these things, but it may require a new RFC, or at least > a BCP, to have any confidence that these things work. I agree that a solution or BCP would be beneficial. However if possible, I'd prefer a generic solution or BCP instead of an individual solution for each header and race condition. The problem exists for almost any header/body updatable within a dialog by things like INVITE, UPDATE, SUBSCRIBE, NOTIFY, REFER, 2xx, 1xx, and other requests. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
