#21 Allow usage of RTCP MUX
draft-ietf-avt-rtp-and-rtcp-mux-07 is currently in the RFC-editor queue. If we allow for RTP and RTCP muxing with RTSP we can half the port consumption for a RTSP based streaming server. Or at least avoid RTCP using additional ports which has been a major complaint from vendors of high capacity servers. As I can see this can be introduced in the following ways:
A. Mandate that RTCP MUX shall be supported by RTSP 2.0 servers and clients supporting RTP transport. A flag indicate may be used to indicate if RTCP is to be used or not instead of the extra port.
B. Allow RTP and RTCP muxing to be optional to support. Include a flag to negotiate this usage. Only when both side indicate support is muxing performed.
I think A is easier and more interoperable in the long run. However it increase the burden in the transition period from RTSP 1.0 to 2.0.
Logged In: YES
user_id=302620
Originator: YES
This is a feature request moving into the right tracker.
I have added text into the core spec for negotiating the usage of RTP and RTCP MUX. It is more along the line of B, but with recommended implementation.
Wouldn't a mux be indicated by supplying the appropriate client and server port for rtcp equal to that of rtp.
I don't see how this needs any special attention.
Additionally the sdp which was given in describe response can indicate this if required for correct transfer which really wouldn't matter under interleaved communication anyway.