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

cowwoc <cowwoc@bbs.darktech.org> Wed, 05 November 2014 16:58 UTC

Return-Path: <cowwoc@bbs.darktech.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 71A9E1A8978 for <rtcweb@ietfa.amsl.com>; Wed, 5 Nov 2014 08:58:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 yKIIhHuwPWyU for <rtcweb@ietfa.amsl.com>; Wed, 5 Nov 2014 08:58:52 -0800 (PST)
Received: from mail-ie0-f178.google.com (mail-ie0-f178.google.com [209.85.223.178]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75E071A8983 for <rtcweb@ietf.org>; Wed, 5 Nov 2014 08:58:52 -0800 (PST)
Received: by mail-ie0-f178.google.com with SMTP id rp18so1099469iec.37 for <rtcweb@ietf.org>; Wed, 05 Nov 2014 08:58:51 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Uc8WcFwZN/HO4HOEwtzmTo1FzVugjQdO4yl9G/q/SIo=; b=LqU6OSWj0l4H4zdjMX1/oLtKJvPPPSJSvsrlbse1AwH5UkLRBPdH7CdfA+JjbezuRM mby8zwVAp6rsKbMyJ8QLNkBlJ2Y6iFUpcN+aVSh6wuoZMh0S2CyWOzxY61luIoUmj0jH 6Rn1LCS6Hl3auvWyAxK3V4ytUknNK1Ac6AD0+WJa10LwODwYGfx2eMBcrMgnpXmOu+FK DCCj4UF6NfmsIHb7HGi64ovd31NteLYPCwKQ2mZqm1IRJpbmFYAUhXHWLYnj8kAiNXqB 6FJRntI7z8yHXr0TZYUnkJTvu9jFULBu++aMoou12yMGoUn4q+w4eX0WKASjjSS0gLgI QrWQ==
X-Gm-Message-State: ALoCoQnuENp17ZLs9zrpoPILTuLO/CA9ZykOfPZ1u6YS/Ekm18wkzKTkoCxEa55kjoplWF/dRGPu
X-Received: by 10.107.128.146 with SMTP id k18mr4456758ioi.69.1415206731810; Wed, 05 Nov 2014 08:58:51 -0800 (PST)
Received: from [192.168.1.100] (206-248-171-209.dsl.teksavvy.com. [206.248.171.209]) by mx.google.com with ESMTPSA id 199sm1727375ion.7.2014.11.05.08.58.51 for <rtcweb@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 05 Nov 2014 08:58:51 -0800 (PST)
Message-ID: <545A5739.9050604@bbs.darktech.org>
Date: Wed, 05 Nov 2014 11:58:33 -0500
From: cowwoc <cowwoc@bbs.darktech.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.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>
In-Reply-To: <CALiegf=c=APH4adLXGeRKAf8rf68yCPL8Sp8mDfAzm18_oSxHg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/Bq9WjztWklOVNzlnlrA2bkooFEs
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 16:58:57 -0000

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?

Gili