IETF Logo Mail Archive

Re: [codec] possible issues to track

Michael Knappe <mknappe@juniper.net> Thu, 25 March 2010 22:02 UTC

Return-Path: <mknappe@juniper.net>
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 6AD113A682E for <codec@core3.amsl.com>; Thu, 25 Mar 2010 15:02:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.036
X-Spam-Level:
X-Spam-Status: No, score=-5.036 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, 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 3Bo-DRkPcD8M for <codec@core3.amsl.com>; Thu, 25 Mar 2010 15:02:42 -0700 (PDT)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175]) by core3.amsl.com (Postfix) with ESMTP id E18433A6B8D for <codec@ietf.org>; Thu, 25 Mar 2010 15:02:38 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob111.postini.com ([64.18.6.12]) with SMTP ID DSNKS6vdku7Ek/8fT+MKB4hZM8ZwwS3FJWob@postini.com; Thu, 25 Mar 2010 15:03:01 PDT
Received: from EMBX02-HQ.jnpr.net ([fe80::18fe:d666:b43e:f97e]) by P-EMHUB02-HQ.jnpr.net ([fe80::88f9:77fd:dfc:4d51%11]) with mapi; Thu, 25 Mar 2010 14:57:32 -0700
From: Michael Knappe <mknappe@juniper.net>
To: Jean-Marc Valin <jean-marc.valin@octasic.com>, Peter Saint-Andre <stpeter@stpeter.im>
Date: Thu, 25 Mar 2010 14:57:30 -0700
Thread-Topic: [codec] possible issues to track
Thread-Index: AcrMZQhadvQxQr2UQLmbhmkh2clr5gAASHVc
Message-ID: <C7D12A5A.137CD%mknappe@juniper.net>
In-Reply-To: <4BABD67A.3040902@octasic.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-Entourage/13.3.0.091002
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Codec WG <codec@ietf.org>
Subject: Re: [codec] possible issues to track
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: Thu, 25 Mar 2010 22:02:43 -0000

The mailing list is definitely easier for discussing the issues, but my
suggestion is that any open items that come up in discussion (as well as the
current status of that item - e.g. Who's working on resolving it) be tracked
somewhere (an official issue tracker or even on the wiki) so that we have
some easily accessible collective memory of our progress.

Mike


On 3/25/10 2:32 PM, "Jean-Marc Valin" <jean-marc.valin@octasic.com> wrote:

> Peter Saint-Andre wrote:
>> - avoid phrasing subjective comparision in relation to ITU codecs
> 
> I was actually surprised to see that one come up. As far as I know, most
> ITU terms of reference include comparisons like "better than G.722 at rate
> X". Does the ITU phrase this differently then we did?
> 
> As for the way of discussing the issues, it seems to me like the mailing
> list is just simpler. Most people so far have commented on the list anyway.
> 
> Cheers,
> 
> Jean-Marc
> _______________________________________________
> codec mailing list
> codec@ietf.org
> https://www.ietf.org/mailman/listinfo/codec

v2.23.0 | Report a Bug | By Email