Hi，
Thanks for comments.
Tag may be used to identify the classification, help to act different when received different UPDATEs.
But i don't think tag will solve the conflicts between new SDP UPDATEs and 2xx-6xx final response or other message, as these UPDATEs are unexpected.
Regards
Dean Willis <dean.willis@xxxxxxxxxxxxx> 写于 2009-03-12 13:35:42:
>
> On Mar 11, 2009, at 10:05 PM, wang.libo@xxxxxxxxxx wrote:
>
> >
> > Hi all,
> >
> > I have just written a rough draft about nested UPDATEs.
> > As it cannot be uploaded at this moment, I send a copy by the list
> > of sipping.
> >
>
> You know, if we used an eTag to identify a dialog-state, we could
> detect and deal with nested/overlapping/etc. dialog state changes.
> Just an idea.
>
>
> --
> Dean
>
-------------------------------------------------------- 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
