Standards Track A. Rao Netscap - RFC Editor

More documents

Recommendations

Info

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]
RFC 2326 Real Time Streaming Protocol April 1998In the worst case, servers should send back:S->C RTSP/1.0 460 Only aggregate operation allowedCSeq: 3One would also hope that server implementations are also forgiving ofthe following:C->S SETUP rtsp://foo.com/test.wav RTSP/1.0Transport: rtp/avp/udp;client_port=6970-6971;mode=playCSeq: 2Since there is only a single stream in this file, it’s not ambiguouswhat this means.14.4 Live Media Presentation Using MulticastThe media server M chooses the multicast address and port. Here, weassume that the web server only contains a pointer to the fulldescription, while the media server M maintains the full description.C->W: GET /concert.sdp HTTP/1.1Host: www.example.comW->C: HTTP/1.1 200 OKContent-Type: application/x-rtslC->M: DESCRIBE rtsp://live.example.com/concert/audio RTSP/1.0CSeq: 1M->C: RTSP/1.0 200 OKCSeq: 1Content-Type: application/sdpContent-Length: 44v=0o=- 2890844526 2890842807 IN IP4 192.16.24.202s=RTSP Sessionm=audio 3456 RTP/AVP 0a=control:rtsp://live.example.com/concert/audioc=IN IP4 224.2.0.1/16C->M: SETUP rtsp://live.example.com/concert/audio RTSP/1.0CSeq: 2Schulzrinne, et. al. Standards Track [Page 69]
Page 2 and 3:
RFC 2326 Real Time Streaming Protoc
Page 4 and 5:
Page 7:
Page 10 and 11:
Page 12 and 13:
Page 14 and 15:
Page 16 and 17:
Page 18 and 19: RFC 2326 Real Time Streaming Protoc
Page 92: RFC 2326 Real Time Streaming Protoc
show all

Standards Track A. Rao Netscap - RFC Editor

Create successful ePaper yourself

Delete template?

Save as template?