RTP Payload Format for MPEG-4 with Flexible Error Resiliency
draft-ietf-avt-mpeg4streams-04
Document | Type |
Expired Internet-Draft
(avt WG)
Expired & archived
|
|
---|---|---|---|
Authors | Paul Christ , Anders Klemets , Christine Guillemot , Stefan Wesner | ||
Last updated | 2000-03-13 | ||
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 | Expired | |
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 a payload format, which can be used for the transport of both MPEG-4 Elementary Streams (ES), i.e audio, visual, BIFS and OD streams and MPEG-4 Sync Layer and Flexmux packet streams, in RTP [1] packets. The payload format allows for protec- tion against loss in a generic way. The mechanisms proposed can op- erate both on full and partial MPEG-4 ES Access Units, on Sync Layer packets, or Flexmux packets. 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 potentially 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.)