IETF Logo Mail Archive

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

tim panton <tim@phonefromhere.com> Wed, 05 November 2014 19:05 UTC

Return-Path: <tim@phonefromhere.com>
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 18F1E1A1BA5 for <rtcweb@ietfa.amsl.com>; Wed, 5 Nov 2014 11:05:38 -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, RCVD_IN_DNSWL_NONE=-0.0001] 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 ttuGRCzr0vKK for <rtcweb@ietfa.amsl.com>; Wed, 5 Nov 2014 11:05:35 -0800 (PST)
Received: from smtp001.apm-internet.net (smtp001-out.apm-internet.net [85.119.248.222]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 061A01A1B91 for <rtcweb@ietf.org>; Wed, 5 Nov 2014 11:05:34 -0800 (PST)
Received: (qmail 94023 invoked from network); 5 Nov 2014 19:05:33 -0000
X-AV-Scan: clean
X-APM-Authkey: 83769 14376
Received: from unknown (HELO zimbra003.verygoodemail.com) (85.119.248.218) by smtp001.apm-internet.net with SMTP; 5 Nov 2014 19:05:33 -0000
Received: from zimbra003.verygoodemail.com (localhost [127.0.0.1]) by zimbra003.verygoodemail.com (Postfix) with ESMTP id 9F50C18A0E38; Wed, 5 Nov 2014 19:05:29 +0000 (GMT)
Received: from [192.168.42.25] (unknown [85.255.234.98]) by zimbra003.verygoodemail.com (Postfix) with ESMTPSA id 0BA0618A0C55; Wed, 5 Nov 2014 19:05:28 +0000 (GMT)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: tim panton <tim@phonefromhere.com>
In-Reply-To: <545A5739.9050604@bbs.darktech.org>
Date: Wed, 05 Nov 2014 19:05:28 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <3377C8F3-40F8-49F4-82A3-30F1886CDE06@phonefromhere.com>
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> <545A5739.9050604@bbs.darktech.org>
To: cowwoc <cowwoc@bbs.darktech.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/m5LbXJAccUFQeOBFoAzq32URxoQ
Cc: rtcweb@ietf.org
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: Wed, 05 Nov 2014 19:05:38 -0000

On 5 Nov 2014, at 16:58, cowwoc <cowwoc@bbs.darktech.org> wrote:

> On 05/11/2014 10:47 AM, Iñaki Baz Castillo 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"
> 
> Why should we treat non-browsers any differently?

My logic for this is that non-browsers are typically statically programmed, to do a single task well,
so don’t have the same over-riding need for interop with everything else.

A browser has no pre-defined use case and so has to be as flexible as possible to accommodate anything.


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

v2.23.0 | Report a Bug | By Email