- From: Eric Rescorla <ekr@rtfm.com>
- Date: Sun, 18 May 2014 10:39:24 -0700
- To: Justin Uberti <juberti@google.com>
- Cc: "kiran.guduru@samsung.com" <kiran.guduru@samsung.com>, Cullen Jennings <fluffy@iii.ca>, public-webrtc <public-webrtc@w3.org>
- Message-ID: <CABcZeBN12KOmp7MtLjZwKAOHb283tZOMDTZvGc06UZ5-Cq7irQ@mail.gmail.com>
On Sun, May 18, 2014 at 10:26 AM, Justin Uberti <juberti@google.com> wrote: > This is a slippery slope towards full capabilities introspection from JS. > I'm not opposed to that, but it's clearly not in scope for 1.0. > > Also, the use of createOffer options to specify the preferences is the > wrong place. I think the right place for this control surface would be on > the RTCRtpSender/Receiver object, as that avoids the need for separate > audio and video APIs, and lets the codecs be controlled per-track. > This would seem to imply that those objects must be accessible prior to CreateOffer(), right? -Ekr > > On Sun, May 18, 2014 at 6:38 AM, Kiran Kumar Guduru < > kiran.guduru@samsung.com> wrote: > >> Hi, >> >> >> >> http://tools.ietf.org/html/draft-guduru-ietf-rtcweb-codec-preferences-00 >> >> has been replaced with >> >> http://tools.ietf.org/html/draft-guduru-rtcweb-codec-preferences-00 >> >> >> >> Only name change, to make it appear in recweb related documents list in >> rtcweb status pages. >> >> >> >> Kiran. >> >> >> >> ------- *Original Message* ------- >> >> *Sender* : Cullen Jennings<fluffy@iii.ca> >> >> *Date* : May 18, 2014 22:18 (GMT+09:00) >> >> *Title* : Re: Avoid sdp mangling in WebRTC by setting codec preferences >> - review request. >> >> >> >> I’ve forwarded this to the webrtc group instead of rtcweb as I suspect >> that is also a good place to discuss it. >> >> >> On May 16, 2014, at 11:03 AM, Kiran Kumar Guduru wrote: >> >> > Dear Chairs, >> > I published an ietf drat related to RTCWEB wrok >> draft-guduru-ietf-rtcweb-codec-preferences-00. >> > The intention of this draft is to avoid SDP mangling. >> > It extends the RTCPeerConnection to allow JS application to set the >> codec preferences, instead of doing it through SDP mangling. >> > When I read the JSEP spec, I find that codec preferences is the only >> thing that requires SDP mangling, but remaining cases we can manage with >> constraints. >> > I hope this draft will be very helpful to make WebRTC more robust and >> will become a working group draft soon. >> > I request you in person to review the draft and let me know your >> comments. >> > The following is the link for the same. >> > >> http://tools.ietf.org/html/draft-guduru-ietf-rtcweb-codec-preferences-00 >> > >> … snip … >> > >> > Have a Nice Day, >> > Kiran. >> > >> > <201405162033058_Z7RK8XTA.gif> >> >> >> >> >> >> >> >> >
Attachments
- image/gif attachment: 201405181908858_QKNMBDIF.gif
Received on Sunday, 18 May 2014 17:40:33 UTC