IETF Logo Mail Archive

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

Daniel-Constantin Mierla <miconda@gmail.com> Wed, 05 November 2014 17:46 UTC

Return-Path: <miconda@gmail.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 CAD401A903E for <rtcweb@ietfa.amsl.com>; Wed, 5 Nov 2014 09:46:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 bk6oHAyLtTLt for <rtcweb@ietfa.amsl.com>; Wed, 5 Nov 2014 09:46:46 -0800 (PST)
Received: from mail-la0-x230.google.com (mail-la0-x230.google.com [IPv6:2a00:1450:4010:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6BF91A9039 for <rtcweb@ietf.org>; Wed, 5 Nov 2014 09:46:45 -0800 (PST)
Received: by mail-la0-f48.google.com with SMTP id gq15so1170107lab.35 for <rtcweb@ietf.org>; Wed, 05 Nov 2014 09:46:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=u/VB9nnBQi3SpdfG7zc/Y738yu1H44Y+heSdvS8fn4E=; b=RRtH3rEK9uSaJyVCN9TWXjNxGc+znzSZ6rWm2QxWCintmzkAtkGCu7zZcabFs69xmD Y3TWqr+Ew6L65+GZ75rR9ngfjQYPIcY9bXszX/o8F0uq3XqMNgO6uZDgD6zGdM7u1s28 G1sUfb7N/Qb4e9K8zMv+oTbSg9g696Y6XyVvUNfAHqWnccFFLFm+YsxRpT4JVDWiNmro zwFqnTg0vVxKX8a/eIHDoWCy4y7NjloAjvY2udZ6FLzD8aTa9bvuoneSJg04WRwadEUD bZbYU5kltZpmxfQ0AxMi0Dc9QUopNhIJlc+dPJe9+gPXUzQNjCCP8HXKzWwiM2UaAHdp p9cw==
X-Received: by 10.112.132.34 with SMTP id or2mr70246850lbb.75.1415209604319; Wed, 05 Nov 2014 09:46:44 -0800 (PST)
Received: from [127.0.0.1] ([2a01:4f8:a0:638e::2]) by mx.google.com with ESMTPSA id ba19sm1554676lab.31.2014.11.05.09.46.42 for <multiple recipients> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 05 Nov 2014 09:46:43 -0800 (PST)
Message-ID: <545A6281.4050601@gmail.com>
Date: Wed, 05 Nov 2014 18:46:41 +0100
From: Daniel-Constantin Mierla <miconda@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:33.0) Gecko/20100101 Thunderbird/33.0
MIME-Version: 1.0
To: Victor Pascual Avila <victor.pascual.avila@gmail.com>, tim panton <tim@phonefromhere.com>
References: <98200BCB-ABC9-4BE0-B11D-B7AEC9F8B2A4@ieca.com> <7594FB04B1934943A5C02806D1A2204B1D4E50D8@ESESSMB209.ericsson.se> <E78E8017-A08F-4061-B2BA-FB3900B1C681@phonefromhere.com> <CAGTXFp-9AtQakpLt+O_eNRNr71uyh26igLb-_56LDUTQ+g5iJg@mail.gmail.com>
In-Reply-To: <CAGTXFp-9AtQakpLt+O_eNRNr71uyh26igLb-_56LDUTQ+g5iJg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/596ST0kSsDUeLLcFAqvxod1f16c
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
Reply-To: miconda@gmail.com
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 17:46:48 -0000

On 05/11/14 18:16, Victor Pascual Avila wrote:
> On Tue, Nov 4, 2014 at 6:01 PM, tim panton <tim@phonefromhere.com> wrote:
>> 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
> I'd be OK with that
I don't see any reason to split on JavaScript API implementations and
the rest.

Moreover, looking back, the web browsers (and the web ecosystem itself)
got to this level mainly due to open source implementations, via
khtml/webkit and gecko/firefox (then servers and other tools), which at
some point were small and not benefiting of any substantial resources.
If any of "must implement" requirements adds limits (financial or not)
to the usage in any kind of major open source licensing models, it is
going to block a lot of innovation and disruption in the field.

Better the freedom to negotiate anything and fail to find some common
grounds in a session than building a walled garden for 'the chosen ones'
-- hopefully the aim is not to build a new pstn-like ecosystem.

Daniel

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

v2.23.0 | Report a Bug | By Email