[EMAIL PROTECTED] wrote:
> Actually, I am wondering that if the UAS receives a SDP Offer without
> direction attribute a=---, does it violate the RFCs if it has different
> answer to that when it receives the SDP offer with direction attribute
> a=sendrecv, in a complete same scenario?
As long as what it answers is a valid answer for what it receives, there
si no requirement that it be consistent from one offer to the next. For
instance, it would be entirely conforming for you to always answer
a=inactive when you get an offer with a=sendrecv, but answer with no a=
when getting an offer with none.
BUT, just because it is conforming doesn't mean it is a reasonable
device, or one I would want to buy. If you expect to interoperate
widely, you should respond the same when offered a=sendrecv and you do
when offered no a=.
Paul
> Alex Zhang
> ESN: 6-554-8782
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> [EMAIL PROTECTED]
> Sent: Monday, July 07, 2008 2:02 AM
> To: [email protected]
> Subject: Re: [Sip-implementors] a=sendrecv in SDP answer
>
>
> From: "Rockson Li (zhengyli)" <[EMAIL PROTECTED]>
>
> I think a=sendrecv should be assume if no direction attribute
> specified.
>
> As per RFC4566,sec 6
>
> a=sendrecv
>
> ...
> If none of the attributes "sendonly", "recvonly",
> "inactive",
> and "sendrecv" is present, "sendrecv" SHOULD be assumed as
> the
> default for sessions that are not of the conference type
> "broadcast" or "H332" (see below).
>
> As Rockson says, RFC 4566 prescribes sendrecv as the default, and I know
> of no statement that if a direction attribute is in the offer that it
> must also be present in the answer, or a general statement that if an
> attribute of a particular sort is present in the offer, an attribute of
> the same sort must be present in the answer.
>
> Dale
> _______________________________________________
> 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
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
