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

Bjoern Hoehrmann <derhoermi@gmx.net> Mon, 16 December 2013 11:09 UTC

Return-Path: <derhoermi@gmx.net>
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 22FC91AD7C2 for <rtcweb@ietfa.amsl.com>; Mon, 16 Dec 2013 03:09:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level:
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] 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 elTwxonpabd6 for <rtcweb@ietfa.amsl.com>; Mon, 16 Dec 2013 03:09:24 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id 35AA21A8026 for <rtcweb@ietf.org>; Mon, 16 Dec 2013 03:09:24 -0800 (PST)
Received: from netb.Speedport_W_700V ([91.35.50.130]) by mail.gmx.com (mrgmx103) with ESMTPA (Nemesis) id 0MWkZL-1W3B0b0iFf-00Xuoq for <rtcweb@ietf.org>; Mon, 16 Dec 2013 12:09:23 +0100
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Harald Alvestrand <harald@alvestrand.no>
Date: Mon, 16 Dec 2013 12:09:22 +0100
Message-ID: <66nta9hflhfrd4ptbhju7cjairofp90n81@hive.bjoern.hoehrmann.de>
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>
In-Reply-To: <52AEBF0A.2020509@alvestrand.no>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:YJ8tS6Zp97UNh/xrY4TZjgrDokCCDtJwW96eBOgl/oS16XQO3Cg zBAUy1+I1eSvPnhEWDrzycY9p9rkDdBLu6uekF/sPP9XzfigXEh447zL2tSUteO24jR6HWE 3cgbYK2o+HMobcwWiI0PaBLJzN0XIh8U9pptmf4KzoPYl/YXWkltd2OFZcjg9bI3YbLqAPg h2vUt8mifrSxaHYV22StA==
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 11:09:26 -0000

* 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.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/