WebRTC Codec Preferences
draft-guduru-ietf-rtcweb-codec-preferences-00
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Kiran Kumar Guduru | ||
Last updated | 2014-05-20 (Latest revision 2014-05-16) | ||
Replaced by | draft-guduru-rtcweb-codec-preferences | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-guduru-rtcweb-codec-preferences | |
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
WebRTC working group prefers mandatory to implement codecs inside the browser to achieve guaranteed interoperability between two WebRTC peers. WebRTC allows browser implementors to support vendor specific codecs apart from mandatory codecs. This document explains the way to give preferences for media codecs in WebRTC context out of the available codecs in browser for creating the offer / answer.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)