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

Dean Willis <dean.willis@softarmor.com> Thu, 12 April 2012 06:50 UTC

Return-Path: <dean.willis@softarmor.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 9FEF421F84D6 for <rtcweb@ietfa.amsl.com>; Wed, 11 Apr 2012 23:50:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.502
X-Spam-Level:
X-Spam-Status: No, score=-101.502 tagged_above=-999 required=5 tests=[AWL=-0.940, BAYES_40=-0.185, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, 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 dvA3jT0oCJmz for <rtcweb@ietfa.amsl.com>; Wed, 11 Apr 2012 23:50:22 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4B96C21F84DF for <rtcweb@ietf.org>; Wed, 11 Apr 2012 23:50:22 -0700 (PDT)
Received: by obbtb4 with SMTP id tb4so2658245obb.31 for <rtcweb@ietf.org>; Wed, 11 Apr 2012 23:50:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=softarmor.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=JiMX7YeDMgeiLrtoHHmrYYe0XzoQTPJjyCVm/sMKf04=; b=VmHprXyALq5r5xv3LhHk3p2ABbFcC386gIurR0/IP++68uO16Zr9yKaNG6ovgc4viV zV1SpEK4D/X0rexXrAFFLjbvIiKB8rDV0qczCdW2tTtNf3Ej5YimasOKrAswG6LmsP4W 0RZRUtAdHWtg6J99DZOwy7FEMM8VTC8ZiHvR0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=JiMX7YeDMgeiLrtoHHmrYYe0XzoQTPJjyCVm/sMKf04=; b=UzT4emk4htMd4LdwxXOSGDiQojPcEOwR2g/7sol1tSSmRHF6nOFVxhy6EV0jHtvnkG 9FpSkQ1CFp7Rnx60e+skdvRKm76TOfXym/i9rs9WTcItZ1aJFdcW69CzwGPYGJP+prdI AxS4mCpQnh8mUtr9fjGiIQoyrQwN6rt58oUW2Y8io160GSusZv2fx2drcCX3gM04sfRl yy7+5ftiGTNrcBllRbuyU3IB55grNgmpUMOKbtMcvZdnwMD7rvACGU14qMWj9I4knQcv LkrNh6rGi/wXIwHaGleQi2jU3GurnQMMhEp96JRJlmvoslsMaLTtRahD+2JqSRzso4fY FmUA==
MIME-Version: 1.0
Received: by 10.60.4.170 with SMTP id l10mr1433557oel.67.1334213421002; Wed, 11 Apr 2012 23:50:21 -0700 (PDT)
Received: by 10.60.33.199 with HTTP; Wed, 11 Apr 2012 23:50:20 -0700 (PDT)
In-Reply-To: <007b01cd12f7$fbcd72e0$f36858a0$@packetizer.com>
References: <CAMKM2Ly-xnVEciL941uOu1Bgwc-wssZ7HNkQuBhsCcgyqfuk5Q@mail.gmail.com> <03ac01cd120d$0ffe95f0$2ffbc1d0$@packetizer.com> <4F7BCD1A.7020508@librevideo.org> <03e301cd1223$153e6b60$3fbb4220$@packetizer.com> <4F7C4FB4.4070703@librevideo.org> <007b01cd12f7$fbcd72e0$f36858a0$@packetizer.com>
Date: Thu, 12 Apr 2012 01:50:20 -0500
Message-ID: <CAOHm=4tqcwmU9OJNYv4-x4GO6z4AYijd3LFcQq=q1_210FhyJg@mail.gmail.com>
From: Dean Willis <dean.willis@softarmor.com>
To: "Paul E. Jones" <paulej@packetizer.com>
Content-Type: multipart/alternative; boundary=e89a8fb1f86203701204bd75c557
X-Gm-Message-State: ALoCoQkN8MTxQd4tcRuhpfDDfWlEeYx2crXtsjyZ9OQZnjkdauKjz7QtjN9Vgc7k1zxJSAwvYQdS
Cc: rtcweb@ietf.org
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: Thu, 12 Apr 2012 06:50:23 -0000

On Thu, Apr 5, 2012 at 1:47 AM, Paul E. Jones <p
>
> While there may be undisclosed IPR on H.264, I find it hard to believe that
> there would be much, if any, at this point.  Keep in mind that H.264 is
> product of the joint effort of a bunch of people who are experts in the
> field.  I would be suspicious of any company not involved in the
> development
> of H.264 claiming to have IPR, because somebody in the joint committee
> probably owns that IPR.  Sure, there might be something ... something very
> minor.  Perhaps.
>
>
Both H.264 and  VP8 are motion-vector codings, right?

A quick search on Google Patents shows about 32,400 existing motion vector
video patents. What do you want to bet some of those apply  to one or the
other? Or both? Or both plus H.263?

Just because they haven't been asserted yet doesn't mean they're not real.
It might mean that the people that own them aren't paying attention. Or
weren't, but have started. Or don't care, but might be willing to sell
their patent to someone who does.

The simple fact is that there are a crapload of patents out there, and
creative reading can get a patent owner fired up enough to start trying to
collect revenue on even a very bad patent -- and with hundreds of thousands
of patents in the area, some of them are likely to be very good. And in
certain venues (the Eastern District of Texas comes to mind), there's a
strong presumption that patents are valid and the courts are known to grant
damages even though a reexamination is pending. And even if the patent is
bogus and you win, you've still spent a lot of money. I'd guess your firm
spends more than my yearly revenue on defending even the lamest individual
suit.

So what I'm saying is that it doesn't matter whether you use H.264 or VP8;
you're eventually going to get sued by somebody, and it's going to be
expensive and annoying. Build in a revenue margin to plan for it. But there
is an argument to make that if you use H.264, you know that somebody with
an M in their name is going to be involved SOON unless you fork out cash in
advance, whereas if you use VP8, you can hope to maybe wait longer for the
surprise and can save your money until then.

That said, they both still make me nervous. Can't we just use tin cans and
string? ;-)

--
Dean