If so, what are the formal reasons for re-sending a NOTIFY with 
unchanged event package data?

Avasarala Ranjit-A20990 wrote:

> Hi
> 
> The Cseq header is for the NOTIFY message while the "version" element is for 
> the dialog information document. So an incremented version value in dialog 
> info xml document indicates that the xml document received is an updated one. 
> If the version is not incremented, then it means that the dialog info doc is 
> same as previous one  (implying no change in dialog info) - though here the 
> received NOTIFY message could have an incremented Cseq value.  
> 
> Regards
> Ranjit
> 
> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Iñaki 
> Baz Castillo
> Sent: Tuesday, January 20, 2009 4:21 PM
> To: SIPImplementors Mailing list
> Subject: [Sip-implementors] RFC 4235 - Why is needed "version" in NOTIFY XML
> 
> Hi, RFC 4235 states that each NOTIFY about a dialog(s) must increment the 
> "version" field value, the the recipient must ignore notifications with no 
> incremented "version" numbers.
> I wonder why this mechanism is needed, is not enough with CSeq? The NOTIFY is 
> part of a dialog and there is already a mechanism to control de sequential 
> requests order (CSeq header).
> 
> Isn't this "version" field a redundant solution? Is it really needed?
> (perhaps I miss something...).
> 
> Thanks for any explanation.
> 
> --
> Iñaki Baz Castillo
> <[email protected]>
> 
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
> 
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors


-- 
Alex Balashov
Evariste Systems
Web    : http://www.evaristesys.com/
Tel    : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
Mobile : (+1) (678) 237-1775
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to