RTP Payload Format for MPEG-4 Audio/Visual Streams
draft-ietf-avt-rfc3016bis-02
Document | Type |
Replaced Internet-Draft
(payload WG)
Expired & archived
|
|
---|---|---|---|
Authors | Malte Schmidt , Frans de Bont , Stefan Doehla , Jaehwan Kim | ||
Last updated | 2011-05-06 (Latest revision 2011-01-11) | ||
Replaces | draft-schmidt-avt-rfc3016bis | ||
Replaced by | draft-ietf-payload-rfc3016bis | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-payload-rfc3016bis | |
Consensus boilerplate | Unknown | ||
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 Real-Time Transport Protocol (RTP) payload formats for carrying each of MPEG-4 Audio and MPEG-4 Visual bitstreams without using MPEG-4 Systems. For the purpose of directly mapping MPEG-4 Audio/Visual bitstreams onto RTP packets, it provides specifications for the use of RTP header fields and also specifies fragmentation rules. It also provides specifications for Media Type registration and the use of Session Description Protocol (SDP). The audio payload format described in this document has some limitations. for new system designs [RFC3640] is preferred.
Authors
Malte Schmidt
Frans de Bont
Stefan Doehla
Jaehwan Kim
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)