RTP Payload Format for H.263 Video Stream
draft-zhu-avt-h263-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Chunrong Zhu | ||
| Last updated | 1996-03-13 (Latest revision 1996-02-12) | ||
| 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 the RTP payload format for encapsulating H.263 bitstreams in Real-Time Transport Protocol (RTP). The H.263 payload header is designed for flexibility and simplicity. RTP can use one of three possible modes for H.263 video streams depending on the desired performance characteristics. The shortest header mode (Mode A) results in simplicity and easy recovery of lost packets, brought about by fragmentation at Group of Block (GOB) boundaries. The long header modes (Mode B and C) result in more efficient use of bandwidth, brought about by fragmentation at Macroblock (MB) boundaries.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)