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

Adrian Farrel <Adrian.Farrel@huawei.com> Tue, 12 January 2010 12:16 UTC

Return-Path: <Adrian.Farrel@huawei.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 8B8C83A69AA; Tue, 12 Jan 2010 04:16:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.533
X-Spam-Level:
X-Spam-Status: No, score=-2.533 tagged_above=-999 required=5 tests=[AWL=0.066, 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 CvmTFcj+L1Xg; Tue, 12 Jan 2010 04:16:34 -0800 (PST)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211]) by core3.amsl.com (Postfix) with ESMTP id 425C53A69BA; Tue, 12 Jan 2010 04:16:34 -0800 (PST)
Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KW400KNFVFJ1K@usaga01-in.huawei.com>; Tue, 12 Jan 2010 04:16:31 -0800 (PST)
Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KW40035OVFHZR@usaga01-in.huawei.com>; Tue, 12 Jan 2010 04:16:31 -0800 (PST)
Date: Tue, 12 Jan 2010 12:14:18 +0000
From: Adrian Farrel <Adrian.Farrel@huawei.com>
To: Stefan Sayer <stefan.sayer@iptego.com>
Message-id: <8903A80C339345EA82F3AEB33F708840@your029b8cecfe>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
Content-type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="response"
Content-transfer-encoding: 7bit
X-Priority: 3
X-MSMail-priority: Normal
References: <20091223171501.7BAE33A697D@core3.amsl.com> <13194D66-2110-4CB2-B130-8807BE57488B@cisco.com> <458913681001111218o3b232e4sd785b3c09809fcbc@mail.gmail.com> <4B4C46E0.8020609@iptego.com>
Cc: IAB IAB <iab@iab.org>, codec@ietf.org, IETF Discussion <ietf@ietf.org>, IESG IESG <iesg@ietf.org>
Subject: Re: [codec] WG Review: Internet Wideband Audio Codec (codec)
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <Adrian.Farrel@huawei.com>
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: Tue, 12 Jan 2010 12:16:36 -0000

Stefan,

> until now other SDOs have failed to produce a widely distributed good 
> quality wideband and full-band codec that would be suitable for the 
> Internet - especially one that is easily distributable - even though the 
> necessary technology has been available for a long time. Further, nothing 
> has substantially changed lately to make it likely that other SDOs are now 
> suddenly willing to or capable of doing that.
>
> The proposal to make IETF CODEC development depend on other SDOs is thus 
> not a constructive one and should not be followed.

Your logic may be flawed.

Until now the IETF has failed to produce a widely distributed good
 quality wideband and full-band codec that would be suitable for the
 Internet - especially one that is easily distributable - even though the
 necessary technology has been available for a long time.

But you don't suggest that as a reason not to do the work in the IETF.

The proposed draft charter does not state that the IETF work should be gated 
on other SDOs nor that the IETF shall not develop a Codec. Rather, it states 
the value of sharing the requirements work developed in the IETF with other 
SDOs, and it notes the benefits of listening to other SDOs if they point to 
existing Codecs that meet or nearly meet the requirements.

In the unlikely event that another SDO says "thanks for the requirements we 
would like to develop a solution in our SDO" we will need to examine the 
feasibility of their proposal and how people can best work on a solution. 
There does not seem to be any benefit in developing two Codecs to meet the 
same set of requirements.

As to Xavier's point: I think he is right that the wording in the charter 
could be usefully re-ordered so that the consultation is mentioned before 
the determination to develop a new solution.

Cheers,
Adrian