Re: [rtcweb] Agenda time request for draft-marjou-rtcweb-audio-codecs-for-interop-01

"Olle E. Johansson" <oej@edvina.net> Wed, 13 March 2013 15:43 UTC

Return-Path: <oej@edvina.net>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F4BC21F8CB8 for <rtcweb@ietfa.amsl.com>; Wed, 13 Mar 2013 08:43:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.532
X-Spam-Level:
X-Spam-Status: No, score=-2.532 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ano7IV-ntREb for <rtcweb@ietfa.amsl.com>; Wed, 13 Mar 2013 08:43:14 -0700 (PDT)
Received: from smtp7.webway.se (smtp7.webway.se [IPv6:2a02:920:212e::205]) by ietfa.amsl.com (Postfix) with ESMTP id D5F3A21F8C82 for <rtcweb@ietf.org>; Wed, 13 Mar 2013 08:43:13 -0700 (PDT)
Received: from [192.168.40.23] (h87-96-134-129.dynamic.se.alltele.net [87.96.134.129]) by smtp7.webway.se (Postfix) with ESMTPA id 2628A93DE3E; Wed, 13 Mar 2013 15:42:57 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: "Olle E. Johansson" <oej@edvina.net>
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD2338D2897F@XMB104ADS.rim.net>
Date: Wed, 13 Mar 2013 16:42:36 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <3C89A60B-3171-49B0-A78F-304337DF8D3D@edvina.net>
References: <E8F5F2C7B2623641BD9ABF0B622D726D0F68869E@xmb-rcd-x11.cisco.com> <CA+9kkMA7x18x3rD9PoPx-rA+4uz7ome3LjQ7sOWHDptz0zJX6g@mail.gmail.com> <CAErhfrx24SR5zwH3oHQi_PhFkfQjCmbMuatwEw2kjJ184MiUpw@mail.gmail.com> <20130313142732.GE12022@audi.shelbyville.oz> <7897A33F-F73A-4C39-B4DA-16F014A43C5C@edvina.net> <BBF5DDFE515C3946BC18D733B20DAD2338D28848@XMB104ADS.rim.net> <8B7442F6-5393-4C5C-88B6-A680742F60E7@edvina.net> <BBF5DDFE515C3946BC18D733B20DAD2338D2897F@XMB104ADS.rim.net>
To: Andrew Allen <aallen@blackberry.com>
X-Mailer: Apple Mail (2.1499)
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Agenda time request for draft-marjou-rtcweb-audio-codecs-for-interop-01
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 13 Mar 2013 15:43:15 -0000

13 mar 2013 kl. 16:23 skrev Andrew Allen <aallen@blackberry.com>om>:

> Olle
> 
> I agree with you which is why a few months ago I proposed the following text that had the "are available to the browser" caveat
> 
> "If other suitable audio codecs are available to the browser to use it is recommended that they are also included in the offer in order to maximize the possibility to establish the session without the need for audio transcoding"

Exactly. I don't think everyone gets the that selecting a small subset as mandatory for WebRTC does NOT exclude all other codecs. Feel
free to add everything you got. Have fun. Let the best mutual codec with the best mutual properties win the session.

/O
> 
> Andrew
> 
> -----Original Message-----
> From: Olle E. Johansson [mailto:oej@edvina.net]
> Sent: Wednesday, March 13, 2013 11:18 AM
> To: Andrew Allen
> Cc: Olle E. Johansson; Ron; rtcweb@ietf.org
> Subject: Re: [rtcweb] Agenda time request for draft-marjou-rtcweb-audio-codecs-for-interop-01
> 
> 
> 13 mar 2013 kl. 15:58 skrev Andrew Allen <aallen@blackberry.com>om>:
> 
>> I think this would be completely out of scope of IETF.
> 
> Agree. So assuming that these codecs are available just because some hardware in a device has a licensed implementation is not a valid assumption for a codec selection as long as we can't assume that any application on that device has access to it.
> 
> /O
>> 
>> -----Original Message-----
>> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
>> Behalf Of Olle E. Johansson
>> Sent: Wednesday, March 13, 2013 10:41 AM
>> To: Ron
>> Cc: rtcweb@ietf.org
>> Subject: Re: [rtcweb] Agenda time request for
>> draft-marjou-rtcweb-audio-codecs-for-interop-01
>> 
>> 
>> 13 mar 2013 kl. 15:27 skrev Ron <ron@debian.org>rg>:
>> 
>>>> these three codecs: make them mandatory to implement when there is
>>>> no cost impact on the browser (e.g. if codec already installed, paid
>>>> by the device vendor...).
>> I would like to propose that someone (it's out of scope for this group) make it mandatory to implement open APIs so that all applications on these devices can use all the codecs implemented in hardware. That's not the case now.
>> 
>> /O
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>> 
>> ---------------------------------------------------------------------
>> This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
> 
> 
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.