Re: [rtcweb] RTCWEB needs an Internet Codec

Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com> Thu, 30 August 2012 14:15 UTC

Return-Path: <stefan.lk.hakansson@ericsson.com>
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 7156221F8535 for <rtcweb@ietfa.amsl.com>; Thu, 30 Aug 2012 07:15:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.082
X-Spam-Level:
X-Spam-Status: No, score=-6.082 tagged_above=-999 required=5 tests=[AWL=0.167, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 883okNFFCr-w for <rtcweb@ietfa.amsl.com>; Thu, 30 Aug 2012 07:15:12 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 8ABC021F8528 for <rtcweb@ietf.org>; Thu, 30 Aug 2012 07:15:12 -0700 (PDT)
X-AuditID: c1b4fb30-b7f7d6d0000042ea-5e-503f756f0295
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id A3.80.17130.F657F305; Thu, 30 Aug 2012 16:15:11 +0200 (CEST)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0237.eemea.ericsson.se (153.88.115.91) with Microsoft SMTP Server id 8.3.264.1; Thu, 30 Aug 2012 16:15:09 +0200
Message-ID: <503F756B.40102@ericsson.com>
Date: Thu, 30 Aug 2012 16:15:07 +0200
From: Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <p06240603cc63f3f41ca9@[99.111.97.136]> <503F46C5.2090607@alvestrand.no> <EDC0A1AE77C57744B664A310A0B23AE240CBCCD8@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <503F61CC.1010709@alvestrand.no>
In-Reply-To: <503F61CC.1010709@alvestrand.no>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrNJMWRmVeSWpSXmKPExsUyM+JvrW5+qX2AwZ4nchZr/7WzOzB6LFny kymAMYrLJiU1J7MstUjfLoEr4/T8b4wFM9krPhyeytzA+Jq1i5GDQ0LAROL+JZYuRk4gU0zi wr31bF2MXBxCAqcYJX6c+A7lLGeU+D11BTNIFa+ApsSed/tYQWwWAVWJ+9c3MIHYbAI2Emu7 p4DZogIhEmu+TWGEqBeUODnzCdgGEQFhia2vesFqhIEWn/r2jhViwXFGiXWNk8CKOAV0JR5+ nMsGYjML2EpcmHOdBcKWl9j+dg7YEUJANe9e32OdwCgwC8mOWUhaZiFpWcDIvIpRODcxMye9 3FwvtSgzubg4P0+vOHUTIzAAD275bbCDcdN9sUOM0hwsSuK8eqr7/YUE0hNLUrNTUwtSi+KL SnNSiw8xMnFwSjUw5j6z2RnXlvnCIyr5SQ5byv8X5+vYr++xCbU8FRGZ/W3bnwoWcXu1JfWK xcp5G2uSrzz/kC0s2x30UWvaYvGJh7aeEq/Z0q14/HrV8UW2AlFCB599nsc/b2f4hhtf35St Ml89TUk6Qz6y0+Tc1YYnywwTe9YstX2gYDQht8f0vMA+Hm2xlZ8qlFiKMxINtZiLihMBxqDG XA4CAAA=
Subject: Re: [rtcweb] RTCWEB needs an Internet Codec
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: Thu, 30 Aug 2012 14:15:13 -0000

On 08/30/2012 02:51 PM, Harald Alvestrand wrote:
> On 08/30/2012 02:38 PM, DRAGE, Keith (Keith) wrote:
>> Surely that argument extends to every possible codec.
> The set of MTI codecs should cover the set of use cases that have
> been identified. Additional MTI codecs that don't cover new use cases
> shouldn't be added.
>
> I believe the use case "distributed music band" in
> draft-ietf-rtcweb-use-cases-and-requirements can't be satisified with
> G.711.

I would argue that for most of the use cases (except those where the 
browser is used to interop with PSTN) the expected quality can't be 
satisfied with G.711. A wideband capable codec at the very least is needed.

Another story is that I think that this is not the right time to mandate 
a codec that meets the quality expectations (and I said why I think so 
in [1]).

[1] http://www.ietf.org/mail-archive/web/rtcweb/current/msg05148.html