Re: [rtcweb] Google VP8 Patent Grant for third parties [Was Re:Proposal for H.263 baseline codec]

Randell Jesup <randell-ietf@jesup.org> Tue, 10 April 2012 19:32 UTC

Return-Path: <randell-ietf@jesup.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 A804911E810A for <rtcweb@ietfa.amsl.com>; Tue, 10 Apr 2012 12:32:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.974
X-Spam-Level:
X-Spam-Status: No, score=-1.974 tagged_above=-999 required=5 tests=[AWL=0.625, 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 JC8Q9QxX3mgJ for <rtcweb@ietfa.amsl.com>; Tue, 10 Apr 2012 12:32:44 -0700 (PDT)
Received: from r2-chicago.webserversystems.com (r2-chicago.webserversystems.com [173.236.101.58]) by ietfa.amsl.com (Postfix) with ESMTP id 2126311E8100 for <rtcweb@ietf.org>; Tue, 10 Apr 2012 12:32:43 -0700 (PDT)
Received: from pool-108-16-41-249.phlapa.fios.verizon.net ([108.16.41.249] helo=[192.168.1.12]) by r2-chicago.webserversystems.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <randell-ietf@jesup.org>) id 1SHgnz-00084H-4g for rtcweb@ietf.org; Tue, 10 Apr 2012 14:32:43 -0500
Message-ID: <4F8489FA.10102@jesup.org>
Date: Tue, 10 Apr 2012 15:28:58 -0400
From: Randell Jesup <randell-ietf@jesup.org>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120312 Thunderbird/11.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CAMKM2Ly-xnVEciL941uOu1Bgwc-wssZ7HNkQuBhsCcgyqfuk5Q@mail.gmail.com> <CAOHm=4uAcLax=25Lw+YMps=swXdAym=qRXtaGQVAXHaeSpoTCQ@mail.gmail.com>
In-Reply-To: <CAOHm=4uAcLax=25Lw+YMps=swXdAym=qRXtaGQVAXHaeSpoTCQ@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - r2-chicago.webserversystems.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jesup.org
X-Source:
X-Source-Args:
X-Source-Dir:
Subject: Re: [rtcweb] Google VP8 Patent Grant for third parties [Was Re: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: Tue, 10 Apr 2012 19:32:44 -0000

On 4/10/2012 2:50 PM, Dean Willis wrote:
>
> On Tue, Apr 3, 2012 at 12:54 PM, Serge Lachapelle <sergel@google.com 
> <mailto:sergel@google.com>> wrote:
>
>
>     Google confirms that the VP8 patent grant applies to both
>     third-party hardware and software implementations of VP8.
>     *
>     *
>
>
> That's very nice of Google, but I'm personally not worried about 
> Google filing suit against me (as a small developer) if I implement 
> using VP8.
>
> What I'm worried about is either a troll who has acquired a patent 
> through the usual fire-sale process, or a Big Old Research Lab that 
> has a gazillion patents but no revenue and decides to start monetizing 
> patents its management team had forgotten existed. Both sorts of 
> entities are very active in today's world of patent fights. And there 
> are patents on design patterns going way back; we're approaching a 
> world of "solid invention" where every alternative design for anything 
> we know how to do has already been described in a patent filing.
>
> So if you really want me to be comfortable with implementing using 
> VP8, buy me an insurance policy that will indemnify me (and any other 
> developer) for any costs related to defending against any future 
> infringement claims on VP8. Perhaps I'd even settle for a free 
> software stack that includes such indemnification in its license. This 
> wouldn't help the hardware implementer, much, however.

Such is the world of patents (especially software/algorithmic patents).  
Stick to stuff that's ~25-30 years old and you're probably ok (though 
someone may ding you for combining old thing A with old thing B).  
Original MPEG-1 for video is probably ok, just don't add anything to it 
or extend it or use it  in a way not originally envisioned (like over 
the internet).

Or live with non-0 risk of patent trolls.

-- 
Randell Jesup
randell-ietf@jesup.org