Re: [rtcweb] Proposal for H.263 baseline codec

"Kevin P. Fleming" <kpfleming@digium.com> Fri, 20 April 2012 20:25 UTC

Return-Path: <kpfleming@digium.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 7EC1321F855B for <rtcweb@ietfa.amsl.com>; Fri, 20 Apr 2012 13:25:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 a6O5Do-V5kR3 for <rtcweb@ietfa.amsl.com>; Fri, 20 Apr 2012 13:24:59 -0700 (PDT)
Received: from mail.digium.com (mail.digium.com [216.207.245.2]) by ietfa.amsl.com (Postfix) with ESMTP id C38FF21F8549 for <rtcweb@ietf.org>; Fri, 20 Apr 2012 13:24:58 -0700 (PDT)
Received: from [10.24.55.203] (helo=zimbra.hsv.digium.com) by mail.digium.com with esmtp (Exim 4.69) (envelope-from <kpfleming@digium.com>) id 1SLKO1-0008Iw-Pn for rtcweb@ietf.org; Fri, 20 Apr 2012 15:24:57 -0500
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.hsv.digium.com (Postfix) with ESMTP id C34911A2006 for <rtcweb@ietf.org>; Fri, 20 Apr 2012 15:24:57 -0500 (CDT)
Received: from zimbra.hsv.digium.com ([127.0.0.1]) by localhost (zimbra.hsv.digium.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MMXCcauUlTqK for <rtcweb@ietf.org>; Fri, 20 Apr 2012 15:24:57 -0500 (CDT)
Received: from [10.24.250.46] (unknown [10.24.250.46]) by zimbra.hsv.digium.com (Postfix) with ESMTPSA id 56E181A2001 for <rtcweb@ietf.org>; Fri, 20 Apr 2012 15:24:57 -0500 (CDT)
Message-ID: <4F91C613.4050701@digium.com>
Date: Fri, 20 Apr 2012 15:24:51 -0500
From: "Kevin P. Fleming" <kpfleming@digium.com>
Organization: Digium, Inc.
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120410 Thunderbird/11.0.1
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CB9A41D4.853AB%stewe@stewe.org>
In-Reply-To: <CB9A41D4.853AB%stewe@stewe.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] Proposal for H.263 baseline codec
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: Fri, 20 Apr 2012 20:25:00 -0000

On 03/29/2012 09:53 AM, Stephan Wenger wrote:

> The other issue, though (the fact that the license grant extends only to
> the VP8 implementation as provided by google, and does not extent to
> derivative works such as hardware implementations) should be moderately
> alarming even for an open source person.  With respect to this clause, I
<snip>

This is concerning, even for us open source software distributors. In 
fact, a similar situation existed some time ago with iLBC; the license 
that GIPS offered covered only the code as distributed as part of the 
RFC (although the language stating this was quite poorly constructed), 
and that code had (and still has) fundamental issues (it has at least 
two places where it invokes 'undefined behavior' according to the C 
standard). When we fixed these problems in our distribution, and then I 
re-read the license, I realized that the license did not allow us to 
distribute this modified version. We later managed to get explicit 
permission from Google to distribute a modified version, as they have 
changed the license to no longer have this restriction.

The WebM patent license has much of the same problem, though: it only 
applies to distributions of the code made by Google, without changes (no 
derivative works). At least, this is my reading of it, being an engineer 
married to a lawyer who handles such things, but not a lawyer myself :-)

-- 
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
Jabber: kfleming@digium.com | SIP: kpfleming@digium.com | Skype: kpfleming
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at www.digium.com & www.asterisk.org