Re: [rtcweb] Cisco to open source its H.264 implementation and absorb MPEG-LA licensing fees

Ron <ron@debian.org> Thu, 12 December 2013 23:11 UTC

Return-Path: <ron@debian.org>
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 BC0DC1AE52E for <rtcweb@ietfa.amsl.com>; Thu, 12 Dec 2013 15:11:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 3LXfVC3RSWQg for <rtcweb@ietfa.amsl.com>; Thu, 12 Dec 2013 15:11:11 -0800 (PST)
Received: from ipmail05.adl6.internode.on.net (ipmail05.adl6.internode.on.net [150.101.137.143]) by ietfa.amsl.com (Postfix) with ESMTP id 9D7F01AE52C for <rtcweb@ietf.org>; Thu, 12 Dec 2013 15:11:10 -0800 (PST)
Received: from ppp14-2-56-86.lns21.adl2.internode.on.net (HELO audi.shelbyville.oz) ([14.2.56.86]) by ipmail05.adl6.internode.on.net with ESMTP; 13 Dec 2013 09:41:03 +1030
Received: from localhost (localhost [127.0.0.1]) by audi.shelbyville.oz (Postfix) with ESMTP id 453604F8F3 for <rtcweb@ietf.org>; Fri, 13 Dec 2013 09:41:02 +1030 (CST)
X-Virus-Scanned: Debian amavisd-new at audi.shelbyville.oz
Received: from audi.shelbyville.oz ([127.0.0.1]) by localhost (audi.shelbyville.oz [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 2jVzQDEGHZoC for <rtcweb@ietf.org>; Fri, 13 Dec 2013 09:41:01 +1030 (CST)
Received: by audi.shelbyville.oz (Postfix, from userid 1000) id 8FCCA4F902; Fri, 13 Dec 2013 09:41:01 +1030 (CST)
Date: Fri, 13 Dec 2013 09:41:01 +1030
From: Ron <ron@debian.org>
To: rtcweb@ietf.org
Message-ID: <20131212231101.GS3245@audi.shelbyville.oz>
References: <A672E2AB-827D-46E8-9EB1-D7ED82B10B94@cisco.com> <20131211193239.GK3245@audi.shelbyville.oz> <558F8D49-4024-4DF1-9A9E-AF422F1292C2@iii.ca> <20131212011550.GM3245@audi.shelbyville.oz> <E8882BCE-4795-4CF5-B785-18C2141A5DE2@iii.ca> <CAD5OKxvy8xGuiR7oUbJJwTaxGfPJ=MHpd8Hp5MfpPLy8LmNaQg@mail.gmail.com> <D5A2C5EC-C65F-4E39-9A56-315B94C5FB1D@iii.ca> <CAD5OKxs-OoqwbQgBy7K4wQRffCk0=8Qmo_xJQdSwhBL2F85v1g@mail.gmail.com> <20131212214310.GR3245@audi.shelbyville.oz> <CECFA3EA.AC30E%stewe@stewe.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CECFA3EA.AC30E%stewe@stewe.org>
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: Re: [rtcweb] Cisco to open source its H.264 implementation and absorb MPEG-LA licensing fees
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: Thu, 12 Dec 2013 23:11:13 -0000

On Thu, Dec 12, 2013 at 10:34:15PM +0000, Stephan Wenger wrote:
> On 12.12.2013, 16:43 , "Ron" <ron@debian.org> wrote:
> >We so far can't even get the organisations who have active contributors
> >in this WG and which hold H.264 patents to comply with their obligations
> >for disclosure under the IETF requirements.[1]
> 
> According to my reading of the IETF IPR policy documents there is no such
> obligation.

Which part of:

   IPR disclosures under Sections 6.1.1. and 6.1.2 are required with
   respect to IPR that is owned directly or indirectly, by the
   individual or his/her employer or sponsor (if any) or that such
   persons otherwise have the right to license or assert.

would you say indicates there is no such obligation?


I won't discount that there may be some slippery reading of the requirements
which people acting in bad faith may be able to ooze between, but if that
were actually the case, then that would be a compelling reason to completely
exclude this technology from consideration at all.

Where is the wide open door that permits them not to disclose which I am
missing here?  It's not like anyone could plausibly be unaware of which
companies are major holders of IPR relevant to H.264, and I'm pretty certain
there are messages posted to this list where people directly confirm their
company is one.

Large amounts of it were declared (with whatever questionable merit) as
applying to VP8.  Are you saying the people who declared that are unaware
that H.264 is also being proposed for use here?

  Ron