Re: [codec] A concrete proposal for requirements and testing
Ron <ron@debian.org> Tue, 12 April 2011 06:41 UTC
Return-Path: <ron@debian.org>
X-Original-To: codec@ietfc.amsl.com
Delivered-To: codec@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 4CAD0E074E for <codec@ietfc.amsl.com>; Mon, 11 Apr 2011 23:41:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZjdtwHu3bsL0 for <codec@ietfc.amsl.com>; Mon, 11 Apr 2011 23:41:02 -0700 (PDT)
Received: from ipmail07.adl2.internode.on.net (ipmail07.adl2.internode.on.net [150.101.137.131]) by ietfc.amsl.com (Postfix) with ESMTP id 2A1FEE0749 for <codec@ietf.org>; Mon, 11 Apr 2011 23:40:58 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmMHAL3xo0120qsf/2dsb2JhbACZBI0ceIh6uRmFbgSFWYgH
Received: from ppp118-210-171-31.lns20.adl6.internode.on.net (HELO audi.shelbyville.oz) ([118.210.171.31]) by ipmail07.adl2.internode.on.net with ESMTP; 12 Apr 2011 16:10:56 +0930
Received: from localhost (localhost [127.0.0.1]) by audi.shelbyville.oz (Postfix) with ESMTP id E51C04F8F3 for <codec@ietf.org>; Tue, 12 Apr 2011 14:49:48 +0930 (CST)
X-Virus-Scanned: Debian amavisd-new at audi.shelbyville.oz
Received: from audi.shelbyville.oz ([127.0.0.1]) by localhost (audi.shelbyville.oz [127.0.0.1]) (amavisd-new, port 10024) with LMTP id qQv1dbUtTAbG for <codec@ietf.org>; Tue, 12 Apr 2011 14:49:48 +0930 (CST)
Received: by audi.shelbyville.oz (Postfix, from userid 1000) id 158824F8FE; Tue, 12 Apr 2011 14:49:48 +0930 (CST)
Date: Tue, 12 Apr 2011 14:49:48 +0930
From: Ron <ron@debian.org>
To: codec@ietf.org
Message-ID: <20110412051947.GP30415@audi.shelbyville.oz>
References: <21200823.2625297.1302284060278.JavaMail.root@lu2-zimbra> <BLU0-SMTP11D0135F8FFEEEB308A1E9D0A70@phx.gbl> <4d9f7107.a7fed80a.542d.ffffa087@mx.google.com> <20110409030611.GG30415@audi.shelbyville.oz> <BLU0-SMTP9917A8ABBC14D6FFE833E6D0A90@phx.gbl> <20110410023345.GM30415@audi.shelbyville.oz> <BANLkTin1pTWfThu1mF=PnBKMz_0_=5f8rw@mail.gmail.com> <20110410180627.GN30415@audi.shelbyville.oz> <4DA2EA85.8010609@soundexpert.info> <F5AD4C2E5FBF304ABAE7394E9979AF7C26BC5E8D@LHREML503-MBX.china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <F5AD4C2E5FBF304ABAE7394E9979AF7C26BC5E8D@LHREML503-MBX.china.huawei.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: Re: [codec] A concrete proposal for requirements and testing
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: Tue, 12 Apr 2011 06:41:03 -0000
Hi Anisse, On Mon, Apr 11, 2011 at 06:26:08PM +0000, Anisse Taleb wrote: > Hi all, > > I feel this thread has somewhat diverged from its initial purpose which was > to have a concrete plan for testing and requirements. Well, its initial purpose, as clearly seen in its first post, was to resolve the disagreement (or possibly confusion?) that resulted from trying to take a hum on those questions, without adequate discussion, at Prague. It diverged from that almost immediately, and has steadfastly refused to return to it. If we can take that as meaning that nobody actually does disagree with the points that Jean-Marc asked to clarify, then I think we can take that as meaning this (original) thread has actually achieved its purpose and we now do have consensus on those points. Is there some formal IETF thing we need to do to acknowledge that now? (as separate from this subthread about an additional planned test) > I have also a feeling > that there are "cultural" differences and divergences as to what "testing" > means. I don't think anyone disagrees on what testing means. I do think we have some disagreement on what tests are relevant though. Some people think testing against G.711, or against codecs that cannot possibly fill the requirements this group set out to achieve, is a fairly pointless exercise. At least in the context of assessing whether we have met the requirements of the WG, and to what standard. And in the face of the test results that we do already have. Such tests may still be interesting to see (I'd be interested in seeing them for one), but I strongly disagree that they are at all serving the aims of the WG, and don't think we should delay its progress if we don't have them in time. > That aside, I would like to inform that a proposal for test plan is currently > being drafted and will be communicated this week. Thank you. I'm very glad to hear that the people who weren't satisfied by the results we've already seen are taking the initiative to resolve that to their full satisfaction. As only they can do. I look forward to seeing your plan, and its results. As I have all of the other tests performed to date. Best, Ron
- [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