Re: [codec] WG Review: Internet Wideband Audio Codec (codec)

stephen botzko <stephen.botzko@gmail.com> Thu, 21 January 2010 15:03 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 B7B573A68DB; Thu, 21 Jan 2010 07:03:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[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 R1Jg40DZEwcs; Thu, 21 Jan 2010 07:03:00 -0800 (PST)
Received: from gv-out-0910.google.com (gv-out-0910.google.com [216.239.58.190]) by core3.amsl.com (Postfix) with ESMTP id D94E73A697E; Thu, 21 Jan 2010 07:02:59 -0800 (PST)
Received: by gv-out-0910.google.com with SMTP id c17so373gvd.15 for <multiple recipients>; Thu, 21 Jan 2010 07:02:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=TQzrGIrCoR5ryGOytz5WN95LoycRgcP3aenOgyaWiRA=; b=QB3fJA23hNZAsaJNEiYm55lIAG+4V3bgMkrb7YHA/ER+qz+IjngkdCefM6KjqhWNUB VvvNClKe4Obz76Gk4XPoOvtVFbYkFbz7ZC8tkwoTfo6Dwmq8xd8l/aMN+fu2oGxH10XG JpUme7iNOy1hm40Q/Ju1EjRhMUrx2vfajpDGI=
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=nzhTbhic+qYEaXiv6j2zqzZCKRU7gJvgbkxncqOr9Cb19XkZp8q+uMpKIcI7jBL3dm tIedXtMRrVY3zL973CuNCec8aRRHXwMZGyl19BfiAuULaSIupKopHlMvxWpzQVbs6yAb tQ1N+geChyDXHOa4RskyYb3KGl7aQuZz8DY4Y=
MIME-Version: 1.0
Received: by 10.102.183.10 with SMTP id g10mr806867muf.40.1264086172205; Thu, 21 Jan 2010 07:02:52 -0800 (PST)
In-Reply-To: <20100121143940.GD19558@audi.shelbyville.oz>
References: <4b3373d7.02135e0a.241a.fffffb62@mx.google.com> <B67FB114-FDA9-4431-A2E2-6ACF344B2EA7@cisco.com> <130EBB38279E9847BAAAE0B8F9905F8C02959C6B@esealmw109.eemea.ericsson.se> <20100121000303.GA1250@besserwisser.org> <130EBB38279E9847BAAAE0B8F9905F8C02959FE1@esealmw109.eemea.ericsson.se> <20100121121352.GD1250@besserwisser.org> <130EBB38279E9847BAAAE0B8F9905F8C0295A258@esealmw109.eemea.ericsson.se> <6e9223711001210509k1bc134bav224a619971d04a77@mail.gmail.com> <22948_1264081478_4B585A46_22948_6286_1_4D1AA2A55522044480C9B9CF97A9340999F1EB@ftrdmel0.rd.francetelecom.fr> <20100121143940.GD19558@audi.shelbyville.oz>
Date: Thu, 21 Jan 2010 10:02:52 -0500
Message-ID: <6e9223711001210702xf1fa693j677213bcbc98e615@mail.gmail.com>
From: stephen botzko <stephen.botzko@gmail.com>
To: Ron <ron@debian.org>
Content-Type: multipart/alternative; boundary="0016364175974283c7047dadff57"
Cc: ietf@ietf.org, codec@ietf.org, ingemar.s.johansson@ericsson.com, iesg@ietf.org, mansaxel@besserwisser.org
Subject: Re: [codec] WG Review: Internet Wideband Audio Codec (codec)
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Should the IETF standardize wideband Internet codec\(s\)? " <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, 21 Jan 2010 15:03:01 -0000

Hi Ron

I agree there's been discussion about existing codecs, and most of it has
been helpful and constructive.

But until the detailed requirements have been determined, I don't think it
is very fruitful to continue it.

IMHO we'll need those details to be more precisely stated (and agreed to) in
order to take this to the next level.  It'd be most efficient to do the
formal assessment only once.

Stephen Botzko
Polycom


On Thu, Jan 21, 2010 at 9:39 AM, Ron <ron@debian.org> wrote:

> On Thu, Jan 21, 2010 at 02:44:36PM +0100,
> stephane.proust@orange-ftgroup.com wrote:
> > In line as well : The first stage of the work has not been done yet : the
> > detailed technical requirements have not been defined and agreed yet, the
> > second stage of the work with other SDOs to analyse if already exiting
> codecs
> > meet these requirements is not done and yet the Charter on the basis of
> which
> > this WG could be launched is formulated as if the conclusion resulting
> from
> > this 2 stages was known and obvious : no existing codec is suitable and
> so a
> > new codec is needed
> >
> > so, again : only these first 2 steps (requirement definition and standard
> > analysis) are, at this stage, relevant to start a WG since the next steps
> > depend on the conclusion of this work.
> >
> > for instance , there could be some middle way between developping a new
> codec
> > and reusing an existing standard : it could be much more efficient to
> simply
> > extend/adapt an existing standard and, to achieve this, it would be
> better to
> > rely on the SDO that have standardized this codec.
>
> Potential candidate codecs have been discussed since the very first BoF,
> and surely before.  We have plenty of representatives from other SDOs
> present in the group, so my question is, if such codecs exist, then surely
> they should be put up, if not as contenders, then as baseline measures of
> best practice in some matter or another.  Why hasn't that happened?
>
> With the exception of a few "G.711 should be enough for anyone" jokes,
> I haven't seen anyone present a "this can already do what you want" codec
> that the group hasn't responded with "we can (already) do better than
> that".
>
> If there are other codecs that we should have to measure up against, then
> indeed I'd warmly welcome other SDOs to make their best suggestions soon,
> for consideration during the next stage of work.  Anything you think puts
> one of the existing candidates to shame in some aspect or another, would
> certainly be a valuable and practical measuring stick we can use.
>
> I'm pretty sure a lot of people have already done many of these
> measurements
> for themselves.  We just need to whittle that down to the ones that give us
> useful bars to raise.  Which ones are we missing still?
>
> Cheers,
> Ron
>
>
>