RTP Payload Format for MPEG-4 with Scaleable & Flexible Error Resiliency
draft-guillemot-genrtp-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Paul Christ , Anders Klemets , Christine Guillemot , Stefan Wesner | ||
| Last updated | 1999-07-02 | ||
| 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 a payload format, which can be used for the transport of both MPEG-4 Elementary Streams (ES) as well as MPEG-4 Sync Layer packet streams, in RTP [1] packets. The payload format allows for protection against loss in a generic way, through frag- mentation, grouping and extension data mechanisms, which can dynamically adapt to network conditions. These mechanisms can operate both on full and partial MPEG-4 Access Units, such as Sync Layer packets, or typed segments, These mechanisms can cover a broad range of protection schemes and avoid extra connection management complexity - e.g. for separate FEC channels - in MPEG-4 applications with a high number of streams.
Authors
Paul Christ
Anders Klemets
Christine Guillemot
Stefan Wesner
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)