Re: [dispatch] [AVT] Proposal to form Internet Wideband Audio Codec WG

Jean-Marc Valin <jean-marc.valin@octasic.com> Wed, 03 June 2009 18:47 UTC

Return-Path: <jean-marc.valin@octasic.com>
X-Original-To: dispatch@core3.amsl.com
Delivered-To: dispatch@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D35343A6E68; Wed, 3 Jun 2009 11:47:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.449
X-Spam-Level:
X-Spam-Status: No, score=-1.449 tagged_above=-999 required=5 tests=[AWL=1.150, 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 kKgfbGD7tXVL; Wed, 3 Jun 2009 11:47:38 -0700 (PDT)
Received: from MAILEXCH.octasic.com (mail.octasic.com [216.208.79.2]) by core3.amsl.com (Postfix) with ESMTP id B5B553A6E35; Wed, 3 Jun 2009 11:47:38 -0700 (PDT)
Received: from [142.138.24.19] ([142.138.24.19]) by MAILEXCH.octasic.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 3 Jun 2009 14:47:35 -0400
Message-ID: <4A26C563.8030200@octasic.com>
Date: Wed, 03 Jun 2009 14:48:03 -0400
From: Jean-Marc Valin <jean-marc.valin@octasic.com>
User-Agent: Thunderbird 2.0.0.21 (X11/20090409)
MIME-Version: 1.0
To: jmh@joelhalpern.com
References: <021701c9e030$0a5deef0$1f19ccd0$%roni@huawei.com> <021201c9e46e$c1459c70$43d0d550$%roni@huawei.com>
In-Reply-To: <021201c9e46e$c1459c70$43d0d550$%roni@huawei.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 03 Jun 2009 18:47:35.0055 (UTC) FILETIME=[C26921F0:01C9E47B]
X-Mailman-Approved-At: Wed, 03 Jun 2009 12:14:57 -0700
Cc: dispatch@ietf.org, avt@ietf.org, Roni Even <Even.roni@huawei.com>
Subject: Re: [dispatch] [AVT] Proposal to form Internet Wideband Audio Codec WG
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jun 2009 18:47:39 -0000

> So far, what strikes me is that most of the folks who would be called 
> upon to evaluate a requirements document, or an actual protocol, have 
> little or no expertise in codec design either from a mathematical or a 
> software perspective (there are a few exceptions in both those 
> regards, folks like Henning), and have little or no experience in the 
> observed difficulties in actually standardizing codecs. (Folks I ahve 
> talked to who have been down that road have indicated that it involves 
> many aspects that are foreign to IETF experience and practice.) 

Let me start by stating that codec design is no rocket science. There 
are many people out there who know how to write audio codecs and many 
more who have sufficient skills to contribute. At this point, there is 
already interest from several people with actual codec design experience 
at Skype, Xiph.Org and SPIRIT. The internet community has clear and 
considerable needs which are not being adequately met by the existing 
standards bodies. We have parties experienced with codec development who 
want to work together within the IETF. Why do you believe the risk of 
not succeeding justifies not even attempting the effort?

Cheers,

    Jean-Marc