Orignal description:
And there is a more situation: if the precondition notification with the orignal precondition OK and add another new precondition(it is legitimate, but unordinary). As the precondition of the session is still exist, the session is still in suspending state. And the one is precondition notification.
Chapter 8 of RFC3312:
When a UAS, acting as an answerer, cannot or is not willing to meet the preconditions in the offer, it SHOULD reject the offer by returning a 580 (Precondition-Failure) response.
So, the precondition can be rejected for wishes of user or UA. So, modification of precondition itself(not precondition satisfied state) MUST be treated as a new modification. And it obeys the natural demand of one side to reject the other side's Offer with too much precondition. :)
As a new modification, the session state would be judge by the way as other new modification.
So the original description in the mail to Christer Holmberg is not correct. I apologize for that.
Gaoyang
-------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender. This message has been scanned for viruses and Spam by ZTE Anti-Spam system.
_______________________________________________ Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip Use sip@xxxxxxxx for new developments of core SIP