Re: [rtcweb] New Version Notification for draft-guduru-rtcweb-codec-preferences-01.txt

Justin Uberti <juberti@google.com> Mon, 21 July 2014 03:30 UTC

Return-Path: <juberti@google.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 F40641B2B16 for <rtcweb@ietfa.amsl.com>; Sun, 20 Jul 2014 20:30:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.379
X-Spam-Level:
X-Spam-Status: No, score=-1.379 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=no
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 2UuhsfV_C08b for <rtcweb@ietfa.amsl.com>; Sun, 20 Jul 2014 20:30:41 -0700 (PDT)
Received: from mail-vc0-x230.google.com (mail-vc0-x230.google.com [IPv6:2607:f8b0:400c:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC0A41A033E for <rtcweb@ietf.org>; Sun, 20 Jul 2014 20:30:40 -0700 (PDT)
Received: by mail-vc0-f176.google.com with SMTP id id10so6460269vcb.7 for <rtcweb@ietf.org>; Sun, 20 Jul 2014 20:30:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=IzcqxdQFKKzNK4+08XAayo86IfL6UsC0Linvs8TeXLE=; b=GwIR7Ah0k2StJlQlbRpL4VN9ha043UgesLBqEU5iO2d9oa8KV6XzTx7q5zVrlIekwB rUQK11bMivaMoyTJHDjydSB4h8uUU9t0JYYHjWdln1GsGAxaKaEfbBan7MaUIj/x3aFe 3AElHveMFjlplWfX9y/d1yx6kHzrAcNIi06jIpTEaKwTlVMyjyhdC46tq28crPIy+oQn 0TYqGd4sTh4QScHjxCs651I5RtxApSeaFLqZ/7xe0gey+DgYAArGwm2XN3Izo29x138A pO1sYeEiWiB0syQlf7bAN/9VUmH5KQGFxHMPKJL/thj6faaDfz1ct3N2Bb467oxjKMUY o2Iw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=IzcqxdQFKKzNK4+08XAayo86IfL6UsC0Linvs8TeXLE=; b=TJo0xOzGEPrXAseftRT6LXvvNyF+ByILAeupl73getdB12iJdvfZ+SlpqPnnwOr7YV Emdipy3eGYe0mM6cfckN7jgk9ikB6NIZxHyQYqkuuIaF765yDX0rB3ZLyIEuFTxqgSg3 18b0qvm9XSkr5mS0upBAN8Qq6KkiznULu6k6UARPtBox+jRsDAfPZ6dsQj6ld8kzt8pF 0YLREaV9Ea8HytMcuQnCrc2kHOH1KpErlncT8pLh7N47MQd16WE6WDa0ZlZVxChdirNy DO2q9ulaI8jtPgvL9kAM3+RkvbntD8WyrW5xRpVJAbqBFQJWkcFIQAij7f8SeJKyGnFZ x43g==
X-Gm-Message-State: ALoCoQlOthKFNoxoDk+y0oZxaXLvCAGpNWbiLZNl7fdinSWpJ30tgNaHmRTb9Bh3zrrniZOJGh+/
X-Received: by 10.52.166.10 with SMTP id zc10mr7005953vdb.61.1405913439938; Sun, 20 Jul 2014 20:30:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.66.242 with HTTP; Sun, 20 Jul 2014 20:30:19 -0700 (PDT)
In-Reply-To: <CAEmcxLW3CP2OizbhwPVX19nyXwNW8-codHjsTyp-hnTNO=9pTQ@mail.gmail.com>
References: <74.10.26169.C4457B35@epcpsbgx4.samsung.com> <CAEmcxLW3CP2OizbhwPVX19nyXwNW8-codHjsTyp-hnTNO=9pTQ@mail.gmail.com>
From: Justin Uberti <juberti@google.com>
Date: Sun, 20 Jul 2014 23:30:19 -0400
Message-ID: <CAOJ7v-08cjGC992+qdpv7aFpaMHh4gkOukeyn1aQubCkYSjJRQ@mail.gmail.com>
To: franklin blek <franklin.blek@gmail.com>
Content-Type: multipart/related; boundary="001a11c2bdaa2c5e7304feabbb21"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/x-IEpHrpZdiCgD1WRhW8gXpik4s
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>, Kiran Kumar Guduru <kiran.guduru@samsung.com>, "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 03:30:43 -0000

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
>>
>>
>>
>>
>>
>>
>