13.07.2015 Views

Standards Track A. Rao Netscap - RFC Editor

Standards Track A. Rao Netscap - RFC Editor

Standards Track A. Rao Netscap - RFC Editor

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>RFC</strong> 2326 Real Time Streaming Protocol April 1998Overview of RTSP header fields12.1 AcceptThe Accept request-header field can be used to specify certainpresentation description content types which are acceptable for theresponse.The "level" parameter for presentation descriptions is properlydefined as part of the MIME type registration, not here.See [H14.1] for syntax.Example of use:Accept: application/rtsl, application/sdp;level=212.2 Accept-EncodingSee [H14.3]12.3 Accept-LanguageSee [H14.4]. Note that the language specified applies to thepresentation description and any reason phrases, not the mediacontent.12.4 AllowThe Allow response header field lists the methods supported by theresource identified by the request-URI. The purpose of this field isto strictly inform the recipient of valid methods associated with theresource. An Allow header field must be present in a 405 (Method notallowed) response.Example of use:Allow: SETUP, PLAY, RECORD, SET_PARAMETER12.5 AuthorizationSee [H14.8]12.6 BandwidthThe Bandwidth request header field describes the estimated bandwidthavailable to the client, expressed as a positive integer and measuredin bits per second. The bandwidth available to the client may changeduring an RTSP session, e.g., due to modem retraining.Schulzrinne, et. al. <strong>Standards</strong> <strong>Track</strong> [Page 46]

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!