Standards Track A. Rao Netscap - RFC Editor

RFC 2326 Real Time Streaming Protocol April 1998Session: 12345678C->S: PLAY rtsp://foo.com/bar.file RTSP/1.0CSeq: 3Session: 12345678S->C: RTSP/1.0 200 OKCSeq: 3Session: 12345678Date: 05 Jun 1997 18:59:15 GMTRTP-Info: url=rtsp://foo.com/bar.file;seq=232433;rtptime=972948234S->C: $\000{2 byte length}{"length" bytes data, w/RTP header}S->C: $\000{2 byte length}{"length" bytes data, w/RTP header}S->C: $\001{2 byte length}{"length" bytes RTCP packet}11 Status Code DefinitionsWhere applicable, HTTP status [H10] codes are reused. Status codesthat have the same meaning are not repeated here. See Table 1 for alisting of which status codes may be returned by which requests.11.1 Success 2xx11.1.1 250 Low on Storage SpaceThe server returns this warning after receiving a RECORD request thatit may not be able to fulfill completely due to insufficient storagespace. If possible, the server should use the Range header toindicate what time period it may still be able to record. Since otherprocesses on the server may be consuming storage spacesimultaneously, a client should take this only as an estimate.11.2 Redirection 3xxSee [H10.3].Within RTSP, redirection may be used for load balancing orredirecting stream requests to a server topologically closer to theclient. Mechanisms to determine topological proximity are beyond thescope of this specification.Schulzrinne, et. al. Standards Track [Page 41]