Re: [rtcweb] selecting codec for RTCweb?

Harald Alvestrand <harald@alvestrand.no> Mon, 05 September 2011 20:10 UTC

Return-Path: <harald@alvestrand.no>
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 AC49C21F8A55 for <rtcweb@ietfa.amsl.com>; Mon, 5 Sep 2011 13:10:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.39
X-Spam-Level:
X-Spam-Status: No, score=-106.39 tagged_above=-999 required=5 tests=[AWL=4.209, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 4ybhIdsHn0ZH for <rtcweb@ietfa.amsl.com>; Mon, 5 Sep 2011 13:10:54 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 09BAE21F8A1A for <rtcweb@ietf.org>; Mon, 5 Sep 2011 13:10:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 4104139E050 for <rtcweb@ietf.org>; Mon, 5 Sep 2011 22:12:29 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xasZX+EgnMug for <rtcweb@ietf.org>; Mon, 5 Sep 2011 22:12:28 +0200 (CEST)
Received: from [192.168.0.14] (c213-89-141-213.bredband.comhem.se [213.89.141.213]) by eikenes.alvestrand.no (Postfix) with ESMTPS id 94D3239E040 for <rtcweb@ietf.org>; Mon, 5 Sep 2011 22:12:28 +0200 (CEST)
Message-ID: <4E652D2C.8080408@alvestrand.no>
Date: Mon, 05 Sep 2011 22:12:28 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.21) Gecko/20110831 Thunderbird/3.1.13
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CA8A4F2F.30765%stewe@stewe.org>
In-Reply-To: <CA8A4F2F.30765%stewe@stewe.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] selecting codec for RTCweb?
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: Mon, 05 Sep 2011 20:10:54 -0000

On 09/05/2011 07:09 PM, Stephan Wenger wrote:
> In this context, Alex and myself drafted and presented in Quebec
> http://www.ietf.org/internet-drafts/draft-wenger-rtcweb-layered-codec-00.tx
> t, which argues against mandation of codec technologies not supporting
> scalability.  I have not seen any significant discussion in Quebec or on
> this mailing list about codec selection, though there was some initial
> noise on this topic during the BOFs.
The other consideration that has been raised is, of course, the issue of 
license-insisted-on versus practiced-without-a-license codecs (I won't 
call them "license required" or "license free"; that would be presumptuous.)

I believe we need a baseline codec that is "good enough", but I have 
neither a clear picture on how to quantify "good enough", nor a 
conviction that the scalability advantages raised in draft-wenger are 
important enough to tilt the balance.

          Harald