Re: [rtcweb] Usecases for innovation.

Bernard Aboba <> Wed, 09 November 2011 23:11 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5AA8911E809A for <>; Wed, 9 Nov 2011 15:11:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.548
X-Spam-Status: No, score=-102.548 tagged_above=-999 required=5 tests=[AWL=0.051, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id J8z1IXdV7b61 for <>; Wed, 9 Nov 2011 15:11:24 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 6317311E8087 for <>; Wed, 9 Nov 2011 15:11:24 -0800 (PST)
Received: from BLU152-DS12 ([]) by with Microsoft SMTPSVC(6.0.3790.4675); Wed, 9 Nov 2011 15:11:24 -0800
X-Originating-IP: []
X-Originating-Email: []
Message-ID: <BLU152-ds12D563F30536059E1EA0E793DF0@phx.gbl>
From: Bernard Aboba <>
To: "'Tim Panton'" <>
References: <>, <> <BLU152-W6072C34EB0609E293E49FC93DF0@phx.gbl> <>
In-Reply-To: <>
Date: Wed, 9 Nov 2011 15:11:23 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQK3klpE9bh0syVZ9dPKHFC+bqO2DQKnvd6zAfyFwKQBGc1qBJOhUjRw
Content-Language: en-us
X-OriginalArrivalTime: 09 Nov 2011 23:11:24.0173 (UTC) FILETIME=[E6889BD0:01CC9F34]
Subject: Re: [rtcweb] Usecases for innovation.
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 09 Nov 2011 23:11:25 -0000

Tim said:

"Both cases point out the fact that tying codecs/networking/negotiation into
one object and only presenting a (somewhat opaque) blob of SDP to represent
them limits what we can do at the javascript end. That may be a limitation
we can live with, but at least we need to acknowledge that it is a

[BA] For webcams with hardware encode/decode, this is an issue.  Given the
performance/power issues, it is important to enable the device
capabilities/codec support to be integrated.  It's one thing to talk about
what codecs a browser needs to support, but it should be recognized that
hardware could supplement those capabilities, and the browser shouldn't be a
bottleneck preventing the hardware from being utilized.