Re: [codec] A concrete proposal for requirements and testing
"Roni Even" <ron.even.tlv@gmail.com> Fri, 08 April 2011 20:31 UTC
Return-Path: <ron.even.tlv@gmail.com>
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 4EF643A696D for <codec@core3.amsl.com>; Fri, 8 Apr 2011 13:31:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 r5-zZaKnQOT5 for <codec@core3.amsl.com>; Fri, 8 Apr 2011 13:31:29 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id D370A3A68CB for <codec@ietf.org>; Fri, 8 Apr 2011 13:31:28 -0700 (PDT)
Received: by wyb29 with SMTP id 29so3752453wyb.31 for <codec@ietf.org>; Fri, 08 Apr 2011 13:33:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:x-mailer:thread-index :content-language; bh=MY7ZPo/LYUD3xOpGwZLzOHbp3YPNzu6gjh+xKgnUrgA=; b=ZD3MkVc0EVWdVYE16mDBVCuSlD185TsknAylM3Tes8RI9X8sT0bHjH16t4zhJzPU6i u0+M/HGQPb24xtms5p1nOIUbEnGqyAYCi7evQO0oFty/G92K/Th1FgDOOXD92rF/AD37 My8xBkpc/kPAaEGizdyT+1ftMlaBVeLmTwzAY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:x-mailer:thread-index:content-language; b=jykj63Ibn16VlZb2Ex28xCuQkUufVPlLtxa4Mr4hO5RQq7ZEvv/OQFqDD/zxvm5ifA C0regFw3sVOPleR2OibIRrP8um+xhc4DDbCJq7uszF7GucMN8hMrR5H7+pifRF7u1FmS oGzLZwHUpKf2AfLAd0e6U+IxZWt+1zBwGyeEU=
Received: by 10.216.191.208 with SMTP id g58mr2229659wen.85.1302294793779; Fri, 08 Apr 2011 13:33:13 -0700 (PDT)
Received: from windows8d787f9 (bzq-79-179-29-234.red.bezeqint.net [79.179.29.234]) by mx.google.com with ESMTPS id h39sm1530173wes.29.2011.04.08.13.33.09 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 08 Apr 2011 13:33:11 -0700 (PDT)
From: Roni Even <ron.even.tlv@gmail.com>
To: 'Paul Coverdale' <coverdale@sympatico.ca>, 'Koen Vos' <koen.vos@skype.net>, 'Roman Shpount' <roman@telurix.com>
References: <BANLkTimN1VduZ9kR2Mgp_w7=p6V1srHBiQ@mail.gmail.com> <21200823.2625297.1302284060278.JavaMail.root@lu2-zimbra> <BLU0-SMTP11D0135F8FFEEEB308A1E9D0A70@phx.gbl>
In-Reply-To: <BLU0-SMTP11D0135F8FFEEEB308A1E9D0A70@phx.gbl>
Date: Fri, 08 Apr 2011 23:32:33 +0300
Message-ID: <4d9f7107.a7fed80a.542d.ffffa087@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0298_01CBF645.3E58BB90"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acv2Ez96c/2qqdL1T6qm0QsBmX99/wAAnvDAAAV9QkA=
Content-Language: en-us
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: Fri, 08 Apr 2011 20:31:30 -0000
And as stated in the charter on deliverables: " Specification of a codec that meets the agreed-upon requirements" I think there are no agreed-upon requirements yet and this is what I see as the current discussion and not if the codec has fulfilled the requirements. Roni Even From: codec-bounces@ietf.org [mailto:codec-bounces@ietf.org] On Behalf Of Paul Coverdale Sent: Friday, April 08, 2011 9:32 PM To: 'Koen Vos'; 'Roman Shpount' Cc: codec@ietf.org Subject: Re: [codec] A concrete proposal for requirements and testing Koen Vos wrote: >quality has been shown to be good enough for the codec to be useful... I think that’s where some people have difficulty. There’s been no systematic attempt to evaluate Opus against the performance requirements given in the codec requirements document (as thin as it is) in a controlled and repeatable manner. …Paul
- [codec] A concrete proposal for requirements and … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Roman Shpount
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Roman Shpount
- Re: [codec] A concrete proposal for requirements … Benjamin M. Schwartz
- Re: [codec] A concrete proposal for requirements … Roni Even
- Re: [codec] A concrete proposal for requirements … Stephen Botzko
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Jan Skoglund
- Re: [codec] A concrete proposal for requirements … Anisse Taleb
- Re: [codec] A concrete proposal for requirements … Erik Norvell
- Re: [codec] A concrete proposal for requirements … Anisse Taleb
- Re: [codec] A concrete proposal for requirements … Anisse Taleb
- Re: [codec] A concrete proposal for requirements … Paul Coverdale
- Re: [codec] A concrete proposal for requirements … Benjamin M. Schwartz
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Paul Coverdale
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Stephen Botzko
- Re: [codec] A concrete proposal for requirements … Anisse Taleb
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Paul Coverdale
- Re: [codec] A concrete proposal for requirements … Stephen Botzko
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Anisse Taleb
- Re: [codec] A concrete proposal for requirements … Paul Coverdale
- Re: [codec] A concrete proposal for requirements … Peter Saint-Andre
- Re: [codec] A concrete proposal for requirements … Stephen Botzko
- Re: [codec] A concrete proposal for requirements … Benjamin M. Schwartz
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Peter Saint-Andre
- Re: [codec] A concrete proposal for requirements … Timothy B. Terriberry
- Re: [codec] A concrete proposal for requirements … Stephan Wenger
- Re: [codec] A concrete proposal for requirements … Monty Montgomery
- Re: [codec] A concrete proposal for requirements … Timothy B. Terriberry
- Re: [codec] A concrete proposal for requirements … Stephan Wenger
- Re: [codec] A concrete proposal for requirements … Gregory Maxwell
- Re: [codec] A concrete proposal for requirements … Monty Montgomery
- Re: [codec] A concrete proposal for requirements … Koen Vos
- Re: [codec] A concrete proposal for requirements … Roman Shpount
- Re: [codec] A concrete proposal for requirements … Koen Vos
- Re: [codec] A concrete proposal for requirements … Stephan Wenger
- Re: [codec] A concrete proposal for requirements … Paul Coverdale
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Gregory Maxwell
- Re: [codec] A concrete proposal for requirements … Roman Shpount
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Koen Vos
- Re: [codec] A concrete proposal for requirements … Paul Coverdale
- Re: [codec] A concrete proposal for requirements … Roni Even
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Kavan Seggie
- Re: [codec] A concrete proposal for requirements … Roni Even
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Roni Even
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Stephen Botzko
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Roni Even
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Stephan Wenger
- Re: [codec] A concrete proposal for requirements … Kat Walsh
- Re: [codec] A concrete proposal for requirements … Stefan Hacker
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Paul Coverdale
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Stephen Botzko
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Serge Smirnoff
- Re: [codec] A concrete proposal for requirements … Anisse Taleb
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Stephen Botzko
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Stephen Botzko
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Stephen Botzko
- Re: [codec] A concrete proposal for requirements … Anisse Taleb
- [codec] Chairs and consensus Cullen Jennings