RTSP 2.0 Asynchronous Notification
draft-stiemerling-rtsp-announce-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Tetsuya Ura , Kenshin Oku , Hiromi Harada , Akira Kobayashi , Martin Stiemerling | ||
Last updated | 2008-02-25 | ||
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
Some IPTV deployments that are using the Real Time Streaming Protocol (RTSP) require the ability of the server to notify clients about asynchronous events occurring during an RTSP session. Current deployments typically use the ANNOUNCE method of RTSP 1.0 for sending such asynchronous events from a server to clients by using some proprietary extensions. However, the ANNOUNCE method has been removed from the current RTSP 2.0 draft, leaving the new specification without a mechanism for sending asynchronous messages from the server. This memo describes a use case for such an asynchronous message and proposes a new RTSP 2.0 method.
Authors
Tetsuya Ura
Kenshin Oku
Hiromi Harada
Akira Kobayashi
Martin Stiemerling
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)