Re: [rtcweb] Straw Poll on Video Codec Alternatives -- No acceptable alternatives

bryandonnovan@gmail.com Tue, 10 December 2013 22:56 UTC

Return-Path: <bryandonnovan@gmail.com>
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 7A2E11AE24F for <rtcweb@ietfa.amsl.com>; Tue, 10 Dec 2013 14:56:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 nx-a2q93Hv6K for <rtcweb@ietfa.amsl.com>; Tue, 10 Dec 2013 14:56:10 -0800 (PST)
Received: from mail-ve0-x235.google.com (mail-ve0-x235.google.com [IPv6:2607:f8b0:400c:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 82CC41A1F1A for <rtcweb@ietf.org>; Tue, 10 Dec 2013 14:56:10 -0800 (PST)
Received: by mail-ve0-f181.google.com with SMTP id oy12so5324345veb.26 for <rtcweb@ietf.org>; Tue, 10 Dec 2013 14:56:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=pQ1LpgRY6UkrCex6YsP/G8YG/6NsDvFDu8UJtxk7DRE=; b=pOHfMUfz/w2YUa9ltLO84L7/R9ElJuSRHOkL0OkwbVRE0xpfifMu+sxaUUHIyhnakm NO3MRre7MW1JKhmQslzvPc+mUL2gPmFvH3K3pNdPqDMgV7k2V2Fkq6ONmUfsOsgxvXNl kwJaOu62jc8nVTT0tzUOUfWxhSg9L+kBeqi82bhHQFF5BZAxJI2i//VvyoaSdO4DPOlg ut4sidPD5izmPZoQ2WUvAYumKn40GGILFu/Oi00ci6c3YBZYELkXCDA5W/lnmjJfMYwe FYzM4090TrpgBGTjhfHQYpdmkzGfP5Hr/iAQsiIs+0jXI8LxQxfzckV8x5S1UrucLl3b CgHg==
MIME-Version: 1.0
X-Received: by 10.52.111.200 with SMTP id ik8mr12366805vdb.2.1386716165006; Tue, 10 Dec 2013 14:56:05 -0800 (PST)
Received: by 10.52.110.138 with HTTP; Tue, 10 Dec 2013 14:56:04 -0800 (PST)
In-Reply-To: <CAHp8n2=zGxiRfb-Mp4ST19A7bxO3d2N2NZ38GCdc+Y8XJNQ10g@mail.gmail.com>
References: <CAD5OKxu_rbOYwEXmoptcie2xRSG7c7QsxOb6uJF88zDYBkGFwg@mail.gmail.com> <CAHp8n2=zGxiRfb-Mp4ST19A7bxO3d2N2NZ38GCdc+Y8XJNQ10g@mail.gmail.com>
Date: Tue, 10 Dec 2013 14:56:04 -0800
Message-ID: <CAMwTW+hD_L+WotE8WpBS08A69-n_753q9hmqMHo4Gkd8SRF1pw@mail.gmail.com>
From: bryandonnovan@gmail.com
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Content-Type: multipart/alternative; boundary="bcaec548a1916b6e3604ed36041b"
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Straw Poll on Video Codec Alternatives -- No acceptable alternatives
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: Tue, 10 Dec 2013 22:56:13 -0000

Preemptive warning from EU to Nokia:
http://hosted.ap.org/dynamic/stories/E/EU_EU_NOKIA

And here again (for the winning photo):
http://www.engadget.com/2013/12/09/ec-chief-warns-nokia-patent-troll/


On Tue, Dec 10, 2013 at 2:37 PM, Silvia Pfeiffer
<silviapfeiffer1@gmail.com>wrote:

> On Wed, Dec 11, 2013 at 9:04 AM, Roman Shpount <roman@telurix.com> wrote:
> > Changing subject per chair's request.
> >
> > On Tue, Dec 10, 2013 at 4:51 PM, Engel Nyst <engel.nyst@gmail.com>
> wrote:
> >>
> >> On 12/10/2013 08:58 PM, Roman Shpount wrote:
> >>>
> >>> VP8 -- This works for me but I see that this will not work for any
> >>> company
> >>> already using H.264 or ever planning to sue Google. If you are already
> >>> using H.264, why do you want to expose yourself to additional IPR
> risks?
> >>> Google license is not acceptable to many larger companies (partially
> due
> >>> to
> >>> this license being automatically revoked if you decide to sue Google
> for
> >>> reasons non related to VP8) . Fail for VP8.
>
>
> So, this should read:
> VP8 - if you are ever planning on suing anyone around VP8, you should
> refrain from using VP8 because the patent rights granted on VP8 will
> evaporate. This also implies to me that if somebody is trying to sue
> any company (including a startup) over VP8, Google's patent rights
> grant evaporates and they open themselves up for a lawsuit by Google.
> As it stands, the number of companies falling into the category of
> wanting to sue Google over VP8 seems to be 1 (Nokia with their patent
> for which they don't intend to give anyone a license). Everyone else
> can feel themselves pretty safe in knowing that if somebody sues them
> over VP8, they expose themselves to the full force of the Google
> lawyers.
>
> To me, that's more safety than H.264 or any other codec grants.
>
> Best Regards,
> Silvia.
> (IANAL)
>
> >>>
> >>
> >> I'm not sure why you say "reasons not related to VP8". VP8 additional
> >> patent grant says:
> >> "If you or your agent or exclusive licensee institute or order or agree
> to
> >> the institution of patent litigation against any entity (including a
> >> cross-claim or counterclaim in a lawsuit) alleging that this
> implementation
> >> of VP8 or any code incorporated within this implementation of VP8
> >> constitutes direct or contributory patent infringement, or inducement of
> >> patent infringement, then any patent rights granted to you under this
> >> License for this implementation of VP8 shall terminate as of the date
> such
> >> litigation is filed." [1]
> >>
> >> Note "alleging that this implementation of VP8 or any code incorporated
> >> within this implementation of VP8". If the allegations are unrelated to
> VP8,
> >> they don't fall within the bounds of "this implementation of VP8" with
> what
> >> it actually contains. Am I reading this wrong?
> >>
> >
> > Thank you for this correction, this was my mistake. I actually agree with
> > your interpretation. This is one of the reasons that I do consider that
> VP8
> > actually provides better IPR protection for me as a product implementer
> then
> > H.264. On the other hand, I also can see how this provision can prevent
> > implement VP8 for some companies.
> >
> > _____________
> > Roman Shpount
> >
> >
> >
> > _______________________________________________
> > rtcweb mailing list
> > rtcweb@ietf.org
> > https://www.ietf.org/mailman/listinfo/rtcweb
> >
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>