Bitrate header in RTSP
draft-wei-mmusic-rtsp-bitrate-header-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Kylin Wei | ||
| Last updated | 2006-06-13 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document presents an integrated solution for multiple bitrates by defining the Bitrate header in RTSP. A client can inquire bitrate range of media source after a successful SETUP request by sending a GET_PARAMETER request with the bitrate parameter to the RTSP server, and then server responds with bitrate range parameter of media source. According to bitrate range parameter value, the client MAY apply for bandwidth reservation by RSVP (Resource Reservation Protocol) [5] or apply for increasing access bandwidth. The client MAY select a suitable bitrate to start with or change transport bitrate during the playing by sending a PLAY request with the Bitrate header.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)