Re: [rtcweb] Input to Video Codec Selection

Harald Alvestrand <harald@alvestrand.no> Sun, 03 March 2013 17:20 UTC

Return-Path: <harald@alvestrand.no>
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 42D6E21F84CA for <rtcweb@ietfa.amsl.com>; Sun, 3 Mar 2013 09:20:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.477
X-Spam-Level:
X-Spam-Status: No, score=-110.477 tagged_above=-999 required=5 tests=[AWL=0.122, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 ZfrugCpJR86t for <rtcweb@ietfa.amsl.com>; Sun, 3 Mar 2013 09:20:09 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 6912121F84C8 for <rtcweb@ietf.org>; Sun, 3 Mar 2013 09:20:09 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 1AB0439E172; Sun, 3 Mar 2013 18:20:08 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ig8O5QKJAHSx; Sun, 3 Mar 2013 18:20:06 +0100 (CET)
Received: from [IPv6:2001:470:de0a:27:393a:5892:b68a:9264] (unknown [IPv6:2001:470:de0a:27:393a:5892:b68a:9264]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 7B2E139E170; Sun, 3 Mar 2013 18:20:06 +0100 (CET)
Message-ID: <51338645.9010306@alvestrand.no>
Date: Sun, 03 Mar 2013 18:20:05 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130221 Thunderbird/17.0.3
MIME-Version: 1.0
To: Cullen Jennings <fluffy@iii.ca>
References: <5130B9C3.3010404@ericsson.com> <92D0D52F3A63344CA478CF12DB0648AA26529174@XMB106BCNC.rim.net> <5131CD20.8060201@alvestrand.no> <9D4FB1F0-2A13-4335-9B90-ADB4D6F37AB6@iii.ca>
In-Reply-To: <9D4FB1F0-2A13-4335-9B90-ADB4D6F37AB6@iii.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Input to Video Codec Selection
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: Sun, 03 Mar 2013 17:20:10 -0000

On 03/03/2013 04:38 PM, Cullen Jennings wrote:
> Harald,
>
> The IPR disclosure says RF but the grant at webm pages is not RF. It includes
>
>   If You or your agent or exclusive licensee institute or order or agree to the institution of patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that any implementation of this specification constitutes direct or contributory patent infringement, or inducement of patent infringement, then any rights granted to You under the License for this specification shall terminate as of the date such litigation is filed.
>
> So there seems to be some inconsistency here or perhaps the IPR grand on IETF page was just much broader than the one on webm page. Can you help make sure the IPR disclosure is correct? I also had the idea that IETF preferred if Google actually disclosed patents that google control as wells other that are known on VP8 in the disclosure.

Cullen, in what way is the WEBM page grant not an RF grant (or more 
precisely: "under a royalty-free and otherwise reasonable and 
non-discriminatory license", which is the precise language used in RFC 
3979 section 6.5)?
I can't remember the last time I saw a royalty-free license commitment 
without a defensive suspension clause.

Re patent numbers:

I've heard Scott Bradner claim that a defensive-suspension filing is not 
covered by the "blanket license" rule in section 6.4.3 of RFC 3979, but 
the first time I heard that was at the RTCWEB meeting, and I objected to 
the claim - I was listening most carefully when we wrote RFC 3979 in the 
IPR working group; my belief at the time we filed this statement was 
that since it's a blanket RF license, it did not require listing 
specific patent numbers. (As you know, listing specific patent numbers 
can be a chore requiring a fair amount of human judgment = lawyer and 
engineer time.

I believe the IETF IPR rules were intended to be biased towards making 
life easy for people willing to do RF licenses; I'd certainly not want 
to make life for those people harder.