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

tim panton <tim@phonefromhere.com> Tue, 04 November 2014 17:01 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 655C61A90D6 for <rtcweb@ietfa.amsl.com>; Tue, 4 Nov 2014 09:01:59 -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 5o3LlKQeMeaC for <rtcweb@ietfa.amsl.com>; Tue, 4 Nov 2014 09:01:57 -0800 (PST)
Received: from smtp002.apm-internet.net (smtp002-out2.apm-internet.net [85.119.248.225]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 529FC1A19E6 for <rtcweb@ietf.org>; Tue, 4 Nov 2014 09:01:57 -0800 (PST)
Received: (qmail 45598 invoked from network); 4 Nov 2014 17:01:55 -0000
X-AV-Scan: clean
X-APM-Authkey: 83769 12891
Received: from unknown (HELO zimbra003.verygoodemail.com) (85.119.248.218) by smtp002.apm-internet.net with SMTP; 4 Nov 2014 17:01:55 -0000
Received: from zimbra003.verygoodemail.com (localhost [127.0.0.1]) by zimbra003.verygoodemail.com (Postfix) with ESMTP id 0D07718A1D8E; Tue, 4 Nov 2014 17:01:50 +0000 (GMT)
Received: from [10.7.79.176] (unknown [193.120.74.172]) by zimbra003.verygoodemail.com (Postfix) with ESMTPSA id 90B1518A0B9A; Tue, 4 Nov 2014 17:01:49 +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: <7594FB04B1934943A5C02806D1A2204B1D4E50D8@ESESSMB209.ericsson.se>
Date: Tue, 4 Nov 2014 17:01:48 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <E78E8017-A08F-4061-B2BA-FB3900B1C681@phonefromhere.com>
References: <98200BCB-ABC9-4BE0-B11D-B7AEC9F8B2A4@ieca.com> <7594FB04B1934943A5C02806D1A2204B1D4E50D8@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/rlJ0x2F2QCJiBDcK_Hy5bJBW7U4
Cc: "rtcweb@ietf.org" <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: Tue, 04 Nov 2014 17:01:59 -0000

On 4 Nov 2014, at 16:55, Christer Holmberg <christer.holmberg@ericsson.com>; wrote:

> Hi Sean,
> 
>> Question #5 (hum)
>> 
>> With respect to the MTI codec:
>>  - Who can live with a requirement that WebRTC User Agents
>>     MUST support  both VP8 and H.264 and WebRTC devices
>>     MUST support  either VP8 or H.264?
>>   - Who can live with a requirement that all endpoints MUST support VP8?
>>   - Who can live with a requirement that all endpoints MUST support H.264?
> 
> As far as I know, we are still discussing the terminology, and meaning of "WebRTC User Agent", "WebRTC device", etc, so I don't think it is a good idea to use that in a hum at this point.
> 
> Or, if you want to use it, please provide a definition, to be used in the hum, of the terminology.

I think it may be possible to dodge the device definition problem by saying:

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

- The latter requirement would also need to be blessed by the w3c of course.

T.


> 
> Regards,
> 
> Christer
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb