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

Harald Alvestrand <harald@alvestrand.no> Mon, 16 December 2013 13:43 UTC

Return-Path: <harald@alvestrand.no>
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 DE26F1AE330 for <rtcweb@ietfa.amsl.com>; Mon, 16 Dec 2013 05:43:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.438
X-Spam-Level:
X-Spam-Status: No, score=-7.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538] 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 XP9NXRlqsuHR for <rtcweb@ietfa.amsl.com>; Mon, 16 Dec 2013 05:43:39 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 5A76E1AE32D for <rtcweb@ietf.org>; Mon, 16 Dec 2013 05:43:38 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id BB4D439E333; Mon, 16 Dec 2013 14:43:40 +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 kZZv+bLN2+7q; Mon, 16 Dec 2013 14:43:38 +0100 (CET)
Received: from [192.168.1.17] (unknown [188.113.88.47]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id E0C4239E2CB; Mon, 16 Dec 2013 14:43:37 +0100 (CET)
Message-ID: <52AF0394.50104@alvestrand.no>
Date: Mon, 16 Dec 2013 14:43:48 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: Bjoern Hoehrmann <derhoermi@gmx.net>
References: <949EF20990823C4C85C18D59AA11AD8B0F88D6@FR712WXCHMBA11.zeu.alcatel-lucent.com> <20131213033344.GW3245@audi.shelbyville.oz> <CECFF758.205FF%mzanaty@cisco.com> <E44893DD4E290745BB608EB23FDDB7620A16219B@008-AM1MPN1-042.mgdnok.nokia.com> <20131214102855.GY3245@audi.shelbyville.oz> <20131214122049.604352b3@rainpc> <20131214132520.GZ3245@audi.shelbyville.oz> <949EF20990823C4C85C18D59AA11AD8B0F98AF@FR712WXCHMBA11.zeu.alcatel-lucent.com> <52AEBF0A.2020509@alvestrand.no> <66nta9hflhfrd4ptbhju7cjairofp90n81@hive.bjoern.hoehrmann.de>
In-Reply-To: <66nta9hflhfrd4ptbhju7cjairofp90n81@hive.bjoern.hoehrmann.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: rtcweb@ietf.org
Subject: Re: [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: Mon, 16 Dec 2013 13:43:42 -0000

On 12/16/2013 12:09 PM, Bjoern Hoehrmann wrote:
> * Harald Alvestrand wrote:
>> On 12/16/2013 01:50 AM, DRAGE, Keith (Keith) wrote:
>>> Of course if you really do want an IETF IPR disclosure under way, then
>>> submit a draft that makes both codecs mandatory and asks for it to be a
>>> WG item. The codec declarations will have to be made against that
>>> document. But do you really believe that will produce any surprise
>>> declarations.
>>>
>>> That draft WG document at the moment does not exist.
>> Keith, it is completely unclear to me why such a draft would cause more
>> disclosures to come forth, given that we have one draft proposing
>> declaring H.264 CBP mandatory that caused no IPR disclosures, and
>> another draft proposing declaring VP8 mandatory that, again, caused no
>> IPR disclosures.
> It looks to me as though the expectation is that once a document is made
> an official Working Group draft then others than those contributing the
> draft have to make disclosures, and since as far as I can tell the draft
> to make VP8 mandatory is not an official Working Group draft, making it
> one would then cause more disclosures to come forth, as you put it. That
> expectation might not be justified but the interpretation of the comment
> above seemed straightforward.
This may be an expectation that some people have, but it has no 
grounding whatsoever in the IETF IPR disclosure rules, where the gating 
factor is that it has been "contributed", and that others "realize" that 
the IPR they know about applies to the contribution.

RFC 3979 section 6.2.1 is pretty explicit. Nowhere in the document is 
the concept of "working group draft" mentioned.

It's been pointed out any number of times that this is what the rules say.

I won't dictate anyone's actions - there are plenty of reasons (some 
good, some bad) that people might conclude that the right action for 
them is to act in ways that are not in accordance with the rules - but 
the rules say what they say - and that does NOT mention "working group 
draft adoption"; the rules apply to ANYTHING that is contributed.