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):||24 December 2005|
|PDF File Size:||9.45 Mb|
|ePub File Size:||4.23 Mb|
|Price:||Free* [*Free Regsitration Required]|
The session identifier is chosen by the media server see Section 3.
The Real Time Streaming Protocol RTSP is a network control protocol designed for use in entertainment and communications systems to control streaming media servers. The identifier is an opaque identifier, and thus is not specific to any particular session description language. The Unsupported header should be returned stating the option for which there is no support. The Expires header indicates a date and time after which the description should be considered stale.
In this example, the client is only interested in the last part of the movie.
Real Time Streaming Protocol – Wikipedia
The mode parameter indicates the methods to be supported for this session. The interpretation depends on the method: To mark a response as “never expires,” an origin server should use an Expires date approximately one year from the time the response is sent. The protocol is used for establishing and controlling media sessions between end points.
In the case where the feature was specified via the Proxy-Require field Section The client uses this value rtc differentiate packets that originated before the seek from packets that originated after the seek. An Allow header field must be present in a Method not allowed response.
Real Time Streaming Protocol
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. In that case, the server MUST return a single option which was actually chosen. Making it part of RTSP rather than relying on a multitude of session description formats greatly simplifies designs rgc firewalls.
Views Read Edit View history. If possible, the server should use the Range header to indicate what time period it may still be able to record. Indicates that the client is willing to accept a media stream that rrc exceeded its expiration time.
Indicates the sequence number of the first packet of the stream. This may, for example, be the result of a resource reservation failure. It is not possible to specify a cache- directive for a specific cache.
Therefore, if a response includes the no-transform directive, an intermediate cache or proxy MUST NOT change the encoding of 23266 stream. If the request contains a Range parameter, the new scale value will take effect at that time. This error will most likely be the eitf of a client attempt to place an invalid Destination parameter in the Transport field.
Ranges are half-open intervals, including the lower point, but excluding the upper point. InfoWorld Media Group, Inc. 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.
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. This makes complete sense when there are multiple streams with aggregate control, but is less than intuitive in the special case where the number of streams is one. In the worst case, servers should send back: 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.
Information on the encodings remains the same. The server MAY return a Transport response header in the response to indicate the values actually chosen. It is meant for use in specific circumstances where preview of the presentation at a higher or lower rate is necessary. 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.
However, some vendors implement proprietary transport protocols. This information may also be available through SDP. 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. The parameter value is expressed as a decimal ratio, e.
Sat, 29 Oct Client C requests a presentation from media server M. This article includes a list of referencesbut itef sources remain unclear because it has insufficient inline citations. The following is an example of using a single RTSP session to control multiple streams. A server SHOULD not allow a client to direct media streams to an address that differs from the address commands are coming from. Note that a session identifier identifies a RTSP session across transport sessions or connections.
Please help improve it or discuss iettf issues on the talk page. This keeps the syntax of the Transport header simple and allows easy parsing of transport information by firewalls. Similarly, in such a tightly bound presentation, it is desirable to be able to control all the streams via a single control message using 232 aggregate Rfx.
In this special case, it is recommended that servers be forgiving of implementations that send: This article needs additional citations for verification.
If the request contains a Range parameter, the new speed value will take effect at that time. Here’s an example of how a multi- stream server might expect a single-stream file to be served: