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 19:56 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 7494E1A6FDE for <rtcweb@ietfa.amsl.com>; Wed, 5 Nov 2014 11:56:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 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, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
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 8qjFawxBSBb4 for <rtcweb@ietfa.amsl.com>; Wed, 5 Nov 2014 11:56:58 -0800 (PST)
Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4D621A6F1E for <rtcweb@ietf.org>; Wed, 5 Nov 2014 11:56:57 -0800 (PST)
Received: by mail-lb0-f180.google.com with SMTP id u10so1283534lbd.25 for <rtcweb@ietf.org>; Wed, 05 Nov 2014 11:56:55 -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=hkv+3i0magQ4t9qcfQE2JvfFzZnd0ZWG76es3chmcg4=; b=ztr+XXBpW7m/0njtLNENIp/RqKKUxGTA3Dky+l6MqdnuIeGAkcNqnV+tn0ezcty7xe efbzZwUqaSbKK8edvp2HLUHVFcZ8HRLT0YzqjGpNU+gGdO5oUENLWWE3eQTrgUNbfYIv NE/GKpS1rAqL7K3DvXB7qXAoKGlHP4Gd/K9c626dduwCunddM314VJzvbKjUain3MV7h IhzPIzwk7J2sB/DXl4DuVgRiNrr/8AqhDGjgxzTyV0Pr9UXNBP8dzypYoUwnVWuCLcDn UC8+cR/XiWY4OGN3OZ4uHULOx0w0IwE76FQOFOL2Dw1lnXadMBWSCat8ZhAYgsu3q/j4 3PfA==
X-Received: by 10.152.170.131 with SMTP id am3mr69778000lac.15.1415217415892; Wed, 05 Nov 2014 11:56:55 -0800 (PST)
Received: from [127.0.0.1] ([2a01:4f8:a0:638e::2]) by mx.google.com with ESMTPSA id ja9sm1664446lbc.30.2014.11.05.11.56.53 for <multiple recipients> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 05 Nov 2014 11:56:55 -0800 (PST)
Message-ID: <545A8103.70009@gmail.com>
Date: Wed, 05 Nov 2014 20:56:51 +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: Iñaki Baz Castillo <ibc@aliax.net>
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> <545A6281.4050601@gmail.com> <CALiegf=tjeeTqvHeF+s7qid5H7BdU-AyeU3=b8Xgu73vwzDBhA@mail.gmail.com>
In-Reply-To: <CALiegf=tjeeTqvHeF+s7qid5H7BdU-AyeU3=b8Xgu73vwzDBhA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/OL5LdspFViVUX4G4zQboOv20YB8
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 19:56:59 -0000

On 05/11/14 19:38, Iñaki Baz Castillo wrote:
> 2014-11-05 18:46 GMT+01:00 Daniel-Constantin Mierla <miconda@gmail.com>:
>> 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.
>
> Very good point.
>
> Chrome exists thanks to an open source project. It wouldn't be fair
> that now Chrome gets something that other users of the same source
> project are not allowed to use due to the licensing business model of
> the "Industry" (Industry = those that do not really contribute to
> *Web*RTC, but just expect WebRTC satisfies some requirements for their
> legacy business).
>
> Of course, if VP8 or H264 or both become a MTI codec for WebRTC
> browsers, then any future effort to introduce a new open and 100%
> rollalty-free video codec will be unfeasible.
>
> Said that, then what? no MTI codec at all?
Yes, better no MTI for video than a MTI allowing only some 'particular'
players.

If the "Industry" wants to make MTI a codec they control, then they have
to make it completely free to everyone. Most of the web ecosystem
(browsers, servers, languages, etc ...) was made free by others and they
don't have to pay to benefit of it, then, whatever is not free, it is
not enforced to anyone in order to be 'on web'.

Daniel

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

v2.23.0 | Report a Bug | By Email