Re: [codec] #18: Frame Sizes

stephen botzko <stephen.botzko@gmail.com> Sat, 01 May 2010 10:57 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 6B05728C113 for <codec@core3.amsl.com>; Sat, 1 May 2010 03:57:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.026
X-Spam-Level:
X-Spam-Status: No, score=-2.026 tagged_above=-999 required=5 tests=[AWL=0.572, BAYES_00=-2.599, 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 Aif4EOhmacR5 for <codec@core3.amsl.com>; Sat, 1 May 2010 03:57:25 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 632FF3A6934 for <codec@ietf.org>; Sat, 1 May 2010 03:57:25 -0700 (PDT)
Received: by wwb24 with SMTP id 24so747046wwb.31 for <codec@ietf.org>; Sat, 01 May 2010 03:57:06 -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=VmAWSBRfWfCnWhqCQ07HJwgXywXaQki2elnS+q+kg+Y=; b=mBZcgoXF0O9ywScXiT9hAf80OY4F9jTi5g9RQFcjx6RMWR2W1HVEy6BcHy3P15nfKh 8LsAKrVTNJii67p21C98PfZzzsp7ixwctseHvUQjM56tzVH8dh278pB3eH/kbSJDub2H W9Y5E3usaV+cK4huDaDbLzK6xx+hTb6WXM8+Q=
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=NTdSfJX1+nT6dAVr41GCjz1+wcG8HdocC9pI/6ivDgGfEVpST/QKz2QnYv3cv57uGQ /FW6ud5No1eXP6X1FQv5USHzLQRKAb+mEpXN0X5CbTxSLb9gIjD2GFmyQrbYQkuJkAjn JTiy6csnFEXWVpgh7R1WX5fdpjxwdp9YULcqE=
MIME-Version: 1.0
Received: by 10.216.172.68 with SMTP id s46mr1657803wel.73.1272711425864; Sat, 01 May 2010 03:57:05 -0700 (PDT)
Received: by 10.216.28.139 with HTTP; Sat, 1 May 2010 03:57:05 -0700 (PDT)
In-Reply-To: <062.d51439b68d5cdc7daff30cac51ddab04@tools.ietf.org>
References: <062.d51439b68d5cdc7daff30cac51ddab04@tools.ietf.org>
Date: Sat, 01 May 2010 06:57:05 -0400
Message-ID: <w2h6e9223711005010357o555c1c80u46599862684a2257@mail.gmail.com>
From: stephen botzko <stephen.botzko@gmail.com>
To: codec@ietf.org
Content-Type: multipart/alternative; boundary="001636416d9370b37d04858638e5"
Subject: Re: [codec] #18: Frame Sizes
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 10:57:26 -0000

I'm not sure there ought to be a "SHALL" on this.  Obviously it needs to be
reasonably small for low delay.

However, the possible frame sizes are often driven by the underlying
technology (transform size being one example).  If we decided on 10 and 20
ms for example, would we actually rule out a codec technology that had to
run at 7.5, 15 and 22.5?

Stephen Botzko



On Sat, May 1, 2010 at 6:45 AM, codec issue tracker <trac@tools.ietf.org>wrote:

> #18: Frame Sizes
>
> ------------------------------------+---------------------------------------
>  Reporter:  hoene@…                 |       Owner:
>     Type:  enhancement             |      Status:  new
>  Priority:  major                   |   Milestone:
> Component:  requirements            |     Version:
>  Severity:  -                       |    Keywords:
>
> ------------------------------------+---------------------------------------
>  Which frame size(s) shall the CODEC support?
>
> --
> Ticket URL: <https://svn.tools.ietf.org/wg/codec/trac/ticket/18>
> codec <http://tools.ietf.org/codec/>
>
> _______________________________________________
> codec mailing list
> codec@ietf.org
> https://www.ietf.org/mailman/listinfo/codec
>