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

Harald Alvestrand <harald@alvestrand.no> Mon, 16 December 2013 08:51 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 55CDB1AE1BD for <rtcweb@ietfa.amsl.com>; Mon, 16 Dec 2013 00:51:33 -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 SO2AQYAAc16i for <rtcweb@ietfa.amsl.com>; Mon, 16 Dec 2013 00:51:26 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id B2D5E1AE0AC for <rtcweb@ietf.org>; Mon, 16 Dec 2013 00:51:26 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id AF8A439E125 for <rtcweb@ietf.org>; Mon, 16 Dec 2013 09:51:28 +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 WwNeRumHqQxl for <rtcweb@ietf.org>; Mon, 16 Dec 2013 09:51:28 +0100 (CET)
Received: from [192.168.1.156] (unknown [188.113.88.47]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 0735A39E062 for <rtcweb@ietf.org>; Mon, 16 Dec 2013 09:51:28 +0100 (CET)
Message-ID: <52AEBF0A.2020509@alvestrand.no>
Date: Mon, 16 Dec 2013 09:51:22 +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: rtcweb@ietf.org
References: <20131212214310.GR3245@audi.shelbyville.oz> <CECFA3EA.AC30E%stewe@stewe.org> <949EF20990823C4C85C18D59AA11AD8B0F8739@FR712WXCHMBA11.zeu.alcatel-lucent.com> <20131213024334.GV3245@audi.shelbyville.oz> <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>
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B0F98AF@FR712WXCHMBA11.zeu.alcatel-lucent.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
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 08:51:33 -0000

On 12/16/2013 01:50 AM, DRAGE, Keith (Keith) wrote:
> I'm not sure exactly where you are trying to take this discussion.
>
> If you are implying that the IPR for either of the two codec specifications is unknown, then we MUST stop any decision making process until it is known, because the WG is bound to take that status into account in making its decision.
>
> But I believe the chairs have stated in prior meetings that the IPR is known, and noone has contradicted that on the list or in the meeting, and where to find it has been reiterated time and time again, in the meeting, on mailing lists and in documents.
>
> And you yourself do not seem to be pointing at any IPR coverage that you know of that has not been publically identified.
>
> The only doubts I have heard about absence of IPR disclosure is specifically against the VP8 codec, with the contention that as the specification has only recently been submitted to ISO, many ISO participants may still be evaluating their patent portfolio against it.
>
> 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's not lack of drafts that causes the lack of disclosures, as far as I
can tell.