Subject: [rtcweb] Fwd: New Version Notification for draft-guduru-ietf-rtcweb-codec-preferences-00.txt

From: Kiran Kumar Guduru <[email-masked]>
Date: Fri, 16 May 2014 13:23:28 +0000 (GMT)

Hi,

I published a draft that enhances RTCPeerConnection object, to provide API for JS App to modify the codec preferences.

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

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