> > An outstanding session-expires mechanism > > should not prevent another from occurring. > > However there is a potential for race conditions > > concerning knowing if UPDATE sent/received > > prior to INVITE 200 response. > > Why cant this be addressed say using something > like the SDP offer/answer semantics? > a subsequent session refresh cant be made > unless the previous request has been answered?
RFC 4028 currently does not have the restriction. Although it would not typically be an issue, such a restriction would prevent refreshing a session while it is taking too long for a re-INVITE to complete. As mentioned, RFC 4028 isn't the only issue. Such race conditions can basically occur for anything that can be updated within a dialog when order sent/received indeterminate (excluding situations remedied by SDP offer/answer rules). If the SIP working group wishes to address it, hopefully the working group would address it in a generic way instead of individually. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
