Re: [codec] this weeks summary
"Raymond (Juin-Hwey) Chen" <rchen@broadcom.com> Mon, 10 May 2010 20:07 UTC
Return-Path: <rchen@broadcom.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 C299C3A69AA for <codec@core3.amsl.com>; Mon, 10 May 2010 13:07:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.109
X-Spam-Level:
X-Spam-Status: No, score=-0.109 tagged_above=-999 required=5 tests=[AWL=-0.110, BAYES_50=0.001]
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 o5XSbjkO7iiR for <codec@core3.amsl.com>; Mon, 10 May 2010 13:06:59 -0700 (PDT)
Received: from mms1.broadcom.com (mms1.broadcom.com [216.31.210.17]) by core3.amsl.com (Postfix) with ESMTP id 2333E3A6A94 for <codec@ietf.org>; Mon, 10 May 2010 12:58:12 -0700 (PDT)
Received: from [10.9.200.131] by mms1.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Mon, 10 May 2010 12:57:53 -0700
X-Server-Uuid: 02CED230-5797-4B57-9875-D5D2FEE4708A
Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.31]) by IRVEXCHHUB01.corp.ad.broadcom.com ([10.9.200.131]) with mapi; Mon, 10 May 2010 12:57:53 -0700
From: "Raymond (Juin-Hwey) Chen" <rchen@broadcom.com>
To: Christian Hoene <hoene@uni-tuebingen.de>, "codec@ietf.org" <codec@ietf.org>
Date: Mon, 10 May 2010 12:57:51 -0700
Thread-Topic: [codec] this weeks summary
Thread-Index: AcrvouSxwCvhij/GQOaYD+wavcY/SwA0ddGw
Message-ID: <CB68DF4CFBEF4942881AD37AE1A7E8C74B90345E60@IRVEXCHCCR01.corp.ad.broadcom.com>
References: <002e01caefa2$ef88c9a0$ce9a5ce0$@de>
In-Reply-To: <002e01caefa2$ef88c9a0$ce9a5ce0$@de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 67F6BACB20S120629110-01-01
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [codec] this weeks summary
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 20:07:00 -0000
Hi Christian, > Raymond did a great job explaining the special requirements of high-density > VoIP gateway. They are differ substantially to those of > soft-phones (but are somewhat similar to VoIP phones with embedded CPUs). The > requirements include low memory footprint, ultra-low > delay, low complexity and mostly narrow band. But aren't those requirements > already covered by existing codecs? Shall this working > group provide a codec profile for end-to-gateway beside the profile for an > end-to-end codec? [Raymond]: Which existing codecs satisfy all these requirements and the three conditions listed at the beginning of the IETF codec WG charter? Also, we are not talking about an additional codec profile for "end-to-gateway"; no, what we are talking about is just part of the "IPend-to-transcoding_gateway-to-PSTNend" scenario that you listed in one of your original emails that discussed the codec requirements. > SpiritDSP and Christian were discussing the need for layered coding - no > consensus yet... [Raymond]: I think layered coding (or embedded coding) is a nice feature to have. Some of the other SDOs have standardized layered codecs. Besides the pros and cons of layered coding already discussed last week, I think another potential benefit is that as the packets of layer-coded bit-stream traverse the network, higher-layer bits can be stripped off by network nodes to reduce congestion. (This is probably not done, but can be done.) > The week before, we were discussing whether to consider Bluetooth and Wireless > IP as use cases. It seems to be a rough consensus > that wireless IP is in-scope and that Bluetooth is out-of-scope because it > requires too special optimizations. However, battery > powered, wireless devices might require low-complexity and low-bandwidth (and > are in-scope?). [Raymond]: I read an article that says that PC was the big thing in the decade of 1990-2000, Internet was the big thing in the decade of 2000- 2010, and Mobile Internet will be the next big thing in the decade of 2010- 2020. Judging from the recent trends in smart phones, netbooks, and Tablets/iPad, it seems that Mobile Internet indeed will be the next big thing this decade. Given this, I think battery-powered wireless Internet- capable devices should be in-scope, and low codec complexity is an important consideration in these devices.
- [codec] this weeks summary Christian Hoene
- Re: [codec] this weeks summary Raymond (Juin-Hwey) Chen
- Re: [codec] this weeks summary Cullen Jennings
- Re: [codec] this weeks summary Raymond (Juin-Hwey) Chen
- Re: [codec] this weeks summary Michael Knappe