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

stephen botzko <stephen.botzko@gmail.com> Sat, 03 April 2010 10:54 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 1B2423A67A7 for <codec@core3.amsl.com>; Sat, 3 Apr 2010 03:54:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.673
X-Spam-Level:
X-Spam-Status: No, score=-0.673 tagged_above=-999 required=5 tests=[AWL=0.195, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, J_CHICKENPOX_72=0.6]
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 6MLR3Zv6b2Ik for <codec@core3.amsl.com>; Sat, 3 Apr 2010 03:54:07 -0700 (PDT)
Received: from mail-iw0-f191.google.com (mail-iw0-f191.google.com [209.85.223.191]) by core3.amsl.com (Postfix) with ESMTP id 204033A672F for <codec@ietf.org>; Sat, 3 Apr 2010 03:54:07 -0700 (PDT)
Received: by iwn29 with SMTP id 29so2116307iwn.17 for <codec@ietf.org>; Sat, 03 Apr 2010 03:54:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=m1HlEMo4+1DewVjYLbfOm7MZ82D9BVUoPavQ2gsT7C8=; b=qP0+qh4HanGXf/bB11DkJEp67rRHgRy3+m5byTxwflBCjmapGtJFR9q3w2tNAwsWcA Wnrv8e4jNytFFHATOd+zzG1ihry2N0WyWIIBXfvfhGo1gznUM1Jjt81Sa8UQDRdJXTeU RvtGpF4fsQWlDWGb2O7LbcJ3cnAz6vABjUtBE=
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=ptqG8nnEOlhhv8pU7bxlxrHQGNar3FYdoYSIU4/CzH4Rg99lOa6UDIGASn6k5VGtdd WVrfedMp1JfA2iFruTzZZ3GlVRctCb1MkKrUJLzcRDX7soTwVswRWvw2DgzNMXKjuSz8 DVXgSFEHRk55S648v03XZCiXDNsIUseuPxwOI=
MIME-Version: 1.0
Received: by 10.231.85.133 with HTTP; Sat, 3 Apr 2010 03:54:03 -0700 (PDT)
In-Reply-To: <071.db71a07d3a8eb1cd6269da2ddeaa0468@tools.ietf.org>
References: <062.4b6a3862c443b2d8917e027f2267f4d2@tools.ietf.org> <071.db71a07d3a8eb1cd6269da2ddeaa0468@tools.ietf.org>
Date: Sat, 03 Apr 2010 06:54:03 -0400
Received: by 10.231.145.17 with SMTP id b17mr800000ibv.94.1270292043771; Sat, 03 Apr 2010 03:54:03 -0700 (PDT)
Message-ID: <l2i6e9223711004030354rccae5932i260286c25e911cda@mail.gmail.com>
From: stephen botzko <stephen.botzko@gmail.com>
To: trac@localhost.amsl.com
Content-Type: multipart/alternative; boundary="0016e64c145a07b1ce048352eaf0"
Cc: codec@ietf.org
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: Sat, 03 Apr 2010 10:54:08 -0000

I personally believe testing tandem operation is a MUST, since devices using
this CODEC will certainly connect into networks where it is not supported.
The idea below that this will "just work" with every ITU codec is
incorrect..

In addition, tandem operation occurs in virtually all conference bridges
(including back-to-back encode/decode with CODEC itself).  So surely
self-tandeming has to be tested anyway.  (Though of course is is common for
devices in the same conference to be using different codecs).

I do not favor just copying the tandem requirements from some other codec's
test plan - unless we are sure that it is in essentially the same ecosystem
as ours.  Ideally the community would identify common use cases, and the
test cases would be derived from those cases.

Stephen Botzko

On Sat, Apr 3, 2010 at 1:39 AM, codec issue tracker <trac@tools.ietf.org>wrote:

> #1: Application: 2.1.  Point to point calls supporting transcoding?
>
> ------------------------------------+---------------------------------------
>  Reporter:  hoene@…                 |       Owner:
>     Type:  enhancement             |      Status:  new
>  Priority:  major                   |   Milestone:
> Component:  requirements            |     Version:
>  Severity:  Active WG Document      |    Keywords:
>
> ------------------------------------+---------------------------------------
>
> Comment(by hoene@…):
>
>  No consensus either until now. Again two opinions:
>
>  a) "To have similar requirements as G.718 and to consider at least cross
>  tandeming conditions with G722.2@12.65 in the characterization phase."
>
>  b) "I think that transcoding must be an explicit non-goal for this codec."
>  "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.  In a VoIP to VoIP
>  topology the codec selected is the one defined by this WG and by
>  definition no transcoding is needed.  And that's it, no test needed,
>  because nobody will use it this way."
>
>  Again, I would suggest to look for volunteers who want to make the
>  subjective tests with G.722.2 and CODEC.
>
> --
> Ticket URL: <https://svn.tools.ietf.org/wg/codec/trac/ticket/1#comment:1>
> codec <http://tools.ietf.org/codec/>
>
> _______________________________________________
> codec mailing list
> codec@ietf.org
> https://www.ietf.org/mailman/listinfo/codec
>