Re: [rtcweb] New Version Notification for draft-guduru-rtcweb-codec-preferences-01.txt
Bernard Aboba <bernard.aboba@gmail.com> Mon, 21 July 2014 13:25 UTC
Return-Path: <bernard.aboba@gmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BB551B2DD9 for <rtcweb@ietfa.amsl.com>; Mon, 21 Jul 2014 06:25:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MVz8csTKwrzw for <rtcweb@ietfa.amsl.com>; Mon, 21 Jul 2014 06:25:26 -0700 (PDT)
Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0AF781B2DE5 for <rtcweb@ietf.org>; Mon, 21 Jul 2014 06:24:24 -0700 (PDT)
Received: by mail-wg0-f46.google.com with SMTP id m15so6485150wgh.5 for <rtcweb@ietf.org>; Mon, 21 Jul 2014 06:24:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=GauDp2i0MvSc8Yq0PsF9alimacAg7oF+hKsAgnBwyJE=; b=XxMHxTDNkAiUda0xDDuDhgFSTOMgy2rTKiZCIGQyok+dAC+EZeAe7y8ulzz0ewG6DR GDArC7LMZOzIV5Da0YW9LHLZ18j68ilOEwvvimQ+kF5kEqi6Cz7DNbCbOv8Bsb9OybDt K3qLdFDiQ8Qh64QrUi/B9lPxlN21C87HOotC3u+sZ1DlGvIcBfUusnXpgEG8ERuEfcgh yn63VI0HQDkCDTqBCsA06PYAKsT6nl/qCWspcA1Wz1z53l6tq+83ssLh19XUT2YaSFtu e3JtNuFU8EH9BLiJrhfIgK2RhHkoVjX7JrmSMWHKkZM3816nXCogQiyaEL4MwRvfFYOL kDnA==
X-Received: by 10.194.92.115 with SMTP id cl19mr23363793wjb.29.1405949063297; Mon, 21 Jul 2014 06:24:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.217.122.65 with HTTP; Mon, 21 Jul 2014 06:24:03 -0700 (PDT)
In-Reply-To: <CAOJ7v-08cjGC992+qdpv7aFpaMHh4gkOukeyn1aQubCkYSjJRQ@mail.gmail.com>
References: <74.10.26169.C4457B35@epcpsbgx4.samsung.com> <CAEmcxLW3CP2OizbhwPVX19nyXwNW8-codHjsTyp-hnTNO=9pTQ@mail.gmail.com> <CAOJ7v-08cjGC992+qdpv7aFpaMHh4gkOukeyn1aQubCkYSjJRQ@mail.gmail.com>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Mon, 21 Jul 2014 09:24:03 -0400
Message-ID: <CAOW+2dsQdBYxu+fYWApL-Muf5He8JnwjvBzKE_HWXFUNoOJQLQ@mail.gmail.com>
To: Justin Uberti <juberti@google.com>
Content-Type: multipart/related; boundary="047d7bfcf88e7dac8404feb406ac"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/sUSHDRGW8OHLZOXa7M5GMpvt76A
Cc: Kiran Kumar Guduru <kiran.guduru@samsung.com>, franklin blek <franklin.blek@gmail.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Subject: Re: [rtcweb] New Version Notification for draft-guduru-rtcweb-codec-preferences-01.txt
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Jul 2014 13:25:29 -0000
I agree with Justin that this draft is not a useful addition. Codecs are only one aspect of capability discovery, and so cannot be treated in isolation. So I would argue that the approach is problematic as well. On Sun, Jul 20, 2014 at 11:30 PM, Justin Uberti <juberti@google.com> wrote: > This seems like a pretty big hammer to solve a fairly small problem. This > proposal adds 6 new API points for the purpose of changing the order of > codecs in createOffer, which seems like a high cost-benefit ratio. And > while the use cases listed here are helpful, they seem somewhat contrived > to me, since it seems unlikely that the application can make better choices > about bandwidth or power consumption than the browser. > > Without a specific, concrete example, I remain unconvinced that this is > worth doing in the 1.0 timeframe. Post-1.0, we can probably find a way to > provide this sort of lower-level control. > > > On Sat, Jul 12, 2014 at 9:41 PM, franklin blek <franklin.blek@gmail.com> > wrote: > >> Hi, >> The draft seems to explain codec preferences in a good way. >> I think this has a good potenitial to be a part of WebRTC1.0. >> >> >> >> On Sat, Jul 5, 2014 at 10:26 AM, Kiran Kumar Guduru < >> kiran.guduru@samsung.com> wrote: >> >>> Hi, >>> >>> A new version of codec preferences draft has been published, by >>> modifying as per the review comments received. >>> >>> Please review and let me know your comments. >>> >>> >>> >>> Thanks & Regards, >>> >>> Kiran. >>> >>> >>> >>> ------- *Original Message* ------- >>> >>> *Sender* : internet-drafts@ietf.org<internet-drafts@ietf.org> >>> >>> *Date* : Jul 02, 2014 18:28 (GMT+09:00) >>> >>> *Title* : New Version Notification for >>> draft-guduru-rtcweb-codec-preferences-01.txt >>> >>> >>> >>> A new version of I-D, draft-guduru-rtcweb-codec-preferences-01.txt >>> has been successfully submitted by Kiran Kumar Guduru and posted to the >>> IETF repository. >>> >>> Name: draft-guduru-rtcweb-codec-preferences >>> Revision: 01 >>> Title: WebRTC Codec Preferences >>> Document date: 2014-07-02 >>> Group: Individual Submission >>> Pages: 7 >>> URL: >>> http://www.ietf.org/internet-drafts/draft-guduru-rtcweb-codec-preferences-01.txt >>> Status: >>> https://datatracker.ietf.org/doc/draft-guduru-rtcweb-codec-preferences/ >>> Htmlized: >>> http://tools.ietf.org/html/draft-guduru-rtcweb-codec-preferences-01 >>> Diff: >>> http://www.ietf.org/rfcdiff?url2=draft-guduru-rtcweb-codec-preferences-01 >>> >>> Abstract: >>> WebRTC specifies to implement a minimum set of required codecs to >>> ensure guaranteed interoperability between WebRTC peers. WebRTC >>> allows browser implementers to support vendor specific codecs apart >>> from mandatory codecs. This document specifies the way for >>> JavaScript applications 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 >>> >>> >>> >>> >>> >>> >> > > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb > >
- [rtcweb] Fwd: New Version Notification for draft-… Kiran Kumar Guduru
- Re: [rtcweb] New Version Notification for draft-g… franklin blek
- Re: [rtcweb] New Version Notification for draft-g… Justin Uberti
- Re: [rtcweb] New Version Notification for draft-g… Kiran Kumar Guduru
- Re: [rtcweb] New Version Notification for draft-g… Bernard Aboba
- Re: [rtcweb] New Version Notification for draft-g… Justin Uberti
- Re: [rtcweb] New Version Notification for draft-g… Makaraju, Maridi Raju (Raju)
- Re: [rtcweb] New Version Notification for draft-g… Kiran Kumar Guduru
- Re: [rtcweb] New Version Notification for draft-g… Kiran Kumar Guduru
- Re: [rtcweb] New Version Notification for draft-g… Justin Uberti
- Re: [rtcweb] New Version Notification for draft-g… Makaraju, Maridi Raju (Raju)
- Re: [rtcweb] New Version Notification for draft-g… franklin blek
- Re: [rtcweb] New Version Notification for draft-g… Kiran Kumar Guduru