Re: [codec] #1: Application: 2.1. Point to point calls supporting transcoding?

Marc Petit-Huguenin <petithug@acm.org> Sun, 28 March 2010 18:24 UTC

Return-Path: <petithug@acm.org>
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 1C7373A68EC for <codec@core3.amsl.com>; Sun, 28 Mar 2010 11:24:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.361
X-Spam-Level:
X-Spam-Status: No, score=-100.361 tagged_above=-999 required=5 tests=[AWL=0.774, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
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 QjGGo8ExYg42 for <codec@core3.amsl.com>; Sun, 28 Mar 2010 11:24:42 -0700 (PDT)
Received: from server.implementers.org (server.implementers.org [69.55.225.91]) by core3.amsl.com (Postfix) with ESMTP id 018583A65A6 for <codec@ietf.org>; Sun, 28 Mar 2010 11:24:42 -0700 (PDT)
Received: by server.implementers.org (Postfix, from userid 1001) id C0D2D6C984E6; Sun, 28 Mar 2010 18:25:08 +0000 (UTC)
Received: from [192.168.2.3] (server.implementers.org [127.0.0.1]) by server.implementers.org (Postfix) with ESMTPA id 426996C984E0; Sun, 28 Mar 2010 18:25:08 +0000 (UTC)
Message-ID: <4BAF9F03.5080706@acm.org>
Date: Sun, 28 Mar 2010 11:25:07 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100307 Iceowl/1.0b1 Icedove/3.0.3
MIME-Version: 1.0
To: stephen botzko <stephen.botzko@gmail.com>
References: <05542EC42316164383B5180707A489EE1D0AA5F554@EMBX02-HQ.jnpr.net> <4BAF9253.1080301@acm.org> <6e9223711003281103m25679fb6l2d334a2e238febe6@mail.gmail.com>
In-Reply-To: <6e9223711003281103m25679fb6l2d334a2e238febe6@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Cc: "codec@ietf.org" <codec@ietf.org>, "James.Rafferty@dialogic.com" <James.Rafferty@dialogic.com>
Subject: Re: [codec] #1: Application: 2.1. Point to point calls supporting transcoding?
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: Sun, 28 Mar 2010 18:24:43 -0000

On 03/28/2010 11:03 AM, stephen botzko wrote:
>>>>
> Sorry, but I still do not understand the need for this testing.  In a cell
> network to VoIP topology, the codec selected must be an ITU codec which we
> already know are working fine for transcoding.
>>>>
> 
> We will NOT know if an ITU codec tandems with this codec with acceptable
> quality unless we test the combination.  The ITU does not warrant that
> their codecs will tandem with anything.  No one does.
> 
> And even in a VOIP framework, the audio will be transcoded sometimes. 
> At least some VOIP infrastructures are set up to use specific codecs
> (for instance G.729) and transcode anything else to that format.  And
> certainly this audio will be transcoded when it enters a cellular or
> PSTN network.
> 
> If you end up with a free internet codec, but everyone has to carry all
> the royalty-bearing codecs also (so that transcoding is never needed),
> then it seems to me that you are not accomplishing your goal.  I think
> tandeming has to be tested, precisely because we expect implementations
> to include devices which only support this codec.

Well, we will have to agree to disagree.

-- 
Marc Petit-Huguenin
Personal email: marc@petit-huguenin.org
Professional email: petithug@acm.org
Blog: http://blog.marc.petit-huguenin.org