Re: [codec] A concrete proposal for requirements and testing
Stephen Botzko <stephen.botzko@gmail.com> Thu, 07 April 2011 18:47 UTC
Return-Path: <stephen.botzko@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 844443A696A for <codec@core3.amsl.com>; Thu, 7 Apr 2011 11:47:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.777
X-Spam-Level:
X-Spam-Status: No, score=-2.777 tagged_above=-999 required=5 tests=[AWL=-0.179, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 KacbH+RINc7O for <codec@core3.amsl.com>; Thu, 7 Apr 2011 11:47:34 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id E05903A696D for <codec@ietf.org>; Thu, 7 Apr 2011 11:47:33 -0700 (PDT)
Received: by vxg33 with SMTP id 33so2632068vxg.31 for <codec@ietf.org>; Thu, 07 Apr 2011 11:49:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=zUWYOBD2Ouii1EsSaumBAKwN0Izrg55yqrmtROvonLs=; b=m2CwRP1/OFtJiGOh4GI23+z/YGtzq7SYDAygmyvEeCZvpIzYnpI4sZP0kIhBHIJFL3 KdGqknp/duq3LwH3oAycznE0KYevbvErB+PaXf7oYedN0e4aRnOAXI3ZzCDLSBfSihB4 i2QbY5kBDX7jJym57BSkFZP45n/WmV+fFw/Uc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=M7aaiNwwZNA28nZCNB6q3SYWrHIbUCrFa9E1by8yXJAMQffpieUCvlfHxql6d0S6BC KtzX4EV26EctUoeOP2YXQjN58nYdItaudCnAacXaFMUXQvYi3Wk/Za6aadBnIB483IWQ SG9eKuDCJx+21H629C6TbG+NwgG7/ywJjm55k=
MIME-Version: 1.0
Received: by 10.52.0.165 with SMTP id 5mr1847992vdf.7.1302202157946; Thu, 07 Apr 2011 11:49:17 -0700 (PDT)
Received: by 10.220.81.18 with HTTP; Thu, 7 Apr 2011 11:49:17 -0700 (PDT)
In-Reply-To: <4D9E0443.6040703@stpeter.im>
References: <64212FE1AE068044AD567CCB214073F123A10234@MAIL2.octasic.com> <F5AD4C2E5FBF304ABAE7394E9979AF7C26BC47FA@LHREML503-MBX.china.huawei.com> <027A93CE4A670242BD91A44E37105AEF17ACA33C36@ESESSCMS0351.eemea.ericsson.se> <20110407125345.GA30415@audi.shelbyville.oz> <BANLkTimeDEPY8va6_MQVztn3YGyTZ2LmVw@mail.gmail.com> <20110407164817.GB30415@audi.shelbyville.oz> <BLU0-SMTP522E3F60CF41CCB8108C96D0A40@phx.gbl> <4D9E0443.6040703@stpeter.im>
Date: Thu, 07 Apr 2011 14:49:17 -0400
Message-ID: <BANLkTi=C2m8MmP26FxW=UTGB+4y6AOMYsA@mail.gmail.com>
From: Stephen Botzko <stephen.botzko@gmail.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: multipart/alternative; boundary="20cf304347060ce85404a0589175"
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 18:47:35 -0000
Early on there was consensus on the need for codec characterization. I see no reason to have that discussion again, I suggest it would be better to get back on track and work through what a sensible test plan would include. Stephen Botzko On Thu, Apr 7, 2011 at 2:36 PM, Peter Saint-Andre <stpeter@stpeter.im>wrote: > On 4/7/11 12:13 PM, Paul Coverdale wrote: > > > It doesn't matter what any single individual on this mailing list thinks > > about Opus quality. What matters is the collective opinion of the > population > > of naïve users who may listen to speech/music over Opus in the future, > and > > how they rate it compared to listening to speech/music via other codecs > (not > > that they will know/care what a codec is...). A well-designed test plan > and > > statistical analysis can give a good estimate of this opinion. > > I completely agree. That's why it is so important for us to publish > draft-ietf-codec-opus as a Proposed Standard. > > The IETF tradition is one of "rough consensus and running code". What > this means is that we work hard on a new technology and publish it as an > RFC ("request for comments"). This is the rough consensus part. > > Then we implement it and deploy it. Testing is something that happens > naturally when we run a technology on networks. This is the "running > code" part. > > Implementation and deployment experience can lead to revisions and > refinements and better specification of the technology. Of course we'll > also seek rough consensus on any modifications, but it's not necessary, > or even desirable, to get that implementation and deployment experience > before we publish a specification as a Proposed Standard RFC. > > Indeed, much discussion has occurred of late within the IETF about > simplifying the Internet Standards Process by making it easier, not > harder, to advance Internet-Drafts to Proposed Standard: > > https://datatracker.ietf.org/doc/draft-housley-two-maturity-levels/ > > Let's get to rough consensus and then start running this code on the > network. That will be the true test. > > Peter > > -- > Peter Saint-Andre > https://stpeter.im/ > > > >
- [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