Re: [codec] [asterisk-dev] Opus and VP8
"Cullen Jennings (fluffy)" <fluffy@cisco.com> Fri, 28 June 2013 22:29 UTC
Return-Path: <fluffy@cisco.com>
X-Original-To: codec@ietfa.amsl.com
Delivered-To: codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74C2221F9CEE for <codec@ietfa.amsl.com>; Fri, 28 Jun 2013 15:29:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 qr1W7gPztru2 for <codec@ietfa.amsl.com>; Fri, 28 Jun 2013 15:29:02 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 2AA8A21F9CF0 for <codec@ietf.org>; Fri, 28 Jun 2013 15:28:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7592; q=dns/txt; s=iport; t=1372458538; x=1373668138; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=+QnhsbeIVLaiQoCZc+utQFBemcMPJ0t9B1p7ZCMYsDY=; b=aDdp4m2wkrBKa9LTHXYExwc4wy5ZoBhIGClGYoOuCrspD+YzKTlZOV3O acPcSdHPFjdTWmmvc2EGSyyrFp37ry5QuyX648u/2faS8gFmwHdbzhREc H+Z6zOT9f8m6J1UzBy47AtwCTX7h+tNcrL5pNAKdgaR8XL7tTD2D8hcMx c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhQFAKsMzlGtJV2Z/2dsb2JhbABbgwkySb8KgQoWdIIjAQEBAwEBAQFrCwUHBAIBCBEDAQIBCiQhBgEKHQgCBA4FCAyHaQMJBQEMsWYNiFKMboExgQQCCyYHBoJ+YwOIaowWXoMQineFJYMRgWk/
X-IronPort-AV: E=Sophos;i="4.87,962,1363132800"; d="scan'208";a="228808386"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-7.cisco.com with ESMTP; 28 Jun 2013 22:28:57 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r5SMSv8H012158 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 28 Jun 2013 22:28:57 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.116]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.02.0318.004; Fri, 28 Jun 2013 17:28:57 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: "Olle E. Johansson" <oej@edvina.net>
Thread-Topic: [codec] [asterisk-dev] Opus and VP8
Thread-Index: AQHOdE7gQokjA1dY20CTLZJcPeAA9g==
Date: Fri, 28 Jun 2013 22:28:56 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB1135B683B@xmb-aln-x02.cisco.com>
References: <51A64F3E.5040002@digium.com> <8E24D629-1D4C-431A-B466-4DD5F0273F9A@edvina.net>
In-Reply-To: <8E24D629-1D4C-431A-B466-4DD5F0273F9A@edvina.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [171.68.20.14]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <D292EB0DD4C15A4686DD3C53E13F7198@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "codec@ietf.org" <codec@ietf.org>
Subject: Re: [codec] [asterisk-dev] Opus and VP8
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Codec WG <codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/codec>, <mailto:codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/codec>
List-Post: <mailto:codec@ietf.org>
List-Help: <mailto:codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jun 2013 22:29:08 -0000
Well, Asterisk does SIP and that has way more IPR on it than Opus, so uh, I guess you will need to decide if you think some random claim on IETF web site is a valid concern or not. Good luck. Note that blocking all forward progress on asterisk by filing claims on an IETF web page is also a risk to the project. (Oh, and TLS has lots of IPR too) PS - every effort possible has been made to ensure that Opus is GPL compatible. On May 30, 2013, at 2:14 AM, Olle E. Johansson <oej@edvina.net> wrote: > Please comment on this statement about Opus from Matt Jordan, the > project leader for the Asterisk project. > > Regards, > /Olle > > Vidarebefordrat brev: > >> Från: Matthew Jordan <mjordan@digium.com> >> Ämne: Re: [asterisk-dev] Opus and VP8 >> Datum: 29 maj 2013 20:55:58 CEST >> Till: asterisk-dev@lists.digium.com >> Svara till: Asterisk Developers Mailing List <asterisk-dev@lists.digium.com> >> >> On 05/25/2013 05:19 AM, Hans Witvliet wrote: >>> -----Original Message----- >>> From: Olle E. Johansson <oej@edvina.net> >>> Reply-to: Asterisk Developers Mailing List >>> <asterisk-dev@lists.digium.com> >>> To: Asterisk Developers Mailing List <asterisk-dev@lists.digium.com> >>> Cc: Olle E. Johansson <oej@edvina.net> >>> Subject: Re: [asterisk-dev] Opus and VP8 >>> Date: Fri, 24 May 2013 13:26:29 +0200 >>> >>> >>> 24 maj 2013 kl. 12:51 skrev Lorenzo Miniero <lminiero@gmail.com>: >>> >>>> PS: a few months ago I also talked, on the #asterisk-dev IRC, about >>>> the support I added for both Opus (transcoding) and VP8 (passthrough) >>>> in Asterisk, codecs that are currently the default ones used in >>>> WebRTC. I checked whether there was an interest in a patch for them, >>>> but at the time there were some concerns about the copyright status of >>>> Opus that prevented it to be considered for integration in Asterisk. >>>> Has this situation changed in the meanwhile? I can open a separate >>>> thread for this if needed. >>>> >>> Lorenzo, >>> >>> >>> Good seeing you here! >>> >>> >>> Due to legal issues I don't think Digium can accept a contribution of >>> Opus and VP8 in the svn repositories today. >>> >>> >>> I would encourage you, if you have these patches, to publish them on a >>> web site like github or sourceforge so w all can help you test it. I >>> really would like for these to be available for the community in an easy >>> form. >>> >> >> <snip> >> >> Hello! I'm going to comment here specifically to clarify Digium's >> position on Opus and VP8 as codecs and their inclusion in Asterisk. >> >> To start, pass through support in the form of a format module is fine >> for both Opus and VP8. It involves no transcoding and hence cannot >> violate any claims against their technology. We'd be happy to see format >> modules in Asterisk. >> >> VP8 is the easier of the two to clarify. A codec for VP8 is probably not >> appropriate, regardless of any patent or IPR issues. Asterisk doesn't >> perform video transcoding. Video transcoding is an intensive operation >> that performs poorly without hardware augmentation. We've always taken >> the stance that software video transcoding in Asterisk would cause more >> problems then it would solve; as such, VP8 as a codec is best left >> outside of Asterisk. >> >> The real question is: what about Opus? >> >> Before that, a word about the American patent system. >> >> The American patent system has devolved into what can only be charitably >> described as mafia-inspired extortion. Non-practicing entities (NPEs) >> are groups of lawyers who have not and never will produce, market, or >> sell a product. The only actions they perform are filing infringement >> claims against businesses and individuals, regardless of whether or not >> that business or individual actually violates a patent, with the sole >> purpose of extracting as much money out of said business or individual >> as they can. The cost of fighting these claims is enormous. The cost of >> losing a fight against even one of these claims is crippling. The NPEs >> know this. Technical merit, logic, rationale, or any kind of morality >> has no applicability here: these folks exist solely to find new and more >> creative ways to make claims against you and take your money. >> >> They'd be happy to put you out of business in the process. >> >> Back to Opus. >> >> There are several IPRs filed against Opus with the unfortunate licensing >> declaration of "Reasonable and Non-Discriminatory License to All >> Implementers with Possible Royalty/Fee." These IPRs have not been >> clarified, and the entities making these claims have not moved one way >> or the other regarding their claims. If any one of these entities >> decides to play the NPE game (see: Alcatel-Lucent), they could crush >> Digium like a bug. They could go after every user, integrator, and >> developer of Asterisk as well. It has the potential of spelling the end >> of the Asterisk project. The risk of this unfortunately does not justify >> the inclusion of Opus as a codec in Asterisk. >> >> Question: I am a user, integrator, and developer of Asterisk that does >> not work for Digium. Since Digium holds the copyright of Asterisk, how >> am I at risk? >> >> Answer: I have no idea. I do know that logic and reasoning does not >> apply where patents are concerned. Caveat emptor. >> >> Question: Asterisk is an open source project. Doesn't that protect me >> somehow? >> >> Answer: No. The GPLv2 specifically states "that any patent must be >> licensed for everyone's free use or not licensed at all". There are >> additional sections that further explain how patents affect software >> licensed under GPLv2; suffice to say that the sections exist to protect >> the freedom of the software; not to protect you from patent trolls. >> >> Question: If all of this is true, why does Google, Mozilla, Xiph.org, >> and others implement Opus? >> >> Answer: They either have an army of lawyers, are willing to roll the >> dice on their future, or are ignorant of how the patent system works. >> >> Question: This is messed up. If all of this is true, how can we ever >> innovate in areas where patents have ever been filed? >> >> Answer: You can't. The system is broken. >> >> Question: What can I do about it? >> >> Answer: Contact your government officials. Complain. The only way this >> situation will get fixed is if the laws are changed. Note that there is >> at least one bill being brought up in the U.S. Senate to address these >> exact deficiencies in the American patent system (and possibly more in >> the House); if you are a U.S. citizen I highly recommend you contact >> your elected Senators/Representatives and express your opinion(s). >> >> I hope this helps everyone understand why we've made our decision. We >> all hope that this situation changes in the near future, but until then, >> we'll have to limit our support of these codecs in Asterisk to >> pass-through only. >> >> Thanks >> >> Matt >> >> -- >> Matthew Jordan >> Digium, Inc. | Engineering Manager >> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA >> Check us out at: http://digium.com & http://asterisk.org >> > > _______________________________________________ > codec mailing list > codec@ietf.org > https://www.ietf.org/mailman/listinfo/codec
- [codec] Fwd: [asterisk-dev] Opus and VP8 Olle E. Johansson
- Re: [codec] [asterisk-dev] Opus and VP8 Cullen Jennings (fluffy)
- Re: [codec] [asterisk-dev] Opus and VP8 Anthony Minessale
- Re: [codec] [asterisk-dev] Opus and VP8 Michael Graves
- Re: [codec] [asterisk-dev] Opus and VP8 Matthew Jordan