Re: [rtcweb] The MTI Codec Questions (what to ask and how to ask them)

Rob Pickering <rob@pickering.org> Thu, 06 November 2014 01:36 UTC

Return-Path: <rob@pickering.org>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D2571A0010 for <rtcweb@ietfa.amsl.com>; Wed, 5 Nov 2014 17:36:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kpZOJ2ZvqSqq for <rtcweb@ietfa.amsl.com>; Wed, 5 Nov 2014 17:36:54 -0800 (PST)
Received: from mail12.bp.ipcortex.net (mail12.bp.ipcortex.net [37.122.192.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 667DB1A000C for <rtcweb@ietf.org>; Wed, 5 Nov 2014 17:36:54 -0800 (PST)
Received: from Robs-MBP.home (host86-133-242-159.range86-133.btcentralplus.com [86.133.242.159]) (authenticated bits=0) by mail12.bp.ipcortex.net (8.14.6/8.14.0) with ESMTP id sA61an0o014347 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <rtcweb@ietf.org>; Thu, 6 Nov 2014 01:36:51 GMT
Message-ID: <545AD0AC.4010204@pickering.org>
Date: Thu, 06 Nov 2014 01:36:44 +0000
From: Rob Pickering <rob@pickering.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <98200BCB-ABC9-4BE0-B11D-B7AEC9F8B2A4@ieca.com> <7594FB04B1934943A5C02806D1A2204B1D4E50D8@ESESSMB209.ericsson.se> <E78E8017-A08F-4061-B2BA-FB3900B1C681@phonefromhere.com> <CALiegf=c=APH4adLXGeRKAf8rf68yCPL8Sp8mDfAzm18_oSxHg@mail.gmail.com> <6CFBDDC9-E38B-4354-BCB1-B0DA93D533E2@phonefromhere.com>
In-Reply-To: <6CFBDDC9-E38B-4354-BCB1-B0DA93D533E2@phonefromhere.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
X-SMTP-Vilter-Version: 1.3.6
X-Spamd-Symbols: BAYES_00, HELO_LH_HOME, RCVD_IN_PBL, RCVD_IN_RP_RNBL, RCVD_IN_SORBS_DUL
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/R_nh9Cf3yfB8Jom9v2sOp_a6RnM
Subject: Re: [rtcweb] The MTI Codec Questions (what to ask and how to ask them)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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, 06 Nov 2014 01:36:56 -0000

On 05/11/2014 19:12, tim panton wrote:
> On 5 Nov 2014, at 15:47, Iñaki Baz Castillo <ibc@aliax.net> wrote:
>
>> 2014-11-04 18:01 GMT+01:00 tim panton <tim@phonefromhere.com>:
>>> All implementations of the rtcweb specification must implement at least one of  VP8 or H.264,
>>> implementations that also implement the w3c’s webRTC javascript  API must implement  both VP8 and H264
>> +1
>>
>> This is obviously the only way-to-go and the only reasonable and
>> feasible decision.
>>
>> BTW and given that this is a W3C business, I would replace:
>>   "implementations that also implement the w3c’s webRTC javascript  API"
>> with:
>>   “browsers"
> Yes, that is the intention, but I think it is easier to get agreement on this clear, if clumsy, definition.
> If you want to come up with a good  definition of a browser, feel free :-)
> Me, I’m dodging that bullet!
+1 to the proposal and sane to dodge the bullet

Perhaps that should read "implementations that also *expose* the w3c's 
javascript API" otherwise there is an interesting case where a compiled 
mobile app isn't a "browser", but the same app using one of the JS app 
frameworks internally is. Externally they have essentially the same 
characteristics.

--
     Rob.