Standards Track A. Rao Netscap - RFC Editor

RFC 2326 Real Time Streaming Protocol April 1998play request and discards the second play request.As another example, if a server has received requests to play ranges10 to 15 and then 13 to 20 (that is, overlapping ranges), the PAUSErequest for NPT=14 would take effect while the server plays the firstrange, with the second PLAY request effectively being ignored,assuming the PAUSE request arrives before the server has startedplaying the second, overlapping range. Regardless of when the PAUSErequest arrives, it sets the NPT to 14.If the server has already sent data beyond the time specified in theRange header, a PLAY would still resume at that point in time, as itis assumed that the client has discarded data after that point. Thisensures continuous pause/play cycling without gaps.10.7 TEARDOWNThe TEARDOWN request stops the stream delivery for the given URI,freeing the resources associated with it. If the URI is thepresentation URI for this presentation, any RTSP session identifierassociated with the session is no longer valid. Unless all transportparameters are defined by the session description, a SETUP requesthas to be issued before the session can be played again.Example:C->S: TEARDOWN rtsp://example.com/fizzle/foo RTSP/1.0CSeq: 892Session: 12345678S->C: RTSP/1.0 200 OKCSeq: 89210.8 GET_PARAMETERThe GET_PARAMETER request retrieves the value of a parameter of apresentation or stream specified in the URI. The content of the replyand response is left to the implementation. GET_PARAMETER with noentity body may be used to test client or server liveness ("ping").Example:S->C: GET_PARAMETER rtsp://example.com/fizzle/foo RTSP/1.0CSeq: 431Content-Type: text/parametersSession: 12345678Content-Length: 15packets_receivedjitterSchulzrinne, et. al. Standards Track [Page 37]