[MMUSIC] Pipelining RTSP SETUP

["Josh Perfetto" <josh@vidiator.com>]

Hello All,

As I read RFC2326, in the typical DESCRIBE followed by multiple SETUPs, the server will first assign the RTSP session ID in response to the first SETUP.  The player is supposed to include this session ID in all subsequent requests.  However, this seems to preclude the possibility of pipelining a second SETUP request with the first one, as the session ID for the second SETUP wouldn't be known at the time it is sent.  Is this correct?

If it is, I would think it is a significant shortcoming, as pipelining is essential when streaming over high-latency wireless networks.  Is this something that could be looked at in 2326bis?

RFC2326 does say that the server doesn't need to generate session identifiers if it has another means of identifying requests, but the player wouldn't know this until it receives the first SETUP response.

-Josh

--
Josh Perfetto
Director of Architecture
Vidiator Technologies
josh@vidiator.com
_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic