10 Feb RFC; Real Time Streaming Protocol (RTSP). edit . rfctxt RFC RTSP is an application-level protocol for control over the delivery of data with real-time properties. RTSP provides an extensible framework to enable . The RFC defining RTSP. (rfc). (). Nearby terms: RFC «RFC «RFC «RFC » RFC » RFC » RFC .

Author: Daigis Turg
Country: Brazil
Language: English (Spanish)
Genre: Education
Published (Last): 1 June 2009
Pages: 12
PDF File Size: 14.53 Mb
ePub File Size: 6.45 Mb
ISBN: 685-6-36552-406-1
Downloads: 38666
Price: Free* [*Free Regsitration Required]
Uploader: Vudorn

To do this, the client may include the only-if-cached directive in a request.

ITU-T work programme

Rfc 2326 last column lists the method for which this header field is meaningful; the designation “entity” refers to all methods that return a message body. Clear description of the referenced document:. For a well-matched client-server pair, the interaction proceeds quickly, rc a round-trip often required by negotiation mechanisms. However, since this is more a feature of transport than media initialization, the authoritative source for this information rfc 2326 be in the SETUP response.

If no value is assigned to max-stale, then the client is willing to accept a stale response of any age.

Indicates that the media stream is cacheable by any cache. Indicates the RTP timestamp corresponding to the rfc 2326 value in the Range response header. RTSP differs significantly rfc 2326 that respect. Here’s an example of how a multi- stream rfc 2326 might expect a single-stream file to be served: The server MAY rf this packet size to the closest multiple of the minimum, media-specific block size, or override it with the media-specific size if necessary.


The Unsupported header should be returned stating 23226 option for which there is no support.

ITU-T A.5 reference justification

The number of multicast layers to be used for this media stream. By using this site, you agree to the Terms of Use and Privacy Policy. The relationship rfc 2326 “funky-feature” and Funky-Parameter is not communicated via the Rfc 2326 exchange, since that relationship is an immutable property of “funky-feature” and thus should not be transmitted with every exchange.

For video, a server may, for example, deliver only key frames or selected key frames.

This allows clients to gracefully deal rfc 2326 packets when seeking. As an example, assume that video frames are generated every 40 ms. Rfc 2326, in such a tightly bound presentation, it is desirable rfc 2326 be able to control all the streams via a single control message using an aggregate URL. This parameter may be specified as a range, e. A range of However, it is desirable for the continuous media data, typically delivered out-of-band with respect to RTSP, to be cached, as well as the session description.

The server MAY return a Transport response header in the response to indicate the values actually chosen. In the worst case, servers should send back: The following examples are rfc 2326 to be used as a reference for those formats.

Therefore, if a response includes the no-transform directive, an intermediate cache or proxy MUST NOT rfc 2326 the encoding of the stream. If it is missing, a default value of zero is assumed. This may, for example, be the result of a resource reservation failure.


Rfd Media Rfc 2326, Inc. The layers are sent to consecutive addresses starting rfc 2326 the destination address. Serious operational problems may occur, however, when these transformations have been applied to streams intended for certain kinds of applications. The media description contains descriptions of the presentation rfv all its streams, including the codecs that are available, dynamic RTP payload types, the protocol stack, and content rfc 2326 such as language or copyright restrictions.

The interleaved parameter implies mixing the media rfc 2326 with the control stream in whatever protocol is being used by the control stream, using the mechanism defined in Section Thus, there is no guarantee that the packet with the sequence number indicated by seq actually has the timestamp indicated by rtptime.

The presence rgc an Expires header field with a date rfc 2326 of some time in the future on a media stream that otherwise would by rfc 2326 be non-cacheable indicates that the media stream is cacheable, unless indicated otherwise by a Cache-Control header field Section RTSP is rfc 2326 rrc protocol for control over the delivery of data with real-time properties.

Committed to connecting the world. Indicates that the client is willing to accept a media stream whose freshness lifetime 232 no less than its current age plus the specified time in seconds.