Standards Track A. Rao Netscap - RFC Editor

RFC 2326 Real Time Streaming Protocol April 1998CSeq: 1S->C RTSP/1.0 200 OKCSeq: 1Content-base: rtsp://foo.com/test.wav/Content-type: application/sdpContent-length: 48v=0o=- 872653257 872653257 IN IP4 172.16.2.187s=mu-law wave filei=audio testt=0 0m=audio 0 RTP/AVP 0a=control:streamid=0C->S SETUP rtsp://foo.com/test.wav/streamid=0 RTSP/1.0Transport: RTP/AVP/UDP;unicast;client_port=6970-6971;mode=playCSeq: 2S->C RTSP/1.0 200 OKTransport: RTP/AVP/UDP;unicast;client_port=6970-6971;server_port=6970-6971;mode=playCSeq: 2Session: 2034820394C->S PLAY rtsp://foo.com/test.wav RTSP/1.0CSeq: 3Session: 2034820394S->C RTSP/1.0 200 OKCSeq: 3Session: 2034820394RTP-Info: url=rtsp://foo.com/test.wav/streamid=0;seq=981888;rtptime=3781123Note the different URL in the SETUP command, and then the switch backto the aggregate URL in the PLAY command. This makes complete sensewhen there are multiple streams with aggregate control, but is lessthan intuitive in the special case where the number of streams isone.In this special case, it is recommended that servers be forgiving ofimplementations that send:C->S PLAY rtsp://foo.com/test.wav/streamid=0 RTSP/1.0CSeq: 3Schulzrinne, et. al. Standards Track [Page 68]