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

Colin Perkins <csp@csperkins.org> Wed, 21 April 2010 10:58 UTC

Return-Path: <csp@csperkins.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 9E9D13A6B4F for <codec@core3.amsl.com>; Wed, 21 Apr 2010 03:58:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.113
X-Spam-Level:
X-Spam-Status: No, score=-3.113 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, J_CHICKENPOX_72=0.6, RCVD_IN_DNSWL_LOW=-1]
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 8qdKNlcsku0I for <codec@core3.amsl.com>; Wed, 21 Apr 2010 03:58:20 -0700 (PDT)
Received: from lon1-msapost-3.mail.demon.net (lon1-msapost-3.mail.demon.net [195.173.77.182]) by core3.amsl.com (Postfix) with ESMTP id D403F3A694C for <codec@ietf.org>; Wed, 21 Apr 2010 03:58:19 -0700 (PDT)
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]) by lon1-post-3.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1O4XdC-0005l1-e5; Wed, 21 Apr 2010 10:58:10 +0000
Message-Id: <41CEDB08-3A9E-44E4-9E45-CCC4A43FE8A6@csperkins.org>
From: Colin Perkins <csp@csperkins.org>
To: codec@ietf.org
In-Reply-To: <071.5e023ebb9f76cbef6eb8421c4bc0c385@tools.ietf.org>
Content-Type: text/plain; charset="WINDOWS-1252"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 21 Apr 2010 11:58:10 +0100
References: <062.407382d901e5e6b8dea15d6e3ae1a2c8@tools.ietf.org> <071.5e023ebb9f76cbef6eb8421c4bc0c385@tools.ietf.org>
X-Mailer: Apple Mail (2.936)
Cc: trac@tools.ietf.org
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:58:20 -0000

On 21 Apr 2010, at 10:54, codec issue tracker wrote:
> #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
>


See RFC 5117.

-- 
Colin Perkins
http://csperkins.org/