The Role of DMIF with RTSP and MPEG-4
draft-balabanian-rtsp-mpeg4-dmif-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Vahe Balabanian | ||
| Last updated | 1998-09-22 | ||
| 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 draft technical proposal describes how MPEG DMIF (Delivery Multimedia Integration Framework) can be used with RTSP for setting MPEG-4 service sessions and subsequently detaching the service. DMIF creates an instance of DMIF RTSP augmented with QoS appropriate for each MPEG-4 stream and also makes use of the FlexMux to carry multiple streams on a single UDP or TCP IP flow. The stream control play/pause etc. using RTSP is executed directly by the MPEG-4 Systems Sync Layer. Comments are solicited and should be addressed to the working group's mailing list at confctrl@isi.edu and/or the authors.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)