A RTP Payload for Redundant Non-Audio Data
draft-smundra-avt-rtp-red-non-audio-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Satish Mundra | ||
| Last updated | 2004-06-09 | ||
| 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 specifies an RTP payload format for encoding redundant non-audio data for use with RFC 2198 redundancy scheme. The primary motivation for the payload format described herein is accurate loss detection and sequencing, and to make the redundancy mechanism independent of clock rate being used for non-audio data. It is hoped that use of this payload format will simplify the implementation of RFC 2198 redundancy mechanism for non-audio data and may improve efficiency of redundancy mechanism if RTCP extended reports (XR) were available to RTP senders.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)