Re: [codec] #13: reference use-cases and topologies!

"Christian Hoene" <hoene@uni-tuebingen.de> Wed, 21 April 2010 10:09 UTC

Return-Path: <hoene@uni-tuebingen.de>
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 1F08628C0E7 for <codec@core3.amsl.com>; Wed, 21 Apr 2010 03:09:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.07
X-Spam-Level:
X-Spam-Status: No, score=-1.07 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_DE=0.35, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_DNSWL_MED=-4, RCVD_IN_SORBS_WEB=0.619]
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 IoaPS4Y+HwKV for <codec@core3.amsl.com>; Wed, 21 Apr 2010 03:09:27 -0700 (PDT)
Received: from mx06.uni-tuebingen.de (mx06.uni-tuebingen.de [134.2.3.3]) by core3.amsl.com (Postfix) with ESMTP id A93283A6A70 for <codec@ietf.org>; Wed, 21 Apr 2010 03:09:26 -0700 (PDT)
Received: from hoeneT60 ([82.113.106.221]) (authenticated bits=0) by mx06.uni-tuebingen.de (8.13.6/8.13.6) with ESMTP id o3LA95p4026792 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <codec@ietf.org>; Wed, 21 Apr 2010 12:09:13 +0200
From: Christian Hoene <hoene@uni-tuebingen.de>
To: codec@ietf.org
References: <062.407382d901e5e6b8dea15d6e3ae1a2c8@tools.ietf.org> <071.5e023ebb9f76cbef6eb8421c4bc0c385@tools.ietf.org>
In-Reply-To: <071.5e023ebb9f76cbef6eb8421c4bc0c385@tools.ietf.org>
Date: Wed, 21 Apr 2010 12:09:02 +0200
Message-ID: <002001cae13a$b0f290c0$12d7b240$@de>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcrhOKZsXYXf9oe/TrGNk6AZJJBbTAAAKKsg
Content-Language: de
X-AntiVirus: NOT checked by Avira MailGate (version: 3.0.0-4; host: mx06)
Subject: Re: [codec] #13: reference use-cases and topologies!
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: Wed, 21 Apr 2010 10:09:28 -0000

Hello all,

this topic is of primal importance.

Are all reference use-cases already listed in the requirements-draft? Currently,
"Point to point calls, Conferencing, Telepresence, Teleoperation, In-game voice chat, Live distributed music performances / Internet music lessons" are listed. Is this list complete? Is this list order rightly?

At least use usages were mentioned previously: 
a) removing the need for echo cancelation because of ultra-low delay, when echoes are called side tones...
b) Push-to-talk (see below)

With are the topologies under study?
a) IPend-to-IPend?
b) IPend-to-transcoding_gateway-to-PSTNend?
c) n to n (decentralized conferencing)
e) IPend-to-legal_interception-to-X

What is important, what is missing?

Christian


PS:
"Scenario: Push-to-talk like service (PTT)

In spite of the development of broadband access (xDSL), a lot of users would only have service access via PSTN modems or mobile links. Also, on these links the available bandwidth might be shared among multiple flows and is subjected to congestion. Then, even low coding rates at about 8 kbps are too high.
If transmission capacity hardly exists, one still can degrade the quality of a telephone call to something like a push-to-talk (PTT) like service having very high latencies. Technically, this scenario takes advantage of bandwidth gains due to disruptive transmission (DTX) modes and very large packets containing multiple speech frames causing a very low packetization overhead."

---------------------------------------------------------------
Dr.-Ing. Christian Hoene
Interactive Communication Systems (ICS), University of Tübingen 
Sand 13, 72076 Tübingen, Germany, Phone +49 7071 2970532 
http://www.net.uni-tuebingen.de/


>-----Original Message-----
>From: codec issue tracker [mailto:trac@tools.ietf.org]
>Sent: Wednesday, April 21, 2010 11:54 AM
>To: hoene@uni-tuebingen.de
>Cc: codec@ietf.org
>Subject: Re: [codec] #13: reference use-cases and topologies!
>
>#13: reference use-cases and topologies!
>------------------------------------+---------------------------------------
> Reporter:  hoene@…                 |       Owner:
>     Type:  defect                  |      Status:  new
> Priority:  critical                |   Milestone:
>Component:  requirements            |     Version:
> Severity:  Active WG Document      |    Keywords:
>------------------------------------+---------------------------------------
>
>Comment(by hoene@…):
>
> The current draft
> http://tools.ietf.org/id/draft-ietf-codec-requirements-00.txt
> mentions:
>
> 2.  Applications
>
>    The following applications should be considered for Internet audio
>    codecs, along with their requirements:
>
>    o  Point to point calls
>
>    o  Conferencing
>
>    o  Telepresence
>
>    o  Teleoperation
>
>    o  In-game voice chat
>
>    o  Live distributed music performances / Internet music lessons
>
>    o  Other applications
>
>--
>Ticket URL: <http://trac.tools.ietf.org/wg/codec/trac/ticket/13#comment:1>
>codec <http://tools.ietf.org/codec/>