IETF Logo Mail Archive

Re: [codec] #16: Multicast?

Mikael Abrahamsson <swmike@swm.pp.se> Sat, 24 April 2010 02:05 UTC

Return-Path: <swmike@swm.pp.se>
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 475683A67CF for <codec@core3.amsl.com>; Fri, 23 Apr 2010 19:05:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.738
X-Spam-Level:
X-Spam-Status: No, score=-5.738 tagged_above=-999 required=5 tests=[AWL=0.511, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 JEPNMsyusxX3 for <codec@core3.amsl.com>; Fri, 23 Apr 2010 19:05:26 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) by core3.amsl.com (Postfix) with ESMTP id 05AE73A67C0 for <codec@ietf.org>; Fri, 23 Apr 2010 19:05:25 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id D4DCA9F; Sat, 24 Apr 2010 04:05:10 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id D16BD9E; Sat, 24 Apr 2010 04:05:10 +0200 (CEST)
Date: Sat, 24 Apr 2010 04:05:10 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "Raymond (Juin-Hwey) Chen" <rchen@broadcom.com>
In-Reply-To: <CB68DF4CFBEF4942881AD37AE1A7E8C74AB3F4A270@IRVEXCHCCR01.corp.ad.broadcom.com>
Message-ID: <alpine.DEB.1.10.1004240401470.6768@uplift.swm.pp.se>
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>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format="flowed"; charset="US-ASCII"
Cc: "codec@ietf.org" <codec@ietf.org>, 'stephen botzko' <stephen.botzko@gmail.com>, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca>
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, 24 Apr 2010 02:05:27 -0000

On Fri, 23 Apr 2010, Raymond (Juin-Hwey) Chen wrote:

> The way I see it, for conference bridge applications at least, I think 
> it would be a big mistake for IETF to recommend a codec with a frame 
> size of 20 ms or higher.  From my analysis above, by doing that we will 
> be stuck with too long a delay and the associated problems.

>From my point of view as a network engineer, it would be a mistake to 
recommend *fixed* frame size at all. The codec needs to be able to handle 
everything from 5ms to 250ms frame size depending on network conditions 
(please see my emails from a few months back regarding the reality of the 
Internet today).

v2.23.0 | Report a Bug | By Email