[rtcweb] H.264 IPR disclosures (or persistent lack thereof)

Ron <ron@debian.org> Fri, 13 December 2013 02:43 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 40D8F1AE0E7 for <rtcweb@ietfa.amsl.com>; Thu, 12 Dec 2013 18:43:45 -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 1XcDfA469Ou8 for <rtcweb@ietfa.amsl.com>; Thu, 12 Dec 2013 18:43:43 -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 227B01AE011 for <rtcweb@ietf.org>; Thu, 12 Dec 2013 18:43:42 -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 13:13:36 +1030
Received: from localhost (localhost [127.0.0.1]) by audi.shelbyville.oz (Postfix) with ESMTP id 261014F903 for <rtcweb@ietf.org>; Fri, 13 Dec 2013 13:13:35 +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 aAqeOpXSMXpB for <rtcweb@ietf.org>; Fri, 13 Dec 2013 13:13:34 +1030 (CST)
Received: by audi.shelbyville.oz (Postfix, from userid 1000) id 817B24F904; Fri, 13 Dec 2013 13:13:34 +1030 (CST)
Date: Fri, 13 Dec 2013 13:13:34 +1030
From: Ron <ron@debian.org>
To: rtcweb@ietf.org
Message-ID: <20131213024334.GV3245@audi.shelbyville.oz>
References: <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> <949EF20990823C4C85C18D59AA11AD8B0F8739@FR712WXCHMBA11.zeu.alcatel-lucent.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B0F8739@FR712WXCHMBA11.zeu.alcatel-lucent.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: [rtcweb] H.264 IPR disclosures (or persistent lack thereof)
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: Fri, 13 Dec 2013 02:43:45 -0000

On Fri, Dec 13, 2013 at 12:30:32AM +0000, DRAGE, Keith (Keith) wrote:
> If Ron can justify such a statement, the he is also in defiance of the IETF
> IPR rules, because he himself is required to make a disclosure. The
> requirement is to disclose if you know of..., not if you own.

Maybe you should actually go read the Note Well RFCs before you engage in
"No U" argumentation that just makes it look like you haven't.

If I owned, or worked for or on behalf of anyone who owned IPR that was
relevant to the work here, I indeed would have disclosed it according to
the obligations noted there.

Since I don't, and I don't actually know specific details of which patents
might apply here (beyond reading of assertions there is a pool, and of
court cases that are being pursued over them, and that many of the people
pushing hard for the adoption of H.264 are holders of them) - I am indeed
discharging the only obligation upon me that I SHOULD point and wave.

> But I believe Stefan is correct. Neither IETF or its contributors has not
> written a document specifying the H.264 codec as an essential part of its
> operation, therefore making a disclosure is not required. If IETF progresses
> to making a statement that incorporation of an H.264 implementation forms an
> essential part of a webrtc specification, then disclosure in IETF will be
> required.

 "Covers or may ultimately Cover a Contribution"

I believe is the language used.

 "unless ... rejected from consideration before a disclosure could reasonably
  be submitted."

And I'm pretty sure we're well past the time of "could reasonably", unless
your position is that we should now immediately reject it from consideration?


> ISO/IEC JTC1 does have a specification for H.264, and I am led to believe
> disclosures of IPR have been made there. Noone involved in this discussion as
> far as I am aware is hiding H.264 IPR. Again I believe as a third party, you
> are also allowed to make IPR disclosures there (certainly every other SDO I
> know of allows third party disclosures).
> 
> And before this degenerates into a discussion of what people want the IETF
> IPR rules to become rather than what they are, take that to the IETF
> discussion list.

 "Contributors must disclose IPR meeting the description in this section;
  there are no exceptions to this rule."

Nobody is arguing for a change to the rules here.  It's the blatant
disregard for them (or perhaps you are trying to subtly demonstrate
that it's simply ignorance of them) which is what concerns me at the
present time.

I'd prefer to just see this remedied by the people who the obligation
falls upon than to make an example of them before the wider IETF.
If it goes that far I would assume it will be with a call for sanctions.


Stephan may still be correct that there is some sneaky back door that
people can hide behind here - but if there is one, all that you've
proved in these statements is that you don't know what it is either.

  Ron