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).

Author: Dolmaran Dilmaran
Country: Nepal
Language: English (Spanish)
Genre: Love
Published (Last): 15 March 2013
Pages: 280
PDF File Size: 7.57 Mb
ePub File Size: 12.62 Mb
ISBN: 668-5-96535-573-4
Downloads: 36116
Price: Free* [*Free Regsitration Required]
Uploader: Vur

Container files are a widely used means to store such presentations.

If it is missing, a default value of zero is assumed. If max-stale is assigned a value, then the client is willing to accept a response that has exceeded its iehf time by no more than the specified number of seconds.

This enables frc server to keep a single storage handle open easily. This information may also be available through SDP. Information on the encodings remains the same. The Real Time Streaming Protocol RTSP is a network control protocol designed for use in entertainment and communications systems to control streaming media servers.

Information on RFC » RFC Editor

Please help improve this article by adding citations to reliable sources. The default is the bit rate of the stream. Since other processes on the server may be consuming storage space simultaneously, a client should take this only as an estimate. The response Session Not Found is returned if the session identifier is invalid.


Real Time Streaming Protocol

Header type support methods Accept R opt. To do this, the client may include the only-if-cached directive in a request. 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.

Learn how and when to remove these template messages. Handbook of Emerging Communications Technologies: Please help improve it or discuss these issues on the talk page. The address to which a stream will be sent. In other projects Wikimedia Commons. July Learn how and when to remove this template message.

It is interpreted according to [H A Transport request header field may contain a list of transport options acceptable to the client.

However, since this is more a feature of transport ieff media initialization, the authoritative source for this information should be in the SETUP response. The default value for the “lower-transport” parameters is specific to the profile. A server SHOULD not allow a client to direct media streams to an address that differs from the address commands are coming from.

For every RTSP request containing the given sequence number, there will be a corresponding response having the same number. In other words, a ratio of 2 has normal play time increase at twice the wallclock rate.

For every second of elapsed wallclock time, 2 seconds of content will be delivered. Indicates the sequence number of the first packet of the stream.


RFC – Real-Time Streaming Protocol Version

It irtf meant for use in specific circumstances where preview of the presentation at a higher or lower rate is necessary. It sets those values not already determined by a presentation description.

For aggregate control, a particular stream may not actually generate a packet for the Range time value returned or implied. It identifies the synchronization source to be associated with the media stream.

In some cases, such as times of extremely poor network connectivity, a client may want a cache to return only those media streams that it currently has stored, and not to receive these from the origin server. Therefore, if a response includes the no-transform directive, an intermediate cache or proxy MUST NOT change the encoding of the stream.

For audio, it may time-scale the audio while preserving pitch or, less desirably, deliver fragments of audio. Hence, it is possible that clients use the same session for controlling many streams constituting a presentation, as long as all the streams come from the same server.

This allows an origin server to prevent caching even by caches that have been configured to return stale responses to client requests. It also allows treating all the streams equally iftf case of any prioritization of streams by the server.