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

"Roni Even" <ron.even.tlv@gmail.com> Thu, 24 December 2009 06:54 UTC

Return-Path: <ron.even.tlv@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 7256B3A68C2; Wed, 23 Dec 2009 22:54:25 -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=[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 aw+EqdPbByWp; Wed, 23 Dec 2009 22:54:25 -0800 (PST)
Received: from mail-fx0-f215.google.com (mail-fx0-f215.google.com [209.85.220.215]) by core3.amsl.com (Postfix) with ESMTP id B75B43A688C; Wed, 23 Dec 2009 22:54:24 -0800 (PST)
Received: by fxm7 with SMTP id 7so7593836fxm.29 for <multiple recipients>; Wed, 23 Dec 2009 22:54:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references :in-reply-to:subject:date:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:content-language; bh=f72bK9O2Weez2aKr4E3VEMvZbvvcpV+QxFGRLNUMDjI=; b=RUCqbktuDR7QKMzqg+S2OGAeBvp/ArO5jsPAc+u8U49CXVMBF44q2rkkwWZoB3fad8 WC0Tzp+xdv3HtTqt8Twf5hsMlK9wmTOZ1gHtq4NO6qVb/ViOaM46YpJ0l+TyRDWjEnku CHwEJX6/BuBrSyBVJcSr81qwRqG1KjqmCkv4M=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; b=OwhCS7h84tLyxa1oyeAi6IxUM9ZJEJTBaP/UPwcBkc3sTFXBdGfNKX4zu+jYMxTKU3 QlWi44/spgY+STttery8IO+heaflJ4eB0mUt0Kj5/KbJFxvGas7eVRgnSRpEHzxXZqPI Qtmb6Bm7rdI3/R5zea0LJOayEVNl5VVCfGVDg=
Received: by 10.223.110.32 with SMTP id l32mr4151715fap.90.1261637643523; Wed, 23 Dec 2009 22:54:03 -0800 (PST)
Received: from windows8d787f9 (bzq-82-81-132-18.red.bezeqint.net [82.81.132.18]) by mx.google.com with ESMTPS id 1sm7139780fks.59.2009.12.23.22.54.01 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 23 Dec 2009 22:54:02 -0800 (PST)
From: Roni Even <ron.even.tlv@gmail.com>
To: 'Robert Elz' <kre@munnari.OZ.AU>, "'Tschofenig, Hannes (NSN - FI/Espoo)'" <hannes.tschofenig@nsn.com>
References: <3D3C75174CB95F42AD6BCC56E5555B450204C143@FIESEXC015.nsn-intra.net> <20091223171501.7BAE33A697D@core3.amsl.com> <14093.1261593597@epsilon.noi.kre.to> <14853.1261600779@epsilon.noi.kre.to>
In-Reply-To: <14853.1261600779@epsilon.noi.kre.to>
Date: Thu, 24 Dec 2009 08:50:30 +0200
Message-ID: <4b33100a.01135e0a.2ab9.ffff8e9b@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-index: AcqEEF215VwqapPNTgSSar+KGaBFqgAU6BkA
Content-language: en-us
Cc: codec@ietf.org, iesg@ietf.org, ietf@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
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, 24 Dec 2009 06:54:25 -0000

Hi,
I am not sure but are you suggesting that the IETF will define the
requirements, metric and quality assessment requirements and all proposed
codecs should provide the results and then the WG will choose the best codec
bases without discussing the codec itself. This is what I would call a
selection process (at least in ITU terms).
The problem is that the IETF process allows anyone to contribute to existing
work hopefully leading to a better the end result. 
What about the change control, does it stay with the original contributor or
can the IETF modify the codec based on input from other parties, which means
that the codec may change by the IETF anyhow. 
Thanks
Roni Even

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Robert Elz
> Sent: Wednesday, December 23, 2009 10:40 PM
> To: Tschofenig, Hannes (NSN - FI/Espoo)
> Cc: iesg@ietf.org; ietf@ietf.org
> Subject: Re: WG Review: Internet Wideband Audio Codec (codec)
> 
>     Date:        Wed, 23 Dec 2009 21:48:18 +0200
>     From:        "Tschofenig, Hannes (NSN - FI/Espoo)"
> <hannes.tschofenig@nsn.com>
>     Message-ID:
> <3D3C75174CB95F42AD6BCC56E5555B450204C143@FIESEXC015.nsn-intra.net>
> 
>   | That's something for the working group to figure out.
>   | My experience: things are typically more complicated than they
> initially
>   | look like.
> 
> Yes, of course, but the proposed charter goes to great lengths to point
> out why solutions from the first and third of the three categories of
> existing codecs are no good, but it more or less ignored the middle
> category - then, it seemed to me, more or less demanded that a new
> codec
> (or perhaps codecs) be developed.
> 
> That's the wrong approach, the emphasis should be on adopting something
> that exists, if at all possible, and only inventing something new if
> there really is no other choice.
> 
> That's why I'd prefer the charter to be revised with that in mind.
> 
>   | WG charters are also written for those who have not followed the
> history
>   | of the work very closely. These folks typically need a bit more
>   | background information.
> 
> Yes, but no-one needs that much ... (no need to delete all of that
> stuff about encumbered technology, just most of it)
> 
> kre
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf