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

Bjoern Hoehrmann <derhoermi@gmx.net> Wed, 30 October 2013 17:30 UTC

Return-Path: <derhoermi@gmx.net>
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 32E7711E81F0 for <rtcweb@ietfa.amsl.com>; Wed, 30 Oct 2013 10:30:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.726
X-Spam-Level:
X-Spam-Status: No, score=-2.726 tagged_above=-999 required=5 tests=[AWL=-0.127, 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 Zy7KllokbAO0 for <rtcweb@ietfa.amsl.com>; Wed, 30 Oct 2013 10:30:43 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by ietfa.amsl.com (Postfix) with ESMTP id A501F21E814E for <rtcweb@ietf.org>; Wed, 30 Oct 2013 10:30:17 -0700 (PDT)
Received: from netb.Speedport_W_700V ([91.35.15.221]) by mail.gmx.com (mrgmx103) with ESMTPA (Nemesis) id 0M0QLp-1VwHRT3gTt-00ubDA for <rtcweb@ietf.org>; Wed, 30 Oct 2013 18:30:15 +0100
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Matthew Kaufman <matthew@matthew.at>
Date: Wed, 30 Oct 2013 18:30:16 +0100
Message-ID: <qbf279hoicb5sghcdngoeskhhe5jvnggpp@hive.bjoern.hoehrmann.de>
References: <52681A96.2020904@alvestrand.no> <52713962.3010201@matthew.at>
In-Reply-To: <52713962.3010201@matthew.at>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:GPem7uCj6NHgx6i6rHMLIycdSvkAYp1dI30rYFLKhRmVbITLmjR e6N5qLAh1FNkFzOn+CIDfTK5Wy9TgjKOqoouhIgXXufwMlt0SH8p08Z8T82gG82BY2ubAXN j5Ub9dTKtYVal+2emBiOouRe2omoNHpUc7qXKU8uh2LzylGoJfI7z5rjk0PSX0M4M1HNzFg 1hpW2PnBZVjqcbOjBHFfQ==
Cc: rtcweb@ietf.org
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: Wed, 30 Oct 2013 17:31:16 -0000

* Matthew Kaufman wrote:
>On 10/23/2013 11:51 AM, Harald Alvestrand wrote:
>> The dominant video codec, H.264, is a royalty-required codec.
>>
>> Do we switch now, or do we give up and live with royalties forever?
>
>This is a little dramatic. One can trivially prove that every technology 
>required to implement H.264 will lose the protection of the patent 
>system in a finite period of time. Much, much sooner than "forever".

The patent systems that are enforced on this planet can trivially be
modified and term extensions are not exactly unheard of. And it seems
pretty clear to me that if we as a society switched from royality co-
decs to free ones then we would be pretty unlikely to switch back to
royality codecs in the forseeable future; if we stick with them we're
likely to pay royalities for whatever non-free codec becomes popular
next, and that process may well continue indefinitely. In this sense,
you would rather have to show that we would make "the switch" later.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/