An Evaluation of Session Initiation Protocol (SIP) for use in Streaming Media Applications
draft-whitehead-sip-for-streaming-media-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Steven Whitehead | ||
| Last updated | 2006-05-09 (Latest revision 2006-03-03) | ||
| Replaced by | draft-whitehead-mmusic-sip-for-streaming-media | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-whitehead-mmusic-sip-for-streaming-media | |
| 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 draft reviews requirements and evaluates solutions to improve the integration of the Session Initiation Protocol (SIP) [RFC3261] to the Real Time Streaming Protocol (RTSP and RTSP v2) [RFC 2326 and IDRTSP] especially in the context of converged media services. The document develops a rationale and solution space for using SIP with streaming media applications. This is done by first considering use cases that are used to define generic requirements to help compare the current and potentially new solutions. The range of solutions is sketched out (at high-level) and advantages and disadvantages discussed. The solutions evaluated address different levels of integration from SIP-only approaches to dual-protocol solutions.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)