Hi all, I would like to know if GStreamer has in-built support for any of the next features and, if not, if they are considered as future work: - Changing transport parameters with RTSP SETUP message as depicted in<a href="http://tools.ietf.org/html/rfc2326"> RFC 2326</a> (10.4) and<a href="http://www.ietf.org/internet-drafts/draft-ietf-mmusic-rfc2326bis-20.txt"> RFC 2326bis</a> (13.3.1), RTSP and RTSP 2.0 standards . This can be used in mobile environments, so, while a RTSP session is active, the client issues a new SETUP message with the new IP address, UDP ports or a new transport method ,so the server can manage the streaming session to redirect the packets through the new connection. - RTP translator support as depicted in <a href="http://tools.ietf.org/html/rfc3550">RFC 3550</a> (7), RTP standard. RTP translators allow multiple streaming management options like re-encoding the media packets 'on-the-fly' or changing network parameters to avoid access denials due to some firewall configurations. I would also like to know if there is any kind of support to Multiple Description Coding (MDC) or SVC (Scalable Video Coding) or there is any ongoing effort in order to do it, so merging different descriptors or layers is possible with current or future GStreamer elements. Thank you so much, Javi