Subject: [MMUSIC] Re: Unicast address for media in RTSP

From: Roman Shpount <[email-masked]>
Date: 28 Feb 2002 20:48:15 GMT

On 28 Feb 2002, Roman Shpount wrote:
> What is the reason why media in unicast session is transmitted to the
> source of RTSP request? Why can't RTSP client specify different address
> for unicast session in SDP? Ability to send media to a different
> destination will be extremely useful to implement applications such as
> music on hold in SIP call from RTSP source.

Rob Lanphier wrote:
> I'm not sure what you mean here.  The client can send a Transport: line
> that contains a destination parameter, and the server can accept that
> line.  As the spec says, this should be used with caution, and many
> implementations may forbid anonymous use of this, because of the
> denial-of-service possibilities associated with this feature.

The latest draft bis as well as the original RFC specify in section 1.6:

 Unicast: The media is transmitted to the source of the RTSP
          request, with the port number chosen by the client.
          Alternatively, the media is transmitted on the same
          reliable stream as RTSP.

This clearly states that the media is always send to the source of the RTSP request and not to the destination specified in the request. This actually contradicts to the section 12.40 of the bis. 
___________________________________
Roman Shpount, VP of Technology
aTelo, Inc. 
2107 Wilson Blvd., Suite 301 
Arlington, VA 22201 
PCN: 703-621-4040 for voice / fax
www.atelo.com

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