Re: [rtcweb] A different perspective on the video codec MTI discussion

Basil Mohamed Gohar <basilgohar@librevideo.org> Thu, 14 March 2013 17:18 UTC

Return-Path: <basilgohar@librevideo.org>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E665A21F8EA7 for <rtcweb@ietfa.amsl.com>; Thu, 14 Mar 2013 10:18:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FDY144SjHDSz for <rtcweb@ietfa.amsl.com>; Thu, 14 Mar 2013 10:18:52 -0700 (PDT)
Received: from mail.zaytoon.hidayahonline.net (zaytoon.hidayahonline.net [173.193.202.83]) by ietfa.amsl.com (Postfix) with ESMTP id 91B5811E81B4 for <rtcweb@ietf.org>; Thu, 14 Mar 2013 10:18:52 -0700 (PDT)
Received: from [10.10.40.120] (rrcs-98-103-138-67.central.biz.rr.com [98.103.138.67]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: basilgohar@librevideo.org) by mail.zaytoon.hidayahonline.net (Postfix) with ESMTPSA id 6820D656DE5 for <rtcweb@ietf.org>; Thu, 14 Mar 2013 13:18:51 -0400 (EDT)
Message-ID: <51420679.2060909@librevideo.org>
Date: Thu, 14 Mar 2013 13:18:49 -0400
From: Basil Mohamed Gohar <basilgohar@librevideo.org>
Organization: Libre Video
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130219 Thunderbird/17.0.3
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CA+23+fE3WRs5SxAUcsjWbxcjzQKxCtW7sdfHtAsbd7MbPyHAtQ@mail.gmail.com> <CAEWS6TJPKXdf7i140wKMZFHBcSVBtCxwzViWYYFgL01D=LdmEg@mail.gmail.com> <F0FCD7D0-969E-46D9-9681-3A64D36F59DF@apple.com>
In-Reply-To: <F0FCD7D0-969E-46D9-9681-3A64D36F59DF@apple.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] A different perspective on the video codec MTI discussion
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 14 Mar 2013 17:18:58 -0000

On 03/14/2013 12:44 PM, David Singer wrote:
> By the way, open-source and license fees are not in direct conflict;
> it's the principles that are. To pick a directly-relevant example,
> there are open-source implementations of H.264 (AVC).  
This is skirting the issue by using the vague term "open-source" in a
way that illustrates the discrepancy of the argument.  For this purpose,
it is important to outline the main argument against the usage of H.264
(AVC) in terms of the free software definition, which can be found here:
https://www.gnu.org/philosophy/free-sw.html
>
> A program is free software if the program's users have the four
> essential freedoms:
>
>   * The freedom to run the program, for any purpose (freedom 0).
>   * The freedom to study how the program works, and change it so it
>     does your computing as you wish (freedom 1). Access to the source
>     code is a precondition for this.
>   * The freedom to redistribute copies so you can help your neighbor
>     (freedom 2).
>   * The freedom to distribute copies of your modified versions to
>     others (freedom 3). By doing this you can give the whole community
>     a chance to benefit from your changes. Access to the source code
>     is a precondition for this.
>
*Requiring* a license fee to allow one or more of these points would
directly intervene in that freedom being available without restriction,
and thus, would prevent the implementation from being free software
according to the above definition.  Though I am not as familiar with
OSI's Open Source Definition (http://opensource.org/osd-annotated), a
cursory reading also indicates that a *requirement* of a license fee
would, by necessity, exclude it from fitting the open source definition
as well.

MPEG-LA's licensing structure for H.264 is strange in that it is a
license for /end-users/, meaning, such as the people that finally use a
product (e.g., the web browser him/herself).  So, the producers of the
software may themselves not require a license, but their users would. 
This is the issue by which a *required* licensing fee (which, due to
encumbrance by patents, is legally binding at this time by choice of the
owners of said patents in many jurisdictions) excludes something from
being free, open source software in this situation.

I talked about this with direct answers from the MPEG-LA here:
http://www.librevideo.org/blog/2010/06/14/mpeg-la-answers-some-questions-about-avch-264-licensing/

The point you make above is, apparently, talking from the perspective of
software producers.  Free software advocates always talk from the
perspective of the *users*, which includes software producers that use
other free software.  The blurring of the meaning of the term
open-source to imply only the software developers/producers is why many
prefer the term free software to this date.

The conclusion of this is that, yes, actually, licensing fee and
open-source (and also free) software are in direct conflict, by
definition.  The fact that some software is released under an
open-source license does not mean all users of that software have access
to it under the conditions of that license.

-- 
Libre Video
http://librevideo.org