The Case for Layered Codecs
draft-wenger-rtcweb-layered-codec-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Stephan Wenger , Alex Eleftheriadis | ||
| Last updated | 2011-07-04 | ||
| 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
RTCWEB is in the process of developing a protocol infrastructure and a browser API to support browser-to-browser real-time communication over IP. Real-time communication necessarily requires the use of encoders and decoders (codecs) for media data. The document advocates mandating support for a class of codecs known as scalable or layered codecs, for their superior network adaptivity, error resilience, and application adaptivity. Examples are provided for use cases currently under discussion, focusing on video coding as the, perhaps, most challenging media type currently under consideration.
Authors
Stephan Wenger
Alex Eleftheriadis
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)