Re: [rtcweb] RTCWEB needs an Internet Codec

Stefan Hacker <hacker.stefan@gmail.com> Fri, 31 August 2012 23:15 UTC

Return-Path: <hacker.stefan@gmail.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 1AA4021F8471 for <rtcweb@ietfa.amsl.com>; Fri, 31 Aug 2012 16:15:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.726
X-Spam-Level:
X-Spam-Status: No, score=-2.726 tagged_above=-999 required=5 tests=[AWL=0.873, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 V2P6skq30dCi for <rtcweb@ietfa.amsl.com>; Fri, 31 Aug 2012 16:15:39 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 44D1E21F846F for <rtcweb@ietf.org>; Fri, 31 Aug 2012 16:15:39 -0700 (PDT)
Received: by bkty12 with SMTP id y12so1520217bkt.31 for <rtcweb@ietf.org>; Fri, 31 Aug 2012 16:15:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=GYClhUN3doJXGCwpZQ5j1m1Q70c7K1s0D1l5Y24Eh3I=; b=sb+O1ZdIv7b9SPMODvX2Pbo2RoCZgKZNxbJZO/URwgmPTtJoSS8AwqrcGEP09d7pOa 57Dfk3UM66y4ASPAt/21DXkod5/oSV0CfSuaOOlIOUFlo6Z5tGOHJXXF/PcsNiwICB5i VvCbC2ACkwn0x1z9F2ZRihhQJPyzg4UwPc/7B6gyytLb5VH4F4MTYFHkex9K64GVp5zd nvcWO9xUhb/ir2Wau8PS8fht6NCVAsT1UG4Mk10bYaF+KeqEbND8/QBFefPaetq0rOiQ cqivfiAFDRPe3NegyhsMMrzioojIgZhiFI4M5LmZ627Fih6X/vsaIMlHfm/d2jgF8zk2 bliQ==
Received: by 10.204.129.14 with SMTP id m14mr4771791bks.7.1346454938255; Fri, 31 Aug 2012 16:15:38 -0700 (PDT)
Received: from [192.168.178.21] (dslb-092-075-111-053.pools.arcor-ip.net. [92.75.111.53]) by mx.google.com with ESMTPS id 14sm4324866bkq.12.2012.08.31.16.15.36 (version=SSLv3 cipher=OTHER); Fri, 31 Aug 2012 16:15:37 -0700 (PDT)
Message-ID: <50414593.2040607@gmail.com>
Date: Sat, 01 Sep 2012 01:15:31 +0200
From: Stefan Hacker <hacker.stefan@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
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> <CAC8DBE4E9704C41BCB290C2F3CC921A162D278D@nasanexd01h.na.qualcomm.com> <503FC1BF.5020004@alvestrand.no> <CAC8DBE4E9704C41BCB290C2F3CC921A162D2B0F@nasanexd01h.na.qualcomm.com> <5040541C.5020008@alvestrand.no> <20120831133845.GW72831@verdi> <5040CE32.5050003@jesup.org> <20120831151247.GY72831@verdi> <p06240608cc66e4862829@[99.111.97.136]>
In-Reply-To: <p06240608cc66e4862829@[99.111.97.136]>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Fri, 31 Aug 2012 23:15:40 -0000

On 01/09/2012 00:09, Randall Gellens wrote:
> Exactly.  The discussion has been going in my view off-track into 
> debates about which codec is best for which environments.  The real 
> issue is mandatory versus recommended.
>
> We can pick G.711 as MTI and rely on implementers to support others.
>
Imho this would be a big mistake. Even if implementers were to pick up 
Opus as quasi MTI after the fact, which I'm not convinced would reliably 
happen, this would critically damage the abilities of RTCWEB at launch.

Remember that the first implementations are not likely to venture far 
into "recommended" territory and for many Opus is still an unknown no 
matter its credentials and advantages.

Opus as an MTI offers the chance to make RTCWEB worth, even desirable, 
using Out-Of-The-Box for the majority of the intended use-cases. It 
ensures implementers have a codec at their hands that not only 
guarantees interoperability but also lets them pick the best possible 
quality, be it for low/high bandwidth or CPU or latency.

Regards,
Stefan