Re: [codec] possible issues to track
Jean-Marc Valin <jean-marc.valin@octasic.com> Thu, 25 March 2010 22:08 UTC
Return-Path: <jean-marc.valin@octasic.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 89ABC3A6BE1 for <codec@core3.amsl.com>; Thu, 25 Mar 2010 15:08:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.469
X-Spam-Level:
X-Spam-Status: No, score=-1.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 ycSWQcNmkqtO for <codec@core3.amsl.com>; Thu, 25 Mar 2010 15:08:29 -0700 (PDT)
Received: from MAILEXCH.octasic.com (mail.octasic.com [70.54.254.106]) by core3.amsl.com (Postfix) with ESMTP id AC10D3A6CD7 for <codec@ietf.org>; Thu, 25 Mar 2010 15:08:28 -0700 (PDT)
Received: from [142.138.24.13] ([142.138.24.13]) by MAILEXCH.octasic.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 25 Mar 2010 18:08:50 -0400
Message-ID: <4BABDFA5.50500@octasic.com>
Date: Thu, 25 Mar 2010 18:11:49 -0400
From: Jean-Marc Valin <jean-marc.valin@octasic.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100317)
MIME-Version: 1.0
To: stephen botzko <stephen.botzko@gmail.com>
References: <4BABD9C2.6070108@octasic.com> <C7D12868.207B0%stewe@stewe.org> <6e9223711003251504l195e0218qc0e27b598ea99b8a@mail.gmail.com>
In-Reply-To: <6e9223711003251504l195e0218qc0e27b598ea99b8a@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 Mar 2010 22:08:50.0105 (UTC) FILETIME=[BF8FCA90:01CACC67]
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:08:30 -0000
stephen botzko wrote: > Perhaps something as simple as saying "not worse" instead of "better". Agreed. Jean-Marc > > Stephen Bozko > > On Thu, Mar 25, 2010 at 2:49 PM, Stephan Wenger <stewe@stewe.org > <mailto:stewe@stewe.org>> wrote: > > No, I just suggest to attempt being just a little bit diplomatic. > Stephan > > > > On 3.25.2010 14:46 , "Jean-Marc Valin" <jean-marc.valin@octasic.com > <mailto:jean-marc.valin@octasic.com>> wrote: > > > Stephan Wenger wrote: > >> The comment was from me, and it was addressed towards the > sensitivities of > >> cross-SDO relationships. It is one thing if the ITU states that > something > >> is better than ITU-Rec xxx, but it is another thing if another > body states > >> this. Certainly without having received appropriate input from > the ITU > >> after requesting it through a liaison. > > > > So do you suggest we drop the ITU codecs from the list? I don't really > > mind, considering that I would not expect that part of the > requirement to > > be a limiting factor. > > > > Jean-Marc > > > >> Stephan > >> > >> > >> > >> On 3.25.2010 14:32 , "Jean-Marc Valin" > <jean-marc.valin@octasic.com <mailto: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 <mailto:codec@ietf.org> > >>> https://www.ietf.org/mailman/listinfo/codec > >> > >> > > > > > _______________________________________________ > codec mailing list > codec@ietf.org <mailto:codec@ietf.org> > https://www.ietf.org/mailman/listinfo/codec > >
- Re: [codec] possible issues to track Michael Knappe
- [codec] possible issues to track Peter Saint-Andre
- Re: [codec] possible issues to track Jean-Marc Valin
- Re: [codec] possible issues to track Stephan Wenger
- Re: [codec] possible issues to track Jean-Marc Valin
- Re: [codec] possible issues to track Stephan Wenger
- Re: [codec] possible issues to track Michael Knappe
- Re: [codec] possible issues to track Benjamin M. Schwartz
- Re: [codec] possible issues to track Michael Knappe
- Re: [codec] possible issues to track stephen botzko
- Re: [codec] possible issues to track Jean-Marc Valin
- Re: [codec] possible issues to track Peter Saint-Andre
- Re: [codec] possible issues to track Jean-Marc Valin
- Re: [codec] possible issues to track Michael Knappe
- Re: [codec] possible issues to track stephen botzko
- Re: [codec] possible issues to track Benjamin M. Schwartz
- Re: [codec] possible issues to track Christian Hoene
- Re: [codec] possible issues to track Michael Knappe
- Re: [codec] possible issues to track stephen botzko
- Re: [codec] possible issues to track Jean-Marc Valin
- Re: [codec] possible issues to track Benjamin M. Schwartz
- Re: [codec] possible issues to track Benjamin M. Schwartz