RTP Payload Format for MPEG-4 Streams
draft-rgcc-avt-mpeg4flexmux-04
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | D Curet , Emmanuel Gouleau | ||
| Last updated | 2000-03-14 (Latest revision 2000-03-15) | ||
| 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 describes an RTP payload format for the transportation of encoded and multiplexed MPEG-4 streams. MPEG-4 is a standard whose aims are to define a generic way to code natural or synthetic scenes. MPEG-4, among other things, supports a normative interface to Intel- lectual Property Management and Protection Systems. MPEG-4 also gives methods to synchronise and multiplex several MPEG-4 encoded streams. RTP, on the other hand, is a protocol that has been especially writ- ten for multimedia stream over the IP network, and to use RTP for the carriage of MPEG-4 data does make sense, enabling such applica- tions as Video on demand or Multicast Teleconferencing.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)