Standards Track A. Rao Netscap - RFC Editor

RFC 2326 Real Time Streaming Protocol April 199812.35 SpeedThis request header fields parameter requests the server to deliverdata to the client at a particular speed, contingent on the server’sability and desire to serve the media stream at the given speed.Implementation by the server is OPTIONAL. The default is the bit rateof the stream.The parameter value is expressed as a decimal ratio, e.g., a value of2.0 indicates that data is to be delivered twice as fast as normal. Aspeed of zero is invalid. If the request contains a Range parameter,the new speed value will take effect at that time.Speed = "Speed" ":" 1*DIGIT [ "." *DIGIT ]Example:Speed: 2.5Use of this field changes the bandwidth used for data delivery. It ismeant for use in specific circumstances where preview of thepresentation at a higher or lower rate is necessary. Implementorsshould keep in mind that bandwidth for the session may be negotiatedbeforehand (by means other than RTSP), and therefore re-negotiationmay be necessary. When data is delivered over UDP, it is highlyrecommended that means such as RTCP be used to track packet lossrates.12.36 ServerSee [H14.39]12.37 SessionThis request and response header field identifies an RTSP sessionstarted by the media server in a SETUP response and concluded byTEARDOWN on the presentation URL. The session identifier is chosen bythe media server (see Section 3.4). Once a client receives a Sessionidentifier, it MUST return it for any request related to thatsession. A server does not have to set up a session identifier if ithas other means of identifying a session, such as dynamicallygenerated URLs.Session = "Session" ":" session-id [ ";" "timeout" "=" delta-seconds ]The timeout parameter is only allowed in a response header. Theserver uses it to indicate to the client how long the server isprepared to wait between RTSP commands before closing the session dueto lack of activity (see Section A). The timeout is measured inSchulzrinne, et. al. Standards Track [Page 57]