Re: [rtcweb] VP8 litigation in Germany?

<Markus.Isomaki@nokia.com> Tue, 12 March 2013 01:28 UTC

Return-Path: <Markus.Isomaki@nokia.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E80E21F8D7A for <rtcweb@ietfa.amsl.com>; Mon, 11 Mar 2013 18:28:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jPUP2q3oNPU2 for <rtcweb@ietfa.amsl.com>; Mon, 11 Mar 2013 18:27:59 -0700 (PDT)
Received: from mgw-sa02.nokia.com (smtp.nokia.com [147.243.1.48]) by ietfa.amsl.com (Postfix) with ESMTP id 7D8CB21F8D77 for <rtcweb@ietf.org>; Mon, 11 Mar 2013 18:27:59 -0700 (PDT)
Received: from vaebh102.NOE.Nokia.com (vaebh102.europe.nokia.com [10.160.244.23]) by mgw-sa02.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r2C1RoWL019123; Tue, 12 Mar 2013 03:27:51 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.57]) by vaebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Tue, 12 Mar 2013 03:27:51 +0200
Received: from 008-AM1MPN1-042.mgdnok.nokia.com ([169.254.2.232]) by 008-AM1MMR1-002.mgdnok.nokia.com ([65.54.30.57]) with mapi id 14.02.0328.011; Tue, 12 Mar 2013 01:27:44 +0000
From: <Markus.Isomaki@nokia.com>
To: <ted.ietf@gmail.com>, <keith.drage@alcatel-lucent.com>
Thread-Topic: [rtcweb] VP8 litigation in Germany?
Thread-Index: AQHOHqpm6kb3TqdDTc2vRZKKqKDI4ZihQSJQ
Date: Tue, 12 Mar 2013 01:27:43 +0000
Message-ID: <E44893DD4E290745BB608EB23FDDB7623BBB9D@008-AM1MPN1-042.mgdnok.nokia.com>
References: <CD613089.973B9%stewe@stewe.org> <E44893DD4E290745BB608EB23FDDB7623BB2E7@008-AM1MPN1-042.mgdnok.nokia.com> <CA+9kkMAeubpx1XE7Up0ccyfrtMW_OiO46fn+TS_i3cTs9TLuhg@mail.gmail.com> <949EF20990823C4C85C18D59AA11AD8B01121E@FR712WXCHMBA11.zeu.alcatel-lucent.com> <CA+9kkMDoLbdPWNUy=gQvn_dj46SA_kZOAAoQtFEAYbB5i2-j-Q@mail.gmail.com>
In-Reply-To: <CA+9kkMDoLbdPWNUy=gQvn_dj46SA_kZOAAoQtFEAYbB5i2-j-Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.129.134.1]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 12 Mar 2013 01:27:51.0063 (UTC) FILETIME=[CFE2E270:01CE1EC0]
X-Nokia-AV: Clean
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] VP8 litigation in Germany?
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 12 Mar 2013 01:28:00 -0000

Hi,

Ted Hardie wrote:
>
>On Mon, Mar 11, 2013 at 6:23 PM, DRAGE, Keith (Keith) <keith.drage@alcatel-
>lucent.com> wrote:
>>
>> As I believe there are no IETF documents that specify H.264 or VP8 directly,
>then you will not get a direct declaration.
>>
>
>This contradicts what I understood Markus to be saying, which is that Nokia
>would supply one.  If I have misunderstood this text:
>
>Nokia is preparing to do a disclosure about it to the  IETF "to ensure that IETF
>working groups and participants have as much information about any IPR
>constraints on a technical proposal as  possible".
>
>I hope he will let me know.
>

Yes, Nokia is preparing a disclosure related to VP8. 

What comes to H.264, the Nokia IPR related to that has been disclosed to those SDOs where that codec has been developed, except for the RTP payload format that is in the IETF. I assume all that is publicly available to interested parties. If I recall correctly, some pointers were floating around prior to IETF 85. I'm sure others on this list know that side better than me.

Markus