The Real Time Streaming Protocol (RTSP) is a network control protocol designed for use in Multimedia Session Control Working Group (MMUSIC WG) of the Internet Engineering Task Force (IETF) and published as RFC in IETF RFC IETF RFC (), Real Time Streaming Protocol Transfer Protocol—HTTP/ IETF RFC IETF RFC (), A DNS RR for. [IETF RFC ]IETF RFC , RTP: A Transport Protocolfor Real-Time Applications. [IETF RFC ]IETF RFC , Real Time Streaming Protocol ( RTSP).
|Published (Last):||28 September 2012|
|PDF File Size:||9.75 Mb|
|ePub File Size:||2.13 Mb|
|Price:||Free* [*Free Regsitration Required]|
Real Time Streaming Protocol
It is also possible that the presentation author may wish to prevent selective retrieval of the streams by the client in order to preserve the artistic effect of the combined media presentation. In the case where the feature was specified ietr the Proxy-Require field Section Thu, 01 Dec This is to make sure that the client-server interaction will proceed without delay when all options are understood by both sides, and only slow down if options oetf not understood as in the case above.
Please help to improve this article by introducing more precise citations. The protocol is used for establishing and controlling media sessions between end points. July Learn how and when to remove this template message. For aggregate control, a particular stream may not actually generate a packet ief the Range time value returned or implied.
For ieff RTSP request containing the given sequence number, there will be a corresponding response having the same number. Header type support methods Accept R opt.
RTSP differs significantly in that respect. Indicates the sequence number of the first packet of the stream. Note that the content types suitable for RTSP are likely to be restricted in practice to presentation descriptions and parameter-value types. Sat, 29 Oct This article needs additional citations for verification. Parameters may be added to each transport, separated by a semicolon. Transports are comma separated, listed in order of preference.
Presented here are the basic RTSP requests. See 232 1 for a listing of which status codes may be returned by which requests. Hence, it is possible that rcf use the same session for controlling many streams constituting a presentation, as long as all the streams come from the same server.
Container files are a widely used means to store such presentations.
InfoWorld Media Group, Inc. The session identifier is needed to distinguish several delivery requests for the same URL coming from the ietff client.
Learn how and when to remove these template messages. The identifier is an opaque identifier, and thus is not specific to any particular session description language. If a particular extension requires that intermediate devices support it, the extension should be tagged in the Proxy-Require field instead see Section It may also give an indication about the timeline of the movie.
The response MUST contain the actual scale value chosen by the server. Handbook of Emerging Communications Technologies: A range of Information on the encodings remains the same. Fields marked with “req.
Views Read Edit View history. Just as an HTTP cache has to store the content type, content language, and so on for the objects it caches, a media cache has to store the presentation description.
The last column lists the method for which this header field is meaningful; the designation “entity” refers to all methods that return a message body. The timestamp is used by the client to compute the round-trip time to the server so that it can adjust the timeout value for retransmissions. 22326 the copy is not up-to-date, it modifies the SETUP transport parameters as appropriate and forwards the request to the origin server.
To the client, an RTSP proxy cache appears like a regular media server, to the media origin server like a rcc.
RFC – part 3 of 4
Only the start time of a media unit such as a video or audio frame is relevant. It is 23326 as a range, e. The purpose of this field is to strictly inform the recipient of valid methods associated with the resource.
This allows clients to gracefully deal with packets when seeking. It should be silently ignored if sent.
The start of playback can be scheduled for any time in the future, although a server may refuse to keep server resources for extended idle periods. A server does not have to set up a session identifier if it has other means of identifying a session, such as iettf generated URLs.
The default transport layer port number is  for both TCP and UDPthe latter being rarely used for the control requests.
As an example, assume that video frames are generated every 40 ms. Please help improve this article by adding citations to reliable sources.