IETF Logo Mail Archive

Re: [codec] #2: Please identify Requirements non-ambiguous and give them priorities.

"Christian Hoene" <hoene@uni-tuebingen.de> Sun, 28 March 2010 16:07 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 582CC3A67CF for <codec@core3.amsl.com>; Sun, 28 Mar 2010 09:07:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.518
X-Spam-Level:
X-Spam-Status: No, score=-2.518 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HELO_EQ_DE=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 y35Cb1+8gzBP for <codec@core3.amsl.com>; Sun, 28 Mar 2010 09:07:00 -0700 (PDT)
Received: from mx06.uni-tuebingen.de (mx06.uni-tuebingen.de [134.2.3.3]) by core3.amsl.com (Postfix) with ESMTP id 71D123A63EB for <codec@ietf.org>; Sun, 28 Mar 2010 09:07:00 -0700 (PDT)
Received: from hoeneT60 (dslb-094-216-236-175.pools.arcor-ip.net [94.216.236.175]) (authenticated bits=0) by mx06.uni-tuebingen.de (8.13.6/8.13.6) with ESMTP id o2SG7IDQ011573 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <codec@ietf.org>; Sun, 28 Mar 2010 18:07:24 +0200
From: Christian Hoene <hoene@uni-tuebingen.de>
To: codec@ietf.org
References: <062.b149f0b1dc7ef14a97a419277d72116d@tools.ietf.org> <071.c09c8cc8f49ba1b8d4aabe1780da9e0a@tools.ietf.org>
In-Reply-To: <071.c09c8cc8f49ba1b8d4aabe1780da9e0a@tools.ietf.org>
Date: Sun, 28 Mar 2010 18:07:19 +0200
Message-ID: <000001cace90$c1e84e40$45b8eac0$@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: AcrMbQ+tSam/HQ2WQa6KDdWKn3TRIACIk/3g
Content-Language: de
X-AntiVirus: NOT checked by Avira MailGate (version: 3.0.0-4; host: mx06)
Subject: Re: [codec] #2: Please identify Requirements non-ambiguous and give them priorities.
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 16:07:02 -0000

Hi,

what do you think about the following classification of requirements?

Requirements:
- Measurable features that the CODEC MUST fulfill.
- Requirements are verified in the qualification phase.

Objective:
- The designer try to work thoughts this objective. E.g., the CODEC SHALL support DTMF.
- Objectives are measured in the qualification phase to know to what degree they are fulfilled.

Priority:
- HIGH: This is required for the main use causes that occur frequently (>10% of all calls, e.g. IP-to-IP transmission). The codec MUST be optimized towards this feature.
- MEDIUM: Might be used from time-to-time (1%), e.g. tandem coding  with G.722.2
- LOW: Rather seldom, the codec needs not to perform very well in this scenario (<=0.1%), e.g. PSTN-to-PSTN interconnect

Cheers

 Christian

---------------------------------------------------------------
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: Thursday, March 25, 2010 11:47 PM
>To: hoene@uni-tuebingen.de
>Cc: codec@ietf.org
>Subject: Re: [codec] #2: Please identify Requirements non-ambiguous and give them priorities.
>
>#2: Please identify Requirements non-ambiguous and give them priorities.
>------------------------------------+---------------------------------------
> Reporter:  hoene@…                 |       Owner:
>     Type:  defect                  |      Status:  new
> Priority:  major                   |   Milestone:
>Component:  requirements            |     Version:
> Severity:  Active WG Document      |    Keywords:
>------------------------------------+---------------------------------------
>
>Comment(by hoene@…):
>
> From Peter Saint-Andre:
> - clarify whether each requirement is nice or necessary
>
>--
>Ticket URL: <http://trac.tools.ietf.org/wg/codec/trac/ticket/2#comment:1>
>codec <http://tools.ietf.org/codec/>

v2.23.0 | Report a Bug | By Email