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

Joel Jaeggli <joelja@bogus.com> Wed, 06 January 2010 04:45 UTC

Return-Path: <joelja@bogus.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 4DEE33A680A; Tue, 5 Jan 2010 20:45:52 -0800 (PST)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zvrTUxqineI6; Tue, 5 Jan 2010 20:45:51 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [147.28.0.81]) by core3.amsl.com (Postfix) with ESMTP id 859CC3A63EB; Tue, 5 Jan 2010 20:45:51 -0800 (PST)
Received: from [192.168.1.151] (c-98-234-104-156.hsd1.ca.comcast.net [98.234.104.156]) (authenticated bits=0) by nagasaki.bogus.com (8.14.3/8.14.3) with ESMTP id o064j3uv038279 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 6 Jan 2010 04:45:45 GMT (envelope-from joelja@bogus.com)
Message-ID: <4B44154E.6070007@bogus.com>
Date: Tue, 05 Jan 2010 20:45:02 -0800
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
References: <4b33100a.01135e0a.2ab9.ffff8e9b@mx.google.com> <3D3C75174CB95F42AD6BCC56E5555B450204C143@FIESEXC015.nsn-intra.net> <20091223171501.7BAE33A697D@core3.amsl.com> <14093.1261593597@epsilon.noi.kre.to> <14853.1261600779@epsilon.noi.kre.to> <2401.1261648036@epsilon.noi.kre.to> <4b3373d7.02135e0a.241a.fffffb62@mx.google.com> <a123a5d60912241926l6f2255e3kc15d1d21573adeb9@mail.gmail.com> <B67FB114-FDA9-4431-A2E2-6ACF344B2EA7@cisco.com> <tslpr5p4hor.fsf@mit.edu> <024e01ca8da8$727e6a70$577b3f50$@us> <4b4380c6.0e1abc0a.5a80.ffffcd97@mx.google.com> <4B44119A.6020904@stpeter.im>
In-Reply-To: <4B44119A.6020904@stpeter.im>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (nagasaki.bogus.com [147.28.0.81]); Wed, 06 Jan 2010 04:45:47 +0000 (UTC)
X-Mailman-Approved-At: Wed, 06 Jan 2010 05:52:08 -0800
Cc: ietf@ietf.org, kre@munnari.oz.au, 'Sam Hartman' <hartmans-ietf@mit.edu>, codec@ietf.org, 'Richard Shockey' <richard@shockey.us>, ik Fältström' <paf@cisco.com>, iesg@ietf.org, 'Patr, 'Phillip Hallam-Baker' <hallam@gmail.com>
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: Wed, 06 Jan 2010 04:45:52 -0000

Peter Saint-Andre wrote:
> But I don't think we can say that relevent members of the IETF community
> do *not* have the competence to work on an audio codec or that they are
> *not* willing to listen to technically competent input from any source
> when it comes to codec technologies. Indeed, the two BoFs at Stockholm
> and Hiroshima would lead, I think, to the opposite conclusion: the
> people who want to do this work appear to be competent (they have
> already developed codecs like Speex, CELT, SILK, IPMR, BV16, and BV32)
> and to be quite committed to rough consensus and running code, we have
> some precedent for doing work of this kind within the IETF (e.g., RFC
> 3951), several longtime IETF participants have experience with digital
> signal processing and similar technologies, a codec working group would
> attract new participants with relevant areas of expertise, and people at
> the BoFs appeared to be quite open to input from the IETF community or
> any interested individual.

+1

This is work we've done before and there seems to be no particular
reason that it should not be done here again.