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

Lorenzo Miniero <lorenzo@meetecho.com> Thu, 14 March 2013 17:56 UTC

Return-Path: <lorenzo@meetecho.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 2869111E813F for <rtcweb@ietfa.amsl.com>; Thu, 14 Mar 2013 10:56:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.719
X-Spam-Level:
X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
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 hwtTJby+QNSM for <rtcweb@ietfa.amsl.com>; Thu, 14 Mar 2013 10:56:09 -0700 (PDT)
Received: from smtpdg10.aruba.it (smtpdg4.aruba.it [62.149.158.234]) by ietfa.amsl.com (Postfix) with ESMTP id C548021F8952 for <rtcweb@ietf.org>; Thu, 14 Mar 2013 10:56:08 -0700 (PDT)
Received: from lminiero-acer ([130.129.20.132]) by smtpcmd04.ad.aruba.it with bizsmtp id BVw21l01f2qyxt601Vw3VQ; Thu, 14 Mar 2013 18:56:06 +0100
Date: Thu, 14 Mar 2013 18:55:51 +0100
From: Lorenzo Miniero <lorenzo@meetecho.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>
Message-ID: <20130314185551.58f0bc1a@lminiero-acer>
In-Reply-To: <34944444-4FEB-4AD0-A90D-1EE8C56C0253@acmepacket.com>
References: <CA+23+fE3WRs5SxAUcsjWbxcjzQKxCtW7sdfHtAsbd7MbPyHAtQ@mail.gmail.com> <CAEWS6TJPKXdf7i140wKMZFHBcSVBtCxwzViWYYFgL01D=LdmEg@mail.gmail.com> <F0FCD7D0-969E-46D9-9681-3A64D36F59DF@apple.com> <51420679.2060909@librevideo.org> <34944444-4FEB-4AD0-A90D-1EE8C56C0253@acmepacket.com>
Organization: Meetecho
X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.0; i386-redhat-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
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:56:10 -0000

Il giorno Thu, 14 Mar 2013 17:39:03 +0000
Hadriel Kaplan <HKaplan@acmepacket.com> ha scritto:

> 
> On Mar 14, 2013, at 1:18 PM, Basil Mohamed Gohar
> <basilgohar@librevideo.org> wrote:
> 
> > 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/
> 
> Interesting - I hadn't realized their license was as viral to
> 'derivative' works as GPLv3.
> 
> So does this mean if a mobile phone vendor had the license for H.264
> in their hardware encoder/decoder, and provided an API to
> applications to use that hardware, that any application using the API
> would also be a new end-product and have to acquire the license as
> well?
> 
> Likewise, if a web-based app framework such as PhoneGap/Titanium/etc.
> acquired a license for H.264 and provided an API for using it to
> their customers'(the app creators) code, that their customers (the
> app creators) would also need to get the license?
> 
> -hadriel
> 


This is indeed an interesting read, thanks Basil for sharing this.

Lorenzo

> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb



-- 
Lorenzo Miniero, COB

Meetecho s.r.l.
Web Conferencing and Collaboration Tools
http://www.meetecho.com