IETF Logo Mail Archive

Re: [codec] #16: Multicast?

"Kevin P. Fleming" <kpfleming@digium.com> Mon, 10 May 2010 19:44 UTC

Return-Path: <kpfleming@digium.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 103AF3A6D45 for <codec@core3.amsl.com>; Mon, 10 May 2010 12:44:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.273
X-Spam-Level:
X-Spam-Status: No, score=-104.273 tagged_above=-999 required=5 tests=[AWL=-0.274, BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 DYO9suDFxaCq for <codec@core3.amsl.com>; Mon, 10 May 2010 12:44:03 -0700 (PDT)
Received: from mail.digium.com (mail.digium.com [216.207.245.2]) by core3.amsl.com (Postfix) with ESMTP id 3340128C272 for <codec@ietf.org>; Mon, 10 May 2010 12:32:52 -0700 (PDT)
Received: from zimbra.digium.internal ([10.24.55.203] helo=zimbra.hsv.digium.com) by mail.digium.com with esmtp (Exim 4.69) (envelope-from <kpfleming@digium.com>) id 1OBYiW-0003xM-IY for codec@ietf.org; Mon, 10 May 2010 14:32:40 -0500
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.hsv.digium.com (Postfix) with ESMTP id 8D531D8024 for <codec@ietf.org>; Mon, 10 May 2010 14:32:40 -0500 (CDT)
Received: from zimbra.hsv.digium.com ([127.0.0.1]) by localhost (zimbra.hsv.digium.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8jJE9ETKdtuS for <codec@ietf.org>; Mon, 10 May 2010 14:32:40 -0500 (CDT)
Received: from [10.24.250.46] (unknown [10.24.250.46]) by zimbra.hsv.digium.com (Postfix) with ESMTPSA id 17275D8023 for <codec@ietf.org>; Mon, 10 May 2010 14:32:40 -0500 (CDT)
Message-ID: <4BE85F57.9040205@digium.com>
Date: Mon, 10 May 2010 14:32:39 -0500
From: "Kevin P. Fleming" <kpfleming@digium.com>
Organization: Digium, Inc.
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100423 Thunderbird/3.0.4
MIME-Version: 1.0
To: codec@ietf.org
References: <062.7439ee5d5fd36480e73548f37cb10207@tools.ietf.org> <001101cae177$e8aa6780$b9ff3680$@de> <t2t6e9223711004211119i6b107798pa01fc4b1d33debf1@mail.gmail.com> <002d01cae188$a330b2c0$e9921840$@de> <CB68DF4CFBEF4942881AD37AE1A7E8C74AB3F4A017@IRVEXCHCCR01.corp.ad.broadcom.com> <4BD11C50.2020206@usherbrooke.ca> <CB68DF4CFBEF4942881AD37AE1A7E8C74AB3F4A287@IRVEXCHCCR01.corp.ad.broadcom.com> <002c01cae939$5c01f400$1405dc00$@de> <CB68DF4CFBEF4942881AD37AE1A7E8C74B903454B3@IRVEXCHCCR01.corp.ad.broadcom.com>, <009901caede1$43f366d0$cbda3470$@de> <BCB3F026FAC4C145A4A3330806FEFDA93AB072BCC6@EMBX01-HQ.jnpr.net> <CB68DF4CFBEF4942881AD37AE1A7E8C74B90345C0D@IRVEXCHCCR01.corp.ad.broadcom.com> <20100507144856.171013mxhy3wdfbc@mail.skype.net> <CB68DF4CFBEF4942881AD37AE1A7E8C74B90345CCF@IRVEXCHCCR01.corp.ad.broadcom.com> <20100509143636.21296os5ryogl1ic@mail.skype.net> <CB68DF4CFBEF4942881AD37AE1A7E8C74B90345E38@IRVEXCHCCR01.corp.ad.broadcom.com>
In-Reply-To: <CB68DF4CFBEF4942881AD37AE1A7E8C74B90345E38@IRVEXCHCCR01.corp.ad.broadcom.com>
X-Enigmail-Version: 1.0.1
OpenPGP: id=05FB8DB2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [codec] #16: Multicast?
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Codec WG <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: Mon, 10 May 2010 19:44:05 -0000

On 05/10/2010 02:11 PM, Raymond (Juin-Hwey) Chen wrote:

> Considering that there are a very large number of Bluetooth headset users and that the current Bluetooth headsets can already be used for making VoIP phone calls, it would be great if the IETF codec can be implemented in future Bluetooth headsets to avoid the additional coding distortion and delay associated with transcoding. However, with that said, I didn't mean to push a "Bluetooth mode" for the IETF codec. I merely wanted to use Bluetooth headset as an example to make a point that a low codec complexity is desirable and a high codec complexity can have negative consequences.

This is all perfectly reasonable, but given the likely timeframe we are
talking about for this codec to be produced and published as a
standards-track RFC, the definition of 'low complexity' in this
discussion is really talking about the 2012-2013 version of 'low
complexity', not today's. It seems highly likely that the MIPS capacity
of the DSPs designed into Bluetooth headsets in 2012 will be vastly
greater than what is used today, if there is an application to take
advantage of the additional MIPS.

I'd hate to see this codec's development constrained in any significant
way by the requirements of a low-complexity device designed in 2009 or
earlier.

-- 
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
skype: kpfleming | jabber: kfleming@digium.com
Check us out at www.digium.com & www.asterisk.org

v2.23.0 | Report a Bug | By Email