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

Alexander Chemeris <Alexander.Chemeris@sipez.com> Wed, 13 January 2010 10:27 UTC

Return-Path: <alexander.chemeris@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 088B93A6AC8; Wed, 13 Jan 2010 02:27:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 r9-SpcyP1dac; Wed, 13 Jan 2010 02:27:19 -0800 (PST)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159]) by core3.amsl.com (Postfix) with ESMTP id 9F2823A6A9B; Wed, 13 Jan 2010 02:27:18 -0800 (PST)
Received: by fg-out-1718.google.com with SMTP id 22so115979fge.13 for <multiple recipients>; Wed, 13 Jan 2010 02:27:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to:cc :content-type; bh=ERPWb5rZ4qwP2dqZzmbR5E7+j253XjMajm7TyaBFbhY=; b=h7kutvE1pBeXCnuquaLVtvCglL/nHHnvndQZBuo12jR+fbcisMlzWuWZJBvYbUVk1I e7OSWcvqKRwh91wHg7oQcCDcV9wdyg9eUK9lxY7PQoN1rVjxUh9PpM/yOBu5yQJmmL3q E6TLoQ9sqUOi+o9Zh7iHzAeGOBBU0lVHTcTeM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=CnV9WHns+DiIWBjKfI4h32FbKoGujxXc4Sfh9HlBAazX5POswwX0bdJ/3+t1s98KsV WNoojBrREUP3jDXITSrD3hKK8Xn7LMMosf1PRzJ/X4tD3bp+FCAzcA8LYgCRCMyPX0WK 0jFGAd8AbWXGZAwi75hzoo4dZp5EGzCQAxBLY=
MIME-Version: 1.0
Sender: alexander.chemeris@gmail.com
Received: by 10.102.14.17 with SMTP id 17mr5924666mun.52.1263378432725; Wed, 13 Jan 2010 02:27:12 -0800 (PST)
In-Reply-To: <000101ca931e$12ea08f0$38be1ad0$@de>
References: <20091223171501.7BAE33A697D@core3.amsl.com> <13194D66-2110-4CB2-B130-8807BE57488B@cisco.com> <458913681001111218o3b232e4sd785b3c09809fcbc@mail.gmail.com> <000101ca931e$12ea08f0$38be1ad0$@de>
From: Alexander Chemeris <Alexander.Chemeris@sipez.com>
Date: Wed, 13 Jan 2010 13:26:52 +0300
X-Google-Sender-Auth: b5bf97199e39db36
Message-ID: <3d032e5d1001130226s2ca789abva75179ea826c7845@mail.gmail.com>
To: Christian Hoene <hoene@uni-tuebingen.de>
Content-Type: text/plain; charset="UTF-8"
Cc: codec@ietf.org, IAB IAB <iab@iab.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
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, 13 Jan 2010 10:27:20 -0000

Hello Christian,

On Tue, Jan 12, 2010 at 03:27, Christian Hoene <hoene@uni-tuebingen.de> wrote:
> Dear Xavior Marjou,
>
>> We fully share the points 1) and 2) stated in the e-mail below from
>> Cullen since implementing and deploying a new codec in networks
>> (gateways, service plate-forms, mediaservers...) and in terminals
>> represents high costs for service providers, manufacturers and chipset
>> providers in terms of development, deployment and testing with risks
>> to create bugs and problems affecting customers. Furthermore, this
>> multiplies the problems of interoperability with already deployed
>> codecs and the transcoding needs to be addressed with related costs
>> (gateways) and quality degradations.
>
> I have heard similar concerns from German traditional telcos, too. However,
> the currently envisioned codec is based on a more Internet like scenario: a
> dumb network and smart end terminal. This means: fewer gateways and less
> transcoding inside the network but smarter end terminals (=phones). Also,
> the codec is intended to be used in an end-to-end fashion with the encoding
> and decoding done at the Internet phones.

This is not entirely right. This codec should be also useful in conference
scenarios, where you have to decode it at conference server and encode
mixed signal again. And if I haven't missed something, this use-case was
explicitly listed in codec requirements.
On the other hand, it was stated in the same requirements, that interoperability
with older codecs is not a goal.

-- 
Regards,
Alexander Chemeris.