Re: [codec] Codec guidelines and requirements drafts

Koen Vos <koen.vos@skype.net> Sat, 05 September 2009 22:51 UTC

Return-Path: <koen.vos@skype.net>
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 660003A67EE for <codec@core3.amsl.com>; Sat, 5 Sep 2009 15:51:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.591
X-Spam-Level:
X-Spam-Status: No, score=-3.591 tagged_above=-999 required=5 tests=[AWL=-2.851, BAYES_20=-0.74]
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 J6CfcGcI3WPk for <codec@core3.amsl.com>; Sat, 5 Sep 2009 15:51:48 -0700 (PDT)
Received: from mail.skype.net (mail.skype.net [212.187.172.39]) by core3.amsl.com (Postfix) with ESMTP id 3EC893A6778 for <codec@ietf.org>; Sat, 5 Sep 2009 15:51:48 -0700 (PDT)
Received: from mail.skype.net (localhost [127.0.0.1]) by mail.skype.net (Postfix) with ESMTP id C434C60327495; Sat, 5 Sep 2009 23:52:10 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=skype.net; h=message-id :date:from:to:cc:subject:references:in-reply-to:mime-version :content-type:content-transfer-encoding; s=mail; bh=BbdlbcvX3b87 o6PHUduxOdISkJs=; b=expvGWllmCsgAac2nO+zpkKgLW9YXP4LmwWS/AS7x/7d xdve6yOXnOfb9zLR01JSvZJLHrRdss7H9E8os5gUx9aN+hh/t0Jyxpnfuqts1ZUr Wmmt1XOp+lFPxBnBpjEeimElb941mnUR/aVrLah4OkmTmZNH0KUS1b0R5Z7AbC8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=skype.net; h=message-id:date:from :to:cc:subject:references:in-reply-to:mime-version:content-type: content-transfer-encoding; q=dns; s=mail; b=kqYviNTHrP9ykw9/l4P/ 4M7M4EKMuBDggNeLV+41IknbTFOBoQWJTvULPjDmG3/2Ziy5kjHKAuWDRwXvTfRY tD7iuOkbsQEW/74mmj9slqk3/RglaDWxgSZ1UBOivOi1q7dkH2YXMJTNweF1kfRS hpkikcj3WZKbRdoT9GsyllU=
Received: from localhost (localhost [127.0.0.1]) by mail.skype.net (Postfix) with ESMTP id C268860327467; Sat, 5 Sep 2009 23:52:10 +0100 (IST)
Received: from mail.skype.net ([127.0.0.1]) by localhost (dub-mail.skype.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qjW24z69LCKr; Sat, 5 Sep 2009 23:52:10 +0100 (IST)
Received: by mail.skype.net (Postfix, from userid 33) id AFEC56032746A; Sat, 5 Sep 2009 23:52:10 +0100 (IST)
Received: from adsl-71-141-110-218.dsl.snfc21.pacbell.net (adsl-71-141-110-218.dsl.snfc21.pacbell.net [71.141.110.218]) by mail.skype.net (Horde Framework) with HTTP; Sat, 05 Sep 2009 15:52:10 -0700
Message-ID: <20090905155210.143958svqk5c29ay@mail.skype.net>
Date: Sat, 05 Sep 2009 15:52:10 -0700
From: Koen Vos <koen.vos@skype.net>
To: Alexander Chemeris <Alexander.Chemeris@sipez.com>, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca>
References: <4AA16546.8050700@octasic.com> <3d032e5d0909050121k3e327b88k987d82b5f2000f31@mail.gmail.com> <4AA26A0B.7080101@usherbrooke.ca>
In-Reply-To: <4AA26A0B.7080101@usherbrooke.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; DelSp="Yes"; format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.3.4)
Cc: "codec@ietf.org" <codec@ietf.org>
Subject: Re: [codec] Codec guidelines and requirements drafts
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: Sat, 05 Sep 2009 22:51:49 -0000

Quoting Jean-Marc Valin:

>> 3) It is also usually stated that VBR is bad for speech transport over
>> the Internet, because it leads to higher loss rates then when CBR is used.
>> [...]
>
> Do you have any reference regarding VBR and loss rate? In any case, I
> think it's clear that both VBR and CBR have valid use cases.

I'm only aware of the opposite relationship between VBR and packet  
loss: short peaks at higher rate are easily handled by the packet  
buffer in the bottleneck (e.g. DSL modem). Even temporarily exceeding  
the network bandwidth only results in a small amount of jitter.
On the other hand, constantly exceeding the network bandwidth not only  
guarantees packet loss, but also keeps the packet buffer filled up,  
easily adding hundreds of milliseconds of extra delay to the call.

Other arguments against using CBR:
- At a given quality level, VBR results in fewer total bits (~ half)  
being sent over the network over the duration of a call.
- VBR helps on the receiving end to estimate the available network  
bandwidth, so that the codec can adjust to it (using a feedback  
channel).

VBR seems better suited for the Internet than CBR.

best,
koen.