IETF Logo Mail Archive

Re: [codec] #16: Multicast?

"Raymond (Juin-Hwey) Chen" <rchen@broadcom.com> Wed, 12 May 2010 18:48 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 35A7A3A6B78 for <codec@core3.amsl.com>; Wed, 12 May 2010 11:48:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.038
X-Spam-Level: *
X-Spam-Status: No, score=1.038 tagged_above=-999 required=5 tests=[AWL=-1.263, BAYES_50=0.001, MANGLED_WRLDWD=2.3]
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 O2rBKiEC52fg for <codec@core3.amsl.com>; Wed, 12 May 2010 11:48:52 -0700 (PDT)
Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by core3.amsl.com (Postfix) with ESMTP id C155328C2B5 for <codec@ietf.org>; Wed, 12 May 2010 11:28:58 -0700 (PDT)
Received: from [10.9.200.131] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Wed, 12 May 2010 11:28:39 -0700
X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201
Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.31]) by IRVEXCHHUB01.corp.ad.broadcom.com ([10.9.200.131]) with mapi; Wed, 12 May 2010 11:28:39 -0700
From: "Raymond (Juin-Hwey) Chen" <rchen@broadcom.com>
To: Cullen Jennings <fluffy@cisco.com>
Date: Wed, 12 May 2010 11:28:37 -0700
Thread-Topic: [codec] #16: Multicast?
Thread-Index: Acrx49plujeniwH8SDWDM1aXftrgHwAGhC9g
Message-ID: <CB68DF4CFBEF4942881AD37AE1A7E8C74B9043D30B@IRVEXCHCCR01.corp.ad.broadcom.com>
References: <062.7439ee5d5fd36480e73548f37cb10207@tools.ietf.org> <3E1D8AD1-B28F-41C5-81C6-478A15432224@csperkins.org> <D6C2F445-BE4A-4571-A56D-8712C16887F1@americafree.tv> <C0347188-A2A1-4681-9F1E-0D2ECC4BDB3B@csperkins.org> <u2x6e9223711004210733g823b4777y404b02330c49dec1@mail.gmail.com> <000001cae173$dba012f0$92e038d0$@de> <r2q6e9223711004211010gfdee1a70q972e8239fef10435@mail.gmail.com> <001101cae177$e8aa6780$b9ff3680$@de> <t2t6e9223711004211119i6b107798pa01fc4b1d33debf1@mail.gmail.com> <002d01cae188$a330b2c0$e9921840$@de> <CB68DF4CFBEF4942881AD37AE1A7E8C74AB3F4A017@IRVEXCHCCR01.corp.ad.broadcom.com> <4BD11C50.2020206@usherbrooke.ca> <CB68DF4CFBEF4942881AD37AE1A7E8C74AB3F4A270@IRVEXCHCCR01.corp.ad.broadcom.com> <12151537-165D-426A-B71F-8B3D76BE4854@cisco.com> <CB68DF4CFBEF4942881AD37AE1A7E8C74B901372FE@IRVEXCHCCR01.corp.ad.broadcom.com> <20100430230756.13687lc1s5o89gsc@mail.skype.net> <CB68DF4CFBEF4942881AD37AE1A7E8C74B90345522@IRVEXCHCCR01.corp.ad.broadcom.com> <07C815A7-8F3C-4F85-A275-4352D0080EEA@cisco.com>
In-Reply-To: <07C815A7-8F3C-4F85-A275-4352D0080EEA@cisco.com>
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: 67F42CDD31G123459208-01-01
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: "codec@ietf.org" <codec@ietf.org>
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: Wed, 12 May 2010 18:48:53 -0000

Hi Cullen,

Hmm... That's interesting.  Would you please share more details of 
your measurement equipment setup, the codec used, the codec frame 
size, the number of codec frames in each packet, the way you 
measured the delay, and the measured delay value, etc.?  

I didn't come up with this 3*(codec frame size) delay number for IP 
phones myself.  A very senior technical lead in Broadcom's IP phone 
chips group told me that, and Broadcom is currently the #1 world-
wide market share leader in IP phone chips, accounting for more than 
half of the world's IP phone chip shipments. Most of the world's 
tier-1 IP phone manufacturers use our IP phone chips at least in 
some of their product lines.

I would be very interested to learn more about your measurements to 
try to reconcile these seemingly contradictory statements from two 
different sources.  Thanks.

Best Regards,

Raymond

-----Original Message-----
From: Cullen Jennings [mailto:fluffy@cisco.com] 
Sent: Wednesday, May 12, 2010 8:00 AM
To: Raymond (Juin-Hwey) Chen
Cc: Koen Vos; codec@ietf.org
Subject: Re: [codec] #16: Multicast?


On May 4, 2010, at 7:15 PM, Raymond (Juin-Hwey) Chen wrote:

> the 3*(codec frame size) delay is very real for IP phone

This does not match the measurements I have. And I certainly don't have 100+ year voip experience but I do have two of the #1 selling enterprise phones connected to an oscilloscope. Test with other phones suggest most the major vendors of IP hard phones have fairly comparable performance when it comes to delay. 
 

Cullen

v2.30.2 | Report a Bug | By Email | System Status