Re: [codec] draft test and processing plan for the IETF Codec
Stephen Botzko <stephen.botzko@gmail.com> Wed, 13 April 2011 17:57 UTC
Return-Path: <stephen.botzko@gmail.com>
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 4D8E0E07DA for <codec@ietfc.amsl.com>; Wed, 13 Apr 2011 10:57:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 h1G6XHJgWQ1Q for <codec@ietfc.amsl.com>; Wed, 13 Apr 2011 10:57:35 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfc.amsl.com (Postfix) with ESMTP id 4758BE0848 for <codec@ietf.org>; Wed, 13 Apr 2011 10:57:35 -0700 (PDT)
Received: by vxg33 with SMTP id 33so817355vxg.31 for <codec@ietf.org>; Wed, 13 Apr 2011 10:57:35 -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=u9ojaoXiXQI+R6ht5FGrGA1JlhPFLxSDPGug3akTR7k=; b=tsrtIuPVUDFGioy+Fw8PDVSfh/uIvVcOhJEU95tP3SZUGQtFd49AxWlPRsOzlsutNZ GIkjlvpImzZrGTHDrNuP7Xy+/UVpEafVI5rBe+itpq1bAn5fg6q3A/jEmV4rFIBuPC03 KbGICLGpSvOjSU5umAp8WU7YTQVFxkrtkBioY=
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=ImRcWEeJbbThxmcr3nMviBYc6XH5oLOCHVLAh8TCP4NxqkusW2GkgpxYKUuddT+RLd /R9AYETlTKKvfRPmAkLeQCX/JthRQxA67L6DO068g4OA4lYEnzMi2f2C9nIymbkUuJEb POn7R+XUyk5Cr9yPbGZu5mTh9tuy4Ehi5RJ6A=
MIME-Version: 1.0
Received: by 10.52.172.2 with SMTP id ay2mr2772421vdc.50.1302717454919; Wed, 13 Apr 2011 10:57:34 -0700 (PDT)
Received: by 10.220.166.14 with HTTP; Wed, 13 Apr 2011 10:57:34 -0700 (PDT)
In-Reply-To: <4DA5D328.3060504@stpeter.im>
References: <F5AD4C2E5FBF304ABAE7394E9979AF7C26BC684E@LHREML503-MBX.china.huawei.com> <4DA5A748.2050401@fas.harvard.edu> <027A93CE4A670242BD91A44E37105AEF17ACA9B583@ESESSCMS0351.eemea.ericsson.se> <4DA5D328.3060504@stpeter.im>
Date: Wed, 13 Apr 2011 13:57:34 -0400
Message-ID: <BANLkTi=DkC8HFSFzQ8q=xWU+zVL7D_aazA@mail.gmail.com>
From: Stephen Botzko <stephen.botzko@gmail.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: multipart/alternative; boundary="bcaec53f2ae724a9be04a0d08bc3"
Cc: "bens@alum.mit.edu" <bens@alum.mit.edu>, "codec@ietf.org" <codec@ietf.org>
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: Wed, 13 Apr 2011 17:57:36 -0000
in-line Stephen On Wed, Apr 13, 2011 at 12:45 PM, Peter Saint-Andre <stpeter@stpeter.im>wrote: > On 4/13/11 8:48 AM, Erik Norvell wrote: > > Hi Ben, all > > > > If the codec is not ready for testing, then I cannot see how it could > > be ready for standardization. To me the steps would be > > > > - freeze the codec when it is stable - test and evaluate - check if > > requirements are met a) if yes standardize b) if not do not > > standarize and rather go back and improve > > > > Informal testing should still be done during development to eliminate > > the risk of b). > > My understanding is that informal testing has already been done by quite > a few participants in this WG. > Yes, and Erik is simply suggesting that should continue while the codec development is underway. > > > I also think the encumbrance of the codec is unclear at this point > > and I don't think rushing to finalize the standard would serve the > > purpose of this WG. Due to the encumbrance there may still be changes > > required which may affect the quality, and the final testing should > > begin after this has been resolved. > > We knew when we started this process that there might be encumbrances. > We even knew that there might be unreported encumbrances that would > emerge only after the codec was published as an RFC, or only after the > code was in use by companies who would be big targets for patent > lawsuits. I see no reason to delay publication until all possible > encumbrances have been resolved, whatever that means (as we all know, > patent claims are not resolved at the IETF, they are resolved in courts > of law). > I think Erik was simply referring to the ongoing work already started by the codec developers [whatever-it-is that is being done in response to the Qualcomm declaration]. It sounds like you are suggesting this work should be halted, and we should simply publish the current codec version??? It would be interesting to know who else would agree with that proposal. > > Peter > > -- > Peter Saint-Andre > https://stpeter.im/ > > > > > _______________________________________________ > codec mailing list > codec@ietf.org > https://www.ietf.org/mailman/listinfo/codec > >
- [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