RTP payload format for MPEG-4 Audio/Visual streams
draft-jnb-mpeg4av-rtp-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Yoshimitsu Kikuchi | ||
| Last updated | 1999-10-28 | ||
| 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 RTP payload formats for the carriage of MPEG-4 Audio and Visual streams[2][3], and an RTCP format for MPEG-4 backward channel messages functionalities[4]. It is based on the RTP/RTCP specification descried in the study on Internet draft for the carriage of MPEG-4 on IP[5]. In this specification, MPEG-4 Audio/Visual bitstreams are directly mapped into RTP packets without using MPEG-4 Systems[6]. The RTP header fields usage and the fragmentation rule for MPEG-4 Visual and Audio bitstreams are specified. It also specifies an RTCP packet usage to carry the MPEG-4 backward channel messages.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)