Re: [rtcweb] VP8 vs H.264 - the core issue

cowwoc <cowwoc@bbs.darktech.org> Thu, 24 October 2013 20:47 UTC

Return-Path: <cowwoc@bbs.darktech.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 4B76911E8387 for <rtcweb@ietfa.amsl.com>; Thu, 24 Oct 2013 13:47:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.291
X-Spam-Level:
X-Spam-Status: No, score=-6.291 tagged_above=-999 required=5 tests=[AWL=-2.692, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 9LA0SpvsT6EO for <rtcweb@ietfa.amsl.com>; Thu, 24 Oct 2013 13:47:47 -0700 (PDT)
Received: from mail-qe0-f44.google.com (mail-qe0-f44.google.com [209.85.128.44]) by ietfa.amsl.com (Postfix) with ESMTP id 34B3A11E8392 for <rtcweb@ietf.org>; Thu, 24 Oct 2013 13:47:33 -0700 (PDT)
Received: by mail-qe0-f44.google.com with SMTP id 6so1828486qeb.3 for <rtcweb@ietf.org>; Thu, 24 Oct 2013 13:47:32 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Ir1yPg/YXaDhO8kVIJoJ2HaEgKLivYHmIBqmuX/2v1I=; b=Z+S7nH7mklQBXBkkn1mTC1hUZCJg5Gn+f5b4N9LvOoIBETCXhx2xwPgZRmdFpBoXZC GHP6bxlFMS9NRkbFGylMjbrzUC7RHhORwhgt2yZoZK4I/nfVa956ETNv2BuiDZ2cWP+u ptTdOFXmtx6LQW37XrdFI+ZMM5L2NLO/yQjBm/mgX66nVcbUSxshMgeFydjqMvvysAhz 7OLIoFo1PI+QRvDBs2jb5XTwX11FjgUUUe4Q8nUToeuQhnfek+fKg02CYUW3IIidcS4K vMgn9zwhLu5jh/tTomux/SDrC6DK0crpsSLtHl5xysJYnnTyvndi656amYXWrFfU8xhf eVRA==
X-Gm-Message-State: ALoCoQmLoZkrxH/+mGOJuIMIx/mVx/m0hw0dDJeu4rH/Mad1ypqVOfZqcU5EsII3u/wGzXBmqB7X
X-Received: by 10.229.109.193 with SMTP id k1mr6214544qcp.9.1382647652596; Thu, 24 Oct 2013 13:47:32 -0700 (PDT)
Received: from [192.168.1.100] (206-248-171-209.dsl.teksavvy.com. [206.248.171.209]) by mx.google.com with ESMTPSA id fx6sm6295618qeb.1.2013.10.24.13.47.31 for <rtcweb@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Oct 2013 13:47:31 -0700 (PDT)
Message-ID: <52698758.5040404@bbs.darktech.org>
Date: Thu, 24 Oct 2013 16:47:20 -0400
From: cowwoc <cowwoc@bbs.darktech.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <52681A96.2020904@alvestrand.no> <526826AF.5030308@librevideo.org> <52690090.2050609@alvestrand.no> <BBE9739C2C302046BD34B42713A1E2A22DFCD683@ESESSMB105.ericsson.se> <AE1A6B5FD507DC4FB3C5166F3A05A4843D45DC08@TK5EX14MBXC266.redmond.corp.microsoft.com> <5269764C.4030801@librevideo.org>
In-Reply-To: <5269764C.4030801@librevideo.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Subject: Re: [rtcweb] VP8 vs H.264 - the core issue
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, 24 Oct 2013 20:47:53 -0000

On 24/10/2013 3:34 PM, Basil Mohamed Gohar wrote:
> On 10/24/2013 12:02 PM, Matthew Kaufman (SKYPE) wrote:
>> On the IPR issue, Google reached agreement with 11 patent holders. There
>> are at least 31 companies in the MPEG-LA H.264 pool. There is
>> considerable technical overlap between VP8 and H.264.
>>
>> My employer is one of those in the H.264 pool, and wasn’t one of the 11
>> companies Google reached an agreement with.
>>
>> Draw your own conclusions and take your own IPR risks.
>>
>> Personally I’d rather the IPR devil I know vs. the IPR devil I don’t know.
>>
>> Google could fix this for most potential users (through indemnification,
>> similar to what Oracle offers its Linux licensees) but has chosen not
>> to. You can draw your own conclusion there, too.
>>
>> Matthew Kaufman
> There are no conclusions to draw due to lack of sufficient evidence for
> anything actionable.  IPR FUD has delayed the adoption of many free,
> non-royalty-bearing formats for too long.  And, again, the IPR "devil we
> know" is meaningless, because there are still IP litigation threats even
> for H.264, MP3, and many other patented, royalty-bearing formats.
>
> So, it contributes little to nothing to the discussion on IPR grounds if
> a substantial declaration, as Ted has advised, is not taken, and such
> claims should really be discounted in any serious consideration when
> weighing options between formats.

     I would like to point out that we still have the option of 
mandating the use of an older codec whose IPR has expired (and let 
clients upgrade to VP8 or H264 as they fit).

     But if the community rejects this approach, then I agree that this 
should not hold back the use of VP8.

Gili