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

Basil Mohamed Gohar <basilgohar@librevideo.org> Thu, 14 March 2013 19:08 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 3FE6111E81AB for <rtcweb@ietfa.amsl.com>; Thu, 14 Mar 2013 12:08:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.384
X-Spam-Level:
X-Spam-Status: No, score=-2.384 tagged_above=-999 required=5 tests=[AWL=0.215, 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 jOOiGfBtru5c for <rtcweb@ietfa.amsl.com>; Thu, 14 Mar 2013 12:08:25 -0700 (PDT)
Received: from mail.zaytoon.hidayahonline.net (zaytoon.hidayahonline.net [173.193.202.83]) by ietfa.amsl.com (Postfix) with ESMTP id 81D5111E80F2 for <rtcweb@ietf.org>; Thu, 14 Mar 2013 12:08:25 -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 DB054656F5C for <rtcweb@ietf.org>; Thu, 14 Mar 2013 15:08:24 -0400 (EDT)
Message-ID: <51422025.8020108@librevideo.org>
Date: Thu, 14 Mar 2013 15:08:21 -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>" <rtcweb@ietf.org>
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> <514211B6.1010202@librevideo.org> <CAD5OKxsDotRmswmZwdKg1Tc0fBf13x=j1rOo7_YTb4tk03Qm0w@mail.gmail.com>
In-Reply-To: <CAD5OKxsDotRmswmZwdKg1Tc0fBf13x=j1rOo7_YTb4tk03Qm0w@mail.gmail.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 19:08:26 -0000

On 03/14/2013 02:11 PM, Roman Shpount wrote:
> One thing that was not clear for me from your blog was if an
> application running on Windows OS and using OS provided API for H.264
> playback is licensed to do so.
Roman,

I again have to put out there *very clearly* that I am not a lawyer.  I
can only take some clear statements I've been given and/or read and
present them together.  But the license that Microsoft provides their
users as stated in the manual is a private, non-commercial license.  So,
if the usage fits those definitions, it seems to be the case.  The
attorney from MPEG-LA made clear that their licensing is for end-user
products.  That's why someone can write an H.264 decoder or encoder, and
ship it without much problem, but it's the *users* of said
decoder/encoder that would face the licensing question.

Does that make sense?  This is what I mean by the licensing being
somewhat odd.  It's totally not a problem (maybe not *totally*, but I
hope you get the idea) for software producers.  It's *totally* a problem
for the users.

It's a shame that people like me, who do not have any real legal
background, and the ones having to explain this, and people that
actually know better are either not speaking about it or are not being
heard.  The problems posed by H.264 licensing for users, and thus the
free software community, are very severe and confusing.

-- 
Libre Video
http://librevideo.org