Re: [codec] A concrete proposal for requirements and testing

Stephan Wenger <stewe@stewe.org> Thu, 07 April 2011 19:22 UTC

Return-Path: <stewe@stewe.org>
X-Original-To: codec@core3.amsl.com
Delivered-To: codec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9F82428C0E5 for <codec@core3.amsl.com>; Thu, 7 Apr 2011 12:22:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.983
X-Spam-Level:
X-Spam-Status: No, score=-1.983 tagged_above=-999 required=5 tests=[AWL=0.617, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t8Y+gXsM2W6b for <codec@core3.amsl.com>; Thu, 7 Apr 2011 12:22:30 -0700 (PDT)
Received: from stewe.org (stewe.org [85.214.122.234]) by core3.amsl.com (Postfix) with ESMTP id 09BD43A690A for <codec@ietf.org>; Thu, 7 Apr 2011 12:22:29 -0700 (PDT)
Received: from [192.168.1.108] (unverified [24.5.184.151]) by stewe.org (SurgeMail 3.9e) with ESMTP id 7178-1743317 for multiple; Thu, 07 Apr 2011 21:24:14 +0200
User-Agent: Microsoft-MacOutlook/14.2.0.101115
Date: Thu, 07 Apr 2011 12:24:05 -0700
From: Stephan Wenger <stewe@stewe.org>
To: "Timothy B. Terriberry" <tterribe@xiph.org>
Message-ID: <C9C35CE8.2A02B%stewe@stewe.org>
Thread-Topic: [codec] A concrete proposal for requirements and testing
In-Reply-To: <4D9E0CBC.1060404@xiph.org>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Originating-IP: 24.5.184.151
X-Authenticated-User: stewe@stewe.org
X-ORBS-Stamp: Your IP (24.5.184.151) was found in the spamhaus database. http://www.spamhaus.net
Cc: codec@ietf.org
Subject: Re: [codec] A concrete proposal for requirements and testing
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Codec WG <codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 07 Apr 2011 19:22:32 -0000

At this point, there is no indication that opus is going to be royalty
free.  In fact, there is evidence to the contrary:
https://datatracker.ietf.org/ipr/1520/

Stephan


On 4.7.2011 12:13 , "Timothy B. Terriberry" <tterribe@xiph.org> wrote:

>> I think that the issues of performance requirements and encumbered
>> technologies are separate. In fact, the WG charter states "The working
>>group
>
>I strongly disagree with this. Groups like my employer, Mozilla, are
>actually interested in deploying this codec on the internet (you know,
>the purpose for which this working group was formed), in things like
>RTC-Web. Royalty-free is a requirement for us, as well as for the W3C,
>where part of that work is being done. The alternatives are things like
>Speex, iLBC, and G.722, not AMR-NB or AMR-WB (see, for example,
>https://bugzilla.mozilla.org/show_bug.cgi?id=476752#c20).
>
>> cannot explicitly rule out the possibility of adopting encumbered
>> technologies". At the end of the day, people will make their own
>>trade-off
>> between Opus performance and whether it is encumbered or not. So the
>> requirements need to include some reasonable performance targets, and
>>AMR-NB
>> and AMR-WB provide those.
>
>This is pure fallacy. You don't need to quote the charter to know that
>the structure of the patent system makes any guarantees impossible. Yet
>if Opus were eventually found to be encumbered, we still couldn't fall
>back to AMR-NB or AMR-WB. If you don't care about such encumbrances,
>then there are plenty of good alternatives, but the lack of them for
>those who do care is one of the reasons this WG was formed. The charter
>states this explicitly.
>
>The charter also mentions the possibility of co-publication of the
>completed codec by the ITU. Now, if you wanted to make such tests a
>requirement for co-publication, that would make perfect sense, but I
>don't believe it makes sense to prevent publication of the codec by this
>WG, regardless of their outcome.
>_______________________________________________
>codec mailing list
>codec@ietf.org
>https://www.ietf.org/mailman/listinfo/codec