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: Kigale Gardazuru
Country: Norway
Language: English (Spanish)
Genre: Travel
Published (Last): 2 April 2014
Pages: 103
PDF File Size: 20.47 Mb
ePub File Size: 20.77 Mb
ISBN: 955-5-44933-231-9
Downloads: 19147
Price: Free* [*Free Regsitration Required]
Uploader: Duzilkree

This article includes a list of referencesbut its sources remain unclear because it has insufficient inline citations. As an example, assume that video frames are generated every 40 ms.

Real Time Streaming Protocol – Wikipedia

Below are the configuration parameters associated with transport: It is interpreted according to [H For audio, it may time-scale the audio while preserving pitch or, less desirably, deliver fragments of audio. Information on the encodings remains the same. The presence of an Expires header field with a date value of some time in the future on a media stream that otherwise would by default be non-cacheable indicates that the media stream is cacheable, unless indicated otherwise by a Cache-Control header field Section If possible, the server should use the Range header to indicate what time period it may still be able to record.

A server does not have to set up frc session identifier if it has other means of identifying a session, such as dynamically generated URLs.

The server MAY return a Transport response header in the response to indicate the values actually chosen. September Learn how and when to remove this template message. That is, the cache must do an end-to-end revalidation every time, if, based solely on the origin server’s Expires, the cached response is stale.

Thus, it does not introduce additional latency. The default is the bit rate of the stream. Here’s an example of how a multi- stream server might expect a single-stream file to be served: The Expires header indicates a date and time after which the description should be considered stale.


Rather than retrieving the whole resource from the origin server, the cache simply copies the streaming rc as it passes by on its way to the client. In that case, the server MUST return a single option which was actually chosen. This allows an origin server to prevent caching even by caches that rf been configured to return stale responses to client requests. The exact behavior allowed to the cache is given by the cache-response directives.

The following examples are not to be used as a reference for those formats. If the request contains a Range parameter, the new speed value will take effect at that time.

It is specified as a range, e. The movie is stored in a container file. The Real Time Streaming Protocol RTSP is a network control protocol designed for use in entertainment and rvc systems to control streaming media servers. Transports are comma separated, listed in order of preference. C indicates to the media server that the network ietg and encryption keys are already given by the conference, so they should not be chosen by the server.

The protocol is used for establishing and controlling media sessions between end points. This information may also be available through SDP. For example, applications for medical imaging, scientific data analysis and those using end-to-end authentication all depend on receiving a stream that is bit-for-bit identical to the original entity-body.

Serious operational problems may occur, however, when these transformations have been applied to streams intended for certain kinds of applications.

Real Time Streaming Protocol

If not 1, the value corresponds to the rate with respect to normal viewing rate. The server is free to use a blocksize which is lower than istf one requested.

However, since this is more a feature of transport than media initialization, the authoritative source for this information should be in the SETUP response. 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 23326.

  ASTM D6910 PDF

Note that not all fields marked “req.

RFC – Real-Time Streaming Protocol Version

This article has multiple issues. For every RTSP request containing the given sequence number, there will be a corresponding response having the same number.

For a well-matched client-server pair, the interaction proceeds quickly, saving a round-trip often required by negotiation mechanisms. Here, we assume that the web server only contains a pointer to the full description, while the media server M maintains the full description.

23266 The server MUST echo the exact same value and MAY, if it has accurate information about this, add a floating point number indicating the number of seconds that has elapsed since it has received the request. To the client, an RTSP proxy cache appears like a regular media server, to the media origin server like a client. Client C requests a presentation from media server M.

When the must-revalidate directive is present in a SETUP response received by a cache, that cache MUST NOT use the entry after it becomes stale to respond to a subsequent request without first revalidating it with the origin server. If it receives this directive, a cache SHOULD either respond using a cached media stream that is consistent with the other constraints of the request, or respond with a Gateway Timeout status.

The response Session Not Found is returned if the session identifier is invalid. RTSP differs significantly in that respect. Container files are a widely used means to store such presentations. The session identifier is chosen by the media server see Section 3. Unsourced material may be challenged and removed. If not provided, the default is PLAY. Note that a session identifier identifies a RTSP session across transport sessions or connections.

The relationship between “funky-feature” and Funky-Parameter is not communicated via the RTSP exchange, since that relationship is an immutable property of “funky-feature” and thus should not be transmitted with every exchange.