Re: [codec] #16: Multicast?

stephen botzko <stephen.botzko@gmail.com> Sat, 01 May 2010 13:31 UTC

Return-Path: <stephen.botzko@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 3EFBC3A6971 for <codec@core3.amsl.com>; Sat, 1 May 2010 06:31:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.798
X-Spam-Level:
X-Spam-Status: No, score=-0.798 tagged_above=-999 required=5 tests=[AWL=-0.800, BAYES_50=0.001, HTML_MESSAGE=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 DI1eyDP598NA for <codec@core3.amsl.com>; Sat, 1 May 2010 06:31:32 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id A0F6F3A694D for <codec@ietf.org>; Sat, 1 May 2010 06:31:26 -0700 (PDT)
Received: by wyb35 with SMTP id 35so799576wyb.31 for <codec@ietf.org>; Sat, 01 May 2010 06:31:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=uJGCnn0Punu6VcXmXSB60QC+Ko/ft7aOxsIpG/fhoTI=; b=kJ+4hNz3scseq3aZ1dT1b3ZXvBGczsZL5b9nsL4G75Wy8OwMVGUvacKTUM+9DdJBtl oNPtj6vxH84GDxM7bUdj6VQjRGFQT8l5wHsqDfckOPu7wKZ9eJk5oPi3lNrDz/H1NJAf wz+1iaV9+RzTyhSh49eaNFTEZnOda/HbmN24w=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=kNAKf4ic1bjG94FgOWdjJjs5p1pb8pIkCScOgzsHn6hufo5YRgibELZOuZNrfOHdlU 8yjJ1ZehPvvOxad4owSUG68tdJ3RKwljmplnxdcGKMSZtzG5QW6TOpBU2HM67HYUhtWM PKIK/xIWMF5cMdI2S0qtadZvwZ+jCgVavwU2Q=
MIME-Version: 1.0
Received: by 10.216.87.194 with SMTP id y44mr3695170wee.157.1272720667048; Sat, 01 May 2010 06:31:07 -0700 (PDT)
Received: by 10.216.28.139 with HTTP; Sat, 1 May 2010 06:31:06 -0700 (PDT)
In-Reply-To: <20100430230756.13687lc1s5o89gsc@mail.skype.net>
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> <CB68DF4CFBEF4942881AD37AE1A7E8C74AB3F4A270@IRVEXCHCCR01.corp.ad.broadcom.com> <12151537-165D-426A-B71F-8B3D76BE4854@cisco.com> <CB68DF4CFBEF4942881AD37AE1A7E8C74B901372FE@IRVEXCHCCR01.corp.ad.broadcom.com> <20100430230756.13687lc1s5o89gsc@mail.skype.net>
Date: Sat, 01 May 2010 09:31:06 -0400
Message-ID: <x2t6e9223711005010631kb53e8d5fmb680b34a43f13416@mail.gmail.com>
From: stephen botzko <stephen.botzko@gmail.com>
To: Koen Vos <koen.vos@skype.net>
Content-Type: multipart/alternative; boundary="0016e6d56693421f630485885f4b"
Cc: 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: Sat, 01 May 2010 13:31:33 -0000

If the frame-size multiplier is due to serialization, then I agree with
Koen's assessment.  In fact on many connections the multiplier would be less
than 1. Dial-up is of course the worst case here, and on those links the
multiplier ought to be close to 2.  Variations due to congestion (and on
some links, polling) are (IMHO) better modeled as jitter.

Gateways are another matter, with the delays being highly dependent on the
product architecture.  Interupt latencies, context switching, bus
architectures, etc. can dominate, so it is totally possible that reducing
the frame size might actually increase the latency (since it increases the
packets per second load on the gateway).  So I agree with Koen on this as
well.

Anecdotal models based on industry experience can be useful guides - though
if we are going to use these models to drive requirements, I'd prefer
something more analytical.

Stephen Botzko

On Sat, May 1, 2010 at 2:07 AM, Koen Vos <koen.vos@skype.net> wrote:

> Quoting "Raymond (Juin-Hwey) Chen":
>
>   One-way delay = codec-independent delay + 3*(codec frame size) + (codec
>> look-ahead) + (codec filtering delay if any)
>>
>> This formula was obtained from an experienced engineer who has been
>> working on IP phones related fields for more than a decade,
>>
>
> At Skype We have 100+ years of combined VoIP experience, and a focus on
> minimizing delay as part of our goal to maximize quality.  The consensus
> among our engineers is that the multiplier is closer to 1 than to 2, at
> least for software VoIP applications over typical Internet connections.
>  Some years ago the situation was slightly worse because dial-up was more
> prevalent.
>
>
>
>  Similar 3X multiplier is also observed in VoIP gateways.  Even with a fast
>> processor/system optimized from ground up to be low-delay, the measured
>> "codec-dependent" one-way delay of such a VoIP gateway using the G.711 codec
>> with a 5 ms frame/packet size is between 12 and 17 ms, or around 3X the
>> frame size.
>>
>
> As I've pointed out before, that doesn't say much about how the delay
> increases with larger frame sizes.  Perhaps the 12~17 ms includes a constant
> delay of 7 ms, and the marginal growth of delay with frame size is 1x.
>
> best,
> koen.
>
> _______________________________________________
> codec mailing list
> codec@ietf.org
> https://www.ietf.org/mailman/listinfo/codec
>