Hi,

We published an Internet Draft, which extends RTCPeerConnection.

It provides API to get the codecs from browser and to set the APP specified codec preferences to browser through CreateOfferAnswerOptions.

The following are  the links for the same.

 

URL:            http://www.ietf.org/internet-drafts/draft-guduru-rtcweb-codec-preferences-00.txt

Status:         https://datatracker.ietf.org/doc/draft-guduru-rtcweb-codec-preferences/

Htmlized:       http://tools.ietf.org/html/draft-guduru-rtcweb-codec-preferences-00


 

------- Original Message -------

Sender : internet-drafts@ietf.org<internet-drafts@ietf.org>

Date : May 17, 2014 13:58 (GMT+09:00)

Title : New Version Notification for draft-guduru-rtcweb-codec-preferences-00.txt

 


A new version of I-D, draft-guduru-rtcweb-codec-preferences-00.txt
has been successfully submitted by Kiran Kumar Guduru and posted to the
IETF repository.

Name: draft-guduru-rtcweb-codec-preferences
Revision: 00
Title: WebRTC Codec Preferences
Document date: 2014-05-17
Group: Individual Submission
Pages: 4
URL:            http://www.ietf.org/internet-drafts/draft-guduru-rtcweb-codec-preferences-00.txt
Status:         https://datatracker.ietf.org/doc/draft-guduru-rtcweb-codec-preferences/
Htmlized:       http://tools.ietf.org/html/draft-guduru-rtcweb-codec-preferences-00


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.

                                                                                  


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat