IETF Logo Mail Archive

Re: [rtcweb] RTCWEB needs an Internet Codec

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 30 August 2012 14:22 UTC

Return-Path: <christer.holmberg@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 9546B21F8610 for <rtcweb@ietfa.amsl.com>; Thu, 30 Aug 2012 07:22:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.172
X-Spam-Level:
X-Spam-Status: No, score=-6.172 tagged_above=-999 required=5 tests=[AWL=0.077, 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 a-MAm0IVCG+D for <rtcweb@ietfa.amsl.com>; Thu, 30 Aug 2012 07:22:00 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id C50BB21F8607 for <rtcweb@ietf.org>; Thu, 30 Aug 2012 07:21:59 -0700 (PDT)
X-AuditID: c1b4fb2d-b7fea6d000002ccb-7f-503f77063346
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 0D.BB.11467.6077F305; Thu, 30 Aug 2012 16:21:58 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.99]) by esessmw0247.eemea.ericsson.se ([153.88.115.93]) with mapi; Thu, 30 Aug 2012 16:21:58 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Harald Alvestrand <harald@alvestrand.no>, "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Date: Thu, 30 Aug 2012 16:21:56 +0200
Thread-Topic: [rtcweb] RTCWEB needs an Internet Codec
Thread-Index: Ac2Gri+4hzHOmoPMT7mccN53hLwz2gADIVKg
Message-ID: <7F2072F1E0DE894DA4B517B93C6A0585340A3DCA98@ESESSCMS0356.eemea.ericsson.se>
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>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrELMWRmVeSWpSXmKPExsUyM+JvrS5buX2AweXpehbH+rrYLJ42nmW0 WPuvnd2B2aP12V5WjysTrrB6LFnykymAOYrLJiU1J7MstUjfLoEro+XaHNaCbzwV3c2XmRoY L3F1MXJySAiYSPTtPc8OYYtJXLi3nq2LkYtDSOAUo8TK5QdYIJwFjBKTuq8AORwcbAIWEt3/ tEEaRATSJZ60/WEEsZkF1CXuLD4HNohFQFXiya5PbCC2MNCCSb9uM0HUm0p8aVrABmEbSVw9 +IEZZCSvQLjEqjW+EKvOMkqc+LkVbA6ngK7Ew49zweoZgY77fmoNE8QucYlbT+YzQRwtILFk z3lmCFtU4uXjf6wQ9aISd9rXQ92mI7FgN8Q9zALaEssWvgar5xUQlDg58wnLBEaxWUjGzkLS MgtJyywkLQsYWVYxCucmZuaklxvqpRZlJhcX5+fpFaduYgTG08Etv3V3MJ46J3KIUZqDRUmc lytpv7+QQHpiSWp2ampBalF8UWlOavEhRiYOTqkGxil8jJef/3Y5JRBmGJ5lF/VtO/8kp6RN O9ex/U3ckPlURXRZyYmN3y8cMzj02aB11gTJdaZtbsWJKrnm507u/3XyUwJL4zuuBOZqDo0X Rfm8axbpXRdWcl+pOKnHrq3uf0h29mkP1/jTXSF8caueHEvm13acqPxB7bOD0EHD2nyFKKsZ NfUKSizFGYmGWsxFxYkAFxe+6HUCAAA=
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
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:22:02 -0000

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

Maybe dubstep was invented that way ;)

Regards,

Christer




>> -----Original Message-----
>> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On 
>> Behalf Of Harald Alvestrand
>> Sent: 30 August 2012 11:56
>> To: rtcweb@ietf.org
>> Subject: Re: [rtcweb] RTCWEB needs an Internet Codec
>>
>> The counterpoint is that having G.711 as the only MTI means that you 
>> get interoperability failure for any application in which G.711 sound 
>> quality is not acceptable.
>>
>> This includes all applications involving music.
>>
>> On 08/29/2012 06:30 PM, Randall Gellens wrote:
>>> At 12:13 AM -0400 8/29/12, Roman Shpount wrote:
>>>
>>>>   I would argue G.711 should be the MTI codec. The rest can be left 
>>>> up to browser implementers.
>>> I agree.
>>>
>>>>   We can argue all we want, but the best royalty free low bitrate 
>>>> codec available will be the one everybody supports.
>>> Very good point, and why we should mandate only one audio codec.
>>>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb

_______________________________________________
rtcweb mailing list
rtcweb@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email