Re: [Sipping] Reconciling O/A rollback with dialog state rollback

["Brett Tate" <brett at broadsoft.com>]

> Christer's proposal 2 for the offer/answer situation 
> is to stay with whatever offer/answer exchange 
> completed successfully last (perhaps in the INVITE/183 below). 

I don't have a strong opinion on the topic; I'd actually prefer 100rel
usage for re-INVITE be deprecated. :)

I'm curious why preferring not to follow rfc3261 section 14.1: "If a UA
receives a non-2xx final response to a re-INVITE, the session parameters
MUST remain unchanged, as if no re-INVITE had been issued."?

If an UPDATE is successfully processed while a re-INVITE is occuring, I
agree that the updates caused by the UPDATE and UPDATE 2xx should not be
rolled back upon re-INVITE failure.


> Would it also be acceptable to stay with whatever remote 
> Target was successfully set last?

What is meant by "successfully set last"?  Is the proposal for 1)
updating per received target update request or 2) it having triggered a
2xx?

Since it might be relevant to the discussion, what is the current
interpretation of rfc3261 concerning a re-INVITE 18x with an updated
Contact?  Is the current proposal to alter the current interpretation of
rfc3261?

Thanks,
Brett
_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sip at ietf.org for new developments of core SIP