Re: [rtcweb] x264 vs OpenH264 (Was: On the topic of MTI video codecs)

Daniel-Constantin Mierla <miconda@gmail.com> Fri, 01 November 2013 17:03 UTC

Return-Path: <miconda@gmail.com>
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 186B911E80DE for <rtcweb@ietfa.amsl.com>; Fri, 1 Nov 2013 10:03:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.374
X-Spam-Level:
X-Spam-Status: No, score=-2.374 tagged_above=-999 required=5 tests=[AWL=0.225, 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 FPbtMVi05ZuP for <rtcweb@ietfa.amsl.com>; Fri, 1 Nov 2013 10:03:46 -0700 (PDT)
Received: from mail-ea0-x231.google.com (mail-ea0-x231.google.com [IPv6:2a00:1450:4013:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id E2A4D11E8117 for <rtcweb@ietf.org>; Fri, 1 Nov 2013 10:03:45 -0700 (PDT)
Received: by mail-ea0-f177.google.com with SMTP id f15so2166763eak.22 for <rtcweb@ietf.org>; Fri, 01 Nov 2013 10:03:45 -0700 (PDT)
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:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=q+TCVuSNE/L/JgYqxfVOPdWRhViM3UyLKUpT1WK8RbU=; b=fwXtz7153bfYLlzX61CtZPLkKhu0j4qA2flZ1CRU87LlxpnCt06i/hL71zNEC0/YvL 8u/NC0Qbrv3N46a+wrjN6zG8cVLmrU79OueAS4BZZyKI2DNijnOt92Xyi6leyg6AE9gl TRjgtH31u8TTkxGcK5f91C6YGF+6maASXVLojpsjL68wMQ6ZA7ZgqST2R53Nctnr6sAq Q54Ht1/+fjWYilrW8x/HJrrTfa0OIAhQc/Z9TPMc9XqHI3ZBDVNr51ZiF8pHvsC3Xhmf 10WXD5gpg7ZwoiSU0scHV2RPddL29pGWNQw0IOOrwNijkJoWkNcMNmTndnYq50g7rjVk Sr6Q==
X-Received: by 10.14.241.74 with SMTP id f50mr4283204eer.29.1383325424871; Fri, 01 Nov 2013 10:03:44 -0700 (PDT)
Received: from [127.0.0.1] (ns.asipto.com. [213.133.111.169]) by mx.google.com with ESMTPSA id a6sm9915271eei.10.2013.11.01.10.03.43 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 01 Nov 2013 10:03:44 -0700 (PDT)
Message-ID: <5273DEEE.4000302@gmail.com>
Date: Fri, 01 Nov 2013 18:03:42 +0100
From: Daniel-Constantin Mierla <miconda@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Max Jonas Werner <mail@makk.es>, cowwoc <cowwoc@bbs.darktech.org>, rtcweb@ietf.org
References: <CAPvvaaLwacOgQq5O8t0bMCJJfKTHbJM9RnawgXLJpKiADtsi2Q@mail.gmail.com> <5273D5C8.304@bbs.darktech.org> <5273D848.2060608@makk.es>
In-Reply-To: <5273D848.2060608@makk.es>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] x264 vs OpenH264 (Was: On the topic of MTI video codecs)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 01 Nov 2013 17:03:47 -0000

On 11/1/13 5:35 PM, Max Jonas Werner wrote:
> On 01.11.2013 17:24, cowwoc wrote:
>> On 01/11/2013 12:19 PM, Emil Ivov wrote:
>>> It would be nice for Mozilla to comment then. They wouldn't have been
>>> required to statically link against it or even distribute it. It is
>>> already possible to use GPL plug-ins with Firefox, so why is x264 an
>>> insurmountable problem?
>> Can I dynamically link x264 against my proprietary application without
>> having to GPL it?
> Actually no: https://www.gnu.org/licenses/gpl-faq.html#LinkingWithGPL
>
> That's why the LGPL (that poses other risks, though) exists.
GPL constraints about open sourcing are for the case when distributing 
the application. You can link anything you want with gpl code and you 
don't have to make the sources available if you don't distribute your 
application.

I think that Emil wanted to say that we, users, don't distribute web 
browsers, we just use them.

Then, if I got it right, no browser will link against the h264 plugin. 
That will be loaded at user will (eventually), by downloading on demand 
from cisco site.

So I, as user, I take Firefox from Mozilla site, then when I need to do 
webrtc, my browser will download (first time) and use the h264 plugin. 
Because I don't distribute further the two, I don't see any restriction 
from gpl here. That's my understanding.

Daniel

-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Trainings - Berlin, Nov 25-28
   - more details about Kamailio trainings at http://www.asipto.com -