[rtcweb] H.264 patent licensing options (was: Re: confirming sense of the room: mti codec)

Florian Weimer <fw@deneb.enyo.de> Wed, 10 December 2014 21:46 UTC

Return-Path: <fw@deneb.enyo.de>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0BBF1A8973 for <rtcweb@ietfa.amsl.com>; Wed, 10 Dec 2014 13:46:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.14
X-Spam-Level: *
X-Spam-Status: No, score=1.14 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_DE=0.35, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V_ckU4JYgsLh for <rtcweb@ietfa.amsl.com>; Wed, 10 Dec 2014 13:46:39 -0800 (PST)
Received: from albireo.enyo.de (albireo.enyo.de [46.237.207.196]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E804A1A8A95 for <rtcweb@ietf.org>; Wed, 10 Dec 2014 13:46:35 -0800 (PST)
Received: from [172.17.203.2] (helo=deneb.enyo.de) by albireo.enyo.de with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) id 1Xyp5Z-0004jr-HE; Wed, 10 Dec 2014 22:46:29 +0100
Received: from fw by deneb.enyo.de with local (Exim 4.80) (envelope-from <fw@deneb.enyo.de>) id 1Xyp5Z-0002UL-7t; Wed, 10 Dec 2014 22:46:29 +0100
From: Florian Weimer <fw@deneb.enyo.de>
To: Andrew Allen <aallen@blackberry.com>
References: <E3FA0C72-48C5-465E-AE15-EB19D8D563A7@ieca.com> <54820E74.90201@mozilla.com> <54861AD6.8090603@reavy.org> <BBF5DDFE515C3946BC18D733B20DAD233998AC05@XMB122CNC.rim.net> <63BC3D6D-03A1-41C2-B92D-C8DD57DC51DB@nostrum.com> <BBF5DDFE515C3946BC18D733B20DAD233998ADF1@XMB122CNC.rim.net>
Date: Wed, 10 Dec 2014 22:46:29 +0100
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD233998ADF1@XMB122CNC.rim.net> (Andrew Allen's message of "Tue, 9 Dec 2014 00:45:03 +0000")
Message-ID: <87d27r9o0a.fsf_-_@mid.deneb.enyo.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/VhU8y3rR2uLiAo3SlyRFzqEwMiM
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: [rtcweb] H.264 patent licensing options (was: Re: confirming sense of the room: mti codec)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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, 10 Dec 2014 21:46:41 -0000

* Andrew Allen:

> Our preference is for H.264 to be the single MTI. We believe that
> Cisco's open source royalty free code offer goes a long long way to
> address the concerns of many related to IPR on H.264

Cisco is required to say this about the patent license they allegedly
confer:

“THIS PRODUCT IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR
THE PERSONAL USE OF A CONSUMER OR OTHER USES IN WHICH IT DOES NOT
RECEIVE REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH THE AVC
STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVC VIDEO THAT WAS ENCODED
BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM
A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO.  NO LICENSE IS GRANTED
OR SHALL BE IMPLIED FOR ANY OTHER USE.  ADDITIONAL INFORMATION MAY BE
OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://WWW.MPEGLA.COM”

This rules out commercial use.  Doesn't this fail the “reasonable”
part of RAND because it is expected that commercial end users obtain a
separate patent license of their own (which is not part of a product
that can be purchased)?  If this is still considered “reasonable”, is
the fact relevant that all published MPEG-LA material about H.264
refers to patent licensing in a broadcasting context (either the
production side, or the receiver side)?  This strongly suggests to me
that they may lack the rights to license H.264 for use in video
conferencing applications.

Furthermore, a service using WebRTC is not a “consumer”, so this
patent license does not extend to the service provider.