I also pay high attention to the topic of "rollback of re-Invite".
As lots of service is implemented on the network using SIP, and different ways
may be carried out by different corporations, it's necessary to define a complete
and clear method to solve the failure when the unsuccessful re-Invite happens.
And the problems "Commit any session parameters that have been sucessfully changed"
metioned in "draft-gaoyang-sipping-session-state-analysis-01.txt" need further discuss,
I think.
Eric.wang
Regards!
-------------------------------------------------------- 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
