Subject: [MMUSIC] RFC 3312: Setting of send and recv tags for send/receive only media stream

From: [email-masked]
Date: Thu, 2 Dec 2004 13:58:04 +0200

Hello,

I have a question on interpretation of the precondition RFC 3312.

The questions is on the following paragraph in RFC 3312:	
<snip>The values of the tags "send", "recv", "local" and "remote" represent the point of view of the entity generating the SDP description. In an offer, "send" is the direction offerer->answerer and "local" is the offerer's access network. In an answer, "send" is the direction answerer->offerer and "local" is the answerer's access network.<snap> 
How have the send/recv tags of preconditions to be set when a sendonly / receiveonly media stream from A to B is to be established? My understanding is as follows:

	INVITE 	(from A, who will be sending the stream)
	a=curr:qos local none
	a=curr:qos remote none
	a=des:qos mandatory local send
	a=des:qos none remote recv

	183 (from B, who will be receiving the stream)
	a=curr:qos remote none
 	a=curr:qos local none
 	a=des:qos mandatory remote send
 	a=des:qos mandatory local recv
 	a=conf:qos remote send

Now the question was whether in the fourth line of the INVITE, it should be
	a=des:qos none remote recv
or
	a=des:qos none remote send

And the same question would apply to the third line of the 183, should it be 
 	a=des:qos mandatory remote send
or
 	a=des:qos mandatory remote recv

-----------------------------------
http://www.imsbook.com
------------------------------------

_______________________________________________
mmusic mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/mmusic