We don't usually specify behavior in no-compliant cases. You are free to
do as you wish - fail the request or cope.
IMO the purpose of the session version is to permit an optimization when
nothing has changed. If you don't do the optimization then there is
little reason to validate the version, and if you do the optimization
then checking the version will degrade the optimization to some extent,
though perhaps not as much as not doing the optimization.
Does anybody check this?
Paul
Rohit Sonalkar wrote:
> Hello,
>
> I have a question about Section 8 of RFC 3264, Modifying a Session. This
> section clearly states that:
>
> 1. If new offer SDP is different from previous SDP, session version must
> be incremented
> 2. It new offer SDP has same version as previous SDP, new SDP must be
> identical to previous SDP
>
> It does not say whether the receiver should treat as invalid the
> following combinations in the new offered SDP:
>
> 1. Different SDP, same version number
> 2. Same SDP, different version number
>
> How should the receiver treat the new offered SDP in either of these two
> cases, how can it 'reject' the offer as invalid?
>
> Thanks
> Rohit
>
>
>
> _______________________________________________
> 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
