Re: [codec] draft test and processing plan for the IETF Codec
Ron <ron@debian.org> Mon, 18 April 2011 14:12 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 5EA4AE078C for <codec@ietfc.amsl.com>; Mon, 18 Apr 2011 07:12:15 -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=[AWL=0.000, 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 tj1ZfZphidaw for <codec@ietfc.amsl.com>; Mon, 18 Apr 2011 07:12:14 -0700 (PDT)
Received: from ipmail06.adl6.internode.on.net (ipmail06.adl6.internode.on.net [150.101.137.145]) by ietfc.amsl.com (Postfix) with ESMTP id AAF7DE0776 for <codec@ietf.org>; Mon, 18 Apr 2011 07:12:11 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjQIAGtErE120qsf/2dsb2JhbACYGY1DeMN+hXEEhWCIIg
Received: from ppp118-210-171-31.lns20.adl6.internode.on.net (HELO audi.shelbyville.oz) ([118.210.171.31]) by ipmail06.adl6.internode.on.net with ESMTP; 18 Apr 2011 23:42:07 +0930
Received: from localhost (localhost [127.0.0.1]) by audi.shelbyville.oz (Postfix) with ESMTP id D8C054F8F3 for <codec@ietf.org>; Mon, 18 Apr 2011 23:42:05 +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 baroF8QP+5Ul for <codec@ietf.org>; Mon, 18 Apr 2011 23:42:00 +0930 (CST)
Received: by audi.shelbyville.oz (Postfix, from userid 1000) id D30914F8FE; Mon, 18 Apr 2011 23:42:00 +0930 (CST)
Date: Mon, 18 Apr 2011 23:42:00 +0930
From: Ron <ron@debian.org>
To: codec@ietf.org
Message-ID: <20110418141200.GE31013@audi.shelbyville.oz>
References: <F5AD4C2E5FBF304ABAE7394E9979AF7C26BC684E@LHREML503-MBX.china.huawei.com> <4DA5A748.2050401@fas.harvard.edu> <F5AD4C2E5FBF304ABAE7394E9979AF7C26BC870C@LHREML503-MBX.china.huawei.com> <20110418114716.GC31013@audi.shelbyville.oz> <BANLkTi=K4nWp3UX7TFtbPJd_iDsy-n3L+w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <BANLkTi=K4nWp3UX7TFtbPJd_iDsy-n3L+w@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: Re: [codec] draft test and processing plan for the IETF Codec
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: Mon, 18 Apr 2011 14:12:15 -0000
On Mon, Apr 18, 2011 at 09:32:23AM -0400, Stephen Botzko wrote: > if we see a result that concerns us, we can follow up. Perhaps the > test plan should say this explicitly, or perhaps we can just agree to > discuss needed follow-ups when we see the results. I believe that is exactly the solution that is being explored in the <4DA7B88F.80002@jmvalin.ca> subthread, which begins: I gave some more thought on your proposed test plan and as Cullen suggested, I think the main cause of disagreement is not that much on the testing, but on the conditions for publishing (large number of BT, NWT). Considering that ultimately, the decision to publish a spec is always based on WG consensus, then I think that problem can be completely bypassed. Once we make it up to the individuals to decide, then we can focus on "simply" designing a good test. So let's get started on the tests that people individually think are important so that we have their results to consider by the time we think we have enough information to decide. Do you see anything wrong with that solution? It looks about as fair and thorough as we can make it to everyone to me. Cheers, Ron
- [codec] draft test and processing plan for the IE… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Schulz, Edward D (Ed)
- Re: [codec] draft test and processing plan for th… Jean-Marc Valin
- Re: [codec] draft test and processing plan for th… Benjamin M. Schwartz
- Re: [codec] draft test and processing plan for th… Stephen Botzko
- Re: [codec] draft test and processing plan for th… Roman Shpount
- Re: [codec] draft test and processing plan for th… Erik Norvell
- Re: [codec] draft test and processing plan for th… Paul Coverdale
- Re: [codec] draft test and processing plan for th… Peter Saint-Andre
- Re: [codec] draft test and processing plan for th… Stephan Wenger
- Re: [codec] draft test and processing plan for th… Benjamin M. Schwartz
- Re: [codec] draft test and processing plan for th… Stephen Botzko
- Re: [codec] draft test and processing plan for th… Peter Saint-Andre
- Re: [codec] draft test and processing plan for th… Stephen Botzko
- Re: [codec] draft test and processing plan for th… Ron
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Jean-Marc Valin
- Re: [codec] draft test and processing plan for th… Gregory Maxwell
- Re: [codec] draft test and processing plan for th… Koen Vos
- Re: [codec] draft test and processing plan for th… Paul Coverdale
- Re: [codec] draft test and processing plan for th… Jean-Marc Valin
- Re: [codec] draft test and processing plan for th… Cullen Jennings
- Re: [codec] draft test and processing plan for th… Jean-Marc Valin
- Re: [codec] draft test and processing plan for th… Jean-Marc Valin
- Re: [codec] draft test and processing plan for th… Koen Vos
- Re: [codec] draft test and processing plan for th… Jean-Marc Valin
- Re: [codec] draft test and processing plan for th… Cullen Jennings
- Re: [codec] draft test and processing plan for th… Roman Shpount
- Re: [codec] draft test and processing plan for th… Koen Vos
- Re: [codec] draft test and processing plan for th… Paul Coverdale
- Re: [codec] draft test and processing plan for th… Jean-Marc Valin
- Re: [codec] draft test and processing plan for th… Koen Vos
- Re: [codec] draft test and processing plan for th… Paul Coverdale
- Re: [codec] draft test and processing plan for th… Koen Vos
- Re: [codec] draft test and processing plan for th… Paul Coverdale
- Re: [codec] draft test and processing plan for th… Koen Vos
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Stephen Botzko
- Re: [codec] draft test and processing plan for th… Ron
- Re: [codec] draft test and processing plan for th… Ron
- Re: [codec] draft test and processing plan for th… Stephen Botzko
- Re: [codec] draft test and processing plan for th… Stephen Botzko
- Re: [codec] draft test and processing plan for th… David Virette
- Re: [codec] draft test and processing plan for th… Ron
- Re: [codec] draft test and processing plan for th… Koen Vos
- Re: [codec] draft test and processing plan for th… Jean-Marc Valin
- Re: [codec] draft test and processing plan for th… Stephen Botzko
- Re: [codec] draft test and processing plan for th… Jean-Marc Valin
- Re: [codec] draft test and processing plan for th… Roman Shpount
- Re: [codec] draft test and processing plan for th… Koen Vos
- Re: [codec] draft test and processing plan for th… Michael Ramalho (mramalho)
- Re: [codec] draft test and processing plan for th… Roman Shpount
- Re: [codec] draft test and processing plan for th… David Virette
- Re: [codec] draft test and processing plan for th… David Virette
- Re: [codec] draft test and processing plan for th… David Virette
- Re: [codec] draft test and processing plan for th… Jean-Marc Valin
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Koen Vos
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Jean-Marc Valin
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Paul Coverdale
- Re: [codec] draft test and processing plan for th… Jean-Marc Valin
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Ron
- Re: [codec] draft test and processing plan for th… Monty Montgomery
- Re: [codec] draft test and processing plan for th… Koen Vos
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Cullen Jennings
- Re: [codec] draft test and processing plan for th… Koen Vos
- Re: [codec] draft test and processing plan for th… Koen Vos
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Anisse Taleb
- Re: [codec] draft test and processing plan for th… Christian Hoene
- Re: [codec] draft test and processing plan for th… Christian Hoene